| /kernel/linux/linux-5.10/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 | 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 | 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 | 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,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,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 | 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,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,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,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,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.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| 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>
|
| 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>
|
| /kernel/linux/linux-5.10/arch/powerpc/mm/nohash/ |
| D | kaslr_booke.c | 104 int subnode, len, i; in overlaps_reserved_region() local
119 for (subnode = fdt_first_subnode(fdt, regions.reserved_mem); in overlaps_reserved_region()
120 subnode >= 0; in overlaps_reserved_region()
121 subnode = fdt_next_subnode(fdt, subnode)) { in overlaps_reserved_region()
126 reg = fdt_getprop(fdt, subnode, "reg", &len); in overlaps_reserved_region()
|
| /kernel/linux/linux-5.10/scripts/dtc/ |
| 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
|
| /kernel/linux/linux-5.10/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 */
|
| /kernel/linux/linux-5.10/arch/arm/boot/compressed/ |
| D | kaslr.c | 95 int subnode, len, i; in intersects_reserved_region() local
110 for (subnode = fdt_first_subnode(fdt, regions->reserved_mem); in intersects_reserved_region()
111 subnode >= 0; in intersects_reserved_region()
112 subnode = fdt_next_subnode(fdt, subnode)) { in intersects_reserved_region()
116 reg = fdt_getprop(fdt, subnode, "reg", &len); in intersects_reserved_region()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/perf/ |
| 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:
|