/Linux-v5.4/drivers/clk/qcom/ |
D | Kconfig | 37 such as msm8916. 50 platforms such as apq8064, msm8660, msm8960 etc. 63 platforms such as apq8016, apq8084, msm8974 etc. 72 platforms such as SDM845. 79 Say Y if you want to use peripheral devices such as UART, SPI, 88 Say Y if you want to support multimedia devices such as display, 95 Say Y if you want to use peripheral devices such as UART, SPI, 102 Say Y if you want to use peripheral devices such as UART, SPI, 110 Say Y if you want to use audio devices such as i2s, pcm, 117 Say Y if you want to use peripheral devices such as UART, SPI, [all …]
|
/Linux-v5.4/sound/soc/mediatek/ |
D | Kconfig | 12 Select Y if you have such device. 23 Select Y if you have such device. 33 Select Y if you have such device. 43 Select Y if you have such device. 53 Select Y if you have such device. 63 Select Y if you have such device. 73 Select Y if you have such device. 84 Select Y if you have such device. 95 Select Y if you have such device. 107 Select Y if you have such device. [all …]
|
/Linux-v5.4/sound/soc/intel/boards/ |
D | Kconfig | 27 Say Y or m if you have such a device. 44 Say Y or m if you have such a device. 56 Say Y or m if you have such a device. This is a recommended option. 96 Say Y or m if you have such a device. This is a recommended option. 108 Say Y or m if you have such a device. This is a recommended option. 120 Say Y or m if you have such a device. This is a recommended option. 132 Say Y or m if you have such a device. This is a recommended option. 144 Say Y or m if you have such a device. This is a recommended option. 156 Say Y or m if you have such a device. This is a recommended option. 168 Say Y or m if you have such a device. This is a recommended option. [all …]
|
/Linux-v5.4/LICENSES/dual/ |
D | MPL-1.1 | 90 to cause the direction or management of such entity, whether by 92 (50%) of the outstanding shares or beneficial ownership of such 129 created by such Contributor (or portions thereof) either on an 136 of such combination), to make, use, sell, offer for sale, have 140 Version (or portions of such combination). 180 has been made available to such recipients. You are responsible for 198 granted by such Contributor under Sections 2.1 or 2.2, 202 know whom to contact. If Contributor obtains such knowledge after 206 (such as notifying appropriate mailing lists or newsgroups) 225 Code. If it is not possible to put such notice in a particular Source [all …]
|
D | CDDL-1.0 | 72 documentation included in or with such code. 80 direction or management of such entity, whether by contract 83 such entity. 127 Modifications created by such Contributor (or portions 135 (or portions of such combination), to make, use, sell, 140 of such combination). 166 of any such Covered Software in Executable form as to how they can 167 obtain such Covered Software in Source Code form in a reasonable 197 make it absolutely clear that any such warranty, support, indemnity 200 any liability incurred by the Initial Developer or such Contributor [all …]
|
D | Apache-2.0 | 33 power, direct or indirect, to cause the direction or management of such 36 ownership of such entity. 84 perform, sublicense, and distribute the Work and such Derivative Works 91 sell, import, and otherwise transfer the Work, where such license 92 applies only to those patent claims licensable by such Contributor that 94 combination of their Contribution(s) with the Work to which such 100 shall terminate as of the date such litigation is filed. 121 such NOTICE file, excluding those notices that do not pertain to any 126 generated by the Derivative Works, if and wherever such third-party 131 Work, provided that such additional attribution notices cannot be [all …]
|
/Linux-v5.4/sound/soc/sof/intel/ |
D | Kconfig | 7 Say Y if you have such a device. 67 Say Y if you have such a device. 82 Say Y if you have such a device. 102 Say Y if you have such a device. 117 Say Y if you have such a device. 132 Say Y if you have such a device. 147 Say Y if you have such a device. 162 Say Y if you have such a device. 177 Say Y if you have such a device. 199 Say Y if you have such a device. [all …]
|
/Linux-v5.4/include/linux/ |
D | rculist.h | 88 * (such as holding appropriate locks) to avoid racing 89 * with another list-mutation primitive, such as list_add_rcu() 92 * the _rcu list-traversal primitives, such as 109 * (such as holding appropriate locks) to avoid racing 110 * with another list-mutation primitive, such as list_add_tail_rcu() 113 * the _rcu list-traversal primitives, such as 134 * (such as holding appropriate locks) to avoid racing 135 * with another list-mutation primitive, such as list_del_rcu() 138 * the _rcu list-traversal primitives, such as 165 * The caller must take whatever precautions are necessary (such as [all …]
|
D | rculist_bl.h | 40 * The caller must take whatever precautions are necessary (such as 42 * list-mutation primitive, such as hlist_bl_add_head_rcu() or 45 * primitives, such as hlist_bl_for_each_entry_rcu(). 67 * (such as holding appropriate locks) to avoid racing 68 * with another list-mutation primitive, such as hlist_bl_add_head_rcu() 71 * the _rcu list-traversal primitives, such as 90 * (such as holding appropriate locks) to avoid racing 91 * with another list-mutation primitive, such as hlist_bl_add_head_rcu() 94 * the _rcu list-traversal primitives, such as
|
D | rculist_nulls.h | 26 * The caller must take whatever precautions are necessary (such as 28 * list-mutation primitive, such as hlist_nulls_add_head_rcu() or 31 * primitives, such as hlist_nulls_for_each_entry_rcu(). 59 * (such as holding appropriate locks) to avoid racing 60 * with another list-mutation primitive, such as hlist_nulls_add_head_rcu() 63 * the _rcu list-traversal primitives, such as 82 * (such as holding appropriate locks) to avoid racing 83 * with another list-mutation primitive, such as hlist_nulls_add_head_rcu() 86 * the _rcu list-traversal primitives, such as
|
D | nfs_iostat.h | 14 * to be integrated into system monitoring tools such as "sar" and 15 * "iostat". As such, the counters are sampled by the tools over 81 * system administrators to monitor such things as how close-to-open 82 * is working, and answer questions such as "why are there so many 85 * They also count anamolous events such as short reads and writes, 87 * change the size of a file (such operations can often be the
|
/Linux-v5.4/arch/arm/mach-omap1/ |
D | Kconfig | 70 have such a board. 76 TI OMAP 1610/1611B H2 board support. Say Y here if you have such 83 TI OMAP 1710 H3 board support. Say Y here if you have such 97 if you have such a board. 111 Support for TI OMAP 730 Perseus2 board. Say Y here if you have such 118 Support for TI OMAP 850 F-Sample board. Say Y here if you have such 137 Say Y here if you have such a PDA, say N otherwise. 158 Say Y here if you have such a phone, say NO otherwise. 165 have such a device. 177 if you have such a device.
|
/Linux-v5.4/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
|
/Linux-v5.4/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 …]
|
/Linux-v5.4/drivers/usb/dwc3/ |
D | Kconfig | 65 Say 'Y' or 'M' here if you have one such device 73 say 'Y' or 'M' if you have one such device. 97 Say 'Y' or 'M' here if you have one such device 108 Say 'Y' or 'M' if you have one such device. 117 Say 'Y' or 'M' if you have one such device. 126 Say 'Y' or 'M' if you have one such device. 139 Say 'Y' or 'M' if you have one such device.
|
/Linux-v5.4/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 …]
|
/Linux-v5.4/Documentation/ |
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 …]
|
/Linux-v5.4/lib/ |
D | Kconfig | 48 architectures which support such operations. 90 logic PIO space shared with MMIO hosts, such as PCI/PCIe, then the 104 the kernel tree does. Such modules that use library CRC-CCITT 112 the kernel tree does. Such modules that use library CRC16 129 the kernel tree does. Such modules that use library CRC ITU-T V.41 139 the kernel tree does. Such modules that use library CRC32/CRC32c 203 the kernel tree does. Such modules that use library CRC64 211 the kernel tree does. Such modules that use library CRC4 219 the kernel tree does. Such modules that use library CRC7 229 kernel tree does. Such modules that use library CRC32c functions [all …]
|
/Linux-v5.4/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
|
/Linux-v5.4/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
|
/Linux-v5.4/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
|
/Linux-v5.4/sound/pci/hda/ |
D | Kconfig | 98 option, such as patch=hda-init. 105 snd-hda-intel driver, such as ALC880. 115 snd-hda-intel driver, such as AD1986A. 125 snd-hda-intel driver, such as STAC9200. 135 snd-hda-intel driver, such as VT1708. 159 snd-hda-intel driver, such as CS4206. 169 snd-hda-intel driver, such as CX20549. 210 snd-hda-intel driver, such as CMI9880.
|
/Linux-v5.4/drivers/net/wireless/intersil/orinoco/ |
D | Kconfig | 77 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that 79 MA301 is such an adaptor. 88 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that 114 A driver for "Hermes" chipset based PCMCIA wireless adaptors, such 118 such as the Linksys, D-Link and Farallon Skyline. It should also 119 work on Symbol cards such as the 3Com AirConnect and Ericsson WLAN. 131 firmware, such as Symbol Wireless Networker LA4100, CompactFlash
|
/Linux-v5.4/sound/soc/uniphier/ |
D | Kconfig | 19 Select Y if you use such device. 30 Select Y if you use such device. 41 Select Y if you use such device. 51 Select Y if you use such device.
|
/Linux-v5.4/include/uapi/linux/ |
D | gpio.h | 20 * @label: a functional name for this GPIO chip, such as a product 42 * @name: the name of this GPIO line, such as the output pin of the line on the 70 * @flags: desired flags for the desired GPIO lines, such as 81 * such as "my-bitbanged-relay" 119 * @handleflags: desired handle flags for the desired GPIO line, such as 121 * @eventflags: desired flags for the desired GPIO event line, such as 124 * such as "my-listener"
|