Searched +full:in +full:- +full:between (Results 1 – 25 of 1018) sorted by relevance
12345678910>>...41
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | fsl-mx25-tcq.txt | 7 - compatible: Should be "fsl,imx25-tcq".
8 - reg: Memory range of the device.
9 - interrupts: Should be the interrupt number associated with this module within
11 - fsl,wires: Should be '<4>' or '<5>'
14 - fsl,pen-debounce-ns: Pen debounce time in nanoseconds.
15 - fsl,pen-threshold: Pen-down threshold for the touchscreen. This is a value
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
20 - fsl,settling-time-ns: Settling time in nanoseconds. The settling time is before
21 the actual touch detection to wait for an even charge distribution in the
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | cadence-quadspi.txt | 4 - compatible : should be one of the following:
5 Generic default - "cdns,qspi-nor".
6 For TI 66AK2G SoC - "ti,k2g-qspi", "cdns,qspi-nor".
7 For TI AM654 SoC - "ti,am654-ospi", "cdns,qspi-nor".
8 - reg : Contains two entries, each of which is a tuple consisting of a
12 - interrupts : Unit interrupt specifier for the controller interrupt.
13 - clocks : phandle to the Quad SPI clock.
14 - cdns,fifo-depth : Size of the data FIFO in words.
15 - cdns,fifo-width : Bus width of the data FIFO in bytes.
16 - cdns,trigger-address : 32-bit indirect AHB trigger address.
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | xilinx_gmii2rgmii.txt | 2 --------------------------------------------------------
5 Independent Interface (RGMII) core provides the RGMII between RGMII-compliant
7 This core can be used in all three modes of operation(10/100/1000 Mb/s).
9 Speed of operation. This core can switch dynamically between the three
12 This converter sits between the ethernet MAC and the external phy.
15 For more details about mdio please refer phy.txt file in the same directory.
18 - compatible : Should be "xlnx,gmii-to-rgmii-1.0"
19 - reg : The ID number for the phy, usually a small integer
20 - phy-handle : Should point to the external phy device.
21 See ethernet.txt file in the same directory.
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 4 provide a glue-less interface to a variety of asynchronous memory devices like
11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
17 - compatible: "ti,davinci-aemif"
18 "ti,keystone-aemif"
19 "ti,da850-aemif"
21 - reg: contains offset/length value for AEMIF control registers
24 - #address-cells: Must be 2. The partition number has to be encoded in the
25 first address cell and it may accept values 0..N-1
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | ti,bq24735.txt | 5 - compatible : "ti,bq24735"
8 - interrupts : Specify the interrupt to be used to trigger when the AC
9 adapter is either plugged in or removed.
10 - ti,ac-detect-gpios : This GPIO is optionally used to read the AC adapter
15 - ti,charge-current : Used to control and set the charging current. This value
16 must be between 128mA and 8.128A with a 64mA step resolution. The POR value
17 is 0x0000h. This number is in mA (e.g. 8192), see spec for more information
19 - ti,charge-voltage : Used to control and set the charging voltage. This value
20 must be between 1.024V and 19.2V with a 16mV step resolution. The POR value
21 is 0x0000h. This number is in mV (e.g. 19200), see spec for more information
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | graph.txt | 4 ---------------
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
12 can not be inferred from device tree parent-child relationships. The device
22 Documentation/devicetree/bindings/media/video-interfaces.txt.
23 Here the ports describe data interfaces, and the links between them are
28 -----------------------------------
30 Ports are described by child 'port' nodes contained in the device node.
34 If more than one port is present in a device node or there is more than one
36 hardware interface, a common scheme using '#address-cells', '#size-cells'
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | field-order.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _field-order:
9 We have to distinguish between progressive and interlaced video.
13 odd and even field are transmitted, and due to a small delay between
22 fields are in fact captured at two different instances in time. An
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
47 In V4L it is assumed that all video cameras transmit fields on the media
48 bus in the same order they were captured, so if the top field was
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-opal-psr | 3 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
4 Description: Power-Shift-Ratio directory for Powernv P9 servers
6 Power-Shift-Ratio allows to provide hints the firmware
7 to shift/throttle power between different entities in
8 the system. Each attribute in this directory indicates
13 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
16 Power-Shift-Ratio between CPU and GPU for a given chip
17 with chip-id X. This file gives the ratio (0-100)
18 which is used by OCC for power-capping.
|
| D | sysfs-bus-iio-adc-max9611 | 4 Contact: linux-iio@vger.kernel.org
6 common input voltage pin (RS+). In Ohms.
11 Contact: linux-iio@vger.kernel.org
13 between RS+ and RS- voltage sense inputs. In Ohms.
17 current flowing between RS+ and RS- inputs.
|
| D | debugfs-hyperv | 5 Description: Fuzz testing status of a vmbus device, whether its in an ON
13 Description: Fuzz testing buffer interrupt delay value between 0 - 1000
21 Description: Fuzz testing message delay value between 0 - 1000 microseconds
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/coresight-cti.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 to one or more CoreSight components and/or a CPU, with CTIs interconnected in
15 not part of the CoreSight graph described in the general CoreSight bindings
18 The CTI component properties define the connections between the individual
22 number is defined at design time, the maximum of each defined in the DEVID
25 CTIs are interconnected in a star topology via the CTM, using a number of
27 described in the DEVID register. The star topology is not required to be
[all …]
|
| /Documentation/input/ |
| D | multi-touch-protocol.rst | 4 Multi-touch (MT) Protocol
7 :Copyright: |copy| 2009-2010 Henrik Rydberg <rydberg@euromail.se>
11 ------------
13 In order to utilize the full power of the new multi-touch and multi-user
15 objects in direct contact with the device surface, is needed. This
16 document describes the multi-touch (MT) protocol which allows kernel
30 --------------
34 packet. Since these events are ignored by current single-touch (ST)
36 in an existing driver.
48 All drivers mark the end of a multi-touch transfer by calling the usual
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-enable-high-lnb-voltage.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 FE_ENABLE_HIGH_LNB_VOLTAGE - Select output DC level between normal LNBf voltages or higher LNBf - v…
31 - 0 - normal 13V and 18V.
33 - >0 - enables slightly higher voltages instead of 13/18V, in order
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
48 On error -1 is returned, and the ``errno`` variable is set
52 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PCI Peer-to-Peer DMA Support
8 between two devices on the bus. This type of transaction is henceforth
9 called Peer-to-Peer (or P2P). However, there are a number of issues that
10 make P2P transactions tricky to do in a perfectly safe way.
13 transactions between hierarchy domains, and in PCIe, each Root Port
18 same PCI bridge, as such devices are all in the same PCI hierarchy
21 between hierarchies.
23 The second issue is that to make use of existing interfaces in Linux,
33 In a given P2P implementation there may be three or more different
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | st,stm32-dma.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/st,stm32-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 DMA is a general-purpose direct memory access controller capable of
13 described in the dma.txt file, using a four-cell specifier for each
19 -bit 9: Peripheral Increment Address
20 0x0: no address increment between transfers
21 0x1: increment address between transfers
22 -bit 10: Memory Increment Address
[all …]
|
| /Documentation/powerpc/ |
| D | associativity.rst | 9 are represented as being members of a sub-grouping domain. This performance
10 characteristic is presented in terms of NUMA node distance within the Linux kernel.
17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property".
18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1.
20 bit 2 of byte 5 in the "ibm,architecture-vec-5" property is used.
23 ------
27 ------
28 With Form 1 a combination of ibm,associativity-reference-points, and ibm,associativity
29 device tree properties are used to determine the NUMA distance between resource groups/domains.
34 The “ibm,associativity-reference-points” property contains a list of one or more numbers
[all …]
|
| /Documentation/misc-devices/ |
| D | lis3lv02d.rst | 12 - Yan Burman <burman.yan@gmail.com>
13 - Eric Piel <eric.piel@tremplin-utc.net>
17 -----------
19 This driver provides support for the accelerometer found in various HP laptops
22 models (full list can be found in drivers/platform/x86/hp_accel.c) will have
31 - 3D position that the accelerometer reports. Format: "(x,y,z)"
33 - read reports the sampling rate of the accelerometer device in HZ.
37 - performs selftest for the chip as specified by chip manufacturer.
40 the laptop to act as a pinball machine-esque joystick. Joystick device can be
41 calibrated. Joystick device can be in two different modes.
[all …]
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | pwm-backlight.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/pwm-backlight.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: pwm-backlight bindings
10 - Lee Jones <lee.jones@linaro.org>
11 - Daniel Thompson <daniel.thompson@linaro.org>
12 - Jingoo Han <jingoohan1@gmail.com>
16 const: pwm-backlight
21 pwm-names: true
[all …]
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 2 -------------------------------------
8 Each video IP core is represented by an AMBA bus child node in the device
9 tree using bindings documented in this directory. Connections between the IP
10 cores are represented as defined in ../video-interfaces.txt.
12 The whole pipeline is represented by an AMBA bus child node in the device
13 tree using bindings documented in ./xlnx,video.txt.
16 -----------------
20 - xlnx,video-format: This property represents a video format transmitted on an
21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
23 core is described in the IP core bindings documentation.
[all …]
|
| /Documentation/hwmon/ |
| D | lm78.rst | 6 * National Semiconductor LM78 / LM78-J
10 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports)
20 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports)
28 - Frodo Looijaard <frodol@dds.nl>
29 - Jean Delvare <jdelvare@suse.de>
32 -----------
34 This driver implements support for the National Semiconductor LM78, LM78-J
37 There is almost no difference between the three supported chips. Functionally,
38 the LM78 and LM78-J are exactly identical. The LM79 has one more VID line,
45 Temperatures are measured in degrees Celsius. An alarm is triggered once
[all …]
|
| D | f71882fg.rst | 103 This is the 64-pin variant of the F71889FG, they have the
119 -----------
125 These chips also have fan controlling features, using either DC or PWM, in
133 ----------
136 interface as documented in sysfs-interface, without any exceptions.
140 -----------
142 Both PWM (pulse-width modulation) and DC fan speed control methods are
148 the border between the highest and one but highest temperature zones, and
149 vica versa. So the temperature zone trip points 1-4 (or 1-2) go from high temp
150 to low temp! This is how things are implemented in the IC, and the driver
[all …]
|
| D | gl518sm.rst | 21 - Frodo Looijaard <frodol@dds.nl>,
22 - Kyösti Mälkki <kmalkki@cc.hut.fi>
23 - Hong-Gunn Chew <hglinux@gunnet.org>
24 - Jean Delvare <jdelvare@suse.de>
27 -----------
43 Temperatures are measured in degrees Celsius. An alarm goes off while the
46 situation. Measurements are guaranteed between -10 degrees and +110
47 degrees, with a accuracy of +/-3 degrees.
49 Rotation speeds are reported in RPM (rotations per minute). An alarm is
50 triggered if the rotation speed has dropped below a programmable limit. In
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 test a single unit of code in isolation, hence the name. A unit test should be
15 paths to be tested in the code under test; this is only possible if the code
20 require installing the kernel on a test machine or in a VM and all require
21 tests to be written in userspace and run on the kernel under test; this is true
37 In short, this means that, yes, you can run KUnit on other architectures, but
40 For more information, see :ref:`kunit-on-non-uml`.
42 What is the difference between a unit test and these other kinds of tests?
45 test, or an end-to-end test.
47 - A unit test is supposed to test a single unit of code in isolation, hence the
[all …]
|
| /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
14 - compatible : "ibm,476gtr-hsta-msi", "ibm,hsta-msi"
15 - reg : register mapping for the HSTA MSI space
16 - interrupts : ordered interrupt mapping for each MSI in the register
|
| /Documentation/devicetree/bindings/leds/ |
| D | ams,as3645a.txt | 5 used in torch mode as well.
7 Ranges below noted as [a, b] are closed ranges between a and b, i.e. a
8 and b are included in the range.
10 Please also see common.txt in the same directory.
18 #address-cells : 1
19 #size-cells : 0
26 flash-timeout-us: Flash timeout in microseconds. The value must be in
28 flash-max-microamp: Maximum flash current in microamperes. Has to be
29 in the range between [200000, 500000] and
31 led-max-microamp: Maximum torch (assist) current in microamperes. The
[all …]
|
12345678910>>...41