| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-platform-chipidea-usb-otg | 7 the application running on the A-device wants to use the bus,
8 and to be 0 when the application no longer wants to use
9 the bus(or wants to work as peripheral). a_bus_req can also
24 application running on the A-device wants to power down
39 that the application running on the B-device wants to use the
40 bus as host, and is 0 when the application no longer wants to
|
| D | sysfs-driver-w1_therm | 13 Users: any user space application which wants to communicate with
29 Users: any user space application which wants to communicate with
43 Users: any user space application which wants to communicate with
65 Users: any user space application which wants to communicate with
86 Users: any user space application which wants to communicate with
107 Users: any user space application which wants to communicate with
135 Users: any user space application which wants to communicate with
|
| D | sysfs-driver-jz4780-efuse | 19 Users: any user space application which wants to read the Chip
|
| D | sysfs-driver-tegra-fuse | 10 Users: any user space application which wants to read the efuses on
|
| /Linux-v5.15/Documentation/devicetree/bindings/clock/ |
| D | ux500.txt | 15 clock in the prcmu-clock node the consumer wants to use.
19 wants to use, possible values are 1, 2, 3, 5, 6. The second
20 cell indicates which clock inside the PRCC block it wants,
25 wants to use, possible values are 1, 2, 3, 5, 6. The second
26 cell indicates which clock inside the PRCC block it wants,
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-driver-w1_ds2438 | 6 Users: any user space application which wants to communicate with DS2438
13 Users: any user space application which wants to communicate with DS2438
|
| D | sysfs-driver-w1_ds28e04 | 6 Users: any user space application which wants to communicate with DS28E04-100
15 Users: any user space application which wants to communicate with DS28E04-100
|
| D | sysfs-driver-w1_ds28ea00 | 6 Users: any user space application which wants to communicate with DS28EA00
|
| D | sysfs-bus-w1 | 11 Users: any user space application which wants to know bus scanning
|
| /Linux-v5.15/drivers/gpu/vga/ |
| D | vgaarb.c | 236 unsigned int wants, legacy_wants, match; in __vga_tryget() local
255 wants = rsrc & ~vgadev->owns; in __vga_tryget()
258 if (wants == 0) in __vga_tryget()
264 legacy_wants = wants & VGA_RSRC_LEGACY_MASK; in __vga_tryget()
346 if (wants & (VGA_RSRC_LEGACY_MEM|VGA_RSRC_NORMAL_MEM)) in __vga_tryget()
348 if (wants & (VGA_RSRC_LEGACY_IO|VGA_RSRC_NORMAL_IO)) in __vga_tryget()
351 if (wants & VGA_RSRC_LEGACY_MASK) in __vga_tryget()
356 vgadev->owns |= wants; in __vga_tryget()
|
| /Linux-v5.15/Documentation/arm/samsung-s3c24xx/ |
| D | cpufreq.rst | 28 and anything else associated with it. Any board that wants to use this
61 Each board that wants to use the cpufreq code must register some basic
|
| /Linux-v5.15/drivers/parport/ |
| D | TODO-parport | 14 with (maybe just log) whatever the printer wants to tell the world.
|
| /Linux-v5.15/drivers/staging/fieldbus/ |
| D | Kconfig | 10 They are typically used when a Linux device wants to expose itself
|
| /Linux-v5.15/drivers/staging/fieldbus/Documentation/ |
| D | fieldbus_dev.txt | 35 They are typically used when a Linux device wants to expose itself as an
45 Any driver that wants to register as a Fieldbus Device should allocate and
|
| /Linux-v5.15/Documentation/block/ |
| D | inline-encryption.rst | 61 knowledge of keyslots - it simply wants to specify an encryption context to
67 upper layers. The generic mode of operation is: each device driver that wants
153 the block layer wants en/decrypted via inline encryption (or the
162 wants to use an algorithm that may not supported by hardware - this function
196 (e.g. when it wants to program a crypto key into the IE hardware, the device
215 functionality they choose. When a layered device wants to pass a clone of that
241 when a WRITE bio wants to use inline encryption on a device that supports both
|
| /Linux-v5.15/drivers/staging/sm750fb/ |
| D | TODO | 7 are supposed to be sample code which is given here if someone wants to
|
| /Linux-v5.15/Documentation/networking/ |
| D | nexthop-group-resilient.rst | 82 this number a "wants count" of a next hop. In case of an event that might
83 cause bucket allocation change, the wants counts for individual next hops
86 Next hops that have fewer buckets than their wants count, are called
97 After assigning wants counts to next hops, an "upkeep" algorithm runs. For
109 There may not be enough "idle" buckets to satisfy the updated wants counts
|
| /Linux-v5.15/Documentation/staging/ |
| D | rpmsg.rst | 74 The caller should specify the channel, the data it wants to send,
95 The caller should specify the channel, the data it wants to send,
120 The caller should specify the channel, the data it wants to send,
140 The caller should specify the channel, the data it wants to send,
159 The user should specify the channel, the data it wants to send,
181 The user should specify the channel, the data it wants to send,
|
| /Linux-v5.15/arch/x86/boot/ |
| D | pmjump.S | 57 # a valid stack if some debugging hack wants to use it.
|
| /Linux-v5.15/Documentation/admin-guide/blockdev/ |
| D | nbd.rst | 10 the client computer wants to read, e.g., /dev/nb0, it sends a
|
| /Linux-v5.15/Documentation/usb/ |
| D | chipidea.rst | 71 if A-device wants to use bus:
78 if B-device wants to use bus:
|
| /Linux-v5.15/drivers/gpu/drm/i915/gt/uc/ |
| D | intel_uc.h | 82 __uc_state_checker(x, func, wants, wanted) \
|
| /Linux-v5.15/Documentation/x86/x86_64/ |
| D | cpu-hotplug-spec.rst | 7 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to
|
| /Linux-v5.15/Documentation/driver-api/xilinx/ |
| D | eemi.rst | 19 Any driver who wants to communicate with PMC using EEMI APIs use the
|
| /Linux-v5.15/Documentation/leds/ |
| D | well-known-leds.txt | 14 wants to use particular feature, you should probe for good name, first,
|
