Searched +full:sub +full:- +full:node (Results 1 – 25 of 303) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/regulator/ |
| D | isl9305.txt | 5 - compatible: "isil,isl9305" or "isil,isl9305h"
6 - reg: I2C slave address, usually 0x68.
7 - regulators: A node that houses a sub-node for each regulator within the
8 device. Each sub-node is identified using the node's name, with valid
9 values being "dcd1", "dcd2", "ldo1" and "ldo2". The content of each sub-node
11 - VINDCD1-supply: A phandle to a regulator node supplying VINDCD1.
12 VINDCD2-supply: A phandle to a regulator node supplying VINDCD2.
13 VINLDO1-supply: A phandle to a regulator node supplying VINLDO1.
14 VINLDO2-supply: A phandle to a regulator node supplying VINLDO2.
17 - Per-regulator optional properties are defined in regulator.txt
[all …]
|
| D | tps65132-regulator.txt | 4 - compatible: "ti,tps65132"
5 - reg: I2C slave address
8 Device supports two regulators OUTP and OUTN. A sub node within the
9 device node describe the properties of these regulators. The sub-node
11 -For regulator outp, the sub node name should be "outp".
12 -For regulator outn, the sub node name should be "outn".
14 -enable-gpios:(active high, output) Regulators are controlled by the input pins.
17 -active-discharge-gpios: (active high, output) Some configurations use delay mechanisms
20 the delay mechanism. Requires specification of ti,active-discharge-time-us
21 -ti,active-discharge-time-us: how long the active discharge gpio should be
[all …]
|
| D | 88pm800.txt | 4 - compatible: "marvell,88pm800"
5 - reg: I2C slave address
6 - regulators: A node that houses a sub-node for each regulator within the
7 device. Each sub-node is identified using the node's name (or the deprecated
8 regulator-compatible property if present), with valid values listed below.
9 The content of each sub-node is defined by the standard binding for
25 regulator-min-microvolt = <600000>;
26 regulator-max-microvolt = <3950000>;
27 regulator-boot-on;
28 regulator-always-on;
[all …]
|
| D | pv88090.txt | 4 - compatible: "pvs,pv88090".
5 - reg: I2C slave address, usually 0x48.
6 - interrupts: the interrupt outputs of the controller
7 - regulators: A node that houses a sub-node for each regulator within the
8 device. Each sub-node is identified using the node's name, with valid
9 values listed below. The content of each sub-node is defined by the
14 - Any optional property defined in regulator.txt
21 interrupt-parent = <&gpio>;
26 regulator-name = "buck1";
27 regulator-min-microvolt = < 600000>;
[all …]
|
| D | pv88080.txt | 4 - compatible: Must be one of the following, depending on the
6 - "pvs,pv88080" (DEPRECATED)
8 - "pvs,pv88080-aa" for PV88080 AA or AB silicon
9 - "pvs,pv88080-ba" for PV88080 BA or BB silicon
11 - reg: I2C slave address, usually 0x49
12 - interrupts: the interrupt outputs of the controller
13 - regulators: A node that houses a sub-node for each regulator within the
14 device. Each sub-node is identified using the node's name, with valid
15 values listed below. The content of each sub-node is defined by the
20 - Any optional property defined in regulator.txt
[all …]
|
| D | 88pm860x.txt | 4 - compatible: "marvell,88pm860x"
5 - reg: I2C slave address
6 - regulators: A node that houses a sub-node for each regulator within the
7 device. Each sub-node is identified using the regulator-compatible
18 regulator-min-microvolt = <1000000>;
19 regulator-max-microvolt = <1500000>;
20 regulator-boot-on;
21 regulator-always-on;
24 regulator-min-microvolt = <1000000>;
25 regulator-max-microvolt = <3000000>;
[all …]
|
| D | max8907.txt | 4 - compatible: "maxim,max8907"
5 - reg: I2C slave address
6 - interrupts: The interrupt output of the controller
7 - mbatt-supply: The input supply for MBATT, BBAT, SDBY, VRTC.
8 - in-v1-supply: The input supply for SD1.
9 - in-v2-supply: The input supply for SD2.
10 - in-v3-supply: The input supply for SD3.
11 - in1-supply: The input supply for LDO1.
13 - in20-supply: The input supply for LDO20.
14 - regulators: A node that houses a sub-node for each regulator within the
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | adi,axi-dmac.txt | 1 Analog Devices AXI-DMAC DMA controller
4 - compatible: Must be "adi,axi-dmac-1.00.a".
5 - reg: Specification for the controllers memory mapped register map.
6 - interrupts: Specification for the controllers interrupt.
7 - clocks: Phandle and specifier to the controllers AXI interface clock
8 - #dma-cells: Must be 1.
10 Required sub-nodes:
11 - adi,channels: This sub-node must contain a sub-node for each DMA channel. For
12 the channel sub-nodes the following bindings apply. They must match the
15 Required properties for adi,channels sub-node:
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,stm32-sai.txt | 4 as I2S standards, LSB or MSB-justified, PCM/DSP, TDM, and AC'97.
5 The SAI contains two independent audio sub-blocks. Each sub-block has
9 - compatible: Should be "st,stm32f4-sai" or "st,stm32h7-sai"
10 - reg: Base address and size of SAI common register set.
11 - clocks: Must contain phandle and clock specifier pairs for each entry
12 in clock-names.
13 - clock-names: Must contain "pclk" "x8k" and "x11k"
15 Mandatory for "st,stm32h7-sai" compatible.
16 Not used for "st,stm32f4-sai" compatible.
19 - interrupts: cpu DAI interrupt line shared by SAI sub-blocks
[all …]
|
| D | cs35l35.txt | 5 - compatible : "cirrus,cs35l35"
7 - reg : the I2C address of the device for I2C
9 - VA-supply, VP-supply : power supplies for the device,
13 - interrupts : IRQ line info CS35L35.
14 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
17 - cirrus,boost-ind-nanohenry: Inductor value for boost converter. The value is
21 - reset-gpios : gpio used to reset the amplifier
23 - cirrus,stereo-config : Boolean to determine if there are 2 AMPs for a
26 - cirrus,audio-channel : Set Location of Audio Signal on Serial Port
30 - cirrus,advisory-channel : Set Location of Advisory Signal on Serial Port
[all …]
|
| D | qcom,sdm845.txt | 5 - compatible:
9 "qcom,sdm845-sndcard"
10 "qcom,db845c-sndcard"
11 "lenovo,yoga-c630-sndcard"
13 - audio-routing:
22 - model:
25 Definition: The user-visible name of this sound card.
27 - aux-devs
33 using "audio-routing".
39 - link-name:
[all …]
|
| /Documentation/admin-guide/media/ |
| D | fimc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
[all …]
|
| D | ti,davinci-rproc.txt | 4 Binding status: Unstable - Subject to changes for DT representation of clocks
7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
8 is used to offload some of the processor-intensive tasks or algorithms, for
11 The processor cores in the sub-system usually contain additional sub-modules
16 DSP Device Node:
18 Each DSP Core sub-system is represented as a single DT node.
21 --------------------
24 - compatible: Should be one of the following,
25 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
27 - reg: Should contain an entry for each value in 'reg-names'.
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-cadence-sierra.txt | 2 -----------------------
5 - compatible: Must be "cdns,sierra-phy-t0" for Sierra in Cadence platform
6 Must be "ti,sierra-phy-t0" for Sierra in TI's J721E SoC.
7 - resets: Must contain an entry for each in reset-names.
9 - reset-names: Must include "sierra_reset" and "sierra_apb".
13 - reg: register range for the PHY.
14 - #address-cells: Must be 1
15 - #size-cells: Must be 0
18 - clocks: Must contain an entry in clock-names.
19 See ../clocks/clock-bindings.txt for details.
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | raideng.txt | 3 RAID Engine nodes are defined to describe on-chip RAID accelerators. Each RAID
4 Engine should have a separate node.
11 - compatible: Should contain "fsl,raideng-v1.0" as the value
15 - reg: offset and length of the register set for the device
16 - ranges: standard ranges property specifying the translation
22 compatible = "fsl,raideng-v1.0";
23 #address-cells = <1>;
24 #size-cells = <1>;
30 There must be a sub-node for each job queue present in RAID Engine
31 This node must be a sub-node of the main RAID Engine node
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-ns2.txt | 1 Binding for dual-GPIO LED found on Network Space v2 (and parents).
4 - compatible: "lacie,ns2-leds".
6 Each LED is represented as a sub-node of the ns2-leds device.
8 Required sub-node properties:
9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.
11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and
12 the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations
15 Optional sub-node properties:
16 - label: Name for this LED. If omitted, the label is taken from the node name.
[all …]
|
| D | leds-an30259a.txt | 1 * Panasonic AN30259A 3-channel LED driver
7 - compatible: Must be "panasonic,an30259a".
8 - reg: I2C slave address.
9 - #address-cells: Must be 1.
10 - #size-cells: Must be 0.
12 Each LED is represented as a sub-node of the panasonic,an30259a node.
14 Required sub-node properties:
15 - reg: Pin that the LED is connected to. Must be 1, 2, or 3.
17 Optional sub-node properties:
18 - function :
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ltc2978.txt | 4 - compatible: should contain one of:
29 - reg: I2C slave address
32 - regulators: A node that houses a sub-node for each regulator controlled by
33 the device. Each sub-node is identified using the node's name, with valid
34 values listed below. The content of each sub-node is defined by the
38 * ltc2972 vout0 - vout1
39 * ltc2974, ltc2975 : vout0 - vout3
40 * ltc2977, ltc2979, ltc2980, ltm2987 : vout0 - vout7
41 * ltc2978 : vout0 - vout7
42 * ltc3880, ltc3882, ltc3884, ltc3886, ltc3887, ltc3889 : vout0 - vout1
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 25 routed to different processor sub-systems on DRA7xx as they are routed through
32 Mailbox Device Node:
34 A Mailbox device node is used to represent a Mailbox IP instance/cluster within
35 a SoC. The sub-mailboxes are represented as child nodes of this parent node.
38 --------------------
39 - compatible: Should be one of the following,
40 "ti,omap2-mailbox" for OMAP2420, OMAP2430 SoCs
41 "ti,omap3-mailbox" for OMAP3430, OMAP3630 SoCs
42 "ti,omap4-mailbox" for OMAP44xx, OMAP54xx, AM33xx,
44 "ti,am654-mailbox" for K3 AM65x and J721E SoCs
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | tps6105x.txt | 3 The TP61050/TPS61052 is a high-power "white LED driver". The
7 - compatible: "ti,tps61050" or "ti,tps61052"
8 - reg: Specifies the I2C slave address
10 Optional sub-node:
15 - regulator: presence of this sub-node puts the chip in regulator mode.
18 - led: presence of this sub-node puts the chip in led mode.
20 - function : see ../leds/common.txt
21 - color : see ../leds/common.txt
22 - label : see ../leds/common.txt
42 regulator-min-microvolt = <5000000>;
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | open.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
34 are called **video-node-centric**.
36 Userspace can check if a V4L2 hardware peripheral is MC-centric by
38 :ref:`device_caps field <device-capabilities>`.
[all …]
|
| /Documentation/devicetree/bindings/ata/ |
| D | ahci-platform.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
4 Each SATA controller should have its own node.
6 It is possible, but not required, to represent each port as a sub-node.
11 - compatible : compatible string, one of:
12 - "brcm,iproc-ahci"
13 - "hisilicon,hisi-ahci"
14 - "cavium,octeon-7130-ahci"
15 - "ibm,476gtr-ahci"
16 - "marvell,armada-380-ahci"
17 - "marvell,armada-3700-ahci"
[all …]
|
| /Documentation/userspace-api/media/ |
| D | glossary.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
32 Device Node
33 A character device node in the file system used to control and
51 **Field-programmable Gate Array**
56 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
65 together make a larger user-facing functional peripheral. For
73 **Inter-Integrated Circuit**
75 A multi-master, multi-slave, packet switched, single-ended,
77 like sub-device hardware components.
79 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
[all …]
|
| /Documentation/driver-api/media/ |
| D | v4l2-subdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 V4L2 sub-devices
4 ----------------
6 Many drivers need to communicate with sub-devices. These devices can do all
8 encoding or decoding. For webcams common sub-devices are sensors and camera
12 driver with a consistent interface to these sub-devices the
13 :c:type:`v4l2_subdev` struct (v4l2-subdev.h) was created.
15 Each sub-device driver must have a :c:type:`v4l2_subdev` struct. This struct
16 can be stand-alone for simple sub-devices or it might be embedded in a larger
18 low-level device struct (e.g. ``i2c_client``) that contains the device data as
[all …]
|
12345678910>>...13