Searched full:subnodes (Results 1 – 25 of 210) sorted by relevance
123456789
| /Linux-v6.6/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.6/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 | 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 | 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 | 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
40 Pinctrl node's client devices use subnodes for pin muxes,
241 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 | 55 Pinctrl node's client devices use subnodes for desired pin configuration.
56 Client device subnodes use below standard properties.
130 uart-w-subnodes-state {
|
| D | qcom,sc8180x-tlmm.yaml | 62 Pinctrl node's client devices use subnodes for desired pin configuration.
63 Client device subnodes use below standard properties.
130 uart-w-subnodes-state {
|
| D | qcom,sc8280xp-tlmm.yaml | 55 Pinctrl node's client devices use subnodes for desired pin configuration.
56 Client device subnodes use below standard properties.
129 uart-w-subnodes-state {
|
| D | qcom,sm8350-tlmm.yaml | 62 Pinctrl node's client devices use subnodes for desired pin configuration.
63 Client device subnodes use below standard properties.
129 uart-w-subnodes-state {
|
| D | qcom,sm6375-tlmm.yaml | 55 Pinctrl node's client devices use subnodes for desired pin configuration.
56 Client device subnodes use below standard properties.
134 uart-w-subnodes-state {
|
| D | qcom,sm6350-tlmm.yaml | 63 Pinctrl node's client devices use subnodes for desired pin configuration.
64 Client device subnodes use below standard properties.
142 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 | fsl,mxs-pinctrl.txt | 17 subnodes. Each of these subnodes represents some desired configuration for
25 Those subnodes under mxs pin controller node will fall into two categories.
|
| 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
|
| D | pinctrl_spear.txt | 35 SPEAr's pinmux nodes act as a container for an arbitrary number of subnodes. Each
36 of these subnodes represents muxing for a pin, a group, or a list of pins or
39 The name of each subnode is not important; all subnodes should be enumerated
|
| /Linux-v6.6/Documentation/devicetree/bindings/rtc/ |
| D | rtc-omap.txt | 23 Optional subnodes:
26 Required pinctrl subnodes properties:
29 Optional pinctrl subnodes properties:
|
| /Linux-v6.6/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.6/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.6/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
