Lines Matching +full:device +full:- +full:tree
2 # Device Tree Control
22 menu "Device Tree Control"
26 bool "Run-time configuration via Device Tree"
29 This feature provides for run-time configuration of U-Boot
30 via a flattened device tree.
33 bool "Board-specific manipulation of Device Tree"
36 U-Boot's device tree (e.g. to delete device from it). This option
37 make the Device Tree writeable and provides a board-specific
38 "board_fix_fdt" callback (called during pre-relocation time), which
39 enables the board initialization to modifiy the Device Tree. The
40 modified copy is subsequently used by U-Boot after relocation.
43 bool "Enable run-time configuration via Device Tree in SPL"
46 Some boards use device tree in U-Boot but only have 4KB of SRAM
47 which is not enough to support device tree. Enable this option to
48 allow such boards to be supported by U-Boot SPL.
57 property "u-boot,dm-spl". The property "u-boot,pre-reloc" doesn't
61 bool "Enable run-time configuration via Device Tree in TPL"
64 Some boards use device tree in U-Boot but only have 4KB of SRAM
65 which is not enough to support device tree. Enable this option to
66 allow such boards to be supported by U-Boot TPL.
69 bool "Enable use of a live tree"
72 Normally U-Boot uses a flat device tree which saves space and
73 avoids the need to unpack the tree before use. However a flat
74 tree does not support modifcation from within U-Boot since it
75 can invalidate driver-model device tree offsets. This option
76 enables a live tree which is available after relocation,
87 If this option is enabled, the device tree will be built and
88 placed as a separate u-boot.dtb file alongside the U-Boot image.
93 If this option is enabled, the device tree will be picked up and
94 built into the U-Boot image. This is suitable for local debugging
96 Boards in the mainline U-Boot tree should not use it.
102 If this option is enabled, the device tree will be provided by
111 This is only useful for Sandbox. Use the -d flag to U-Boot to
117 If this option is enabled, the device tree used for DT
118 control will be read from a device tree binary, at a memory
119 location passed to U-Boot by the prior stage bootloader.
124 string "Default Device Tree for DT control"
127 This option specifies the default Device Tree used for DT control.
129 $ make DEVICE_TREE=<device-tree-name>
132 string "List of device tree files to include for DT control"
136 This option specifies a list of device tree files to use for DT
137 control. These will be packaged into a FIT. At run-time, U-boot
140 device tree files (without the directory or .dtb suffix)
154 bool "Support embedding several DTBs in a FIT image for u-boot"
156 This option provides hooks to allow U-boot to parse an
175 string "List of device tree files to include for DT control in SPL"
179 This option specifies a list of device tree files to use for DT
180 control in the SPL. These will be packaged into a FIT. At run-time,
183 device tree files (without the directory or .dtb suffix)
224 bool "User-defined location"
242 aligned on 2-byte boundary.
245 string "List of device tree properties to drop for SPL"
246 default "interrupt-parent" if SPL_PINCTRL && SPL_CLK
247 default "clocks clock-names interrupt-parent" if SPL_PINCTRL
248 default "pinctrl-0 pinctrl-names interrupt-parent" if SPL_CLK
249 default "pinctrl-0 pinctrl-names clocks clock-names interrupt-parent"
251 Since SPL normally runs in a reduced memory space, the device tree
252 is cut down to only what is needed to load and start U-Boot. Only
253 nodes marked with the property "u-boot,dm-pre-reloc" will be
254 included. In addition, some properties are not used by U-Boot and
259 string "List of device tree properties to drop for U-Boot"
263 Since kernel dtb feature is enabled, U-Boot prop use the same device tree as SPL.
264 At sometimes there is different require for list of device tree properties to drop
265 for U-Boot prop, so providing this configure which has higher priority, that if it
274 device tree nodes and converting their contents into platform data
276 device tree contents itself. The latter is fairly compact, but the
279 This option enables generation of platform data from the device
280 tree as C code. This code creates devices using U_BOOT_DEVICE()
296 device tree nodes and converting their contents into platform data
298 device tree contents itself. The latter is fairly compact, but the
301 This option enables generation of platform data from the device
302 tree as C code. This code creates devices using U_BOOT_DEVICE()