Searched full:between (Results 1 – 25 of 1252) sorted by relevance
12345678910>>...51
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-adc-hi8435 | 23 The low voltage threshold range is between 2..21V.
24 Hysteresis between low and high thresholds can not be lower then 2 and
43 The high voltage threshold range is between 3..22V.
44 Hysteresis between low and high thresholds can not be lower then 2 and
|
| D | sysfs-class-backlight-adp5520 | 17 is an input code between 0 and 127, which is transformed to a
18 value between 0 mA and 30 mA using linear or non-linear
30 input code between 0 and 127, which is transformed to a value
31 between 0 mA and 30 mA using linear or non-linear algorithms.
|
| D | sysfs-class-backlight-adp8860 | 22 is an input code between 0 and 127, which is transformed to a
23 value between 0 mA and 30 mA using linear or non-linear
36 input code between 0 and 127, which is transformed to a value
37 between 0 mA and 30 mA using linear or non-linear algorithms.
|
| D | sysfs-class-led-driver-turris-omnia | 9 The microcontroller cycles between 8 levels of this global
11 integer value between 0 and 100. It is therefore convenient to be
|
| D | sysfs-firmware-opal-psr | 7 to shift/throttle power between different entities in
16 Power-Shift-Ratio between CPU and GPU for a given chip
|
| D | sysfs-bus-iio-adc-max9611 | 13 between RS+ and RS- voltage sense inputs. In Ohms.
17 current flowing between RS+ and RS- inputs.
|
| D | debugfs-hyperv | 13 Description: Fuzz testing buffer interrupt delay value between 0 - 1000
21 Description: Fuzz testing message delay value between 0 - 1000 microseconds
|
| D | sysfs-platform-hidma-mgmt | 62 Contains a value between 0 and 31. Maximum number of
75 of two and can be between 128 and 1024.
83 Contains a value between 0 and 31. Maximum number of
97 of two and can be between 128 and 1024.
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | fsl-mx25-tcq.txt | 16 between 1 and 4096. It is the ratio between the internal reference voltage
17 and the measured voltage after the plate was precharged. Resistance between
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-enable-high-lnb-voltage.rst | 13 FE_ENABLE_HIGH_LNB_VOLTAGE - Select output DC level between normal LNBf voltages or higher LNBf - v…
39 Select output DC level between normal LNBf voltages or higher LNBf
40 voltages between 0 (normal) or a value grater than 0 for higher
|
| /Documentation/devicetree/bindings/net/ |
| D | xilinx_gmii2rgmii.txt | 5 Independent Interface (RGMII) core provides the RGMII between RGMII-compliant
9 Speed of operation. This core can switch dynamically between the three
12 This converter sits between the ethernet MAC and the external phy.
|
| /Documentation/devicetree/bindings/dma/ |
| D | st,stm32-dma.yaml | 20 0x0: no address increment between transfers
21 0x1: increment address between transfers
23 0x0: no address increment between transfers
24 0x1: increment address between transfers
|
| /Documentation/devicetree/bindings/mtd/ |
| D | cadence-quadspi.txt | 29 mode chip select outputs are de-asserted between
31 - cdns,tsd2d-ns : Delay in nanoseconds between one chip select being
33 - cdns,tchsh-ns : Delay in nanoseconds between last bit of current
36 - cdns,tslch-ns : Delay in nanoseconds between setting qspi_n_ss_out low
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 96 Time between the end of one asynchronous memory
99 between a read followed by read or a write
103 Time between the beginning of a memory cycle
108 Time between the activation and deactivation of
113 Time between the deactivation of the read
120 Time between the beginning of a memory cycle
125 Time between the activation and deactivation of
130 Time between the deactivation of the write
|
| /Documentation/devicetree/bindings/ |
| D | graph.txt | 7 control flow to devices, but there can be more complex connections between
10 There already is a simple directed graph between devices tree nodes using
23 Here the ports describe data interfaces, and the links between them are
87 Links between endpoints
94 their 'remote-endpoint' phandles pointing at each other form a link between the
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | ti,bq24735.txt | 16 must be between 128mA and 8.128A with a 64mA step resolution. The POR value
20 must be between 1.024V and 19.2V with a 16mV step resolution. The POR value
24 value must be between 128mA and 8.064A with a 128mA step resolution. The
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | hsta.txt | 6 between the plb4 and plb6 system buses to provide high speed data
7 transfer between memory and system peripherals as well as support for
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | ciu2.txt | 13 the CIU and may have a value between 0 and 63. The second cell is
14 the bit within the bank and may also have a value between 0 and 63.
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-omap-dmtimer.txt | 11 - ti,prescaler: Should be a value between 0 and 7, see the timers datasheet
12 - ti,clock-source: Set dmtimer parent clock, values between 0 and 2:
|
| /Documentation/userspace-api/media/v4l/ |
| D | field-order.rst | 9 We have to distinguish between progressive and interlaced video.
13 odd and even field are transmitted, and due to a small delay between
23 object on screen may well move between one field and the next. For
29 combine to frames. We distinguish between top (aka odd) and bottom (aka
43 determined by the video standard. Hence the distinction between temporal
127 any dropped fields between them (fields can drop individually),
|
| /Documentation/firmware-guide/acpi/ |
| D | extcon-intel-int3496.rst | 12 between an USB host and an USB peripheral controller.
22 Index 2 The output gpio for muxing of the data pins between the USB host and
27 There is a mapping between indices and GPIO connection IDs as follows
|
| /Documentation/input/ |
| D | multi-touch-protocol.rst | 53 The main difference between the stateless type A protocol and the stateful
107 raw data for all present contacts are sent between every synchronization
189 indicate the distance between the contact and the surface.
264 The distance, in surface units, between the contact and the surface. Zero
285 support is possible if the device can distinguish between the two axis, but
286 not (uniquely) any values in between. In such cases, the range of
297 the device cannot distinguish between the intended touch point and the
302 device cannot distinguish between the intended touch point and the tool
312 between different tool types, such as a finger or a pen. In such cases, the
352 the device can distinguish between a finger along the Y axis (0) and a
[all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | baikal,bt1-axi.yaml | 18 another: from CPU to SoC peripherals and between some SoC peripherals
19 (mostly between peripheral devices and RAM, but also between DMA and
|
| /Documentation/devicetree/bindings/display/exynos/ |
| D | exynos_hdmi.txt | 29 e) mout_hdmi: It is required by the driver to switch between the 2
46 i) tmds_clko_user: MUX used to switch between oscclk and tmds_clko,
49 k) pixel_clko_user: MUX used to switch between oscclk and pixel_clko,
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 18 The CTI component properties define the connections between the individual
31 In general the connections between CTI and components via the trigger signals
36 between CTI and the CPU core and ETM if present. In the case of a v8
45 on the connections between the CTI and other components for correct operation.
49 between CTI and other CoreSight components.
51 Certain triggers between CoreSight devices and the CTI have specific types
107 propagated between sockets.
133 between this CTI and another hardware device. This device may be a CPU,
|
12345678910>>...51