Lines Matching full:tree

4 Open Firmware Device Tree Unittest
13 is attached to the live tree dynamically, independent of the machine's
23 from the unflattened device tree data structure. This interface is used by
30 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
32 drivers/of/unittest.c. Currently, following Device Tree Source Include files
62 Un-flattened device tree structure:
64 Un-flattened device tree consists of connected device_node(s) in form of a tree
67     // following struct members are used to construct the tree
76 Figure 1, describes a generic structure of machine's un-flattened device tree
78 ``*parent``, that is used to traverse the tree in the reverse direction. So, at
105 Figure 1: Generic structure of un-flattened device tree
109 machine's device tree (if present). So, when selftest_data_add() is called,
110 at first it reads the flattened device tree data linked into the kernel image
117 blob. And finally, if the machine's device tree (i.e live tree) is present,
118 then it attaches the unflattened test data tree to the live tree, else it
119 attaches itself as a live device tree.
122 live tree as explained below. To explain the same, the test data tree described
123 in Figure 2 is attached to the live tree described in Figure 1::
134 Figure 2: Example test data tree to be attached to live tree.
136 According to the scenario above, the live tree is already present so it isn't
141 given parent in live tree. But, if parent already has a child then the new node
143 data node is attached to the live tree above (Figure 1), the final structure is
179 Figure 3: Live device tree structure after attaching the testcase-data.
189 already present in the live tree), then the node isn't attached rather its
190 properties are updated to the live tree's node by calling the function
200 whole tree). selftest_data_remove() calls detach_node_and_children() that uses
201 of_detach_node() to detach the nodes from the live device tree.