| /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 …]
|
| /Documentation/ |
| D | speculation.txt | 9 employ speculative execution techniques such as branch prediction, performing
13 such as the contents of registers. However, in some cases it is possible to
14 observe its impact on microarchitectural state, such as the presence or
15 absence of data in caches. Such state may form side-channels which can be
30 Which, on arm64, may be compiled to an assembly sequence such as::
|
| D | nommu-mmap.txt | 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 …]
|
| D | robust-futex-ABI.txt | 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 29
|
| /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/devicetree/bindings/bus/ |
| D | ti-sysc.txt | 4 hardware for devices connected to various interconnects such as L3
43 target module in question such as revision, sysc and syss
46 interconnect target module in question such as
52 multiple ranges such as device L4 range for control and
87 for the related CLKCTRL register bits 8 to 15 such as
136 Note that other SoCs, such as am335x can have multiple child devices. On am335x
|
| /Documentation/vm/ |
| D | numa.rst | 57 For some architectures, such as x86, Linux will "hide" any node representing a
82 memory, Linux must decide whether to order the zonelists such that allocations
85 such as DMA or DMA32, represent relatively scarce resources. Linux chooses
110 such as taskset(1) and numactl(1), and program interfaces such as
126 allows such allocations to fallback to other nearby nodes when a node that
134 A typical model for making such an allocation is to obtain the node id of the
137 the node id returned. When such an allocation fails, the requesting subsystem
146 memory exclusively from a node without memory. To support such
|
| /Documentation/networking/ |
| D | devlink-trap.rst | 10 Devices capable of offloading the kernel's datapath and perform functions such
16 Without processing such packets, the bridge module could never populate its
22 error datagram. Without letting the kernel route such packets itself, utilities
23 such as ``traceroute`` could never work.
98 action of such traps is not allowed, as it can easily break the control
117 Such traps can be shared by multiple device drivers and their description must
170 clearly documented. Such traps can correspond to device-specific exceptions and
181 traps. These groups allow the user to batch operations such as setting the trap
208 Device drivers should focus their tests on device-specific functionality, such
|
| /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
133 on 32bit CPUs. Such operations are frequently necessary to convert
|
| /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 | 21 required drivers such as storage hardware (such as SCSI or USB!)
28 D) e.g. required library dependencies of the init binary such as
37 non-script binary such as ``/bin/sh`` and confirm its successful execution.
|
| /Documentation/driver-api/gpio/ |
| D | legacy.rst | 19 passes such pin configuration data to drivers.
25 often have a few such pins to help with pin scarcity on SOCs; and there are
38 of pins configured as "output", which is very useful in such "wire-OR"
43 sometimes level triggered. Such IRQs may be configurable as system
72 optional code supporting such an implementation strategy, described later
114 test if such number from such a structure could reference a GPIO, you
125 of GPIO numbers, and whether new controllers can be added at runtime. Such issues
168 Use the following calls to access such GPIOs,
191 of instructions in such cases (reading or writing a hardware register),
192 and not to need spinlocks. Such optimized calls can make bitbanging
[all …]
|
| /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/networking/device_drivers/qlogic/ |
| D | LICENSE.qlge | 43 For example, if you distribute copies of such a program, whether
75 refers to any such program or work, and a "work based on the Program"
102 distribute such modifications or work under the terms of Section 1
114 when run, you must cause it, when started running for such
121 does not normally print such an announcement, your work based on
162 received the program in object code or executable form with such
187 this License will not have their licenses terminated so long as such
227 such claims; this section has the sole purpose of protecting the
244 countries not thus excluded. In such case, this License incorporates
248 of the General Public License from time to time. Such new versions will
[all …]
|
| D | LICENSE.qlcnic | 43 For example, if you distribute copies of such a program, whether
75 refers to any such program or work, and a "work based on the Program"
102 distribute such modifications or work under the terms of Section 1
114 when run, you must cause it, when started running for such
121 does not normally print such an announcement, your work based on
162 received the program in object code or executable form with such
187 this License will not have their licenses terminated so long as such
227 such claims; this section has the sole purpose of protecting the
244 countries not thus excluded. In such case, this License incorporates
248 of the General Public License from time to time. Such new versions will
[all …]
|
| /Documentation/scsi/ |
| D | LICENSE.qla4xxx | 44 For example, if you distribute copies of such a program, whether
76 refers to any such program or work, and a "work based on the Program"
103 distribute such modifications or work under the terms of Section 1
115 when run, you must cause it, when started running for such
122 does not normally print such an announcement, your work based on
163 received the program in object code or executable form with such
188 this License will not have their licenses terminated so long as such
228 such claims; this section has the sole purpose of protecting the
245 countries not thus excluded. In such case, this License incorporates
249 of the General Public License from time to time. Such new versions will
[all …]
|
| D | LICENSE.qla2xxx | 45 For example, if you distribute copies of such a program, whether
77 refers to any such program or work, and a "work based on the Program"
104 distribute such modifications or work under the terms of Section 1
116 when run, you must cause it, when started running for such
123 does not normally print such an announcement, your work based on
164 received the program in object code or executable form with such
189 this License will not have their licenses terminated so long as such
229 such claims; this section has the sole purpose of protecting the
246 countries not thus excluded. In such case, this License incorporates
250 of the General Public License from time to time. Such new versions will
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | platform.rst | 24 list of resources such as addresses and IRQs::
99 that are populated on a given board. Without such tables, often the
101 a kernel for a specific target board. Such board-specific kernels are
119 leaving that for system infrastructure. Such drivers can't be hotplugged
131 This style of driver is discouraged. If you're updating such a driver,
133 outside the driver. This will usually be cleanup, since such drivers
134 tend to already have "normal" modes, such as ones using device nodes that
137 None the less, there are some APIs to support such legacy drivers. Avoid
138 using these calls except with such hotplug-deficient drivers::
173 three different ways to find such a match:
|
| /Documentation/driver-api/thermal/ |
| D | intel_powerclamp.rst | 70 level C-state. The intel_powerclamp driver is conceived as such a
83 effect. Threads are also bound to the CPU such that they cannot be
87 Running as SCHED_FIFO and relatively high priority, also allows such
131 When used in a causal control system, such as a temperature control,
147 calibration is implemented. The goals for doing such a calibration
157 enter idle without extra wakeups (such as external interrupts).
165 progress and results, such as on a Westmere system::
210 idle time is injected when such a condition is detected. Currently,
212 enhancement might be to throttle the offending IRQ, such as delaying
238 normal cases, such as scp a large file, applications can be throttled
|
| /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/ABI/testing/ |
| D | sysfs-bus-iio-temperature-max31856 | 6 such as those caused by broken thermocouple wires.
8 '1' = An open circuit such as broken thermocouple wires
|