Lines Matching full:tree

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
51 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
53 drivers/of/unittest.c. Currently, following Device Tree Source Include files
83 Un-flattened device tree structure:
85 Un-flattened device tree consists of connected device_node(s) in form of a tree
88     // following struct members are used to construct the tree
97 Figure 1, describes a generic structure of machine's un-flattened device tree
99 ``*parent``, that is used to traverse the tree in the reverse direction. So, at
126 Figure 1: Generic structure of un-flattened device tree
130 machine's device tree (if present). So, when selftest_data_add() is called,
131 at first it reads the flattened device tree data linked into the kernel image
138 blob. And finally, if the machine's device tree (i.e live tree) is present,
139 then it attaches the unflattened test data tree to the live tree, else it
140 attaches itself as a live device tree.
143 live tree as explained below. To explain the same, the test data tree described
144 in Figure 2 is attached to the live tree described in Figure 1::
155 Figure 2: Example test data tree to be attached to live tree.
157 According to the scenario above, the live tree is already present so it isn't
162 given parent in live tree. But, if parent already has a child then the new node
164 data node is attached to the live tree above (Figure 1), the final structure is
200 Figure 3: Live device tree structure after attaching the testcase-data.
210 already present in the live tree), then the node isn't attached rather its
211 properties are updated to the live tree's node by calling the function
221 whole tree). selftest_data_remove() calls detach_node_and_children() that uses
222 of_detach_node() to detach the nodes from the live device tree.