Searched refs:subnodes (Results 1 – 25 of 160) sorted by relevance
1234567
| /Linux-v5.4/Documentation/devicetree/bindings/iio/adc/ |
| D | fsl,imx25-gcq.txt | 11 - #address-cells: Should be <1> (setting for the subnodes)
12 - #size-cells: Should be <0> (setting for the subnodes)
23 Optionally you can define subnodes which define the reference voltage
26 Required properties for subnodes:
36 Optional properties for subnodes:
|
| /Linux-v5.4/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| D | arcx,anybus-controller.txt | 26 Optional: use of subnodes
30 specified in subnodes to the controller node.
32 The subnodes are identified by the standard 'reg' property. Which information
36 Required controller node properties when using subnodes:
|
| /Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | cirrus,madera-pinctrl.txt | 23 - pinctrl-0 : a phandle to the node containing the subnodes containing default
26 Required subnodes:
28 arbitrary number of configuration subnodes, one for each group or pin
31 Required properties of configuration subnodes:
38 Optional properties of configuration subnodes:
|
| D | pinctrl-sirf.txt | 16 SiRFprimaII's pinmux nodes act as a container for an arbitrary number of subnodes.
17 Each of these subnodes represents some desired configuration for a group of pins.
28 For example, pinctrl might have subnodes like the following:
|
| D | pinctrl-atlas7.txt | 63 SiRFatlas7's pinmux nodes act as a container for an abitrary number of subnodes.
64 Each of these subnodes represents some desired configuration for a group of pins.
75 For example, pinctrl might have subnodes like the following:
|
| D | qcom,apq8064-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a
32 The name of each subnode is not important; all subnodes should be enumerated
48 Non-empty subnodes must specify the 'pins' property.
|
| D | qcom,ipq4019-pinctrl.txt | 30 subnodes. Each of these subnodes represents some desired configuration for a
35 The name of each subnode is not important; all subnodes should be enumerated
49 Non-empty subnodes must specify the 'pins' property.
|
| D | qcom,ipq8064-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a
32 The name of each subnode is not important; all subnodes should be enumerated
48 Non-empty subnodes must specify the 'pins' property.
|
| D | qcom,msm8660-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a
32 The name of each subnode is not important; all subnodes should be enumerated
48 Non-empty subnodes must specify the 'pins' property.
|
| D | qcom,msm8974-pinctrl.txt | 27 subnodes. Each of these subnodes represents some desired configuration for a
32 The name of each subnode is not important; all subnodes should be enumerated
46 Non-empty subnodes must specify the 'pins' property.
|
| D | ste,nomadik.txt | 15 subnodes. Each of these subnodes represents some desired configuration for a
20 The name of each subnode is not important; all subnodes should be enumerated
21 and processed purely based on their content. The subnodes use the generic
|
| D | fsl,imx27-pinctrl.txt | 6 The iomuxc driver node should define subnodes containing of pinctrl configuration subnodes.
57 node. If gpio subnodes are defined "#address-cells", "#size-cells" and "ranges"
|
| D | lantiq,pinctrl-falcon.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a
18 The name of each subnode is not important as long as it is unique; all subnodes
|
| D | xlnx,zynq-pinctrl.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a
21 The name of each subnode is not important; all subnodes should be enumerated
|
| /Linux-v5.4/Documentation/devicetree/bindings/rtc/ |
| D | rtc-omap.txt | 23 Optional subnodes:
26 Required pinctrl subnodes properties:
29 Optional pinctrl subnodes properties:
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | amlogic,axg-sound-card.txt | 40 Backend dai-link subnodes:
45 subnodes
47 Required codec subnodes properties:
51 Optional codec subnodes properties:
|
| D | qcom,apq8016-sbc.txt | 37 Dai-link subnode properties and subnodes:
39 Required dai-link subnodes:
44 Required CPU/CODEC subnodes properties:
|
| D | st,stm32-sai.txt | 24 SAI subnodes:
25 Two subnodes corresponding to SAI sub-block instances A et B can be defined.
28 SAI subnodes required properties:
46 SAI subnodes Optional properties:
|
| D | qcom,sdm845.txt | 25 Each subnode of sndcard represents either a dailink, and subnodes of each
33 = CPU, PLATFORM, CODEC dais subnodes
|
| /Linux-v5.4/Documentation/devicetree/bindings/phy/ |
| D | rcar-gen2-phy.txt | 22 - #address-cells: number of address cells for the USB channel subnodes, must
24 - #size-cells: number of size cells for the USB channel subnodes, must be <0>.
28 The USB PHY device tree node should have the subnodes corresponding to the USB
29 channels. These subnodes must contain the following properties:
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | cortina,gemini-ethernet.txt | 16 for the subnodes
18 The subnodes represents the two ethernet ports in this device.
22 Required subnodes:
|
| /Linux-v5.4/scripts/dtc/ |
| D | dtc-parser.y | 77 %type <nodelist> subnodes
249 '{' proplist subnodes '}' ';'
531 subnodes:
536 | subnode subnodes
|
| /Linux-v5.4/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 19 some extra properties / subnodes). It allows describing more complex,
38 Partitions are then defined in subnodes of the partitions node.
40 For backwards compatibility partitions as direct subnodes of the flash device are
42 NOTE: also for backwards compatibility, direct subnodes that have a compatible
|
| /Linux-v5.4/Documentation/devicetree/bindings/bus/ |
| D | moxtet.txt | 16 Required properties of subnodes:
23 case the devices can be defined as subnodes of the moxtet node.
|
| /Linux-v5.4/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smd-rpm.txt | 14 The RPM exposes resources to its subnodes. The rpm_requests node must be
35 for information on the regulator subnodes that can exist under the rpm_requests.
|
1234567
