5 config SUPPORT_OF_CONTROL
19 menu "Device Tree Control"
20 depends on SUPPORT_OF_CONTROL
23 bool "Run-time configuration via Device Tree"
24 select OF_LIBFDT if !OF_PLATDATA
25 select OF_REAL if !OF_PLATDATA
27 This feature provides for run-time configuration of U-Boot
28 via a flattened device tree.
33 Indicates that a real devicetree is available which can be accessed
34 at runtime. This means that dev_read_...() functions can be used to
35 read data from the devicetree for each device. This is true if
36 OF_CONTROL is enabled in U-Boot proper.
39 bool "Board-specific manipulation of Device Tree"
41 In certain circumstances it is necessary to be able to modify
42 U-Boot's device tree (e.g. to delete device from it). This option
43 make the Device Tree writeable and provides a board-specific
44 "board_fix_fdt" callback (called during pre-relocation time), which
45 enables the board initialization to modifiy the Device Tree. The
46 modified copy is subsequently used by U-Boot after relocation.
49 bool "Enable run-time configuration via Device Tree in SPL"
50 depends on SPL && OF_CONTROL
51 select SPL_OF_LIBFDT if !SPL_OF_PLATDATA
52 select SPL_OF_REAL if !SPL_OF_PLATDATA
54 Some boards use device tree in U-Boot but only have 4KB of SRAM
55 which is not enough to support device tree. Disable this option to
56 allow such boards to be supported by U-Boot SPL.
59 bool "Enable run-time configuration via Device Tree in TPL"
60 depends on TPL && OF_CONTROL
61 select TPL_OF_LIBFDT if !TPL_OF_PLATDATA
62 select TPL_OF_REAL if !TPL_OF_PLATDATA
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"
70 depends on DM && OF_CONTROL
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 modification 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,
77 and can be adjusted as needed.
80 prompt "Provider of DTB for DT control"
84 bool "Separate DTB for DT control"
86 If this option is enabled, the device tree will be built and
87 placed as a separate u-boot.dtb file alongside the U-Boot image.
90 bool "Embedded DTB for DT control"
92 If this option is enabled, the device tree will be picked up and
93 built into the U-Boot image. This is suitable for local debugging
94 and development only and is not recommended for production devices.
95 Boards in the mainline U-Boot tree should not use it.
100 bool "Provided by the board (e.g a previous loader) at runtime"
101 default y if SANDBOX || OF_HAS_PRIOR_STAGE
103 If this option is enabled, the device tree is provided at runtime by
104 a custom function called board_fdt_blob_setup(). The board must
105 implement this function if it wishes to provide special behaviour.
107 With this option, the device tree build by U-Boot may be overridden or
108 ignored. See OF_HAS_PRIOR_STAGE.
110 Note: Boards which use this to handle a device tree passed from an
111 earlier stage should enable OF_HAS_PRIOR_STAGE.
113 config OF_HAS_PRIOR_STAGE
116 Indicates that a prior stage of the firmware (before U-Boot proper)
117 makes use of device tree and this board normally boots with that prior
118 stage, that provides a devicetree to U-Boot.
120 This means that the device tree built in U-Boot should not be packaged
121 in the firmware image. Instead, the prior stage's device tree should
122 be so packaged. At runtime, the prior stage reads this, does any
123 necessary fix-ups, then passes it to U-Boot. See OF_BOARD.
125 This option does not preclude using the U-Boot device tree, e.g. for
126 development purposes, but it is not recommended, and likely will not
127 even work, for production systems.
129 Note: This option must be set in Kconfig and cannot be enabled or
130 disabled in the board's defconfig file.
132 config DEFAULT_DEVICE_TREE
133 string "Default Device Tree for DT control"
134 depends on OF_CONTROL
136 This option specifies the default Device Tree used for DT control.
137 It can be overridden from the command line:
138 $ make DEVICE_TREE=<device-tree-name>
141 string "List of device tree files to include for DT control"
142 depends on SPL_LOAD_FIT || MULTI_DTB_FIT
143 default DEFAULT_DEVICE_TREE
145 This option specifies a list of device tree files to use for DT
146 control. These will be packaged into a FIT. At run-time, U-boot
147 or SPL will select the correct DT to use by examining the
148 hardware (e.g. reading a board ID value). This is a list of
149 device tree files (without the directory or .dtb suffix)
150 separated by <space>.
152 config OF_OVERLAY_LIST
153 string "List of device tree overlays to include for DT control"
154 depends on SPL_LOAD_FIT_APPLY_OVERLAY
156 This option specifies a list of device tree overlays to use for DT
157 control. This option can then be used by a FIT generator to include
158 the overlays in the FIT image.
161 prompt "OF LIST compression"
162 depends on MULTI_DTB_FIT
163 default MULTI_DTB_FIT_NO_COMPRESSION
165 config MULTI_DTB_FIT_LZO
167 depends on SYS_MALLOC_F
170 Compress the FIT image containing the DTBs available for the SPL
171 using LZO compression. (requires lzop on host).
173 config MULTI_DTB_FIT_GZIP
175 depends on SYS_MALLOC_F
178 Compress the FIT image containing the DTBs available for the SPL
179 using GZIP compression. (requires gzip on host)
181 config MULTI_DTB_FIT_NO_COMPRESSION
182 bool "No compression"
184 Do not compress the FIT image containing the DTBs available for the SPL.
185 Use this options only if LZO is not available and the DTBs are very small.
189 prompt "Location of uncompressed DTBs"
190 depends on (MULTI_DTB_FIT_GZIP || MULTI_DTB_FIT_LZO)
191 default MULTI_DTB_FIT_DYN_ALLOC if SYS_MALLOC_F
193 config MULTI_DTB_FIT_DYN_ALLOC
194 bool "Dynamically allocate the memory"
195 depends on SYS_MALLOC_F
197 config MULTI_DTB_FIT_USER_DEFINED_AREA
198 bool "User-defined location"
201 config MULTI_DTB_FIT_UNCOMPRESS_SZ
202 hex "Size of memory reserved to uncompress the DTBs"
205 This is the size of this area where the DTBs are uncompressed.
206 If this area is dynamically allocated, make sure that
207 SYS_MALLOC_F_LEN is big enough to contain it.
209 config MULTI_DTB_FIT_USER_DEF_ADDR
210 hex "Address of memory where dtbs are uncompressed"
211 depends on MULTI_DTB_FIT_USER_DEFINED_AREA
213 the FIT image containing the DTBs is uncompressed in an area defined
214 at compilation time. This is the address of this area. It must be
215 aligned on 2-byte boundary.
218 bool "Support swapping dtbs at a later point in boot"
219 depends on MULTI_DTB_FIT
221 It is possible during initial boot you may need to use a generic
222 dtb until you can fully determine the board your running on. This
223 config allows boards to implement a function at a later point
224 during boot to switch to the "correct" dtb.
227 bool "Support embedding several DTBs in a FIT image for u-boot"
229 This option provides hooks to allow U-boot to parse an
230 appended FIT image and enable board specific code to then select
231 the correct DTB to be used. Use this if you need to support
232 multiple DTBs but don't use the SPL.
235 config SPL_MULTI_DTB_FIT
236 depends on SPL_LOAD_FIT && SPL_OF_REAL
237 bool "Support embedding several DTBs in a FIT image for the SPL"
239 This option provides the SPL with the ability to select its own
240 DTB at runtime from an appended FIT image containing several DTBs.
241 This allows using the same SPL binary on multiple platforms.
242 The primary purpose is to handle different versions of
243 the same platform without tweaking the platform code if the
244 differences can be expressed in the DTBs (common examples are: bus
245 capabilities, pad configurations).
248 string "List of device tree files to include for DT control in SPL"
249 depends on SPL_MULTI_DTB_FIT
252 This option specifies a list of device tree files to use for DT
253 control in the SPL. These will be packaged into a FIT. At run-time,
254 the SPL will select the correct DT to use by examining the
255 hardware (e.g. reading a board ID value). This is a list of
256 device tree files (without the directory or .dtb suffix)
257 separated by <space>.
260 prompt "SPL OF LIST compression"
261 depends on SPL_MULTI_DTB_FIT
262 default SPL_MULTI_DTB_FIT_LZO
264 config SPL_MULTI_DTB_FIT_LZO
266 depends on SYS_MALLOC_F
269 Compress the FIT image containing the DTBs available for the SPL
270 using LZO compression. (requires lzop on host).
272 config SPL_MULTI_DTB_FIT_GZIP
274 depends on SYS_MALLOC_F
277 Compress the FIT image containing the DTBs available for the SPL
278 using GZIP compression. (requires gzip on host)
280 config SPL_MULTI_DTB_FIT_NO_COMPRESSION
281 bool "No compression"
283 Do not compress the FIT image containing the DTBs available for the SPL.
284 Use this options only if LZO is not available and the DTBs are very small.
288 prompt "Location of uncompressed DTBs"
289 depends on (SPL_MULTI_DTB_FIT_GZIP || SPL_MULTI_DTB_FIT_LZO)
290 default SPL_MULTI_DTB_FIT_DYN_ALLOC if SYS_MALLOC_F
292 config SPL_MULTI_DTB_FIT_DYN_ALLOC
293 bool "Dynamically allocate the memory"
294 depends on SYS_MALLOC_F
296 config SPL_MULTI_DTB_FIT_USER_DEFINED_AREA
297 bool "User-defined location"
300 config SPL_MULTI_DTB_FIT_UNCOMPRESS_SZ
301 hex "Size of memory reserved to uncompress the DTBs"
302 depends on (SPL_MULTI_DTB_FIT_GZIP || SPL_MULTI_DTB_FIT_LZO)
305 This is the size of this area where the DTBs are uncompressed.
306 If this area is dynamically allocated, make sure that
307 SPL_SYS_MALLOC_F_LEN is big enough to contain it.
309 config SPL_MULTI_DTB_FIT_USER_DEF_ADDR
310 hex "Address of memory where dtbs are uncompressed"
311 depends on SPL_MULTI_DTB_FIT_USER_DEFINED_AREA
313 the FIT image containing the DTBs is uncompressed in an area defined
314 at compilation time. This is the address of this area. It must be
315 aligned on 2-byte boundary.
317 config OF_SPL_REMOVE_PROPS
318 string "List of device tree properties to drop for SPL"
319 depends on SPL_OF_CONTROL
320 default "interrupt-parent interrupts" if SPL_PINCTRL && SPL_CLK
321 default "clocks clock-names interrupt-parent interrupts" if SPL_PINCTRL
322 default "pinctrl-0 pinctrl-names interrupt-parent interrupts" if SPL_CLK
323 default "pinctrl-0 pinctrl-names clocks clock-names interrupt-parent interrupts"
325 Since SPL normally runs in a reduced memory space, the device tree
326 is cut down to only what is needed to load and start U-Boot. Only
327 nodes marked with the property "u-boot,dm-pre-reloc" will be
328 included. In addition, some properties are not used by U-Boot and
329 can be discarded. This option defines the list of properties to
332 config OF_DTB_PROPS_REMOVE
333 bool "Enable removal of device tree properties"
334 depends on OF_CONTROL
336 Some boards have restricted amount of storage for U-Boot image.
337 If the generated binary doesn't fit into available image storage,
338 the built-in device tree could probably be cut down by removing
339 some not required device tree properties to reduce the image size.
340 Enable this option and define the properties to be removed in the
341 CONFIG_OF_REMOVE_PROPS list. Do not enable this option if you must
342 pass the built-in DTB directly to the kernel!
344 config OF_REMOVE_PROPS
345 string "List of device tree properties to drop"
346 depends on OF_DTB_PROPS_REMOVE
347 default "interrupt-parent interrupts" if PINCTRL
349 Some properties are not used by U-Boot and can be discarded.
350 This option defines the list of properties to discard.
352 config SPL_OF_PLATDATA
353 bool "Generate platform data for use in SPL"
354 depends on SPL_OF_CONTROL
356 select SPL_OF_PLATDATA_DRIVER_RT if !SPL_OF_PLATDATA_INST
358 For very constrained SPL environments the overhead of decoding
359 device tree nodes and converting their contents into platform data
360 is too large. This overhead includes libfdt code as well as the
361 device tree contents itself. The latter is fairly compact, but the
362 former can add 3KB or more to a Thumb 2 Image.
364 This option enables generation of platform data from the device
365 tree as C code. This code creates devices using U_BOOT_DRVINFO()
366 declarations. The benefit is that it allows driver code to access
367 the platform data directly in C structures, avoidin the libfdt
370 This option works by generating C structure declarations for each
371 compatible string, then adding platform data and U_BOOT_DRVINFO
372 declarations for each node. See of-plat.txt for more information.
377 Indicates that a real devicetree is available which can be accessed
378 at runtime. This means that dev_read_...() functions can be used to
379 read data from the devicetree for each device. This is true if
380 SPL_OF_CONTROL is enabled and not SPL_OF_PLATDATA
384 config SPL_OF_PLATDATA_PARENT
385 bool "Support parent information in devices"
388 Generally it is useful to be able to access the parent of a device
389 with of-platdata. To save space this can be disabled, but in that
390 case dev_get_parent() will always return NULL;
392 config SPL_OF_PLATDATA_INST
393 bool "Declare devices at build time"
395 Declare devices as udevice instances so that they do not need to be
396 bound when U-Boot starts. This can save time and code space.
398 config SPL_OF_PLATDATA_NO_BIND
399 bool "Don't allow run-time binding of devices"
400 depends on SPL_OF_PLATDATA_INST
403 This removes the ability to bind devices at run time, thus saving
404 some code space in U-Boot. This can be disabled if binding is needed,
405 at the code of some code size increase.
407 config SPL_OF_PLATDATA_RT
408 bool "Use a separate struct for device runtime data"
409 depends on SPL_OF_PLATDATA_INST
412 For systems running SPL from read-only memory it is convenient to
413 separate out the runtime information, so that the devices don't need
414 to be copied before being used. This moves the read-write parts of
415 struct udevice (at present just the flags) into a separate struct,
416 which is allocated at runtime.
418 config SPL_OF_PLATDATA_DRIVER_RT
421 Use a separate struct for driver runtime data.
423 This enables the driver_rt information, used with of-platdata when
424 of-platdata-inst is not used. It allows finding devices by their
432 Indicates that a real devicetree is available which can be accessed
433 at runtime. This means that dev_read_...() functions can be used to
434 read data from the devicetree for each device. This is true if
435 TPL_OF_CONTROL is enabled and not TPL_OF_PLATDATA
437 config TPL_OF_PLATDATA
438 bool "Generate platform data for use in TPL"
439 depends on TPL_OF_CONTROL
441 select TPL_OF_PLATDATA_DRIVER_RT if !TPL_OF_PLATDATA_INST
443 For very constrained SPL environments the overhead of decoding
444 device tree nodes and converting their contents into platform data
445 is too large. This overhead includes libfdt code as well as the
446 device tree contents itself. The latter is fairly compact, but the
447 former can add 3KB or more to a Thumb 2 Image.
449 This option enables generation of platform data from the device
450 tree as C code. This code creates devices using U_BOOT_DRVINFO()
451 declarations. The benefit is that it allows driver code to access
452 the platform data directly in C structures, avoidin the libfdt
455 This option works by generating C structure declarations for each
456 compatible string, then adding platform data and U_BOOT_DRVINFO
457 declarations for each node. See of-plat.txt for more information.
461 config TPL_OF_PLATDATA_PARENT
462 bool "Support parent information in devices"
465 Generally it is useful to be able to access the parent of a device
466 with of-platdata. To save space this can be disabled, but in that
467 case dev_get_parent() will always return NULL;
469 config TPL_OF_PLATDATA_INST
470 bool "Declare devices at build time"
473 Declare devices as udevice instances so that they do not need to be
474 bound when U-Boot starts. This can save time and code space.
476 config TPL_OF_PLATDATA_NO_BIND
477 bool "Don't allow run-time binding of devices"
478 depends on TPL_OF_PLATDATA_INST
481 This removes the ability to bind devices at run time, thus saving
482 some code space in U-Boot. This can be disabled if binding is needed,
483 at the code of some code size increase.
485 config TPL_OF_PLATDATA_RT
486 bool "Use a separate struct for device runtime data"
487 depends on TPL_OF_PLATDATA_INST
490 For systems running TPL from read-only memory it is convenient to
491 separate out the runtime information, so that the devices don't need
492 to be copied before being used. This moves the read-write parts of
493 struct udevice (at present just the flags) into a separate struct,
494 which is allocated at runtime.
496 config TPL_OF_PLATDATA_DRIVER_RT
499 Use a separate struct for driver runtime data.
501 This enables the driver_rt information, used with of-platdata when
502 of-platdata-inst is not used. It allows finding devices by their