Searched refs:subnodes (Results 1 – 25 of 170) sorted by relevance
1234567
| /linux/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| A 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/Documentation/devicetree/bindings/rtc/ |
| A D | rtc-omap.txt | 23 Optional subnodes:
26 Required pinctrl subnodes properties:
29 Optional pinctrl subnodes properties:
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| A D | partition.txt | 19 some extra properties / subnodes). It allows describing more complex,
30 For backwards compatibility partitions as direct subnodes of the flash device are
32 NOTE: also for backwards compatibility, direct subnodes that have a compatible
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | amlogic,axg-sound-card.txt | 40 Backend dai-link subnodes:
45 subnodes
47 Required codec subnodes properties:
51 Optional codec subnodes properties:
|
| A D | qcom,apq8016-sbc.txt | 44 Dai-link subnode properties and subnodes:
46 Required dai-link subnodes:
51 Required CPU/CODEC subnodes properties:
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| A 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.
|
| A D | xlnx,zynq-pinctrl.yaml | 18 subnodes. Each of these subnodes represents some desired configuration for a
26 The name of each subnode is not important; all subnodes should be enumerated
48 Pinctrl node's client devices use subnodes for pin muxes,
128 Pinctrl node's client devices use subnodes for pin configurations,
|
| A 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:
|
| A 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.
|
| A 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.
|
| A 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
50 Non-empty subnodes must specify the 'pins' property.
|
| A 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
|
| A 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.
|
| A 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"
|
| A D | intel,lgm-io.yaml | 28 Pinctrl node's client devices use subnodes for desired pin configuration.
29 Client device subnodes use below standard properties.
|
| A 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
|
| A D | qcom,sc8180x-pinctrl.yaml | 60 Pinctrl node's client devices use subnodes for desired pin configuration.
61 Client device subnodes use below standard properties.
138 uart-w-subnodes-state {
|
| A D | qcom,sm8350-pinctrl.yaml | 53 Pinctrl node's client devices use subnodes for desired pin configuration.
54 Client device subnodes use below standard properties.
131 uart-w-subnodes-state {
|
| A D | qcom,sm6350-pinctrl.yaml | 53 Pinctrl node's client devices use subnodes for desired pin configuration.
54 Client device subnodes use below standard properties.
134 uart-w-subnodes-state {
|
| A D | xlnx,zynqmp-pinctrl.yaml | 19 subnodes. Each of these subnodes represents some desired configuration for a
27 The name of each subnode is not important; all subnodes should be enumerated
41 Pinctrl node's client devices use subnodes for pin muxes,
242 Pinctrl node's client devices use subnodes for pin configurations,
|
| /linux/Documentation/devicetree/bindings/phy/ |
| A D | rcar-gen2-phy.txt | 23 - #address-cells: number of address cells for the USB channel subnodes, must
25 - #size-cells: number of size cells for the USB channel subnodes, must be <0>.
29 The USB PHY device tree node should have the subnodes corresponding to the USB
30 channels. These subnodes must contain the following properties:
|
| /linux/scripts/dtc/ |
| A D | dtc-parser.y | 81 %type <nodelist> subnodes
253 '{' proplist subnodes '}' ';'
535 subnodes:
540 | subnode subnodes
|
| /linux/Documentation/devicetree/bindings/net/ |
| A D | cortina,gemini-ethernet.txt | 16 for the subnodes
18 The subnodes represents the two ethernet ports in this device.
22 Required subnodes:
|
| /linux/Documentation/devicetree/bindings/bus/ |
| A D | moxtet.txt | 16 Required properties of subnodes:
23 case the devices can be defined as subnodes of the moxtet node.
|
| /linux/Documentation/devicetree/bindings/leds/ |
| A D | cznic,turris-omnia-leds.yaml | 39 No subnodes need to be added for subchannels since this controller only
72 * No subnodes are needed, this controller only supports RGB
|
Completed in 29 milliseconds
1234567