Searched +full:sub +full:- +full:nodes (Results 1 – 25 of 371) sorted by relevance
12345678910>>...15
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
D | dev-subdev.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 6 Sub-device Interface 13 components as software blocks called sub-devices. 15 V4L2 sub-devices are usually kernel-only objects. If the V4L2 driver 17 media entities. Applications will be able to enumerate the sub-devices 21 In addition to make sub-devices discoverable, drivers can also choose to 23 sub-device driver and the V4L2 device driver support this, sub-devices 26 - query, read and write sub-devices controls 28 - subscribe and unsubscribe to events and retrieve them 30 - negotiate image formats on individual pads [all …]
|
/linux-6.12.1/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 …]
|
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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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/samsung/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 …]
|
/linux-6.12.1/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 31 - ti,am62a-c7xv-dsp [all …]
|
D | ti,k3-r5f-rproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-r5f-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 dual-core Arm Cortex R5F 20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode 21 called "Single-CPU" mode, where only Core0 is used, but with ability to use 27 Each Dual-Core R5F sub-system is represented as a single DTS node 28 representing the cluster, with a pair of child DT nodes representing [all …]
|
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 …]
|
/linux-6.12.1/Documentation/devicetree/bindings/pinctrl/ |
D | canaan,k210-fpioa.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/canaan,k210-fpioa.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Damien Le Moal <dlemoal@kernel.org> 16 a per-pin basis. 20 const: canaan,k210-fpioa 29 - description: Controller reference clock source 30 - description: APB interface clock source 32 clock-names: [all …]
|
D | img,pistachio-pinctrl.txt | 8 each. The GPIO banks are represented as sub-nodes of the pad controller node. 10 Please refer to pinctrl-bindings.txt, ../gpio/gpio.txt, and 11 ../interrupt-controller/interrupts.txt for generic information regarding 15 -------------------------------------------- 16 - compatible: "img,pistachio-system-pinctrl". 17 - reg: Address range of the pinctrl registers. 19 Required properties for GPIO bank sub-nodes: 20 -------------------------------------------- 21 - interrupts: Interrupt line for the GPIO bank. 22 - gpio-controller: Indicates the device is a GPIO controller. [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/bus/ |
D | omap-ocp2scp.txt | 1 * OMAP OCP2SCP - ocp interface to scp interface 4 - compatible : Should be "ti,am437x-ocp2scp" for AM437x processor 5 Should be "ti,omap-ocp2scp" for all others 6 - reg : Address and length of the register set for the device 7 - #address-cells, #size-cells : Must be present if the device has sub-nodes 8 - ranges : the child address space are mapped 1:1 onto the parent address space 9 - ti,hwmods : must be "ocp2scp_usb_phy" 11 Sub-nodes: 12 All the devices connected to ocp2scp are described using sub-node to ocp2scp 15 compatible = "ti,omap-ocp2scp"; [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/opp/ |
D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Viresh Kumar <viresh.kumar@linaro.org> 13 Devices work at voltage-current-frequency combinations and some implementations 25 pattern: '^opp-table(-[a-z0-9]+)?$' 27 opp-shared: 29 Indicates that device nodes using this OPP Table Node's phandle switch 36 '^opp(-?[0-9]+)*$': [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/phy/ |
D | berlin-sata-phy.txt | 2 --------------- 5 - compatible: should be one of 6 "marvell,berlin2-sata-phy" 7 "marvell,berlin2q-sata-phy" 8 - address-cells: should be 1 9 - size-cells: should be 0 10 - phy-cells: from the generic PHY bindings, must be 1 11 - reg: address and length of the register 12 - clocks: reference to the clock entry 14 Sub-nodes: [all …]
|
D | phy-miphy365x.txt | 8 - compatible : Should be "st,miphy365x-phy" 9 - st,syscfg : Phandle / integer array property. Phandle of sysconfig group 11 an entry for each port sub-node, specifying the control 14 Required nodes : A sub-node is required for each channel the controller 16 'reg' and 'reg-names' properties are used inside these 17 nodes to describe the controller's topology. These nodes 21 - #phy-cells : Should be 1 (See second example) 23 - PHY_TYPE_SATA 24 - PHY_TYPE_PCI 25 - reg : Address and length of register sets for each device in [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/mailbox/ |
D | ti,omap-mailbox.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Suman Anna <s-anna@ti.com> 35 lines can also be routed to different processor sub-systems on DRA7xx as they 46 Mailbox Controller Nodes 49 within a SoC. The sub-mailboxes (actual communication channels) are 50 represented as child nodes of this parent node. 56 "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/mtd/ |
D | samsung-s3c2410.txt | 4 - compatible : The possible values are: 5 "samsung,s3c2410-nand" 6 "samsung,s3c2412-nand" 7 "samsung,s3c2440-nand" 8 - reg : register's location and length. 9 - #address-cells, #size-cells : see nand-controller.yaml 10 - clocks : phandle to the nand controller clock 11 - clock-names : must contain "nand" 13 Optional child nodes: 14 Child nodes representing the available nand chips. [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/soc/ti/ |
D | ti,pruss.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 TI Programmable Real-Time Unit and Industrial Communication Subsystem 11 - Suman Anna <s-anna@ti.com> 15 The Programmable Real-Time Unit and Industrial Communication Subsystem 16 (PRU-ICSS a.k.a. PRUSS) is present on various TI SoCs such as AM335x, AM437x, 17 Keystone 66AK2G, OMAP-L138/DA850 etc. A PRUSS consists of dual 32-bit RISC 18 cores (Programmable Real-Time Units, or PRUs), shared RAM, data and 23 peripheral interfaces, fast real-time responses, or specialized data handling. [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/powerpc/fsl/ |
D | srio-rmu.txt | 5 node is composed of three types of sub-nodes ("fsl-srio-msg-unit", 6 "fsl-srio-dbell-unit" and "fsl-srio-port-write-unit"). 10 - compatible 13 Definition: Must include "fsl,srio-rmu-vX.Y", "fsl,srio-rmu". 18 - reg 20 Value type: <prop-encoded-array> 25 - fsl,liodn 26 Usage: optional-but-recommended (for devices with PAMU) 27 Value type: <prop-encoded-array> 33 (msg-unit, doorbell, port-write). [all …]
|
D | raideng.txt | 1 * Freescale 85xx RAID Engine nodes 3 RAID Engine nodes are defined to describe on-chip RAID accelerators. Each RAID 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 …]
|
/linux-6.12.1/net/xfrm/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 52 bool "Transformation sub policy support" 55 Support sub policy for developers. By using sub policy with main 57 Policy which lives shorter time in kernel should be a sub. 68 where mobile nodes change their attachment point to the Internet. 131 environment with IPsec configuration where mobile nodes 133 information can be found in the internet-draft 134 <draft-sugimoto-mip6-pfkey-migrate>.
|
/linux-6.12.1/Documentation/devicetree/bindings/mfd/ |
D | as3722.txt | 4 ------------------- 5 - compatible: Must be "ams,as3722". 6 - reg: I2C device address. 7 - interrupt-controller: AS3722 has internal interrupt controller which takes the 8 interrupt request from internal sub-blocks like RTC, regulators, GPIOs as well 10 - #interrupt-cells: Should be set to 2 for IRQ number and flags. 12 of AS3722 are defined at dt-bindings/mfd/as3722.h 14 interrupts.txt, using dt-bindings/irq. 17 -------------------- 18 - ams,enable-internal-int-pullup: Boolean property, to enable internal pullup on [all …]
|
12345678910>>...15