Lines Matching full:tree
1 Driver Model Compiled-in Device Tree / Platform Data
8 Device tree is the standard configuration method in U-Boot. It is used to
12 The overhead of adding device tree access to U-Boot is fairly modest,
14 that in most cases it is best to use device tree for configuration.
19 case the overhead of device tree access may be too great.
23 bypasses the use of device tree completely, effectively creating a parallel
27 device tree contents into C code which can be compiled into the SPL binary.
42 - Device tree does not describe data types. But the C code must define a
48 in the device tree file.
51 the naming in the device tree, which may result in C identifiers that
56 the code less robust in the face of device-tree changes. It also
64 normally also supports device tree it must use #ifdef to separate
83 A new tool called 'dtoc' converts a device tree file either into a set of
162 This avoids the code overhead of converting the device tree data to
184 driver will not be able to support device tree, since the of-platdata
185 structure is not available when device tree is used. It would make no sense
186 to use this structure if device tree were available, since the structure has
198 Drivers should always support device tree as an option. The of-platdata
202 existing device tree decoding logic should be kept in the
216 * the device tree (or the C structures when of-platdata is used).
224 /* Decode the device tree data */
271 start of the newly allocated area. In the case where device tree is used,
276 SPL must use either of-platdata or device tree. Drivers cannot use both at
277 the same time, but they must support device tree. Supporting of-platdata is
280 The device tree becomes in accessible when CONFIG_SPL_OF_PLATDATA is enabled,
281 since the device-tree access code is not compiled in. A corollary is that
284 tree data, since then libfdt would still be needed for those drivers and
315 - Consider programmatically reading binding files instead of device tree