5 config SUPPORT_OF_CONTROL
22 menu "Device Tree Control"
23 depends on SUPPORT_OF_CONTROL
26 bool "Run-time configuration via Device Tree"
28 select OF_LIBFDT if !OF_PLATDATA
30 This feature provides for run-time configuration of U-Boot
31 via a flattened device tree.
34 bool "Board-specific manipulation of Device Tree"
36 In certain circumstances it is necessary to be able to modify
37 U-Boot's device tree (e.g. to delete device from it). This option
38 make the Device Tree writeable and provides a board-specific
39 "board_fix_fdt" callback (called during pre-relocation time), which
40 enables the board initialization to modifiy the Device Tree. The
41 modified copy is subsequently used by U-Boot after relocation.
44 bool "Enable run-time configuration via Device Tree in SPL"
45 depends on SPL && OF_CONTROL
46 select SPL_OF_LIBFDT if !SPL_OF_PLATDATA
48 Some boards use device tree in U-Boot but only have 4KB of SRAM
49 which is not enough to support device tree. Disable this option to
50 allow such boards to be supported by U-Boot SPL.
53 bool "Enable run-time configuration via Device Tree in TPL"
54 depends on TPL && OF_CONTROL
55 select TPL_OF_LIBFDT if !TPL_OF_PLATDATA
57 Some boards use device tree in U-Boot but only have 4KB of SRAM
58 which is not enough to support device tree. Enable this option to
59 allow such boards to be supported by U-Boot TPL.
62 bool "Enable use of a live tree"
63 depends on DM && OF_CONTROL
65 Normally U-Boot uses a flat device tree which saves space and
66 avoids the need to unpack the tree before use. However a flat
67 tree does not support modification from within U-Boot since it
68 can invalidate driver-model device tree offsets. This option
69 enables a live tree which is available after relocation,
70 and can be adjusted as needed.
73 prompt "Provider of DTB for DT control"
77 bool "Separate DTB for DT control"
80 If this option is enabled, the device tree will be built and
81 placed as a separate u-boot.dtb file alongside the U-Boot image.
84 bool "Embedded DTB for DT control"
86 If this option is enabled, the device tree will be picked up and
87 built into the U-Boot image. This is suitable for local debugging
88 and development only and is not recommended for production devices.
89 Boards in the mainline U-Boot tree should not use it.
92 bool "Provided by the board at runtime"
95 If this option is enabled, the device tree will be provided by
96 the board at runtime if the board supports it, instead of being
97 bundled with the image.
100 bool "Host filed DTB for DT control"
103 If this option is enabled, DTB will be read from a file on startup.
104 This is only useful for Sandbox. Use the -d flag to U-Boot to
105 specify the file to read.
107 config OF_PRIOR_STAGE
108 bool "Prior stage bootloader DTB for DT control"
110 If this option is enabled, the device tree used for DT
111 control will be read from a device tree binary, at a memory
112 location passed to U-Boot by the prior stage bootloader.
116 config DEFAULT_DEVICE_TREE
117 string "Default Device Tree for DT control"
118 depends on OF_CONTROL
120 This option specifies the default Device Tree used for DT control.
121 It can be overridden from the command line:
122 $ make DEVICE_TREE=<device-tree-name>
125 string "List of device tree files to include for DT control"
126 depends on SPL_LOAD_FIT || MULTI_DTB_FIT
127 default DEFAULT_DEVICE_TREE
129 This option specifies a list of device tree files to use for DT
130 control. These will be packaged into a FIT. At run-time, U-boot
131 or SPL will select the correct DT to use by examining the
132 hardware (e.g. reading a board ID value). This is a list of
133 device tree files (without the directory or .dtb suffix)
134 separated by <space>.
136 config OF_OVERLAY_LIST
137 string "List of device tree overlays to include for DT control"
138 depends on SPL_LOAD_FIT_APPLY_OVERLAY
140 This option specifies a list of device tree overlays to use for DT
141 control. This option can then be used by a FIT generator to include
142 the overlays in the FIT image.
145 prompt "OF LIST compression"
146 depends on MULTI_DTB_FIT
147 default MULTI_DTB_FIT_NO_COMPRESSION
149 config MULTI_DTB_FIT_LZO
151 depends on SYS_MALLOC_F
154 Compress the FIT image containing the DTBs available for the SPL
155 using LZO compression. (requires lzop on host).
157 config MULTI_DTB_FIT_GZIP
159 depends on SYS_MALLOC_F
162 Compress the FIT image containing the DTBs available for the SPL
163 using GZIP compression. (requires gzip on host)
165 config MULTI_DTB_FIT_NO_COMPRESSION
166 bool "No compression"
168 Do not compress the FIT image containing the DTBs available for the SPL.
169 Use this options only if LZO is not available and the DTBs are very small.
173 prompt "Location of uncompressed DTBs"
174 depends on (MULTI_DTB_FIT_GZIP || MULTI_DTB_FIT_LZO)
175 default MULTI_DTB_FIT_DYN_ALLOC if SYS_MALLOC_F
177 config MULTI_DTB_FIT_DYN_ALLOC
178 bool "Dynamically allocate the memory"
179 depends on SYS_MALLOC_F
181 config MULTI_DTB_FIT_USER_DEFINED_AREA
182 bool "User-defined location"
185 config MULTI_DTB_FIT_UNCOMPRESS_SZ
186 hex "Size of memory reserved to uncompress the DTBs"
187 depends on (MULTI_DTB_FIT_GZIP || MULTI_DTB_FIT_LZO)
190 This is the size of this area where the DTBs are uncompressed.
191 If this area is dynamically allocated, make sure that
192 SYS_MALLOC_F_LEN is big enough to contain it.
194 config MULTI_DTB_FIT_USER_DEF_ADDR
195 hex "Address of memory where dtbs are uncompressed"
196 depends on MULTI_DTB_FIT_USER_DEFINED_AREA
198 the FIT image containing the DTBs is uncompressed in an area defined
199 at compilation time. This is the address of this area. It must be
200 aligned on 2-byte boundary.
203 bool "Support swapping dtbs at a later point in boot"
204 depends on MULTI_DTB_FIT
206 It is possible during initial boot you may need to use a generic
207 dtb until you can fully determine the board your running on. This
208 config allows boards to implement a function at a later point
209 during boot to switch to the "correct" dtb.
212 bool "Support embedding several DTBs in a FIT image for u-boot"
214 This option provides hooks to allow U-boot to parse an
215 appended FIT image and enable board specific code to then select
216 the correct DTB to be used. Use this if you need to support
217 multiple DTBs but don't use the SPL.
220 config SPL_MULTI_DTB_FIT
221 depends on SPL_LOAD_FIT && SPL_OF_CONTROL && !SPL_OF_PLATDATA
222 bool "Support embedding several DTBs in a FIT image for the SPL"
224 This option provides the SPL with the ability to select its own
225 DTB at runtime from an appended FIT image containing several DTBs.
226 This allows using the same SPL binary on multiple platforms.
227 The primary purpose is to handle different versions of
228 the same platform without tweaking the platform code if the
229 differences can be expressed in the DTBs (common examples are: bus
230 capabilities, pad configurations).
233 string "List of device tree files to include for DT control in SPL"
234 depends on SPL_MULTI_DTB_FIT
237 This option specifies a list of device tree files to use for DT
238 control in the SPL. These will be packaged into a FIT. At run-time,
239 the SPL will select the correct DT to use by examining the
240 hardware (e.g. reading a board ID value). This is a list of
241 device tree files (without the directory or .dtb suffix)
242 separated by <space>.
245 prompt "SPL OF LIST compression"
246 depends on SPL_MULTI_DTB_FIT
247 default SPL_MULTI_DTB_FIT_LZO
249 config SPL_MULTI_DTB_FIT_LZO
251 depends on SYS_MALLOC_F
254 Compress the FIT image containing the DTBs available for the SPL
255 using LZO compression. (requires lzop on host).
257 config SPL_MULTI_DTB_FIT_GZIP
259 depends on SYS_MALLOC_F
262 Compress the FIT image containing the DTBs available for the SPL
263 using GZIP compression. (requires gzip on host)
265 config SPL_MULTI_DTB_FIT_NO_COMPRESSION
266 bool "No compression"
268 Do not compress the FIT image containing the DTBs available for the SPL.
269 Use this options only if LZO is not available and the DTBs are very small.
273 prompt "Location of uncompressed DTBs"
274 depends on (SPL_MULTI_DTB_FIT_GZIP || SPL_MULTI_DTB_FIT_LZO)
275 default SPL_MULTI_DTB_FIT_DYN_ALLOC if SYS_MALLOC_F
277 config SPL_MULTI_DTB_FIT_DYN_ALLOC
278 bool "Dynamically allocate the memory"
279 depends on SYS_MALLOC_F
281 config SPL_MULTI_DTB_FIT_USER_DEFINED_AREA
282 bool "User-defined location"
285 config SPL_MULTI_DTB_FIT_UNCOMPRESS_SZ
286 hex "Size of memory reserved to uncompress the DTBs"
287 depends on (SPL_MULTI_DTB_FIT_GZIP || SPL_MULTI_DTB_FIT_LZO)
290 This is the size of this area where the DTBs are uncompressed.
291 If this area is dynamically allocated, make sure that
292 SPL_SYS_MALLOC_F_LEN is big enough to contain it.
294 config SPL_MULTI_DTB_FIT_USER_DEF_ADDR
295 hex "Address of memory where dtbs are uncompressed"
296 depends on SPL_MULTI_DTB_FIT_USER_DEFINED_AREA
298 the FIT image containing the DTBs is uncompressed in an area defined
299 at compilation time. This is the address of this area. It must be
300 aligned on 2-byte boundary.
302 config OF_SPL_REMOVE_PROPS
303 string "List of device tree properties to drop for SPL"
304 depends on SPL_OF_CONTROL
305 default "interrupt-parent interrupts" if SPL_PINCTRL && SPL_CLK
306 default "clocks clock-names interrupt-parent interrupts" if SPL_PINCTRL
307 default "pinctrl-0 pinctrl-names interrupt-parent interrupts" if SPL_CLK
308 default "pinctrl-0 pinctrl-names clocks clock-names interrupt-parent interrupts"
310 Since SPL normally runs in a reduced memory space, the device tree
311 is cut down to only what is needed to load and start U-Boot. Only
312 nodes marked with the property "u-boot,dm-pre-reloc" will be
313 included. In addition, some properties are not used by U-Boot and
314 can be discarded. This option defines the list of properties to
317 config OF_DTB_PROPS_REMOVE
318 bool "Enable removal of device tree properties"
319 depends on OF_CONTROL
321 Some boards have restricted amount of storage for U-Boot image.
322 If the generated binary doesn't fit into available image storage,
323 the built-in device tree could probably be cut down by removing
324 some not required device tree properties to reduce the image size.
325 Enable this option and define the properties to be removed in the
326 CONFIG_OF_REMOVE_PROPS list. Do not enable this option if you must
327 pass the built-in DTB directly to the kernel!
329 config OF_REMOVE_PROPS
330 string "List of device tree properties to drop"
331 depends on OF_DTB_PROPS_REMOVE
332 default "interrupt-parent interrupts" if PINCTRL
334 Some properties are not used by U-Boot and can be discarded.
335 This option defines the list of properties to discard.
337 config SPL_OF_PLATDATA
338 bool "Generate platform data for use in SPL"
339 depends on SPL_OF_CONTROL
341 select SPL_OF_PLATDATA_DRIVER_RT if !SPL_OF_PLATDATA_INST
343 For very constrained SPL environments the overhead of decoding
344 device tree nodes and converting their contents into platform data
345 is too large. This overhead includes libfdt code as well as the
346 device tree contents itself. The latter is fairly compact, but the
347 former can add 3KB or more to a Thumb 2 Image.
349 This option enables generation of platform data from the device
350 tree as C code. This code creates devices using U_BOOT_DRVINFO()
351 declarations. The benefit is that it allows driver code to access
352 the platform data directly in C structures, avoidin the libfdt
355 This option works by generating C structure declarations for each
356 compatible string, then adding platform data and U_BOOT_DRVINFO
357 declarations for each node. See of-plat.txt for more information.
361 config SPL_OF_PLATDATA_PARENT
362 bool "Support parent information in devices"
365 Generally it is useful to be able to access the parent of a device
366 with of-platdata. To save space this can be disabled, but in that
367 case dev_get_parent() will always return NULL;
369 config SPL_OF_PLATDATA_INST
370 bool "Declare devices at build time"
372 Declare devices as udevice instances so that they do not need to be
373 bound when U-Boot starts. This can save time and code space.
375 config SPL_OF_PLATDATA_NO_BIND
376 bool "Don't allow run-time binding of devices"
377 depends on SPL_OF_PLATDATA_INST
380 This removes the ability to bind devices at run time, thus saving
381 some code space in U-Boot. This can be disabled if binding is needed,
382 at the code of some code size increase.
384 config SPL_OF_PLATDATA_RT
385 bool "Use a separate struct for device runtime data"
386 depends on SPL_OF_PLATDATA_INST
389 For systems running SPL from read-only memory it is convenient to
390 separate out the runtime information, so that the devices don't need
391 to be copied before being used. This moves the read-write parts of
392 struct udevice (at present just the flags) into a separate struct,
393 which is allocated at runtime.
395 config SPL_OF_PLATDATA_DRIVER_RT
398 Use a separate struct for driver runtime data.
400 This enables the driver_rt information, used with of-platdata when
401 of-platdata-inst is not used. It allows finding devices by their
406 config TPL_OF_PLATDATA
407 bool "Generate platform data for use in TPL"
408 depends on TPL_OF_CONTROL
410 select TPL_OF_PLATDATA_DRIVER_RT if !TPL_OF_PLATDATA_INST
412 For very constrained SPL environments the overhead of decoding
413 device tree nodes and converting their contents into platform data
414 is too large. This overhead includes libfdt code as well as the
415 device tree contents itself. The latter is fairly compact, but the
416 former can add 3KB or more to a Thumb 2 Image.
418 This option enables generation of platform data from the device
419 tree as C code. This code creates devices using U_BOOT_DRVINFO()
420 declarations. The benefit is that it allows driver code to access
421 the platform data directly in C structures, avoidin the libfdt
424 This option works by generating C structure declarations for each
425 compatible string, then adding platform data and U_BOOT_DRVINFO
426 declarations for each node. See of-plat.txt for more information.
430 config TPL_OF_PLATDATA_PARENT
431 bool "Support parent information in devices"
434 Generally it is useful to be able to access the parent of a device
435 with of-platdata. To save space this can be disabled, but in that
436 case dev_get_parent() will always return NULL;
438 config TPL_OF_PLATDATA_INST
439 bool "Declare devices at build time"
442 Declare devices as udevice instances so that they do not need to be
443 bound when U-Boot starts. This can save time and code space.
445 config TPL_OF_PLATDATA_NO_BIND
446 bool "Don't allow run-time binding of devices"
447 depends on TPL_OF_PLATDATA_INST
450 This removes the ability to bind devices at run time, thus saving
451 some code space in U-Boot. This can be disabled if binding is needed,
452 at the code of some code size increase.
454 config TPL_OF_PLATDATA_RT
455 bool "Use a separate struct for device runtime data"
456 depends on TPL_OF_PLATDATA_INST
459 For systems running TPL from read-only memory it is convenient to
460 separate out the runtime information, so that the devices don't need
461 to be copied before being used. This moves the read-write parts of
462 struct udevice (at present just the flags) into a separate struct,
463 which is allocated at runtime.
465 config TPL_OF_PLATDATA_DRIVER_RT
468 Use a separate struct for driver runtime data.
470 This enables the driver_rt information, used with of-platdata when
471 of-platdata-inst is not used. It allows finding devices by their