Searched refs:subnode (Results 1 – 25 of 73) sorted by relevance
123
| /Linux-v6.6/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,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,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 | lantiq,pinctrl-xway.txt | 23 The name of each subnode is not important as long as it is unique; all subnodes
26 Each subnode only affects those parameters that are explicitly listed. In
27 other words, a subnode that lists a mux function but no pin configuration
29 Similarly, a pin subnode that describes a pullup parameter implies no
36 Required subnode-properties:
106 Required subnode-properties:
110 Optional subnode-properties:
|
| D | pinctrl-palmas.txt | 22 The name of each subnode is not important; all subnodes should be enumerated
25 Each subnode only affects those parameters that are explicitly listed. In
26 other words, a subnode that lists a mux function but no pin configuration
28 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | berlin,pinctrl.txt | 10 configurations, one per function. Each subnode has the group name and
29 Required subnode-properties:
|
| D | nvidia,tegra124-xusb-padctl.txt | 40 Each subnode describes groups of lanes along with parameters and pads that
44 Each subnode only applies the parameters that are explicitly listed. In other
45 words, if a subnode that lists a function but no pin configuration parameters
47 subnode that describes only an IDDQ parameter implies no information about
|
| D | actions,s700-pinctrl.txt | 39 The name of each subnode is not important; all subnodes should be enumerated
42 Each subnode only affects those parameters that are explicitly listed. In
43 other words, a subnode that lists a mux function but no pin configuration
45 Similarly, a pin subnode that describes a pullup parameter implies no
52 to specify in a pin configuration subnode:
|
| D | actions,s900-pinctrl.txt | 39 The name of each subnode is not important; all subnodes should be enumerated
42 Each subnode only affects those parameters that are explicitly listed. In
43 other words, a subnode that lists a mux function but no pin configuration
45 Similarly, a pin subnode that describes a pullup parameter implies no
52 to specify in a pin configuration subnode:
|
| /Linux-v6.6/scripts/dtc/ |
| D | dtc-parser.y | 86 %type <node> subnode
558 | subnode subnodes
562 | subnode propdef
569 subnode:
578 | DT_OMIT_NO_REF subnode
582 | DT_LABEL subnode
|
| /Linux-v6.6/arch/powerpc/mm/nohash/ |
| D | kaslr_booke.c | 102 int subnode, len, i; in overlaps_reserved_region() local
117 for (subnode = fdt_first_subnode(fdt, regions.reserved_mem); in overlaps_reserved_region()
118 subnode >= 0; in overlaps_reserved_region()
119 subnode = fdt_next_subnode(fdt, subnode)) { in overlaps_reserved_region()
124 reg = fdt_getprop(fdt, subnode, "reg", &len); in overlaps_reserved_region()
|
| /Linux-v6.6/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 */
|
| /Linux-v6.6/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>
|
| D | mt8173-rt5650.txt | 10 - codec-capture : the subnode of rt5650 codec capture
11 Required codec-capture subnode properties:
|
| /Linux-v6.6/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:
|
| /Linux-v6.6/Documentation/devicetree/bindings/edac/ |
| D | apm-xgene-edac.txt | 27 Required properties for memory controller subnode:
33 Required properties for PMD subnode:
39 Required properties for L3 subnode:
44 Required properties for SoC subnode:
|
| /Linux-v6.6/Documentation/devicetree/bindings/clock/st/ |
| D | st,clkgen.txt | 7 address is common of all subnode.
31 Each subnode should use the binding described in [2]..[7]
|
| /Linux-v6.6/Documentation/devicetree/bindings/mfd/ |
| D | tps6105x.txt | 12 This subnode selects the chip's operational mode.
13 There can be at most one single available subnode.
|
| /Linux-v6.6/Documentation/devicetree/bindings/hwmon/ |
| D | npcm750-pwm-fan.txt | 23 fan subnode format:
25 Under fan subnode can be upto 8 child nodes, each child node representing a fan.
26 Each fan subnode must have one PWM channel and at least one Fan tach channel.
|
| /Linux-v6.6/Documentation/firmware-guide/acpi/dsd/ |
| D | phy.rst | 60 The "fixed-link" is described by a data-only subnode of the
64 The subnode should comprise a required property ("speed") and
162 MAC node example with a "fixed-link" subnode.
179 Name (LNK0, Package(){ // Data-only subnode of port
|
123
