5 config SUPPORT_OF_CONTROL
22 config BINMAN_STANDALONE_FDT
27 This option tells U-Boot build system that a standalone device tree
28 source is explicitly required when using binman to package U-Boot.
30 This is not necessary in a common scenario where a device tree source
31 that contains the binman node is provided in the arch/<arch>/dts
32 directory for a specific board. Such device tree sources are built for
33 OF_SEPARATE or OF_EMBED. However for a scenario like the board device
34 tree blob is not provided in the U-Boot build tree, but fed to U-Boot
35 in the runtime, e.g.: in the OF_BOARD case that it is passed by
36 a prior stage bootloader. For such scenario, a standalone device tree
37 blob containing binman node to describe how to package U-Boot should
38 be provided explicitly.
40 menu "Device Tree Control"
41 depends on SUPPORT_OF_CONTROL
44 bool "Run-time configuration via Device Tree"
46 select OF_LIBFDT if !OF_PLATDATA
47 select OF_REAL if !OF_PLATDATA
49 This feature provides for run-time configuration of U-Boot
50 via a flattened device tree.
55 Indicates that a real devicetree is available which can be accessed
56 at runtime. This means that dev_read_...() functions can be used to
57 read data from the devicetree for each device. This is true if
58 OF_CONTROL is enabled in U-Boot proper.
61 bool "Board-specific manipulation of Device Tree"
63 In certain circumstances it is necessary to be able to modify
64 U-Boot's device tree (e.g. to delete device from it). This option
65 make the Device Tree writeable and provides a board-specific
66 "board_fix_fdt" callback (called during pre-relocation time), which
67 enables the board initialization to modifiy the Device Tree. The
68 modified copy is subsequently used by U-Boot after relocation.
71 bool "Enable run-time configuration via Device Tree in SPL"
72 depends on SPL && OF_CONTROL
73 select SPL_OF_LIBFDT if !SPL_OF_PLATDATA
74 select SPL_OF_REAL if !SPL_OF_PLATDATA
76 Some boards use device tree in U-Boot but only have 4KB of SRAM
77 which is not enough to support device tree. Disable this option to
78 allow such boards to be supported by U-Boot SPL.
81 bool "Enable run-time configuration via Device Tree in TPL"
82 depends on TPL && OF_CONTROL
83 select TPL_OF_LIBFDT if !TPL_OF_PLATDATA
84 select TPL_OF_REAL if !TPL_OF_PLATDATA
86 Some boards use device tree in U-Boot but only have 4KB of SRAM
87 which is not enough to support device tree. Enable this option to
88 allow such boards to be supported by U-Boot TPL.
91 bool "Enable use of a live tree"
92 depends on DM && OF_CONTROL
94 Normally U-Boot uses a flat device tree which saves space and
95 avoids the need to unpack the tree before use. However a flat
96 tree does not support modification from within U-Boot since it
97 can invalidate driver-model device tree offsets. This option
98 enables a live tree which is available after relocation,
99 and can be adjusted as needed.
102 prompt "Provider of DTB for DT control"
103 depends on OF_CONTROL
106 bool "Separate DTB for DT control"
109 If this option is enabled, the device tree will be built and
110 placed as a separate u-boot.dtb file alongside the U-Boot image.
113 bool "Embedded DTB for DT control"
115 If this option is enabled, the device tree will be picked up and
116 built into the U-Boot image. This is suitable for local debugging
117 and development only and is not recommended for production devices.
118 Boards in the mainline U-Boot tree should not use it.
121 bool "Provided by the board (e.g a previous loader) at runtime"
124 If this option is enabled, the device tree will be provided by
125 the board at runtime if the board supports it, instead of being
126 bundled with the image.
129 bool "Host filed DTB for DT control"
132 If this option is enabled, DTB will be read from a file on startup.
133 This is only useful for Sandbox. Use the -d flag to U-Boot to
134 specify the file to read.
138 config DEFAULT_DEVICE_TREE
139 string "Default Device Tree for DT control"
140 depends on OF_CONTROL
142 This option specifies the default Device Tree used for DT control.
143 It can be overridden from the command line:
144 $ make DEVICE_TREE=<device-tree-name>
147 string "List of device tree files to include for DT control"
148 depends on SPL_LOAD_FIT || MULTI_DTB_FIT
149 default DEFAULT_DEVICE_TREE
151 This option specifies a list of device tree files to use for DT
152 control. These will be packaged into a FIT. At run-time, U-boot
153 or SPL will select the correct DT to use by examining the
154 hardware (e.g. reading a board ID value). This is a list of
155 device tree files (without the directory or .dtb suffix)
156 separated by <space>.
158 config OF_OVERLAY_LIST
159 string "List of device tree overlays to include for DT control"
160 depends on SPL_LOAD_FIT_APPLY_OVERLAY
162 This option specifies a list of device tree overlays to use for DT
163 control. This option can then be used by a FIT generator to include
164 the overlays in the FIT image.
167 prompt "OF LIST compression"
168 depends on MULTI_DTB_FIT
169 default MULTI_DTB_FIT_NO_COMPRESSION
171 config MULTI_DTB_FIT_LZO
173 depends on SYS_MALLOC_F
176 Compress the FIT image containing the DTBs available for the SPL
177 using LZO compression. (requires lzop on host).
179 config MULTI_DTB_FIT_GZIP
181 depends on SYS_MALLOC_F
184 Compress the FIT image containing the DTBs available for the SPL
185 using GZIP compression. (requires gzip on host)
187 config MULTI_DTB_FIT_NO_COMPRESSION
188 bool "No compression"
190 Do not compress the FIT image containing the DTBs available for the SPL.
191 Use this options only if LZO is not available and the DTBs are very small.
195 prompt "Location of uncompressed DTBs"
196 depends on (MULTI_DTB_FIT_GZIP || MULTI_DTB_FIT_LZO)
197 default MULTI_DTB_FIT_DYN_ALLOC if SYS_MALLOC_F
199 config MULTI_DTB_FIT_DYN_ALLOC
200 bool "Dynamically allocate the memory"
201 depends on SYS_MALLOC_F
203 config MULTI_DTB_FIT_USER_DEFINED_AREA
204 bool "User-defined location"
207 config MULTI_DTB_FIT_UNCOMPRESS_SZ
208 hex "Size of memory reserved to uncompress the DTBs"
209 depends on (MULTI_DTB_FIT_GZIP || MULTI_DTB_FIT_LZO)
212 This is the size of this area where the DTBs are uncompressed.
213 If this area is dynamically allocated, make sure that
214 SYS_MALLOC_F_LEN is big enough to contain it.
216 config MULTI_DTB_FIT_USER_DEF_ADDR
217 hex "Address of memory where dtbs are uncompressed"
218 depends on MULTI_DTB_FIT_USER_DEFINED_AREA
220 the FIT image containing the DTBs is uncompressed in an area defined
221 at compilation time. This is the address of this area. It must be
222 aligned on 2-byte boundary.
225 bool "Support swapping dtbs at a later point in boot"
226 depends on MULTI_DTB_FIT
228 It is possible during initial boot you may need to use a generic
229 dtb until you can fully determine the board your running on. This
230 config allows boards to implement a function at a later point
231 during boot to switch to the "correct" dtb.
234 bool "Support embedding several DTBs in a FIT image for u-boot"
236 This option provides hooks to allow U-boot to parse an
237 appended FIT image and enable board specific code to then select
238 the correct DTB to be used. Use this if you need to support
239 multiple DTBs but don't use the SPL.
242 config SPL_MULTI_DTB_FIT
243 depends on SPL_LOAD_FIT && SPL_OF_REAL
244 bool "Support embedding several DTBs in a FIT image for the SPL"
246 This option provides the SPL with the ability to select its own
247 DTB at runtime from an appended FIT image containing several DTBs.
248 This allows using the same SPL binary on multiple platforms.
249 The primary purpose is to handle different versions of
250 the same platform without tweaking the platform code if the
251 differences can be expressed in the DTBs (common examples are: bus
252 capabilities, pad configurations).
255 string "List of device tree files to include for DT control in SPL"
256 depends on SPL_MULTI_DTB_FIT
259 This option specifies a list of device tree files to use for DT
260 control in the SPL. These will be packaged into a FIT. At run-time,
261 the SPL will select the correct DT to use by examining the
262 hardware (e.g. reading a board ID value). This is a list of
263 device tree files (without the directory or .dtb suffix)
264 separated by <space>.
267 prompt "SPL OF LIST compression"
268 depends on SPL_MULTI_DTB_FIT
269 default SPL_MULTI_DTB_FIT_LZO
271 config SPL_MULTI_DTB_FIT_LZO
273 depends on SYS_MALLOC_F
276 Compress the FIT image containing the DTBs available for the SPL
277 using LZO compression. (requires lzop on host).
279 config SPL_MULTI_DTB_FIT_GZIP
281 depends on SYS_MALLOC_F
284 Compress the FIT image containing the DTBs available for the SPL
285 using GZIP compression. (requires gzip on host)
287 config SPL_MULTI_DTB_FIT_NO_COMPRESSION
288 bool "No compression"
290 Do not compress the FIT image containing the DTBs available for the SPL.
291 Use this options only if LZO is not available and the DTBs are very small.
295 prompt "Location of uncompressed DTBs"
296 depends on (SPL_MULTI_DTB_FIT_GZIP || SPL_MULTI_DTB_FIT_LZO)
297 default SPL_MULTI_DTB_FIT_DYN_ALLOC if SYS_MALLOC_F
299 config SPL_MULTI_DTB_FIT_DYN_ALLOC
300 bool "Dynamically allocate the memory"
301 depends on SYS_MALLOC_F
303 config SPL_MULTI_DTB_FIT_USER_DEFINED_AREA
304 bool "User-defined location"
307 config SPL_MULTI_DTB_FIT_UNCOMPRESS_SZ
308 hex "Size of memory reserved to uncompress the DTBs"
309 depends on (SPL_MULTI_DTB_FIT_GZIP || SPL_MULTI_DTB_FIT_LZO)
312 This is the size of this area where the DTBs are uncompressed.
313 If this area is dynamically allocated, make sure that
314 SPL_SYS_MALLOC_F_LEN is big enough to contain it.
316 config SPL_MULTI_DTB_FIT_USER_DEF_ADDR
317 hex "Address of memory where dtbs are uncompressed"
318 depends on SPL_MULTI_DTB_FIT_USER_DEFINED_AREA
320 the FIT image containing the DTBs is uncompressed in an area defined
321 at compilation time. This is the address of this area. It must be
322 aligned on 2-byte boundary.
324 config OF_SPL_REMOVE_PROPS
325 string "List of device tree properties to drop for SPL"
326 depends on SPL_OF_CONTROL
327 default "interrupt-parent interrupts" if SPL_PINCTRL && SPL_CLK
328 default "clocks clock-names interrupt-parent interrupts" if SPL_PINCTRL
329 default "pinctrl-0 pinctrl-names interrupt-parent interrupts" if SPL_CLK
330 default "pinctrl-0 pinctrl-names clocks clock-names interrupt-parent interrupts"
332 Since SPL normally runs in a reduced memory space, the device tree
333 is cut down to only what is needed to load and start U-Boot. Only
334 nodes marked with the property "u-boot,dm-pre-reloc" will be
335 included. In addition, some properties are not used by U-Boot and
336 can be discarded. This option defines the list of properties to
339 config OF_DTB_PROPS_REMOVE
340 bool "Enable removal of device tree properties"
341 depends on OF_CONTROL
343 Some boards have restricted amount of storage for U-Boot image.
344 If the generated binary doesn't fit into available image storage,
345 the built-in device tree could probably be cut down by removing
346 some not required device tree properties to reduce the image size.
347 Enable this option and define the properties to be removed in the
348 CONFIG_OF_REMOVE_PROPS list. Do not enable this option if you must
349 pass the built-in DTB directly to the kernel!
351 config OF_REMOVE_PROPS
352 string "List of device tree properties to drop"
353 depends on OF_DTB_PROPS_REMOVE
354 default "interrupt-parent interrupts" if PINCTRL
356 Some properties are not used by U-Boot and can be discarded.
357 This option defines the list of properties to discard.
359 config SPL_OF_PLATDATA
360 bool "Generate platform data for use in SPL"
361 depends on SPL_OF_CONTROL
363 select SPL_OF_PLATDATA_DRIVER_RT if !SPL_OF_PLATDATA_INST
365 For very constrained SPL environments the overhead of decoding
366 device tree nodes and converting their contents into platform data
367 is too large. This overhead includes libfdt code as well as the
368 device tree contents itself. The latter is fairly compact, but the
369 former can add 3KB or more to a Thumb 2 Image.
371 This option enables generation of platform data from the device
372 tree as C code. This code creates devices using U_BOOT_DRVINFO()
373 declarations. The benefit is that it allows driver code to access
374 the platform data directly in C structures, avoidin the libfdt
377 This option works by generating C structure declarations for each
378 compatible string, then adding platform data and U_BOOT_DRVINFO
379 declarations for each node. See of-plat.txt for more information.
384 Indicates that a real devicetree is available which can be accessed
385 at runtime. This means that dev_read_...() functions can be used to
386 read data from the devicetree for each device. This is true if
387 SPL_OF_CONTROL is enabled and not SPL_OF_PLATDATA
391 config SPL_OF_PLATDATA_PARENT
392 bool "Support parent information in devices"
395 Generally it is useful to be able to access the parent of a device
396 with of-platdata. To save space this can be disabled, but in that
397 case dev_get_parent() will always return NULL;
399 config SPL_OF_PLATDATA_INST
400 bool "Declare devices at build time"
402 Declare devices as udevice instances so that they do not need to be
403 bound when U-Boot starts. This can save time and code space.
405 config SPL_OF_PLATDATA_NO_BIND
406 bool "Don't allow run-time binding of devices"
407 depends on SPL_OF_PLATDATA_INST
410 This removes the ability to bind devices at run time, thus saving
411 some code space in U-Boot. This can be disabled if binding is needed,
412 at the code of some code size increase.
414 config SPL_OF_PLATDATA_RT
415 bool "Use a separate struct for device runtime data"
416 depends on SPL_OF_PLATDATA_INST
419 For systems running SPL from read-only memory it is convenient to
420 separate out the runtime information, so that the devices don't need
421 to be copied before being used. This moves the read-write parts of
422 struct udevice (at present just the flags) into a separate struct,
423 which is allocated at runtime.
425 config SPL_OF_PLATDATA_DRIVER_RT
428 Use a separate struct for driver runtime data.
430 This enables the driver_rt information, used with of-platdata when
431 of-platdata-inst is not used. It allows finding devices by their
439 Indicates that a real devicetree is available which can be accessed
440 at runtime. This means that dev_read_...() functions can be used to
441 read data from the devicetree for each device. This is true if
442 TPL_OF_CONTROL is enabled and not TPL_OF_PLATDATA
444 config TPL_OF_PLATDATA
445 bool "Generate platform data for use in TPL"
446 depends on TPL_OF_CONTROL
448 select TPL_OF_PLATDATA_DRIVER_RT if !TPL_OF_PLATDATA_INST
450 For very constrained SPL environments the overhead of decoding
451 device tree nodes and converting their contents into platform data
452 is too large. This overhead includes libfdt code as well as the
453 device tree contents itself. The latter is fairly compact, but the
454 former can add 3KB or more to a Thumb 2 Image.
456 This option enables generation of platform data from the device
457 tree as C code. This code creates devices using U_BOOT_DRVINFO()
458 declarations. The benefit is that it allows driver code to access
459 the platform data directly in C structures, avoidin the libfdt
462 This option works by generating C structure declarations for each
463 compatible string, then adding platform data and U_BOOT_DRVINFO
464 declarations for each node. See of-plat.txt for more information.
468 config TPL_OF_PLATDATA_PARENT
469 bool "Support parent information in devices"
472 Generally it is useful to be able to access the parent of a device
473 with of-platdata. To save space this can be disabled, but in that
474 case dev_get_parent() will always return NULL;
476 config TPL_OF_PLATDATA_INST
477 bool "Declare devices at build time"
480 Declare devices as udevice instances so that they do not need to be
481 bound when U-Boot starts. This can save time and code space.
483 config TPL_OF_PLATDATA_NO_BIND
484 bool "Don't allow run-time binding of devices"
485 depends on TPL_OF_PLATDATA_INST
488 This removes the ability to bind devices at run time, thus saving
489 some code space in U-Boot. This can be disabled if binding is needed,
490 at the code of some code size increase.
492 config TPL_OF_PLATDATA_RT
493 bool "Use a separate struct for device runtime data"
494 depends on TPL_OF_PLATDATA_INST
497 For systems running TPL from read-only memory it is convenient to
498 separate out the runtime information, so that the devices don't need
499 to be copied before being used. This moves the read-write parts of
500 struct udevice (at present just the flags) into a separate struct,
501 which is allocated at runtime.
503 config TPL_OF_PLATDATA_DRIVER_RT
506 Use a separate struct for driver runtime data.
508 This enables the driver_rt information, used with of-platdata when
509 of-platdata-inst is not used. It allows finding devices by their