Lines Matching refs:nodes

19 Structurally, the DT is a tree, or acyclic graph with named nodes, and
20 nodes may have an arbitrary number of named properties encapsulating
32 or create new ones by defining new nodes and properties.  Be wary,
250 platform devices roughly correspond to device nodes at the root of the
251 tree and children of simple memory mapped bus nodes.
319 this DT and decide which nodes to create platform_devices for.
322 at all.  The /chosen, /aliases, and /memory nodes are informational
323 nodes that don't describe devices (although arguably memory could be
332 for nodes that have a 'compatible' property.  First, it is generally
337 For each of these nodes, Linux allocates and registers a
340 Why is using a platform_device for these nodes a safe assumption?
345 same hierarchy is also found in the DT, where I2C device nodes only
362 In the Tegra example, this accounts for the /soc and /sound nodes, but
381 will also get its child nodes registered.  In the Tegra case, the code
392 could be written to just assume simple-bus compatible nodes will