| /linux/Documentation/devicetree/bindings/pinctrl/ |
| A 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:
|
| A 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):
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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.
|
| A 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:
|
| A 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:
|
| A 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.
|
| A 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.
|
| /linux/Documentation/devicetree/bindings/clock/ |
| A 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
|
| /linux/scripts/dtc/ |
| A D | dtc-parser.y | 80 %type <node> subnode
540 | subnode subnodes
544 | subnode propdef
551 subnode:
560 | DT_OMIT_NO_REF subnode
564 | DT_LABEL subnode
|
| /linux/arch/powerpc/mm/nohash/ |
| A D | kaslr_booke.c | 108 int subnode, len, i; in overlaps_reserved_region() local
123 for (subnode = fdt_first_subnode(fdt, regions.reserved_mem); in overlaps_reserved_region()
124 subnode >= 0; in overlaps_reserved_region()
125 subnode = fdt_next_subnode(fdt, subnode)) { in overlaps_reserved_region()
130 reg = fdt_getprop(fdt, subnode, "reg", &len); in overlaps_reserved_region()
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | qcom,sdm845.txt | 36 Each subnode of sndcard represents either a dailink, and subnodes of each
47 Value type: <subnode>
52 Value type: <subnode>
57 Value type: <subnode>
|
| A 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>
|
| A D | qcom,sm8250.yaml | 37 Each subnode represents a dai link. Subnodes of each dai links would be
49 description: Holds subnode which indicates cpu dai.
55 description: Holds subnode which indicates platform dai.
61 description: Holds subnode which indicates codec dai.
|
| /linux/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| A 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 */
|
| /linux/Documentation/devicetree/bindings/perf/ |
| A D | apm-xgene-pmu.txt | 22 Required properties for L3C subnode:
26 Required properties for IOB subnode:
30 Required properties for MCB subnode:
35 Required properties for MC subnode:
|