Searched +full:sub +full:- +full:nodes (Results 1 – 25 of 639) sorted by relevance
12345678910>>...26
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | meson,pinctrl.txt | 4 - compatible: one of "amlogic,meson8-cbus-pinctrl"
5 "amlogic,meson8b-cbus-pinctrl"
6 "amlogic,meson8m2-cbus-pinctrl"
7 "amlogic,meson8-aobus-pinctrl"
8 "amlogic,meson8b-aobus-pinctrl"
9 "amlogic,meson8m2-aobus-pinctrl"
10 "amlogic,meson-gxbb-periphs-pinctrl"
11 "amlogic,meson-gxbb-aobus-pinctrl"
12 "amlogic,meson-gxl-periphs-pinctrl"
13 "amlogic,meson-gxl-aobus-pinctrl"
[all …]
|
| D | renesas,rza1-pinctrl.txt | 5 Pin multiplexing and GPIO configuration is performed on a per-pin basis
6 writing configuration values to per-port register sets.
12 -------------------
15 - compatible: should be:
16 - "renesas,r7s72100-ports": for RZ/A1H
17 - "renesas,r7s72101-ports", "renesas,r7s72100-ports": for RZ/A1M
18 - "renesas,r7s72102-ports": for RZ/A1L
20 - reg
27 pinctrl: pin-controller@fcfe3000 {
28 compatible = "renesas,r7s72100-ports";
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | meson,pinctrl.txt | 4 - compatible: one of "amlogic,meson8-cbus-pinctrl"
5 "amlogic,meson8b-cbus-pinctrl"
6 "amlogic,meson8m2-cbus-pinctrl"
7 "amlogic,meson8-aobus-pinctrl"
8 "amlogic,meson8b-aobus-pinctrl"
9 "amlogic,meson8m2-aobus-pinctrl"
10 "amlogic,meson-gxbb-periphs-pinctrl"
11 "amlogic,meson-gxbb-aobus-pinctrl"
12 "amlogic,meson-gxl-periphs-pinctrl"
13 "amlogic,meson-gxl-aobus-pinctrl"
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/ |
| D | marvell-pxa168.txt | 4 - compatible: should be "marvell,pxa168-eth".
5 - reg: address and length of the register set for the device.
6 - interrupts: interrupt for the device.
7 - clocks: pointer to the clock for the device.
10 - port-id: Ethernet port number. Should be '0','1' or '2'.
11 - #address-cells: must be 1 when using sub-nodes.
12 - #size-cells: must be 0 when using sub-nodes.
13 - phy-handle: see ethernet.txt file in the same directory.
14 - local-mac-address: see ethernet.txt file in the same directory.
16 Sub-nodes:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | marvell-pxa168.txt | 4 - compatible: should be "marvell,pxa168-eth".
5 - reg: address and length of the register set for the device.
6 - interrupts: interrupt for the device.
7 - clocks: pointer to the clock for the device.
10 - port-id: Ethernet port number. Should be '0','1' or '2'.
11 - #address-cells: must be 1 when using sub-nodes.
12 - #size-cells: must be 0 when using sub-nodes.
13 - phy-handle: see ethernet.txt file in the same directory.
18 Sub-nodes:
19 Each PHY can be represented as a sub-node. This is not mandatory.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/kapi/ |
| D | v4l2-intro.rst | 2 ------------
5 hardware: most devices have multiple ICs, export multiple device nodes in
6 /dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
13 called 'sub-devices'.
16 creating V4L device nodes and video_buf for handling the video buffers
20 connecting to sub-devices themselves. Some of this is quite complicated
30 A good example to look at as a reference is the v4l2-pci-skeleton.c
36 -------------------------
42 2) A way of initializing and commanding sub-devices (if any).
44 3) Creating V4L2 device nodes (/dev/videoX, /dev/vbiX and /dev/radioX)
[all …]
|
| D | v4l2-subdev.rst | 1 V4L2 sub-devices
2 ----------------
4 Many drivers need to communicate with sub-devices. These devices can do all
6 encoding or decoding. For webcams common sub-devices are sensors and camera
10 driver with a consistent interface to these sub-devices the
11 :c:type:`v4l2_subdev` struct (v4l2-subdev.h) was created.
13 Each sub-device driver must have a :c:type:`v4l2_subdev` struct. This struct
14 can be stand-alone for simple sub-devices or it might be embedded in a larger
16 low-level device struct (e.g. ``i2c_client``) that contains the device data as
19 it easy to go from a :c:type:`v4l2_subdev` to the actual low-level bus-specific
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------
7 hardware: most devices have multiple ICs, export multiple device nodes in
8 /dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
15 called 'sub-devices'.
18 creating V4L device nodes and video_buf for handling the video buffers
22 connecting to sub-devices themselves. Some of this is quite complicated
32 A good example to look at as a reference is the v4l2-pci-skeleton.c
38 -------------------------
44 2) A way of initializing and commanding sub-devices (if any).
[all …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | open.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
18 The bridge driver exposes one or more V4L2 device nodes
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**
33 devices. The devices that are fully controlled via V4L2 device nodes
34 are called **video-node-centric**.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 3 The Freescale Management Complex (fsl-mc) is a hardware resource
5 network-oriented packet processing applications. After the fsl-mc
14 - compatible
16 Definition: Must be "fsl,qoriq-mc". A Freescale Management Complex
21 - reg
22 Value type: <prop-encoded-array>
26 -the first region is the command portal for the
29 -the second region is the MC control registers. This
33 - msi-parent
38 - ranges
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/ata/ |
| D | ahci-platform.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
6 It is possible, but not required, to represent each port as a sub-node.
11 - compatible : compatible string, one of:
12 - "allwinner,sun4i-a10-ahci"
13 - "brcm,iproc-ahci"
14 - "hisilicon,hisi-ahci"
15 - "cavium,octeon-7130-ahci"
16 - "ibm,476gtr-ahci"
17 - "marvell,armada-380-ahci"
18 - "marvell,armada-3700-ahci"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ata/ |
| D | ahci-platform.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
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"
18 - "snps,dwc-ahci"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | phy-stm32-usbphyc.txt | 14 |_ PHY port#2 ----| |________________
23 - compatible: must be "st,stm32mp1-usbphyc"
24 - reg: address and length of the usb phy control register set
25 - clocks: phandle + clock specifier for the PLL phy clock
26 - #address-cells: number of address cells for phys sub-nodes, must be <1>
27 - #size-cells: number of size cells for phys sub-nodes, must be <0>
30 - assigned-clocks: phandle + clock specifier for the PLL phy clock
31 - assigned-clock-parents: the PLL phy clock parent
32 - resets: phandle + reset specifier
34 Required nodes: one sub-node per port the controller provides.
[all …]
|
| D | brcm-sata-phy.txt | 4 - compatible: should be one or more of
5 "brcm,bcm7216-sata-phy"
6 "brcm,bcm7425-sata-phy"
7 "brcm,bcm7445-sata-phy"
8 "brcm,iproc-ns2-sata-phy"
9 "brcm,iproc-nsp-sata-phy"
10 "brcm,phy-sata3"
11 "brcm,iproc-sr-sata-phy"
12 "brcm,bcm63138-sata-phy"
13 - address-cells: should be 1
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/phy/ |
| D | phy-stm32-usbphyc.txt | 14 |_ PHY port#2 ----| |________________
23 - compatible: must be "st,stm32mp1-usbphyc"
24 - reg: address and length of the usb phy control register set
25 - clocks: phandle + clock specifier for the PLL phy clock
26 - #address-cells: number of address cells for phys sub-nodes, must be <1>
27 - #size-cells: number of size cells for phys sub-nodes, must be <0>
30 - assigned-clocks: phandle + clock specifier for the PLL phy clock
31 - assigned-clock-parents: the PLL phy clock parent
32 - resets: phandle + reset specifier
34 Required nodes: one sub-node per port the controller provides.
[all …]
|
| D | brcm-sata-phy.txt | 4 - compatible: should be one or more of
5 "brcm,bcm7425-sata-phy"
6 "brcm,bcm7445-sata-phy"
7 "brcm,iproc-ns2-sata-phy"
8 "brcm,iproc-nsp-sata-phy"
9 "brcm,phy-sata3"
10 "brcm,iproc-sr-sata-phy"
11 - address-cells: should be 1
12 - size-cells: should be 0
13 - reg: register ranges for the PHY PCB interface
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | mv-xor.txt | 4 - compatible: Should be one of the following:
5 - "marvell,orion-xor"
6 - "marvell,armada-380-xor"
7 - "marvell,armada-3700-xor".
8 - reg: Should contain registers location and length (two sets)
11 - clocks: pointer to the reference clock
13 The DT node must also contains sub-nodes for each XOR channel that the
14 XOR engine has. Those sub-nodes have the following required
16 - interrupts: interrupt of the XOR channel
18 The sub-nodes used to contain one or several of the following
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/dma/ |
| D | mv-xor.txt | 4 - compatible: Should be one of the following:
5 - "marvell,orion-xor"
6 - "marvell,armada-380-xor"
7 - "marvell,armada-3700-xor".
8 - reg: Should contain registers location and length (two sets)
11 - clocks: pointer to the reference clock
13 The DT node must also contains sub-nodes for each XOR channel that the
14 XOR engine has. Those sub-nodes have the following required
16 - interrupts: interrupt of the XOR channel
18 The sub-nodes used to contain one or several of the following
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-dsp-rproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-dsp-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The TI K3 family of SoCs usually have one or more TI DSP Core sub-systems
14 that are used to offload some of the processor-intensive tasks or algorithms,
17 These processor sub-systems usually contain additional sub-modules like
23 Each DSP Core sub-system is represented as a single DT node. Each node has a
29 - $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml#
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | ralink,rt3883-pci.txt | 7 - compatible: must be "ralink,rt3883-pci"
9 - reg: specifies the physical base address of the controller and
12 - #address-cells: specifies the number of cells needed to encode an
15 - #size-cells: specifies the number of cells used to represent the size
18 - ranges: specifies the translation between child address space and parent
23 - status: indicates the operational status of the device.
26 2) Child nodes
28 The main node must have two child nodes which describes the built-in
35 - interrupt-controller: identifies the node as an interrupt controller
37 - #address-cells: specifies the number of cells needed to encode an
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pci/ |
| D | ralink,rt3883-pci.txt | 7 - compatible: must be "ralink,rt3883-pci"
9 - reg: specifies the physical base address of the controller and
12 - #address-cells: specifies the number of cells needed to encode an
15 - #size-cells: specifies the number of cells used to represent the size
18 - ranges: specifies the translation between child address space and parent
23 - status: indicates the operational status of the device.
26 2) Child nodes
28 The main node must have two child nodes which describes the built-in
35 - interrupt-controller: identifies the node as an interrupt controller
37 - #address-cells: specifies the number of cells needed to encode an
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/media/v4l-drivers/ |
| D | fimc.rst | 6 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
15 drivers/media/platform/exynos4-is directory.
18 --------------
20 S5PC100 (mem-to-mem only), S5PV210, EXYNOS4210
23 ------------------
25 - camera parallel interface capture (ITU-R.BT601/565);
26 - camera serial interface capture (MIPI-CSI2);
27 - memory-to-memory processing (color space conversion, scaling, mirror
29 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
30 instance to any parallel video input or any MIPI-CSI front-end);
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/media/ |
| D | rcar_vin.txt | 1 Renesas R-Car Video Input driver (rcar_vin)
2 -------------------------------------------
4 The rcar_vin device provides video input capabilities for the Renesas R-Car
10 on Gen3 platforms to a CSI-2 receiver.
12 - compatible: Must be one or more of the following
13 - "renesas,vin-r8a7743" for the R8A7743 device
14 - "renesas,vin-r8a7745" for the R8A7745 device
15 - "renesas,vin-r8a7778" for the R8A7778 device
16 - "renesas,vin-r8a7779" for the R8A7779 device
17 - "renesas,vin-r8a7790" for the R8A7790 device
[all …]
|
12345678910>>...26