Searched full:between (Results 1 – 25 of 1458) sorted by relevance
12345678910>>...59
/Documentation/netlink/specs/ |
D | devlink.yaml | 35 # TODO: fill in the attributes in between 42 # TODO: fill in the attributes in between 54 # TODO: fill in the attributes in between 61 # TODO: fill in the attributes in between 68 # TODO: fill in the attributes in between 75 # TODO: fill in the attributes in between 106 # TODO: fill in the attributes in between 113 # TODO: fill in the attributes in between 120 # TODO: fill in the attributes in between 131 # TODO: fill in the attributes in between [all …]
|
/Documentation/devicetree/bindings/spi/ |
D | cdns,qspi-nor-peripheral-props.yaml | 25 outputs are de-asserted between transactions. 29 Delay in nanoseconds between one chip select being de-activated 34 Delay in nanoseconds between last bit of current transaction and 39 Delay in nanoseconds between setting qspi_n_ss_out low and
|
/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-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-bus-iio-adc-max9611 | 13 between RS+ and RS- voltage sense inputs. In Ohms. 17 current flowing between RS+ and RS- inputs.
|
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 | 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/networking/devlink/ |
D | sfc.rst | 23 - For boards where the management function is split between multiple 27 - For boards where the management function is split between multiple 52 - Expansion ROM version. For boards where the expansion ROM is split between
|
/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/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/mm/ |
D | zsmalloc.rst | 59 the number of zspages with usage ratio between 10% and 20% 61 the number of zspages with usage ratio between 20% and 30% 63 the number of zspages with usage ratio between 30% and 40% 65 the number of zspages with usage ratio between 40% and 50% 67 the number of zspages with usage ratio between 50% and 60% 69 the number of zspages with usage ratio between 60% and 70% 71 the number of zspages with usage ratio between 70% and 80% 73 the number of zspages with usage ratio between 80% and 90% 75 the number of zspages with usage ratio between 90% and 99%
|
/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/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. 268 The distance, in surface units, between the contact and the surface. Zero 289 support is possible if the device can distinguish between the two axes, but 290 not (uniquely) any values in between. In such cases, the range of 301 the device cannot distinguish between the intended touch point and the 306 device cannot distinguish between the intended touch point and the tool 316 between different tool types, such as a finger or a pen. In such cases, the 356 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/arm/ |
D | arm,coresight-cti.yaml | 17 The CTI component properties define the connections between the individual 30 In general the connections between CTI and components via the trigger signals 35 between CTI and the CPU core and ETM if present. In the case of a v8 44 on the connections between the CTI and other components for correct operation. 48 between CTI and other CoreSight components. 50 Certain triggers between CoreSight devices and the CTI have specific types 109 propagated between sockets. 135 between this CTI and another hardware device. This device may be a CPU,
|
/Documentation/driver-api/pci/ |
D | p2pdma.rst | 8 between two devices on the bus. This type of transaction is henceforth 13 transactions between hierarchy domains, and in PCIe, each Root Port 21 between hierarchies. 40 * Orchestrator - A driver which orchestrates the flow of data between 43 In many cases there could be overlap between these three types (i.e.,
|
/Documentation/userspace-api/media/mediactl/ |
D | media-controller-intro.rst | 24 blocks are shared between different functions, creating dependencies 25 between seemingly unrelated devices.
|
/Documentation/driver-api/iio/ |
D | intro.rst | 10 or both. The aim is to fill the gap between the somewhat similar hwmon and 15 In some cases there is considerable overlap between these and IIO.
|
12345678910>>...59