Lines Matching refs:node

26 links from one node to another outside of the natural tree structure.
34 maximize use of existing support code, but since property and node
117 property in the root device tree node, and comparing it with the
190 Most of this data is contained in the /chosen node, and when booting
202 match the usual semantic of struct resource.  The chosen node may also
211 is used to parse the chosen node including kernel parameters,
326 of device each node represents, or even if a node represents a device
329 considered a device).  The children of the /soc node are memory mapped
330 devices, but the codec@1a is an i2c device, and the sound node
334 know what to do with each node?
338 assumed that any node with a 'compatible' property represents a device
339 of some kind, and second, it can be assumed that any node at the root
351 ever appear as children of an I2C bus node.  Ditto for SPI, MDIO, USB,
355 tree.  Therefore, if a DT node is at the root of the tree, then it
361 tree, there is no need to provide a starting node (the first NULL), a
368 what about the children of the SoC node?  Shouldn't they be registered
372 i2c_client for each child node, an SPI bus driver will register
375 SoC node and simply registers platform_devices for each of its
385 of_device_id table, and any node that matches an entry in that table
415 because it must decide whether to register each node as either a
418 be too invasive.  If a node is compatible with "arm,primecell", then