Searched full:subnodes (Results 1 – 25 of 169) sorted by relevance
1234567
/Documentation/devicetree/bindings/sound/ |
D | amlogic,axg-sound-card.txt | 14 Subnodes: 40 Backend dai-link subnodes: 45 subnodes 47 Required codec subnodes properties: 51 Optional codec subnodes properties:
|
D | qcom,apq8016-sbc.txt | 44 Dai-link subnode properties and subnodes: 46 Required dai-link subnodes: 51 Required CPU/CODEC subnodes properties:
|
D | st,stm32-sai.txt | 24 SAI subnodes: 25 Two subnodes corresponding to SAI sub-block instances A et B can be defined. 28 SAI subnodes required properties: 46 SAI subnodes Optional properties:
|
/Documentation/devicetree/bindings/rtc/ |
D | rtc-omap.txt | 23 Optional subnodes: 26 Required pinctrl subnodes properties: 29 Optional pinctrl subnodes properties:
|
/Documentation/devicetree/bindings/pinctrl/ |
D | pinctrl-sirf.txt | 16 SiRFprimaII's pinmux nodes act as a container for an arbitrary number of subnodes. 17 Each of these subnodes represents some desired configuration for a group of pins. 28 For example, pinctrl might have subnodes like the following:
|
D | qcom,apq8064-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a 32 The name of each subnode is not important; all subnodes should be enumerated 48 Non-empty subnodes must specify the 'pins' property.
|
D | qcom,ipq4019-pinctrl.txt | 30 subnodes. Each of these subnodes represents some desired configuration for a 35 The name of each subnode is not important; all subnodes should be enumerated 50 Non-empty subnodes must specify the 'pins' property.
|
D | qcom,ipq8064-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a 32 The name of each subnode is not important; all subnodes should be enumerated 48 Non-empty subnodes must specify the 'pins' property.
|
D | qcom,msm8660-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a 32 The name of each subnode is not important; all subnodes should be enumerated 48 Non-empty subnodes must specify the 'pins' property.
|
D | pinctrl-atlas7.txt | 63 SiRFatlas7's pinmux nodes act as a container for an arbitrary number of subnodes. 64 Each of these subnodes represents some desired configuration for a group of pins. 75 For example, pinctrl might have subnodes like the following:
|
D | qcom,msm8974-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a 32 The name of each subnode is not important; all subnodes should be enumerated 46 Non-empty subnodes must specify the 'pins' property.
|
D | lantiq,pinctrl-falcon.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a 18 The name of each subnode is not important as long as it is unique; all subnodes
|
D | fsl,imx27-pinctrl.txt | 6 The iomuxc driver node should define subnodes containing of pinctrl configuration subnodes. 57 node. If gpio subnodes are defined "#address-cells", "#size-cells" and "ranges"
|
D | intel,lgm-io.yaml | 28 Pinctrl node's client devices use subnodes for desired pin configuration. 29 Client device subnodes use below standard properties.
|
D | ste,nomadik.txt | 15 subnodes. Each of these subnodes represents some desired configuration for a 20 The name of each subnode is not important; all subnodes should be enumerated 21 and processed purely based on their content. The subnodes use the generic
|
D | xlnx,zynq-pinctrl.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a 21 The name of each subnode is not important; all subnodes should be enumerated
|
D | qcom,pmic-mpp.txt | 58 subnodes. Each of these subnodes represents some desired configuration for a 63 SUBNODES: 65 The name of each subnode is not important; all subnodes should be enumerated
|
D | pinctrl-palmas.txt | 17 subnodes. Each of these subnodes represents some desired configuration for a 22 The name of each subnode is not important; all subnodes should be enumerated
|
/Documentation/devicetree/bindings/spi/ |
D | adi,axi-spi-engine.txt | 14 Optional subnodes: 15 Subnodes are use to represent the SPI slave devices connected to the SPI
|
/Documentation/devicetree/bindings/remoteproc/ |
D | mtk,scp.txt | 17 Subnodes 20 Subnodes of the SCP represent rpmsg devices. The names of the devices are not
|
/Documentation/devicetree/bindings/bus/ |
D | moxtet.txt | 16 Required properties of subnodes: 23 case the devices can be defined as subnodes of the moxtet node.
|
/Documentation/devicetree/bindings/net/ |
D | cortina,gemini-ethernet.txt | 16 for the subnodes 18 The subnodes represents the two ethernet ports in this device. 22 Required subnodes:
|
/Documentation/devicetree/bindings/mfd/ |
D | mfd.txt | 21 consider all subnodes of the MFD device as separate devices akin to how 22 "simple-bus" indicates when to see subnodes as children for a simple
|
/Documentation/devicetree/bindings/phy/ |
D | rcar-gen2-phy.txt | 23 - #address-cells: number of address cells for the USB channel subnodes, must 25 - #size-cells: number of size cells for the USB channel subnodes, must be <0>. 29 The USB PHY device tree node should have the subnodes corresponding to the USB 30 channels. These subnodes must contain the following properties:
|
/Documentation/devicetree/bindings/mtd/ |
D | partition.txt | 19 some extra properties / subnodes). It allows describing more complex, 38 Partitions are then defined in subnodes of the partitions node. 40 For backwards compatibility partitions as direct subnodes of the flash device are 42 NOTE: also for backwards compatibility, direct subnodes that have a compatible
|
1234567