| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 15 and audio data. The current implementation only logs such errors.
17 restarting from a known position. In the case of such errors outside of a
21 and after a number of such errors are detected the bus might be reset. Note
42 3. Timeouts: In a number of cases such as ChannelPrepare or
46 recommendation on timeouts. If such configurations do not complete, the
47 driver will return a -ETIMEOUT. Such timeouts are symptoms of a faulty
57 such as frame reconfiguration would be handled at different times). A global
63 implementation does not provide a recovery mechanism for such errors, Slave
|
| /Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 7 the expectation that such a filesystem is backed by a read-only device
8 such as dm-verity or CDROM. This allows systems that have a verified
25 included, but they can be excluded using kernel command line option such
27 different mechanisms such as ``CONFIG_MODULE_SIG`` and
|
| /Documentation/devicetree/bindings/input/ |
| D | e3x0-button.txt | 9 - "ettus,e3x0-button": For devices such as the NI Ettus Research USRP E3x0
11 - <0 30 1>, <0 31 1>: For devices such as the NI Ettus Research USRP E3x0
13 - "press", "release": For devices such as the NI Ettus Research USRP E3x0
|
| /Documentation/driver-api/usb/ |
| D | gadget.rst | 14 development project. This is the first such API released on Linux to
24 - Flexible enough to expose more complex USB device capabilities such
43 distinguish drivers running inside such hardware from the more familiar
84 Examples of such controller hardware include the PCI-based NetChip
90 functions, using calls to the controller driver. Because such
109 - handling life cycle events, such as managing bindings to
115 Such drivers may be modules of proprietary code, although that
144 Other layers may exist. These could include kernel layers, such as
146 on standard POSIX system call APIs such as ``open()``, ``close()``,
148 be an option. Such user mode code will not necessarily be subject to
[all …]
|
| D | hotplug.rst | 28 actively (calling such a user mode helper program directly).
31 such programs are called "policy agents" here. Typically they involve
91 which contains the entries from each driver's ``MODULE_DEVICE_TABLE``. Such
95 See ``linux/usb.h`` for full information about such table entries; or look
100 macros such as these, and use driver_info to store more information::
125 need such a struct usb_driver.
|
| /Documentation/staging/ |
| D | speculation.rst | 11 employ speculative execution techniques such as branch prediction, performing
15 such as the contents of registers. However, in some cases it is possible to
16 observe its impact on microarchitectural state, such as the presence or
17 absence of data in caches. Such state may form side-channels which can be
32 Which, on arm64, may be compiled to an assembly sequence such as::
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 5 The kernel has limited support for memory mapping under no-MMU conditions, such
82 (such as ramfs or tmpfs) may choose to honour an open, truncate, mmap
85 as for the MMU case. If the filesystem does not provide any such
104 of such are frame buffers and flash devices. If the driver does not
105 provide any such support, then the mapping request will be denied.
138 However, for memory that isn't required to be precleared - such as that
177 support futexes (such as an I/O chardev mapping).
212 to indicate the permitted types of mapping on such devices. The default is
228 implement it. Such is the case for the framebuffer driver which attempts to
229 direct the call to the device-specific driver. Under such circumstances, the
[all …]
|
| /Documentation/devicetree/bindings/gnss/ |
| D | mediatek.yaml | 30 description: An optional reset line, with names such as RESET or NRESET.
34 description: Comes with pin names such as PPS1 or 1PPS.
43 Regulator providing backup voltage, pin names such as VBAT or VBACKUP.
|
| /Documentation/mm/ |
| D | numa.rst | 55 For some architectures, such as x86, Linux will "hide" any node representing a
80 memory, Linux must decide whether to order the zonelists such that allocations
83 such as DMA or DMA32, represent relatively scarce resources. Linux chooses
108 such as taskset(1) and numactl(1), and program interfaces such as
124 allows such allocations to fallback to other nearby nodes when a node that
132 A typical model for making such an allocation is to obtain the node id of the
135 the node id returned. When such an allocation fails, the requesting subsystem
144 memory exclusively from a node without memory. To support such
|
| /Documentation/sound/cards/ |
| D | via82xx-mixer.rst | 6 Setting it to ``Input2`` on such boards will cause recording to hang, or fail
8 at ``Input1`` for such cards.
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 13 such as NFS may not be able to hold such a reference, and so need a
67 Note that such a dentry can acquire children, name, ancestors, etc.
70 in such subtree are retained only as long as there are references;
94 (such as an anonymous one created by d_obtain_alias), if appropriate.
157 filesystem to communicate such information to nfsd. See the Export
204 On some exportable filesystems (such as NFS) unlinking a file that
219 to another bdi (the client bdi). Such threads get a private balance
222 storage is not local (such as exported NFS filesystems), this
237 threads to handle writeback. Certain filesystems, such as NFS, flush
240 waiting for writeback when closing such files.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | sprd,sc27xx-pmic.txt | 10 - Battery management system, such as charger, fuel gauge.
12 - User interface function, such as indicator, flash LED and so on.
13 - IC level interface, such as power on/off control, RTC and typec and so on.
|
| /Documentation/admin-guide/ |
| D | init.rst | 14 partition), required drivers such as storage hardware (such as SCSI or
24 dependencies of the init binary such as ``/lib/ld-linux.so.2`` missing or
34 simple non-script binary such as ``/bin/sh`` and confirm its successful
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 47 function should attempt to detect such cases and return a non-zero error
60 with such requirements should verify the kernel compilation using
115 To ensure that such cases do not result in functions being omitted from a
127 * Placing such code into special linker sections, and rejecting unwinding from
145 and it may not be possible to identify whether such unwinding will be reliable.
148 Architectures which cannot identify when it is reliable to unwind such cases
154 Architectures which can identify when it is reliable to unwind such cases (or
155 have no such cases) should attempt to unwind across exception boundaries, as
215 Architectures might not always be able to unwind such sequences, such as when
250 such cases, or report the unwinding as unreliable.
[all …]
|
| /Documentation/timers/ |
| D | hrtimers.rst | 11 such high-resolution timer implementations in practice, we came to the
13 such an approach. We initially didn't believe this ('there must be a way
16 several reasons why such integration is hard/impossible:
31 in turn decreases robustness. Such a design still leads to rather large
44 identified as "timeouts". Such timeouts are usually set up to cover
45 error conditions in various I/O paths, such as networking and block
71 Another potential benefit is that such a separation allows even more
92 such as radix trees and hashes, we chose the red black tree as the basic
119 hrtimer functions now have clearer behavior and clearer names - such as
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 22 Driver developers can use compatible string "match" values such as
29 continue to specify an SoC-specific compatible string value, such as
33 IP block-specific compatible string (such as "sifive,uart0") should
|
| /Documentation/networking/dsa/ |
| D | bcm_sf2.rst | 8 - xDSL gateways such as BCM63138
9 - streaming/multimedia Set Top Box such as BCM7445
10 - Cable Modem/residential gateways such as BCM7145/BCM3390
61 function to setup resources such as register ranges and interrupts. This
86 firmware gets reloaded. The SF2 driver relies on such events to properly set its
90 device and the switch driver registers a ``fixed_link_update`` callback for such
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 14 some cases, such as re-initializing (and maybe resetting). After such
39 specific to their host bus (such as PCI, or the platform bus).
44 they are requested to use such an address.
67 SMBus adapter) needs some fault recovery (such as resetting),
133 when a slave stretches clocks too far. I2C has no such
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | sleep.yaml | 16 reasonably describe. Thus, each device controlled in such a manner
33 Some devices may share a clock domain with each other, such that they should
35 such nodes should be placed on a virtual bus, where the bus has the sleep
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-thermocouple | 7 cables. The device can also detect if such a condition occurs.
17 such as those caused by broken thermocouple wires.
|
| /Documentation/locking/ |
| D | robust-futex-ABI.rst | 29 For robust_futexes to work, the user code (typically in a library such
33 probably causing deadlock or other such failure of the other threads
48 kernel, then it can actually have two such structures - one using 32 bit
88 specified 'offset'. Should a thread die while holding any such locks,
89 the kernel will walk this list, mark any such locks with a bit
108 other links between the locks, such as the reverse side of a double
130 thread currently holding such a lock, if any, is marked with the threads
158 the list starting at 'head'. For each such address, if the bottom 30
|
| /Documentation/mm/damon/ |
| D | design.rst | 241 To make such access pattern maintained period analysis easier, DAMON maintains
257 and applies it to monitoring operations-related data structures such as the
282 One straightforward approach for such schemes would be profile-guided
292 effective, and therefore widely be used. However, implementing such schemes
298 To allow users to reduce such redundancy and inefficiencies by offloading the
301 level. For such specifications, DAMON starts monitoring, finds regions having
355 region's characteristics. Hence, DAMOS resets the age of regions when any such
389 resources. Preventing such issues by tuning the access pattern could be
475 consume unnecessary system resources. To avoid such consumption, the user would
476 need to manually monitor some metrics such as free memory ratio, and turn
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | platform.rst | 24 list of resources such as addresses and IRQs::
100 that are populated on a given board. Without such tables, often the
102 a kernel for a specific target board. Such board-specific kernels are
120 leaving that for system infrastructure. Such drivers can't be hotplugged
132 This style of driver is discouraged. If you're updating such a driver,
134 outside the driver. This will usually be cleanup, since such drivers
135 tend to already have "normal" modes, such as ones using device nodes that
138 None the less, there are some APIs to support such legacy drivers. Avoid
139 using these calls except with such hotplug-deficient drivers::
174 three different ways to find such a match:
|
| /Documentation/usb/ |
| D | ehci.rst | 21 such devices. When USB 1.1 devices plug into USB 2.0 hubs, they
35 Such new systems have been available since early 2002, and became much
105 You should also have a driver for a "companion controller", such as
140 can't, such as "high bandwidth" periodic (interrupt or ISO) transfers.
141 Also, some values in device descriptors (such as polling intervals for
145 Those hubs report some failures, such as disconnections, differently when
179 enough for a single device at 20 MByte/sec, putting three such devices
212 But rather than depending on such large I/O buffers to make synchronous
215 Such URB queuing should work with all the USB 1.1 HC drivers too.
|
| /Documentation/driver-api/firmware/ |
| D | introduction.rst | 27 as such mechanisms such as asynchronous probe can help supplement drivers.
|