Lines Matching refs:tree

9 is attached to the live tree dynamically, independent of the machine's
19 from the unflattened device tree data structure. This interface is used by
55 Un-flattened device tree structure:
57 Un-flattened device tree consists of connected device_node(s) in form of a tree
60 // following struct members are used to construct the tree
69 Figure 1, describes a generic structure of machine's un-flattened device tree
71 *parent, that is used to traverse the tree in the reverse direction. So, at
98 Figure 1: Generic structure of un-flattened device tree
102 machine's device tree (if present). So, when selftest_data_add() is called,
103 at first it reads the flattened device tree data linked into the kernel image
110 blob. And finally, if the machine's device tree (i.e live tree) is present,
111 then it attaches the unflattened test data tree to the live tree, else it
112 attaches itself as a live device tree.
115 live tree as explained below. To explain the same, the test data tree described
116  in Figure 2 is attached to the live tree described in Figure 1.
127 Figure 2: Example test data tree to be attached to live tree.
129 According to the scenario above, the live tree is already present so it isn't
134 given parent in live tree. But, if parent already has a child then the new node
136 data node is attached to the live tree above (Figure 1), the final structure is
172 Figure 3: Live device tree structure after attaching the testcase-data.
182 already present in the live tree), then the node isn't attached rather its
183 properties are updated to the live tree's node by calling the function
192 whole tree). selftest_data_remove() calls detach_node_and_children() that uses
193 of_detach_node() to detach the nodes from the live device tree.