Searched full:bound (Results 1 – 25 of 217) sorted by relevance
123456789
| /Documentation/devicetree/bindings/mailbox/ |
| D | mediatek,gce-props.yaml | 33 Some gce-events are hardware-bound and cannot be changed by software.
38 On the other hand, some gce-events are not hardware-bound and can be
40 event ID 855, which is not bound to any hardware, to 1 when the driver
42 is already bound to VDEC_LAT1, so we need to select another event ID to
43 achieve the same purpose. This event ID can be any ID that is not bound
45 To determine if the event ID is bound to the hardware or used by a
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-set-rec-carrier-range.rst | 13 LIRC_SET_REC_CARRIER_RANGE - Set lower bound of the carrier used to modulate
41 <LIRC_SET_REC_CARRIER_RANGE>` with the lower bound first and later call
42 :ref:`LIRC_SET_REC_CARRIER <LIRC_SET_REC_CARRIER>` with the upper bound.
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-colorimetry.rst | 39 - The upper bound for the maximum light level among all individual
41 When equal to 0 no such upper bound is present.
44 - The upper bound for the maximum average light level among the
46 cd/m\ :sup:`2`. When equal to 0 no such upper bound is present.
|
| D | selections-common.rst | 12 and is bound to a sub-device's pad. On the V4L2 interface the selection
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-usbip-vudc | 7 gadget driver which is currently bound to this
9 only if gadget driver is bound, otherwise error
|
| D | sysfs-class-devlink | 63 consumer devices have been bound to their corresponding
86 bound to their driver.
88 'available' means the supplier has bound to its driver and is
95 bound successfully to their drivers.
|
| D | sysfs-devices-vfio-dev | 5 This directory is created when the device is bound to a
|
| D | sysfs-devices-coredump | 6 device is bound to a driver, which provides the .coredump()
|
| D | sysfs-bus-event_source-devices-dsa | 29 IDXD DSA pmu is bound for access to all dsa pmu
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 102 with another driver bound to the interface, eg. a power management
147 that isn't bound to your driver.
149 Probe will never be called for an interface bound to a driver.
153 Once your driver is bound to an interface, disconnect can be
|
| /Documentation/networking/ |
| D | devmem.rst | 85 an RX queue bound to devmem.
127 that has been bound.
141 The socket must be flow steered to the dmabuf bound RX queue::
157 Devmem data is received directly into the dmabuf bound to the NIC in 'NIC
211 regular TCP data that landed on an RX queue not bound to a dmabuf.
225 Failure to do so will exhaust the limited dmabuf that is bound to the RX queue
|
| D | af_xdp.rst | 53 The socket is then finally bound with a bind() call to a device and a
75 indeed bound to that device and ring number. If not, the packet is
112 system call. A UMEM is bound to a netdev and queue id, via the bind()
235 dropped. E.g. an AF_XDP socket is bound to netdev eth0 and
269 sockets bound to the same netdev and queue id. The UMEM (tied to the
272 we have bound to. To use this mode, create the first socket and bind
321 bound to different queue ids and/or netdevs. In this case you have to
323 netdev,queue_id pair. Let us say you want to create two sockets bound
333 case where sockets were bound to the same queue id and
341 created for you and bound to the shared UMEM. You can use this
[all …]
|
| /Documentation/input/ |
| D | notifier.rst | 16 - KBD_UNBOUND_KEYCODE events are sent if the keycode is not bound to a keysym.
35 || !bound) {
|
| /Documentation/driver-api/ |
| D | console.rst | 54 - means the driver is not bound and if echo'ed, commands the driver
58 - means the driver is bound and if echo'ed, commands the driver to
114 driver is bound or not.
132 driver, which was previously bound, becomes unbound. The console layer
|
| D | device_link.rst | 18 dependencies, i.e. that one device must be bound to a driver before
31 supplier is bound to a driver, and they're unbound before the supplier
100 a driver has been bound to the supplier device.
159 not bind before the MMU is bound. To achieve this, a device link with
274 * When a supplier device is bound to a driver, links to its consumers
302 bound to a driver are updated to ``DL_STATE_SUPPLIER_UNBIND``.
308 Consumers that are bound are freed from their driver; consumers that are
|
| D | wmi.rst | 14 which will be bound to compatible WMI devices by the driver core.
|
| /Documentation/hwmon/ |
| D | adt7462.rst | 64 - point1: Set the pwm speed at a lower temperature bound.
65 - point2: Set the pwm speed at a higher temperature bound.
|
| D | adt7470.rst | 63 - point1: Set the pwm speed at a lower temperature bound.
64 - point2: Set the pwm speed at a higher temperature bound.
|
| /Documentation/scheduler/ |
| D | sched-bwc.rst | 95 period is 1ms. There is also an upper bound on the period length of 1s.
178 For highly-threaded, non-cpu bound applications this non-expiration nuance
195 The interaction between cpu-bound and non-cpu-bound-interactive applications
198 on the same CPU it is theoretically possible that the non-cpu bound application
200 cpu-bound application from fully using its quota by that same amount. In these
|
| /Documentation/devicetree/bindings/input/ |
| D | adc-joystick.yaml | 55 Represents a joystick axis bound to the given ADC channel.
63 description: Index of an io-channels list entry bound to this axis.
|
| /Documentation/spi/ |
| D | spidev.rst | 39 bound when these are defined using a struct spi_board_info with a
43 bound when these are defined using a Device Tree node that has a
47 be bound when these are defined using a ACPI device object with a
69 When the spidev driver is bound to a SPI device, the sysfs node for the
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 35 having multiple Raw Gadget instances bound to different UDCs.
48 for details. Multiple Raw Gadget instances (bound to different UDCs) can be
|
| /Documentation/core-api/ |
| D | circular-buffers.rst | 114 they will return a lower bound as the producer controls the head index,
118 To the consumer it will show an upper bound as the producer may be busy
122 will return a lower bound as the consumer controls the tail index, but the
126 To the producer it will show an upper bound as the consumer may be busy
|
| /Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.yaml | 90 - description: range lower bound
91 - description: range upper bound
|
| /Documentation/devicetree/bindings/virtio/ |
| D | virtio-device.yaml | 14 are bound to, like mmio or pci.
|
123456789