Searched full:bound (Results 1 – 25 of 167) sorted by relevance
1234567
| /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.
|
| D | lirc-set-rec-carrier.rst | 39 sets the upper bound frequency that will be recognized by the device.
|
| /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/scheduler/ |
| D | sched-bwc.rst | 44 upper bound on the period length of 1s. Additional restrictions exist when
118 For highly-threaded, non-cpu bound applications this non-expiration nuance
135 The interaction between cpu-bound and non-cpu-bound-interactive applications
138 on the same CPU it is theoretically possible that the non-cpu bound application
140 cpu-bound application from fully using its quota by that same amount. In these
|
| /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-coredump | 6 device is bound to a driver, which provides the .coredump()
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 102 with another driver bound the interface, eg. a power management
145 that isn't bound to your driver.
147 Probe will never be called for an interface bound to a driver.
151 Once your driver is bound to an interface, disconnect can be
|
| /Documentation/networking/ |
| 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 | 15 - KBD_UNBOUND_KEYCODE events are sent if the keycode is not bound to a keysym.
34 || !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
|
| /Documentation/core-api/ |
| D | workqueue.rst | 105 unless specifically overridden, a work item of a bound workqueue will
115 Each worker-pool bound to an actual CPU implements concurrency
137 mark a bound wq to ignore the concurrency management. Please refer to
169 worker-pools which host workers which are not bound to any
177 expected and using bound wq may end up creating large number
207 worker-pool from starting execution. This is useful for bound
232 Currently, for a bound wq, the maximum limit for ``@max_active`` is
262 Work items w0, w1, w2 are queued to a bound wq q0 on the same CPU.
351 cycles, using a bound wq is usually beneficial due to the increased
|
| 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/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/devicetree/bindings/input/ |
| D | adc-joystick.yaml | 47 Represents a joystick axis bound to the given ADC channel.
55 description: Index of an io-channels list entry bound to this axis.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | da9062.txt | 54 The DA9062 regulators are bound using their names listed below:
65 The DA9061 regulators are bound using their names listed below:
|
| /Documentation/timers/ |
| D | timers-howto.rst | 94 worst case, fire an interrupt for your upper bound.
98 be balanced with what is an acceptable upper bound on
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-bus-usb | 27 drivers may change this setting when they are bound.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | rockchip,iommu.txt | 5 its master device. Each slave device is bound to a single master device, and
|
| /Documentation/PCI/endpoint/ |
| D | pci-endpoint.rst | 172 * bind: ops to perform when a EPC device has been bound to EPF device
211 the function driver when the EPF device is bound to the EPC device.
225 pci_epf_bind() should be invoked when the EPF device has been bound to
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | overview.rst | 282 Each object in the DPRC is a Linux "device" and is bound to a driver.
284 scenario and the objects bound to each driver. A brief description
347 The DPRC driver is bound to DPRC objects and does runtime management
362 and those objects are bound to the allocator when the bus is probed.
368 The DPIO driver is bound to DPIO objects and provides services that allow
391 The Ethernet driver is bound to a DPNI and implements the kernel
|
| /Documentation/devicetree/bindings/thermal/ |
| D | db8500-thermal.txt | 14 - tripN-cdev-num : number of the cooling devices which can be bound to trip
|
1234567