Home
last modified time | relevance | path

Searched full:wants (Results 1 – 25 of 1268) sorted by relevance

12345678910>>...51

/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-platform-chipidea-usb-otg7 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
Dsysfs-driver-w1_therm13 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
Dsysfs-bus-iio-dac6 is useful when one wants to change the DAC output codes. For
37 is useful when one wants to change the DAC output codes. For
/linux-6.14.4/Documentation/devicetree/bindings/clock/
Dstericsson,u8500-clks.yaml40 prcmu-clock node the consumer wants to use.
52 which PRCC block the consumer wants to use, possible values are 1, 2, 3,
54 wants, possible values are 0 thru 31.
66 block the consumer wants to use, possible values are 1, 2, 3, 5, 6. The
67 second cell indicates which clock inside the PRCC block it wants, possible
80 which PRCC block the consumer wants to use, possible values are 1, 2, 3
82 it wants to control, possible values are 0 thru 31.
/linux-6.14.4/arch/powerpc/kernel/ptrace/
Dptrace32.c48 * data is a pointer specifying where the user wants the in compat_arch_ptrace()
106 * data is a pointer specifying where the user wants the in compat_arch_ptrace()
120 /* Determine which register the user wants */ in compat_arch_ptrace()
123 /* Determine which part of the register the user wants */ in compat_arch_ptrace()
153 * data is the 4 bytes that the user wants written in compat_arch_ptrace()
206 * data is the 4 bytes that the user wants written in compat_arch_ptrace()
216 /* Determine which register the user wants */ in compat_arch_ptrace()
/linux-6.14.4/drivers/gpu/drm/xe/
Dxe_gt_sriov_pf_control_types.h18 * @XE_GT_SRIOV_STATE_FLR_SEND_START: indicates that the PF wants to send a FLR START command.
24 * @XE_GT_SRIOV_STATE_FLR_SEND_FINISH: indicates that the PF wants to send a FLR FINISH message.
38 * @XE_GT_SRIOV_STATE_STOP_SEND_STOP: indicates that the PF wants to send a STOP command.
/linux-6.14.4/drivers/gpu/drm/i915/gvt/
Dvgpu.c165 * This function is called when user wants to activate a virtual GPU.
177 * This function is called when user wants to deactivate a virtual GPU.
202 * This function is called when user wants to release a virtual GPU.
222 * This function is called when user wants to destroy a virtual GPU.
262 * This function is called when user wants to create an idle virtual GPU.
300 * This function is called when user wants to destroy an idle virtual GPU.
413 * This function is called when user wants to reset a virtual GPU through
503 * This function is called when user wants to reset a virtual GPU.
/linux-6.14.4/Documentation/ABI/stable/
Dsysfs-driver-w1_ds24386 Users: any user space application which wants to communicate with DS2438
13 Users: any user space application which wants to communicate with DS2438
Dsysfs-driver-w1_ds28e046 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
/linux-6.14.4/Documentation/staging/
Drpmsg.rst74 The caller should specify the endpoint, the data it wants to send,
96 The caller should specify the endpoint, the data it wants to send,
122 The caller should specify the endpoint, the data it wants to send,
143 The caller should specify the endpoint, the data it wants to send,
163 The user should specify the channel, the data it wants to send,
185 The user should specify the channel, the data it wants to send,
/linux-6.14.4/include/linux/
Dpci_hotplug.h19 * @enable_slot: Called when the user wants to enable a specific pci slot
20 * @disable_slot: Called when the user wants to disable a specific pci slot
35 * the user wants to do something to a specific slot (query it for information,
Dkgdb.h125 * @gdb_regs: A pointer to hold the registers in the order GDB wants.
135 * @gdb_regs: A pointer to hold the registers in the order GDB wants.
170 * they are handled here. The code should return -1 if it wants to
171 * process more packets, and a %0 or %1 if it wants to exit from the
/linux-6.14.4/arch/parisc/kernel/
Dsignal32.h26 * Userspace can read the hidden structure if it *wants* but is never
48 * The 32-bit ABI wants at least 48 bytes for a function call frame:
/linux-6.14.4/sound/soc/intel/atom/sst/
Dsst_stream.c147 * This function is called by any function which wants to start
240 * This function is called by any function which wants to pause
285 * This function is called by any function which wants to resume
353 * This function is called by any function which wants to stop
388 * This function is called by any function which wants to drain
426 * This function is called by any function which wants to free
/linux-6.14.4/drivers/md/
Ddm-rq.c228 /* The target wants to complete the I/O */ in dm_done()
235 /* The target wants to requeue the I/O */ in dm_done()
239 /* The target wants to requeue the I/O after a delay */ in dm_done()
403 /* The target wants to requeue the I/O */ in map_request()
406 /* The target wants to requeue the I/O after a delay */ in map_request()
410 /* The target wants to complete the I/O */ in map_request()
/linux-6.14.4/drivers/dca/
Ddca-core.c169 * @dev - the device that wants dca service
224 * @dev - the device that wants dca service
255 * @dev - the device that wants dca service
280 * @dev - the device that wants dca service
/linux-6.14.4/Documentation/devicetree/bindings/sound/
Dnvidia,tegra210-i2s.yaml46 per bit clock rate. I/O module which wants to use this clock
49 some other I/O wants to reference from a particular I2Sx
/linux-6.14.4/Documentation/admin-guide/blockdev/
Dzram.rst346 If admin wants to use incompressible page writeback, they could do it via::
383 If an admin wants to write a specific page in zram device to the backing device,
394 any writeback. IOW, if admin wants to apply writeback budget, they should
405 If admin wants to limit writeback as per-day 400M, they could do it
420 If an admin wants to see the remaining writeback budget since last set::
424 If an admin wants to disable writeback limit, they could do::
433 If admin wants to measure writeback count in a certain period, they could
/linux-6.14.4/Documentation/mm/
Dhmm.rst45 Concretely, this means that code that wants to leverage devices like GPUs needs
147 device driver that wants to mirror a process address space must start with the
159 When the device driver wants to populate a range of virtual addresses, it can
218 For instance if the device driver wants pages for a range with at least read
227 Now let's say the driver wants to do the same except for one page in the range for
228 which it wants to have write permission. Now driver set::
/linux-6.14.4/drivers/i2c/busses/
Di2c-gxp.c376 /* Master sent start and wants to read */ in gxp_i2c_slave_irq_handler()
385 /* Master wants to write to us */ in gxp_i2c_slave_irq_handler()
402 /* Master wants to read */ in gxp_i2c_slave_irq_handler()
404 /* Master wants another byte */ in gxp_i2c_slave_irq_handler()
418 /* Master wants to write to us */ in gxp_i2c_slave_irq_handler()
/linux-6.14.4/Documentation/filesystems/caching/
Dbackend-api.rst62 When a cache backend wants to bring a cache online, it should first register
399 object to be in and what it wants to do during the operation:
401 * ``FSCACHE_WANT_PARAMS`` - The caller just wants to access cache
404 * ``FSCACHE_WANT_READ`` - The caller wants to read data.
406 * ``FSCACHE_WANT_WRITE`` - The caller wants to write to or resize the
/linux-6.14.4/drivers/usb/gadget/
DKconfig395 application may choose to do whatever it wants with the data
397 wants as audio data to the USB Host.
427 application may choose to do whatever it wants with the data
429 wants as audio data to the USB Host.
/linux-6.14.4/include/net/netfilter/
Dnf_tproxy.h60 * This is used when the user wants to intercept a connection matching
74 * or to 0. The user already stated that he wants redirection
/linux-6.14.4/Documentation/networking/
Dnexthop-group-resilient.rst82 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-6.14.4/Documentation/filesystems/
Djournalling.rst120 jbd2_journal_unlock_updates(). Ext4 uses this when it wants a
148 File system is free to perform fast commits as and when it wants as long as it
152 :c:func:`jbd2_fc_end_commit()`. If the file system wants JBD2 to perform a full

12345678910>>...51