Searched refs:wants (Results 1 – 25 of 189) sorted by relevance
12345678
| /Linux-v5.4/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-tegra-fuse | 10 Users: any user space application which wants to read the efuses on
|
| D | sysfs-block-aoe | 27 state means that the driver wants to send more commands to the
|
| D | sysfs-platform-kim | 40 When one of the protocols Bluetooth, FM or GPS wants to make
|
| /Linux-v5.4/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.4/Documentation/ABI/stable/ |
| 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 | 10 Users: any user space application which wants to know bus scanning
|
| /Linux-v5.4/drivers/gpu/vga/ |
| D | vgaarb.c | 245 unsigned int wants, legacy_wants, match; in __vga_tryget() local
264 wants = rsrc & ~vgadev->owns; in __vga_tryget()
267 if (wants == 0) in __vga_tryget()
273 legacy_wants = wants & VGA_RSRC_LEGACY_MASK; in __vga_tryget()
363 if (wants & (VGA_RSRC_LEGACY_MEM|VGA_RSRC_NORMAL_MEM)) in __vga_tryget()
365 if (wants & (VGA_RSRC_LEGACY_IO|VGA_RSRC_NORMAL_IO)) in __vga_tryget()
368 if (wants & VGA_RSRC_LEGACY_MASK) in __vga_tryget()
376 vgadev->owns |= wants; in __vga_tryget()
|
| /Linux-v5.4/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.4/drivers/parport/ |
| D | TODO-parport | 14 with (maybe just log) whatever the printer wants to tell the world.
|
| /Linux-v5.4/drivers/staging/fieldbus/ |
| D | Kconfig | 10 They are typically used when a Linux device wants to expose itself
|
| /Linux-v5.4/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.4/drivers/staging/sm750fb/ |
| D | TODO | 7 are supposed to be sample code which is given here if someone wants to
|
| /Linux-v5.4/Documentation/ |
| D | rpmsg.txt | 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.4/arch/x86/boot/ |
| D | pmjump.S | 57 # a valid stack if some debugging hack wants to use it.
|
| /Linux-v5.4/Documentation/admin-guide/blockdev/ |
| D | nbd.rst | 10 the client computer wants to read, e.g., /dev/nb0, it sends a
|
| /Linux-v5.4/Documentation/usb/ |
| D | chipidea.rst | 71 if A-device wants to use bus:
78 if B-device wants to use bus:
|
| /Linux-v5.4/drivers/rpmsg/ |
| D | Kconfig | 5 # RPMSG always gets selected by whoever wants it
|
| /Linux-v5.4/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.4/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-sirf.txt | 42 For a specific board, if it wants to use uart2 without hardware flow control,
|
| D | pinctrl-atlas7.txt | 97 For a specific board, if it wants to use sd1,
|
| /Linux-v5.4/Documentation/vm/ |
| D | hmm.rst | 47 Concretely, this means that code that wants to leverage devices like GPUs needs
149 device driver that wants to mirror a process address space must start with the
194 When the device driver wants to populate a range of virtual addresses, it can
296 and the device driver wants pages for a range with at least read permission,
305 Now let's say the driver wants to do the same except for one page in the range for
306 which it wants to have write permission. Now driver set::
|
| /Linux-v5.4/Documentation/fb/ |
| D | cmap_xfbdev.rst | 54 that the app wants to match to. The above code is doing what looks like a least
|
| /Linux-v5.4/drivers/staging/wusbcore/Documentation/ |
| D | wusb-cbaf | 45 (connection key). Device saves them for the next time it wants to
|
12345678
