Searched full:subnodes (Results 1 – 25 of 211) sorted by relevance
123456789
/Linux-v6.1/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:
|
/Linux-v6.1/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
D | arcx,anybus-controller.txt | 26 Optional: use of subnodes 30 specified in subnodes to the controller node. 32 The subnodes are identified by the standard 'reg' property. Which information 36 Required controller node properties when using subnodes:
|
/Linux-v6.1/Documentation/devicetree/bindings/pinctrl/ |
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 | xlnx,zynq-pinctrl.yaml | 18 subnodes. Each of these subnodes represents some desired configuration for a 26 The name of each subnode is not important; all subnodes should be enumerated 48 Pinctrl node's client devices use subnodes for pin muxes, 128 Pinctrl node's client devices use subnodes for pin configurations,
|
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,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 | 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 | 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 | xlnx,zynqmp-pinctrl.yaml | 19 subnodes. Each of these subnodes represents some desired configuration for a 27 The name of each subnode is not important; all subnodes should be enumerated 41 Pinctrl node's client devices use subnodes for pin muxes, 242 Pinctrl node's client devices use subnodes for pin configurations,
|
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
|
D | qcom,msm8909-tlmm.yaml | 53 Pinctrl node's client devices use subnodes for desired pin configuration. 54 Client device subnodes use below standard properties. 138 uart-w-subnodes-state {
|
D | qcom,mdm9615-pinctrl.txt | 59 subnodes. Each of these subnodes represents some desired configuration for a 67 The name of each subnode is not important; all subnodes should be enumerated
|
D | qcom,sc8180x-pinctrl.yaml | 62 Pinctrl node's client devices use subnodes for desired pin configuration. 63 Client device subnodes use below standard properties. 148 uart-w-subnodes-state {
|
D | qcom,sm8350-pinctrl.yaml | 55 Pinctrl node's client devices use subnodes for desired pin configuration. 56 Client device subnodes use below standard properties. 141 uart-w-subnodes-state {
|
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 | bitmain,bm1880-pinctrl.txt | 15 subnodes. Each of these subnodes represents some desired configuration for a 21 options. The name of each subnode is not important; all subnodes should be
|
/Linux-v6.1/Documentation/devicetree/bindings/rtc/ |
D | rtc-omap.txt | 23 Optional subnodes: 26 Required pinctrl subnodes properties: 29 Optional pinctrl subnodes properties:
|
/Linux-v6.1/Documentation/devicetree/bindings/mtd/ |
D | partition.txt | 19 some extra properties / subnodes). It allows describing more complex, 30 For backwards compatibility partitions as direct subnodes of the flash device are 32 NOTE: also for backwards compatibility, direct subnodes that have a compatible
|
/Linux-v6.1/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
|
/Linux-v6.1/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.
|
/Linux-v6.1/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
|
123456789