Home
last modified time | relevance | path

Searched full:subnodes (Results 1 – 25 of 258) sorted by relevance

1234567891011

/openbmc/u-boot/include/linux/
H A Dlibfdt.h31 /* Add the FDT_BEGIN_NODE tags of subnodes, including their names */
34 /* Add all subnodes of a matching node */
104 * are the names of the immediate subnodes nodes (but not the properties
105 * or subnodes of those subnodes).
108 * and the FDT_BEGIN_NODE and FDT_END_NODE of all subnodes of /. The latter
109 * ensures that we capture the names of the subnodes. In a hashing situation
111 * properties, names of subnodes or number of subnodes would be detected.
202 * immediate subnodes, so in this case we would get the FDT_BEGIN_NODE and
203 * FDT_END_NODE of all subnodes of /.
207 * names of subnodes or number of subnodes would be detected.
/openbmc/u-boot/tools/dtoc/
H A Dfdt.py221 subnodes: A list of subnodes for this node, each a Node object
231 self.subnodes = []
250 for subnode in self.subnodes:
265 """Scan a node's properties and subnodes
267 This fills in the props and subnodes properties, recursively
268 searching into subnodes so that the entire tree is built.
282 self.subnodes.append(node)
297 for subnode in self.subnodes:
413 self.subnodes.append(subnode)
420 subnodes since the last sync.
[all …]
/openbmc/u-boot/doc/device-tree-bindings/pmic/
H A Dsandbox.txt20 To bind each regulator, the optional regulator subnodes should exists.
22 Optional subnodes:
23 - ldo/buck subnodes of each device's regulator (see regulator binding info)
/openbmc/linux/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/
H A Darcx,anybus-controller.txt26 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:
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Dqcom,ipq8064-pinctrl.txt27 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.
H A Dqcom,ipq4019-pinctrl.txt30 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.
H A Dqcom,apq8064-pinctrl.txt27 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.
H A Dpinctrl-sirf.txt16 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:
H A Dxlnx,zynq-pinctrl.yaml18 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,
H A Dste,nomadik.txt15 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
H A Dlantiq,pinctrl-falcon.txt13 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
H A Dfsl,imx27-pinctrl.txt6 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"
H A Dxlnx,zynqmp-pinctrl.yaml18 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
40 Pinctrl node's client devices use subnodes for pin muxes,
241 Pinctrl node's client devices use subnodes for pin configurations,
H A Dqcom,msm8909-tlmm.yaml55 Pinctrl node's client devices use subnodes for desired pin configuration.
56 Client device subnodes use below standard properties.
130 uart-w-subnodes-state {
H A Dpinctrl-palmas.txt17 subnodes. Each of these subnodes represents some desired configuration for a
22 The name of each subnode is not important; all subnodes should be enumerated
H A Dqcom,sc8280xp-tlmm.yaml55 Pinctrl node's client devices use subnodes for desired pin configuration.
56 Client device subnodes use below standard properties.
129 uart-w-subnodes-state {
H A Dqcom,sm6375-tlmm.yaml55 Pinctrl node's client devices use subnodes for desired pin configuration.
56 Client device subnodes use below standard properties.
134 uart-w-subnodes-state {
H A Dqcom,sc8180x-tlmm.yaml62 Pinctrl node's client devices use subnodes for desired pin configuration.
63 Client device subnodes use below standard properties.
130 uart-w-subnodes-state {
H A Dqcom,sm8350-tlmm.yaml62 Pinctrl node's client devices use subnodes for desired pin configuration.
63 Client device subnodes use below standard properties.
129 uart-w-subnodes-state {
H A Dintel,lgm-io.yaml28 Pinctrl node's client devices use subnodes for desired pin configuration.
29 Client device subnodes use below standard properties.
/openbmc/linux/Documentation/devicetree/bindings/rtc/
H A Drtc-omap.txt23 Optional subnodes:
26 Required pinctrl subnodes properties:
29 Optional pinctrl subnodes properties:
/openbmc/u-boot/tools/binman/etype/
H A Du_boot_dtb_with_ucode.py64 self.collate = len(self.ucode.subnodes) > 1
65 for node in self.ucode.subnodes:
77 for node in self.ucode.subnodes:
/openbmc/linux/Documentation/devicetree/bindings/spi/
H A Dadi,axi-spi-engine.txt14 Optional subnodes:
15 Subnodes are use to represent the SPI slave devices connected to the SPI
/openbmc/linux/Documentation/devicetree/bindings/bus/
H A Dmoxtet.txt16 Required properties of subnodes:
23 case the devices can be defined as subnodes of the moxtet node.
/openbmc/u-boot/doc/device-tree-bindings/regulator/
H A Dsandbox.txt12 Required subnodes:
29 Example PMIC's regulator subnodes:

1234567891011