| /linux/drivers/hwmon/pmbus/ |
| H A D | Kconfig | 12 This driver can also be built as a module. If so, the module will
27 This driver can also be built as a module. If so, the module will
36 This driver can also be built as a module. If so, the module will
47 This driver can also be built as a module. If so, the module will
57 This driver can also be built as a module. If so, the module will
67 This driver can also be built as a module. If so, the module will
76 This driver can also be built as a module. If so, the module will
85 This driver can also be built as a module. If so, the module will
95 This driver can also be built as a module. If so, the module
105 This driver can also be built as a module. If so, the module will
[all …]
|
| /linux/drivers/rtc/ |
| H A D | Kconfig | 158 This driver can also be built as a module. If so, the module
172 This driver can also be built as a module. If so, the module
182 This driver can also be built as a module. If so, the module
192 This driver can also be built as a module. If so, the module
202 This driver can also be built as a module. If so, the module
213 This driver can also be built as a module. If so, the module
223 This driver can also be built as a module. If so, the module
234 This driver can also be built as a module. If so, the module will
244 This driver can also be built as a module. If so, the module
264 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/drivers/mmc/host/ |
| H A D | toshsd.h | 37 #define SD_CMD 0x00 /* also for SDIO */
38 #define SD_ARG0 0x04 /* also for SDIO */
39 #define SD_ARG1 0x06 /* also for SDIO */
41 #define SD_BLOCKCOUNT 0x0a /* also for SDIO */
42 #define SD_RESPONSE0 0x0c /* also for SDIO */
43 #define SD_RESPONSE1 0x0e /* also for SDIO */
44 #define SD_RESPONSE2 0x10 /* also for SDIO */
45 #define SD_RESPONSE3 0x12 /* also for SDIO */
46 #define SD_RESPONSE4 0x14 /* also for SDIO */
47 #define SD_RESPONSE5 0x16 /* also for SDIO */
[all …]
|
| /linux/tools/memory-model/Documentation/ |
| H A D | glossary.txt | 25 See also "Control Dependency" and "Data Dependency".
32 but atomic_read_acquire() and atomic_xchg_acquire() also include
40 See also "Happens-Before", "Reads-From", "Relaxed", and "Release".
47 It is also possible to have a coherence link within a CPU, which
52 See also "From-reads" and "Reads-from".
67 See also "Address Dependency" and "Data Dependency".
86 See also "Pairing".
103 See also "Address Dependency" and "Control Dependency".
110 It is also possible to have a from-reads link within a CPU, which
115 See also "Coherence" and "Reads-from".
[all …]
|
| /linux/drivers/iio/temperature/ |
| H A D | Kconfig | 41 This driver can also be built as a module. If so, the module will
64 This driver can also be built as a module. If so, the module will
76 This driver can also be built as a module. If so, the module will
88 This driver can also be built as a module. If so, the module will
98 This driver can also be built as a module. If so, the module will
108 This driver can also be built as a module. If so, the module will
118 This driver can also be built as a module. If so, the module will
129 This driver can also be built as a module. If so, the module will
140 This driver can also be built as a module. If so, the module will
150 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/drivers/hid/i2c-hid/ |
| H A D | Kconfig | 21 This support is also available as a module. If so, the module
22 will be called i2c-hid-acpi. It will also build/depend on the
27 # No "depends on OF" because this can also be used for manually
39 This support is also available as a module. If so, the module
40 will be called i2c-hid-of. It will also build/depend on the
55 This support is also available as a module. If so, the module
56 will be called i2c-hid-of-elan. It will also build/depend on
71 This support is also available as a module. If so, the module
72 will be called i2c-hid-of-goodix. It will also build/depend on
|
| /linux/drivers/usb/gadget/udc/ |
| H A D | Kconfig | 14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
44 gadget drivers to also be dynamically linked.
56 gadget drivers to also be dynamically linked.
103 all gadget drivers to also be dynamically linked.
130 gadget drivers to also be dynamically linked.
146 gadget drivers to also be dynamically linked.
168 gadget drivers to also be dynamically linked.
180 gadget drivers to also be dynamically linked.
204 gadget drivers to also be dynamically linked.
215 gadget drivers to also be dynamically linked.
[all …]
|
| /linux/drivers/net/ieee802154/ |
| H A D | Kconfig | 21 This driver can also be built as a module. To do so say M here.
33 This driver can also be built as a module. To do so, say M here.
45 This driver can also be built as a module. To do so, say M here.
56 This driver can also be built as a module. To do so, say M here.
66 This driver can also be built as a module. To do so say M here.
77 This driver can also be built as a module. To do so, say M here.
89 This driver can also be built as a module. To do so, say M here.
110 This driver can also be built as a module. To do so, say M here.
121 This driver can also be built as a module. To do so say M here.
|
| /linux/drivers/w1/masters/ |
| H A D | Kconfig | 16 This driver can also be built as a module. If so, the module will be
26 This support is also available as a module. If so, the module
36 This support is also available as a module. If so, the module
46 This driver can also be built as a module. If so, the module
62 This support is also available as a module. If so, the module
78 This support is also available as a module. If so, the module
88 This support is also available as a module. If so, the module
|
| /linux/drivers/misc/eeprom/ |
| H A D | Kconfig | 24 as read-only won't help recover from this. Also, if your chip
32 This driver can also be built as a module. If so, the module
46 This driver can also be built as a module. If so, the module
59 This driver can also be built as a module. If so, the module
79 supports both read and write commands and also the command to
82 This driver can also be built as a module. If so, the module
106 This driver can also be built as a module. If so, the module
119 This driver can also be built as a module. If so, the module
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-probe.txt | 74 List up current probe events. This can also accept filtering patterns of
100 can also list functions in a user space executable / shared library.
101 This also can accept a FILTER rule argument.
126 are also stored in the cache file.
141 space tracing. Can also be used with --funcs option.
144 Demangle application symbols. --no-demangle is also available
148 Demangle kernel symbols. --no-demangle-kernel is also available
173 … "\_\_return" suffix is automatically added to the function name. You can also specify a group nam…
177 It is also possible to specify a probe point by the source line number or lazy matching by using 'S…
189 …ed to probe on a specific versioned symbols, like @GLIBC_... suffixes, or also you need to specify…
[all …]
|
| /linux/drivers/iio/gyro/ |
| H A D | Kconfig | 41 This driver can also be built as a module. If so, the module
53 This driver can also be built as a module. If so, the module will be
63 This driver can also be built as a module. If so, the module
75 driver connected via I2C or SPI. This driver also supports BMI055
78 This driver can also be built as a module. If so, the module
100 This driver can also be built as a module. If so, the module
147 Also need to enable at least one of I2C and SPI interface drivers
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-led-trigger-netdev | 32 Setting this value also immediately changes the LED state.
89 Setting this value also immediately changes the LED state.
104 Setting this value also immediately changes the LED state.
119 Setting this value also immediately changes the LED state.
134 Setting this value also immediately changes the LED state.
149 Setting this value also immediately changes the LED state.
164 Setting this value also immediately changes the LED state.
179 Setting this value also immediately changes the LED state.
192 Setting this value also immediately changes the LED state.
|
| /linux/Documentation/mm/ |
| H A D | balance.rst | 15 the caller may also wish to avoid waking kswapd.
45 due to ignoring possibly lower usage in the lower class zones. Also,
52 balancing problem, and stays as close to 2.2 behavior as possible. Also,
63 The appended patch implements the second solution. It also "fixes" two
65 for non-sleepable allocations. Second, the HIGHMEM zone is also balanced,
68 fall back into regular zone. This also makes sure that HIGHMEM pages
72 kswapd also needs to know about the zones it should balance. kswapd is
92 pages is below watermark[WMARK_LOW]; in which case zone_wake_kswapd is also set.
|
| /linux/include/media/i2c/ |
| H A D | tvaudio.h | 18 #define I2C_ADDR_TDA9874 0xb0 /* also used by 9875 */
21 #define I2C_ADDR_TDA9840 0x84 /* also used by TA8874Z */
22 #define I2C_ADDR_TDA985x_L 0xb4 /* also used by 9873 */
24 #define I2C_ADDR_TDA9874 0xb0 /* also used by 9875 */
25 #define I2C_ADDR_TEA6300 0x80 /* also used by 6320 */
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen3/ |
| H A D | other.json | 22 …dispatch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when …
28 …dispatch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when …
34 …dispatch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when …
40 …dispatch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when …
52 …dispatch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when …
58 …dispatch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when …
64 …dispatch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when …
|
| /linux/Documentation/networking/ |
| H A D | nf_flowtable.rst | 9 also provides hardware offload support. The flowtable supports for the layer 3
72 The flowtable entry also stores the NAT configuration, so all packets are
77 TCP RST and FIN packets are also passed up to the classic IP forwarding path to
78 release the flow gracefully. Packets that exceed the MTU are also passed up to
127 flowtable datapath also deals with layer 2 decapsulation.
157 The flowtable infrastructure also supports for bridge VLAN filtering actions
158 such as PVID and untagged. You can also stack a classic VLAN device on top of
208 The flowtable hardware offload infrastructure also supports for the DSA
228 also made a very complete and comprehensive summary called "A state of network
230 mainlined [3]_ and it also makes a rough summary of this work [4]_.
|
| /linux/drivers/misc/ |
| H A D | Kconfig | 30 This driver can also be built as a module. If so, the module
71 The ibmasm driver also enables the OS to use the UART on the
122 you should select this option and then also choose an appropriate
126 You will also have to select some flash card format drivers. MMC/SD
153 This driver can also be built as a module. If so, the module
172 contain storage devices). You also need either a host
329 This driver can also be built as a module. If so, the module
339 This driver can also be built as a module. If so, the module
349 This driver can also be built as a module. If so, the module
359 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/Documentation/gpu/rfc/ |
| H A D | i915_small_bar.h | 20 * here, also note that no current region type will ever return -1 here.
82 * regions (for other types the value here will also
86 * zero, see also @probed_cpu_visible_size.
100 * creates some ambiguity for the params which are considered immutable. Also in
136 * memory is directly visible/mappable through the CPU (which we also
148 * Also note that since the kernel only supports flat-CCS on objects
160 * also &__drm_i915_memory_region_info.probed_cpu_visible_size),
163 * also successfully load the i915 kernel module. In such cases the
|
| /linux/Documentation/block/ |
| H A D | inline-encryption.rst | 30 Inline encryption hardware is also very different from "self-encrypting drives",
41 also want support for falling back to the kernel crypto API when actual inline
42 encryption hardware is absent. We also want inline encryption to work with
53 Encryption contexts also introduce constraints on bio merging; the block layer
70 layers to also evict keys from any keyslots they are present in.
94 We also introduce ``struct blk_crypto_profile`` to contain all generic inline
102 The blk_crypto_profile also manages the hardware's keyslots, when applicable.
118 ``struct request`` also contains a pointer to the original bio_crypt_ctx.
137 likewise for the block layer's keyslot management logic. It is also desirable
141 Therefore, we also introduce *blk-crypto-fallback*, which is an implementation
[all …]
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | floppy.rst | 8 A FAQ list may be found in the fdutils package (see below), and also
24 You may also enter the following line in /etc/lilo.conf, in the description
36 prompt options coming last. That's why there are also options to
93 DMA channel for the floppy driver. This option is also useful
99 later are OK. You also need at least a 486 to use nodma.
100 If you use nodma mode, I suggest you also set the FIFO
183 problems. However, some older drives, and also some laptops
217 This package also contains a new version of mtools which allows to
219 It also contains additional documentation about the floppy driver.
241 sure to mention also the type of the filesystem in the subject line.
|
| /linux/Documentation/driver-api/ |
| H A D | rfkill.rst | 16 The subsystem also provides the ability to react on button presses and
52 The rfkill core code also notifies userspace of state changes, and provides
72 implement an rfkill driver instead. This also applies if the platform provides
89 rfkill drivers that control devices that can be hard-blocked unless they also
102 devices and sets of devices. It also notifies userspace about device addition
111 system. Also, it is possible to switch all rfkill drivers (or all drivers of
112 a specified type) into a state which also updates the default state for
|
| H A D | parport-lowlevel.rst | 74 claiming a port for exclusive use, and so on. They also include
235 SEE ALSO
284 SEE ALSO
350 SEE ALSO
493 SEE ALSO
530 SEE ALSO
576 SEE ALSO
617 SEE ALSO
663 SEE ALSO
698 SEE ALSO
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 61 colorspace. Also, y has nothing to do with luminance. Together x and y
79 chromaticity coordinates from the CIE xyY colorspace) but also the white
95 intensity of the color. So each colorspace also defines a transfer
113 in the CIE XYZ colorspace. Also note that Y'CbCr is often called YCbCr
119 color is also associated with the Y'CbCr color.
134 Unfortunately, in some cases limited range RGB is also used where the
135 components use the range [16…235]. And full range Y'CbCr also exists
150 mix of different standards also led to very confusing naming conventions
163 article is also very useful.
|
| /linux/Documentation/usb/ |
| H A D | ehci.rst | 18 USB 1.1 devices may also be used on USB 2.0 systems. When plugged
50 This driver is regularly tested on x86 hardware, and has also been
62 High Speed Isochronous (ISO) transfer support is also functional, but
82 just because the EHCI driver is also present.
87 Also, some shortcuts have been taken with the scheduling periodic
105 You should also have a driver for a "companion controller", such as
141 Also, some values in device descriptors (such as polling intervals for
156 but aggregate throughput is also affected by issues like delays between
158 overall system load. Latency is also a performance concern.
218 queue all the buffers from a scatterlist. They also use scatterlist DMA
|