Searched full:subnode (Results 1 – 25 of 191) sorted by relevance
12345678
| /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,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,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,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,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 | brcm,bcm2835-gpio.txt | 38 configuration. Each subnode only affects those parameters that are explicitly
39 listed. In other words, a subnode that lists only a mux function implies no
40 information about any pull configuration. Similarly, a subnode that lists only
61 Required subnode-properties:
65 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,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,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 | 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,pmic-mpp.txt | 63 The name of each subnode is not important; all subnodes should be enumerated
66 Each subnode only affects those parameters that are explicitly listed. In
67 other words, a subnode that lists a mux function but no pin configuration
69 Similarly, a pin subnode that describes a pullup parameter implies no
73 to specify in a pin configuration subnode:
79 this subnode. Valid pins are:
|
| D | xlnx,zynq-pinctrl.txt | 21 The name of each subnode is not important; all subnodes should be enumerated
35 to specify in a pinmux subnode:
39 to specify in a pinconf subnode:
69 a pin configuration 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,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,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.
|
| /Documentation/devicetree/bindings/clock/ |
| D | ux500.txt | 13 - prcmu-clock: a subnode with one clock cell for PRCMU (power,
16 - prcc-periph-clock: a subnode with two clock cells for
22 - prcc-kernel-clock: a subnode with two clock cells for
28 - rtc32k-clock: a subnode with zero clock cells for the 32kHz
30 - smp-twd-clock: a subnode for the ARM SMP Timer Watchdog cluster
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,sdm845.txt | 25 Each subnode of sndcard represents either a dailink, and subnodes of each
36 Value type: <subnode>
41 Value type: <subnode>
46 Value type: <subnode>
|
| D | qcom,apq8096.txt | 59 Each subnode of sndcard represents either a dailink, and subnodes of each
70 Value type: <subnode>
75 Value type: <subnode>
80 Value type: <subnode>
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | qcom,pon.txt | 16 Optional subnode:
17 -pwrkey: Specifies the subnode pwrkey and should follow the
19 -resin: Specifies the subnode resin and should follow the
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | fsl,imx25-gcq.txt | 16 Required when at least one subnode uses the this reference.
18 Required when at least one subnode uses this reference.
20 Required when at least one subnode uses this reference.
|
| /Documentation/devicetree/bindings/media/ |
| D | qcom,venus.txt | 56 video-decoder and video-encoder, and one optional firmware subnode.
57 Firmware subnode is needed when the platform does not have TrustZone.
59 Every of video-encoder or video-decoder subnode should have:
83 The firmware subnode must have:
|
12345678