| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | xlnx,pinctrl-zynq.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,
|
| H A 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:
|
| H A 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
|
| H A 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
|
| H A 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"
|
| H A D | qcom,msm8909-tlmm.yaml | 43 Pinctrl node's client devices use subnodes for desired pin configuration.
44 Client device subnodes use below standard properties.
124 uart-w-subnodes-state {
|
| H A 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,
252 Pinctrl node's client devices use subnodes for pin configurations,
|
| H A D | qcom,sm8350-tlmm.yaml | 48 Pinctrl node's client devices use subnodes for desired pin configuration.
49 Client device subnodes use below standard properties.
121 uart-w-subnodes-state {
|
| H A D | qcom,sc8180x-tlmm.yaml | 49 Pinctrl node's client devices use subnodes for desired pin configuration.
50 Client device subnodes use below standard properties.
124 uart-w-subnodes-state {
|
| H A D | nuvoton,ma35d1-pinctrl.yaml | 76 Pinctrl node's client devices use subnodes for desired pin configuration.
77 Client device subnodes use below standard properties.
82 A pinctrl node should contain at least one subnodes representing the
|
| H A 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
|
| H A D | qcom,sc8280xp-tlmm.yaml | 43 Pinctrl node's client devices use subnodes for desired pin configuration.
44 Client device subnodes use below standard properties.
123 uart-w-subnodes-state {
|
| H A D | qcom,sm6375-tlmm.yaml | 43 Pinctrl node's client devices use subnodes for desired pin configuration.
44 Client device subnodes use below standard properties.
128 uart-w-subnodes-state {
|
| H A D | qcom,sm6350-tlmm.yaml | 49 Pinctrl node's client devices use subnodes for desired pin configuration.
50 Client device subnodes use below standard properties.
134 uart-w-subnodes-state {
|
| H A D | qcom,sdx65-tlmm.yaml | 41 Pinctrl node's client devices use subnodes for desired pin configuration.
42 Client device subnodes use below standard properties.
139 uart-w-subnodes-state {
|
| H A 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.
|
| H A 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
|
| H A 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.
|
| H A 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
|
| H A D | fsl,scu-pinctrl.yaml | 31 Pinctrl node's client devices use subnodes for desired pin configuration.
32 Client device subnodes use below standard properties.
|
| H A D | fsl,imx8ulp-pinctrl.yaml | 28 Pinctrl node's client devices use subnodes for desired pin configuration.
29 Client device subnodes use below standard properties.
|
| /linux/Documentation/devicetree/bindings/rtc/ |
| H A D | rtc-omap.txt | 23 Optional subnodes:
26 Required pinctrl subnodes properties:
29 Optional pinctrl subnodes properties:
|
| /linux/Documentation/devicetree/bindings/bus/ |
| H A D | moxtet.txt | 16 Required properties of subnodes:
23 case the devices can be defined as subnodes of the moxtet node.
|
| /linux/Documentation/devicetree/bindings/firmware/ |
| H A D | nxp,imx95-scmi-pinctrl.yaml | 20 Pinctrl node's client devices use subnodes for desired pin configuration.
21 Client device subnodes use below standard properties.
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | mfd.txt | 21 should consider all subnodes of the MFD device as separate and independent
23 Similarly to how "simple-bus" indicates when to see subnodes as children for
|