Searched full:subnode (Results 1 – 25 of 263) sorted by relevance
1234567891011
| /Linux-v6.1/Documentation/devicetree/bindings/pinctrl/ |
| D | lantiq,pinctrl-falcon.txt | 18 The name of each subnode is not important as long as it is unique; all subnodes
21 Each subnode only affects those parameters that are explicitly listed. In
22 other words, a subnode that lists a mux function but no pin configuration
24 Similarly, a pin subnode that describes a pullup parameter implies no
31 Required subnode-properties:
49 Required subnode-properties:
53 Optional subnode-properties:
|
| D | pinctrl-vt8500.txt | 25 configuration. Each subnode only affects those parameters that are explicitly
26 listed. In other words, a subnode that lists only a mux function implies no
27 information about any pull configuration. Similarly, a subnode that lists only
30 Required subnode-properties:
33 Optional subnode-properties:
|
| D | axis,artpec6-pinctrl.txt | 8 A pinctrl node should contain at least one subnode representing the pinctrl
9 groups available on the machine. Each subnode will list the mux function
10 required and what pin group it will use. Each subnode will also configure the
15 Required subnode-properties:
49 Optional subnode-properties (see pinctrl-bindings.txt):
|
| D | qcom,mdm9615-pinctrl.txt | 67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
|
| D | qcom,apq8064-pinctrl.txt | 32 The name of each subnode is not important; all subnodes should be enumerated
35 Each subnode only affects those parameters that are explicitly listed. In
36 other words, a subnode that lists a mux function but no pin configuration
38 Similarly, a pin subnode that describes a pullup parameter implies no
43 to specify in a pin configuration subnode:
|
| D | qcom,ipq4019-pinctrl.txt | 35 The name of each subnode is not important; all subnodes should be enumerated
38 Each subnode only affects those parameters that are explicitly listed. In
39 other words, a subnode that lists a mux function but no pin configuration
41 Similarly, a pin subnode that describes a pullup parameter implies no
46 to specify in a pin configuration subnode:
|
| D | qcom,ipq8064-pinctrl.txt | 32 The name of each subnode is not important; all subnodes should be enumerated
35 Each subnode only affects those parameters that are explicitly listed. In
36 other words, a subnode that lists a mux function but no pin configuration
38 Similarly, a pin subnode that describes a pullup parameter implies no
43 to specify in a pin configuration subnode:
|
| D | qcom,msm8660-pinctrl.txt | 32 The name of each subnode is not important; all subnodes should be enumerated
35 Each subnode only affects those parameters that are explicitly listed. In
36 other words, a subnode that lists a mux function but no pin configuration
38 Similarly, a pin subnode that describes a pullup parameter implies no
43 to specify in a pin configuration subnode:
|
| D | qcom,ipq8074-pinctrl.txt | 67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
|
| D | qcom,apq8084-pinctrl.txt | 67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
|
| D | qcom,msm8960-pinctrl.txt | 67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
|
| D | qcom,msm8976-pinctrl.txt | 67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode.
|
| D | qcom,sdm845-pinctrl.txt | 59 The name of each subnode is not important; all subnodes should be enumerated
62 Each subnode only affects those parameters that are explicitly listed. In
63 other words, a subnode that lists a mux function but no pin configuration
65 Similarly, a pin subnode that describes a pullup parameter implies no
70 to specify in a pin configuration subnode:
76 this subnode.
|
| D | brcm,bcm2835-gpio.txt | 41 configuration. Each subnode only affects those parameters that are explicitly
42 listed. In other words, a subnode that lists only a mux function implies no
43 information about any pull configuration. Similarly, a subnode that lists only
64 Required subnode-properties:
68 Optional subnode-properties:
|
| D | qcom,msm8974-pinctrl.txt | 32 The name of each subnode is not important; all subnodes should be enumerated
35 Each subnode only affects those parameters that are explicitly listed. In
36 other words, a subnode that lists a mux function but no pin configuration
38 Similarly, a pin subnode that describes a pullup parameter implies no
43 to specify in a pin configuration subnode:
|
| D | qcom,msm8916-pinctrl.txt | 67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
|
| D | qcom,msm8994-pinctrl.txt | 69 The name of each subnode is not important; all subnodes should be enumerated
72 Each subnode only affects those parameters that are explicitly listed. In
73 other words, a subnode that lists a mux function but no pin configuration
75 Similarly, a pin subnode that describes a pullup parameter implies no
80 to specify in a pin configuration subnode:
86 this subnode.
|
| D | qcom,msm8998-pinctrl.txt | 67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode.
|
| D | qcom,qcs404-pinctrl.txt | 70 The name of each subnode is not important; all subnodes should be enumerated
73 Each subnode only affects those parameters that are explicitly listed. In
74 other words, a subnode that lists a mux function but no pin configuration
76 Similarly, a pin subnode that describes a pullup parameter implies no
81 to specify in a pin configuration subnode:
87 this subnode.
|
| D | qcom,sc7180-pinctrl.txt | 76 The name of each subnode is not important; all subnodes should be enumerated
79 Each subnode only affects those parameters that are explicitly listed. In
80 other words, a subnode that lists a mux function but no pin configuration
82 Similarly, a pin subnode that describes a pullup parameter implies no
87 to specify in a pin configuration subnode:
93 this subnode.
|
| D | qcom,sm8150-pinctrl.txt | 76 The name of each subnode is not important; all subnodes should be enumerated
79 Each subnode only affects those parameters that are explicitly listed. In
80 other words, a subnode that lists a mux function but no pin configuration
82 Similarly, a pin subnode that describes a pullup parameter implies no
87 to specify in a pin configuration subnode:
93 this subnode.
|
| D | nvidia,tegra20-pinmux.txt | 18 The name of each subnode is not important; all subnodes should be enumerated
21 Each subnode only affects those parameters that are explicitly listed. In
22 other words, a subnode that lists a mux function but no pin configuration
24 Similarly, a pin subnode that describes a pullup parameter implies no
30 Required subnode-properties:
34 Optional subnode-properties:
|
| /Linux-v6.1/Documentation/devicetree/bindings/clock/ |
| D | stericsson,u8500-clks.yaml | 38 description: A subnode with one clock cell for PRCMU (power, reset, control
50 description: A subnode with two clock cells for PRCC (peripheral
64 description: A subnode with two clock cells for PRCC (peripheral reset
78 description: A subnode with two reset cells for the reset portions of the
92 description: A subnode with zero clock cells for the 32kHz RTC clock.
102 description: A subnode for the ARM SMP Timer Watchdog cluster with zero
113 description: A subnode with three clock cells for externally routed clocks,
|
| /Linux-v6.1/Documentation/devicetree/bindings/sound/ |
| D | qcom,apq8096.txt | 67 Each subnode of sndcard represents either a dailink, and subnodes of each
78 Value type: <subnode>
83 Value type: <subnode>
88 Value type: <subnode>
|
| /Linux-v6.1/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| D | arcx,anybus-controller.txt | 34 for the subnode.
40 Required subnode properties:
41 - reg: Must contain the host index of the card this subnode describes:
63 /* optional subnode for a card plugged into the first host */
|
1234567891011
