Searched full:respective (Results 1 – 25 of 227) sorted by relevance
12345678910
| /Documentation/ABI/testing/ |
| D | sysfs-bus-counter | 28 Discrete set of available values for the respective device
48 respective counter.
55 respective counter.
155 Discrete set of available values for the respective Count Y
169 phase of the respective A and B quadrature encoding signals.
208 Rising edges on signal A updates the respective count.
213 signal A updates the respective count; if the direction
215 updates the respective count. Quadrature encoding
220 signal B updates the respective count; if the direction
222 updates the respective count. Quadrature encoding
[all …]
|
| /Documentation/driver-api/ |
| D | generic-counter.rst | 59 data affects respective Count data, and the Synapse represents this
63 triggers the respective Count's count function evaluation to update the
82 input signals as defined by the respective count functions. Within the
84 each associated with a set of Signals, whose respective Synapse
107 Rising edges on signal A updates the respective count. The input level
116 updates the respective count; if the direction is backward, falling
117 edges on quadrature pair signal A updates the respective count.
122 updates the respective count; if the direction is backward, falling
123 edges on quadrature pair signal B updates the respective count.
128 respective count. Quadrature encoding determines the direction.
[all …]
|
| /Documentation/devicetree/bindings/soundwire/ |
| D | qcom,soundwire.yaml | 81 or applicable for the respective data port.
92 or applicable for the respective data port.
103 or applicable for the respective data port.
114 or applicable for the respective data port.
125 or applicable for the respective data port.
136 or applicable for the respective data port.
149 or applicable for the respective data port.
166 or applicable for the respective data port.
183 or applicable for the respective data port.
199 or applicable for the respective data port.
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rt6245-regulator.yaml | 38 Over current level selection. Each respective value means the current
46 Over temperature level selection. Each respective value means the degree
54 Power good signal delay time selection. Each respective value means the
63 Buck switch frequency selection. Each respective value means 400KHz,
|
| /Documentation/hwmon/ |
| D | gxp-fan-ctrl.rst | 25 pwm[0-7] Fan 0 to 7 respective PWM value (0-255)
26 fan[0-7]_fault Fan 0 to 7 respective fault status: 1 fail, 0 ok
27 fan[0-7]_enable Fan 0 to 7 respective enabled status: 1 enabled, 0 disabled
|
| D | ina3221.rst | 36 corresponding alarm when the respective current
40 corresponding alarm when the respective current
51 when the respective current is above this value
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-firewire | 34 u24 of the respective unit directory entries.
90 Contents of a respective textual descriptor leaf.
96 Contents of a respective textual descriptor leaf.
107 Contents of a respective textual descriptor leaf.
|
| /Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 18 64-bit qword is the soft-dirty one. If set, the respective PTE was
25 the soft-dirty bit on the respective PTE.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | max77620.txt | 68 regulators, GPIOs and 32kHz clocks are provided in their respective
69 configuration nodes which is explained in respective sub-system DT
129 regulator, power, please refer respective device-tree binding document
130 under their respective sub-system directories.
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-kovaplus | 68 When written, this file lets one write the respective profile
83 When read, these files return the respective profile buttons.
96 When written, this file lets one write the respective profile
112 When read, these files return the respective profile settings.
|
| D | sysfs-driver-hid-roccat-pyra | 57 When written, this file lets one write the respective profile
72 When read, these files return the respective profile buttons.
85 When written, this file lets one write the respective profile
101 When read, these files return the respective profile settings.
|
| D | sysfs-driver-hid-roccat-koneplus | 61 When written, this file lets one write the respective profile
76 When read, these files return the respective profile buttons.
89 When written, this file lets one write the respective profile
105 When read, these files return the respective profile settings.
|
| D | sysfs-driver-hid-roccat-savu | 8 respective profile buttons to the mouse. The data has to be
32 When written, this file lets one write the respective profile
|
| /Documentation/devicetree/bindings/usb/ |
| D | isp1301.txt | 9 ISP1301 instance associated with the respective USB driver
|
| /Documentation/userspace-api/media/v4l/ |
| D | tuner.rst | 16 field of the respective struct :c:type:`v4l2_input`
48 modulator. The ``type`` field of the respective struct
|
| D | vidioc-g-fmt.rst | 46 struct :c:type:`v4l2_format` to the respective buffer (stream)
51 the respective member of the ``fmt`` union. In case of video capture
59 ``type`` field and all fields of the respective ``fmt`` union member.
|
| D | querycap.rst | 26 Other features can be queried by calling the respective ioctl, for
|
| /Documentation/devicetree/bindings/media/ |
| D | mediatek,mt8195-jpegenc.yaml | 25 Points to the respective IOMMU block with master port as argument, see
56 List of the hardware port in respective IOMMU block for current Socs.
|
| D | mediatek,mt8195-jpegdec.yaml | 25 Points to the respective IOMMU block with master port as argument, see
56 List of the hardware port in respective IOMMU block for current Socs.
|
| /Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | fsl,imx-weim-peripherals.yaml | 18 supported by the respective device.
|
| /Documentation/devicetree/bindings/hwinfo/ |
| D | samsung,exynos-chipid.yaml | 36 to determine the ASV bin of an SoC if respective information
|
| /Documentation/devicetree/bindings/i2c/ |
| D | hpe,gxp-i2c.yaml | 35 registers represent the respective bit position.
|
| /Documentation/gpu/ |
| D | drm-usage-stats.rst | 50 String shall contain the name this driver registered as via the respective
85 Value shall be in specified time units which the respective GPU engine spent
150 objects belong to this client, in the respective memory region.
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-tegra194-p2u.yaml | 29 description: Should be the physical address space and length of respective each P2U instance.
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 157 respective packets based on the packet type (major) and number of tries
223 packets, started when the respective packet begins (re-)transmission (i.e.
251 collections may only be accessed and modified under the respective lock. If
274 Some packet fields may be read outside of the respective locks guarding
413 indicates a response to a request, the respective request is looked up in
443 and modified under the respective lock.
450 Some request fields may be read outside of the respective locks guarding
490 registry and event ID, are required to uniquely identify a respective class
541 transport layer), it will be put on its respective event queue
|
12345678910