Searched refs:wants (Results 1 – 25 of 228) sorted by relevance
12345678910
| /Linux-v6.6/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
|
| D | sysfs-class-fc | 25 If an admin wants to remove an FC application identifier
|
| /Linux-v6.6/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-v6.6/drivers/pci/ |
| D | vgaarb.c | 214 unsigned int wants, legacy_wants, match; in __vga_tryget() local
234 wants = rsrc & ~vgadev->owns; in __vga_tryget()
237 if (wants == 0) in __vga_tryget()
244 legacy_wants = wants & VGA_RSRC_LEGACY_MASK; in __vga_tryget()
332 if (wants & (VGA_RSRC_LEGACY_MEM|VGA_RSRC_NORMAL_MEM)) in __vga_tryget()
334 if (wants & (VGA_RSRC_LEGACY_IO|VGA_RSRC_NORMAL_IO)) in __vga_tryget()
337 if (wants & VGA_RSRC_LEGACY_MASK) in __vga_tryget()
342 vgadev->owns |= wants; in __vga_tryget()
|
| /Linux-v6.6/drivers/staging/fieldbus/ |
| D | Kconfig | 10 They are typically used when a Linux device wants to expose itself
|
| /Linux-v6.6/drivers/parport/ |
| D | TODO-parport | 14 with (maybe just log) whatever the printer wants to tell the world.
|
| /Linux-v6.6/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-v6.6/arch/arc/kernel/ |
| D | entry.S | 192 mov r0, r12 ; EFA in case ptracer/gdb wants stop_pc
195 ; save callee regs in case tracer/gdb wants to peek
|
| /Linux-v6.6/drivers/staging/sm750fb/ |
| D | TODO | 7 are supposed to be sample code which is given here if someone wants to
|
| /Linux-v6.6/arch/arm/boot/dts/nxp/imx/ |
| D | imx6q-apalis-ixora-v1.2.dts | 107 * UART2 and UART3. If one wants to disable the transceiver force
108 * the GPIO to output-low, if one wants to control the transceiver
|
| /Linux-v6.6/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-v6.6/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-v6.6/Documentation/admin-guide/blockdev/ |
| D | nbd.rst | 10 the client computer wants to read, e.g., /dev/nb0, it sends a
|
| D | zram.rst | 319 If admin wants to use incompressible page writeback, they could do it via::
356 If an admin wants to write a specific page in zram device to the backing device,
367 any writeback. IOW, if admin wants to apply writeback budget, they should
378 If admin wants to limit writeback as per-day 400M, they could do it
393 If an admin wants to see the remaining writeback budget since last set::
397 If an admin wants to disable writeback limit, they could do::
406 If admin wants to measure writeback count in a certain period, they could
|
| /Linux-v6.6/arch/x86/boot/ |
| D | pmjump.S | 57 # a valid stack if some debugging hack wants to use it.
|
| /Linux-v6.6/Documentation/usb/ |
| D | chipidea.rst | 72 if A-device wants to use bus:
79 if B-device wants to use bus:
|
| /Linux-v6.6/arch/arm64/boot/dts/freescale/ |
| D | imx8x-colibri-iris.dtsi | 85 * This turns the LVDS transceiver on. If one wants to turn the
|
| /Linux-v6.6/drivers/gpu/drm/i915/gt/uc/ |
| D | intel_uc.h | 86 __uc_state_checker(x, func, wants, wanted) \
|
| /Linux-v6.6/Documentation/arch/x86/x86_64/ |
| D | cpu-hotplug-spec.rst | 7 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to
|
12345678910
