2 # For a description of the syntax of this configuration file,
3 # see the file Documentation/kbuild/kconfig-language.txt in the
4 # Linux kernel source tree.
6 mainmenu "U-Boot $(UBOOTVERSION) Configuration"
8 comment "Compiler: $(CC_VERSION_TEXT)"
10 source "scripts/Kconfig.include"
12 # Allow defaults in arch-specific code to override any given here
20 This option cannot be enabled. It is used as dependency
21 for broken and incomplete features.
26 This option cannot be enabled. It it used as a dependency for
27 code that relies on deprecated features that will be removed and
28 the conversion deadline has passed.
31 string "Local version - append to U-Boot release"
33 Append an extra string to the end of your U-Boot version.
34 This will show up in your boot log, for example.
35 The string you set here will be appended after the contents of
36 any files with a filename matching localversion* in your
37 object and source tree, in that order. Your total string can
38 be a maximum of 64 characters.
40 config LOCALVERSION_AUTO
41 bool "Automatically append version information to the version string"
44 This will try to automatically determine if the current tree is a
45 release tree by looking for Git tags that belong to the current
48 A string of the format -gxxxxxxxx will be added to the localversion
49 if a Git-based tree is found. The string generated by this will be
50 appended after any matching localversion* files, and after the value
51 set in CONFIG_LOCALVERSION.
53 (The actual string used here is the first eight characters produced
54 by running the command:
56 $ git rev-parse --verify HEAD
58 which is done within the script "scripts/setlocalversion".)
60 config CC_OPTIMIZE_FOR_SIZE
61 bool "Optimize for size"
64 Enabling this option will pass "-Os" instead of "-O2" to gcc
65 resulting in a smaller U-Boot image.
67 This option is enabled by default for U-Boot.
69 config OPTIMIZE_INLINING
70 bool "Allow compiler to uninline functions marked 'inline' in full U-Boot"
73 This option determines if U-Boot forces gcc to inline the functions
74 developers have marked 'inline'. Doing so takes away freedom from gcc to
75 do what it thinks is best, which is desirable in some cases for size
78 config SPL_OPTIMIZE_INLINING
79 bool "Allow compiler to uninline functions marked 'inline' in SPL"
83 This option determines if U-Boot forces gcc to inline the functions
84 developers have marked 'inline'. Doing so takes away freedom from gcc to
85 do what it thinks is best, which is desirable in some cases for size
88 config TPL_OPTIMIZE_INLINING
89 bool "Allow compiler to uninline functions marked 'inline' in TPL"
93 This option determines if U-Boot forces gcc to inline the functions
94 developers have marked 'inline'. Doing so takes away freedom from gcc to
95 do what it thinks is best, which is desirable in some cases for size
99 bool "Enable code coverage analysis"
102 Enabling this option will pass "--coverage" to gcc to compile
103 and link code instrumented for coverage analysis.
105 config CC_HAS_ASM_INLINE
106 def_bool $(success,echo 'void foo(void) { asm inline (""); }' | $(CC) -x c - -c -o /dev/null)
108 config DISTRO_DEFAULTS
109 bool "Select defaults suitable for booting general purpose Linux distributions"
111 select CMDLINE_EDITING
112 select CMD_BOOTI if ARM64
113 select CMD_BOOTZ if ARM && !ARM64
114 select CMD_DHCP if CMD_NET
115 select CMD_ENV_EXISTS
119 select CMD_FS_GENERIC
120 select CMD_PART if PARTITIONS
121 select CMD_PING if CMD_NET
122 select CMD_PXE if NET
124 select ENV_VARS_UBOOT_CONFIG
126 select SUPPORT_RAW_INITRD
130 imply USE_BOOTCOMMAND
132 Select this to enable various options and commands which are suitable
133 for building u-boot for booting general purpose Linux distributions.
135 config ENV_VARS_UBOOT_CONFIG
136 bool "Add arch, board, vendor and soc variables to default environment"
138 Define this in order to add variables describing the
139 U-Boot build configuration to the default environment.
140 These will be named arch, cpu, board, vendor, and soc.
141 Enabling this option will cause the following to be defined:
149 int "Number of DRAM banks"
150 default 1 if ARCH_SUNXI || ARCH_OWL
153 This defines the number of DRAM banks.
155 config SYS_BOOT_GET_CMDLINE
156 bool "Enable kernel command line setup"
158 Enables allocating and saving kernel cmdline in space between
159 "bootm_low" and "bootm_low" + BOOTMAPSZ.
161 config SYS_BOOT_GET_KBD
162 bool "Enable kernel board information setup"
164 Enables allocating and saving a kernel copy of the bd_info in
165 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
168 bool "Enable malloc() pool before relocation"
172 Before relocation, memory is very limited on many platforms. Still,
173 we can provide a small malloc() pool if needed. Driver model in
174 particular needs this to operate, so that it can allocate the
175 initial serial device and any others that are needed.
177 config SYS_MALLOC_F_LEN
178 hex "Size of malloc() pool before relocation"
179 depends on SYS_MALLOC_F
180 default 0x1000 if AM33XX
181 default 0x2800 if SANDBOX
182 default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
183 ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
184 ARCH_LS1012A || ARCH_LS1021A || ARCH_LS1043A || \
185 ARCH_LS1046A || ARCH_QEMU)
188 Before relocation, memory is very limited on many platforms. Still,
189 we can provide a small malloc() pool if needed. Driver model in
190 particular needs this to operate, so that it can allocate the
191 initial serial device and any others that are needed.
193 config SYS_MALLOC_LEN
194 hex "Define memory for Dynamic allocation"
195 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
196 default 0x2000000 if ARCH_ROCKCHIP
198 This defines memory to be allocated for Dynamic allocation
199 TODO: Use for other architectures
201 config SPL_SYS_MALLOC_F_LEN
202 hex "Size of malloc() pool in SPL before relocation"
203 depends on SYS_MALLOC_F && SPL
204 default 0x2800 if RCAR_GEN3
205 default SYS_MALLOC_F_LEN
207 Before relocation, memory is very limited on many platforms. Still,
208 we can provide a small malloc() pool if needed. Driver model in
209 particular needs this to operate, so that it can allocate the
210 initial serial device and any others that are needed.
212 config TPL_SYS_MALLOC_F_LEN
213 hex "Size of malloc() pool in TPL before relocation"
214 depends on SYS_MALLOC_F && TPL
215 default SYS_MALLOC_F_LEN
217 Before relocation, memory is very limited on many platforms. Still,
218 we can provide a small malloc() pool if needed. Driver model in
219 particular needs this to operate, so that it can allocate the
220 initial serial device and any others that are needed.
223 bool "Configure standard U-Boot features (expert users)"
226 This option allows certain base U-Boot options and settings
227 to be disabled or tweaked. This is for specialized
228 environments which can tolerate a "non-standard" U-Boot.
229 Use this only if you really know what you are doing.
232 config SYS_MALLOC_CLEAR_ON_INIT
233 bool "Init with zeros the memory reserved for malloc (slow)"
236 This setting is enabled by default. The reserved malloc
237 memory is initialized with zeros, so first malloc calls
238 will return the pointer to the zeroed memory. But this
241 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
242 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
243 Then the boot time can be significantly reduced.
245 When disabling this, please check if malloc calls, maybe
246 should be replaced by calloc - if one expects zeroed memory.
248 config SYS_MALLOC_DEFAULT_TO_INIT
249 bool "Default malloc to init while reserving the memory for it"
252 It may happen that one needs to move the dynamic allocation
253 from one to another memory range, eg. when moving the malloc
254 from the limited static to a potentially large dynamic (DDR)
257 If so then on top of setting the updated memory aside one
258 needs to bring the malloc init.
260 If such a scenario is sought choose yes.
263 bool "Enable debug information for tools"
265 Enable generation of debug information for tools such as mkimage.
266 This can be used for debugging purposes. With debug information
267 it is possible to set breakpoints on particular lines, single-step
268 debug through the source code, etc.
273 bool "64bit physical address support"
275 Say Y here to support 64bit physical memory address.
276 This can be used not only for 64bit SoCs, but also for
277 large physical address extension on 32bit SoCs.
280 bool "Build U-Boot as BIOS replacement"
283 This option allows to build a ROM version of U-Boot.
284 The build process generally requires several binary blobs
285 which are not shipped in the U-Boot source tree.
286 Please, see doc/arch/x86.rst for details.
289 string "SPL image used in the combined SPL+U-Boot image"
290 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
291 default "spl/u-boot-spl.bin"
294 Select the SPL build target that shall be generated by the SPL
295 build process (default spl/u-boot-spl.bin). This image will be
296 used to generate a combined image with SPL and main U-Boot
297 proper as one single image.
300 string "Build target special images"
301 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
302 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
303 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
304 default "u-boot-elf.srec" if RCAR_GEN3
305 default "u-boot.itb" if SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
306 ARCH_SUNXI || RISCV || ARCH_ZYNQMP)
307 default "u-boot.kwb" if ARCH_KIRKWOOD
308 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
309 default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
311 Some SoCs need special image types (e.g. U-Boot binary
312 with a special header) as build targets. By defining
313 CONFIG_BUILD_TARGET in the SoC / board header, this
314 special image will be automatically built upon calling
317 config SYS_CUSTOM_LDSCRIPT
318 bool "Use a custom location for the U-Boot linker script"
320 Normally when linking U-Boot we will look in the board directory,
321 the CPU directory and finally the "cpu" directory of the architecture
322 for the ile "u-boot.lds" and use that as our linker. However, in
323 some cases we need to provide a different linker script. To do so,
324 enable this option and then provide the location under
328 depends on SYS_CUSTOM_LDSCRIPT
329 string "Custom ldscript location"
331 Path within the source tree to the linker script to use for the
334 config ERR_PTR_OFFSET
338 Some U-Boot pointers have redundant information, so we can use a
339 scheme where we can return either an error code or a pointer with the
340 same return value. The default implementation just casts the pointer
341 to a number, however, this may fail on platforms where the end of the
342 address range is used for valid pointers (e.g. 0xffffff00 is a valid
343 heap pointer in socfpga SPL).
344 For such platforms, this value provides an upper range of those error
345 pointer values - up to 'MAX_ERRNO' bytes below this value must be
346 unused/invalid addresses.
348 config PLATFORM_ELFENTRY
350 default "__start" if MIPS
353 endmenu # General setup
357 config ANDROID_BOOT_IMAGE
358 bool "Enable support for Android Boot Images"
359 default y if FASTBOOT
361 This enables support for booting images which use the Android
365 bool "Support Flattened Image Tree"
369 This option allows you to boot the new uImage structure,
370 Flattened Image Tree. FIT is formally a FDT, which can include
371 images of various types (kernel, FDT blob, ramdisk, etc.)
372 in a single blob. To boot this new uImage structure,
373 pass the address of the blob to the "bootm" command.
374 FIT is very flexible, supporting compression, multiple images,
375 multiple configurations, verification through hashing and also
376 verified boot (secure boot using RSA).
380 config FIT_EXTERNAL_OFFSET
381 hex "FIT external data offset"
384 This specifies a data offset in fit image.
385 The offset is from data payload offset to the beginning of
386 fit image header. When specifies a offset, specific data
387 could be put in the hole between data payload and fit image
388 header, such as CSF data on i.MX platform.
390 config FIT_ENABLE_SHA256_SUPPORT
391 bool "Support SHA256 checksum of FIT image contents"
395 Enable this to support SHA256 checksum of FIT image contents. A
396 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
397 the image contents have not been corrupted.
399 config FIT_ENABLE_SHA384_SUPPORT
400 bool "Support SHA384 checksum of FIT image contents"
404 Enable this to support SHA384 checksum of FIT image contents. A
405 SHA384 checksum is a 384-bit (48-byte) hash value used to check that
406 the image contents have not been corrupted. Use this for the highest
409 config FIT_ENABLE_SHA512_SUPPORT
410 bool "Support SHA512 checksum of FIT image contents"
414 Enable this to support SHA512 checksum of FIT image contents. A
415 SHA512 checksum is a 512-bit (64-byte) hash value used to check that
416 the image contents have not been corrupted.
419 bool "Enable signature verification of FIT uImages"
424 select IMAGE_SIGN_INFO
426 This option enables signature verification of FIT uImages,
427 using a hash signed and verified using RSA. If
428 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
429 hashing is available using hardware, then the RSA library will use
430 it. See doc/uImage.FIT/signature.txt for more details.
432 WARNING: When relying on signed FIT images with a required signature
433 check the legacy image format is disabled by default, so that
434 unsigned images cannot be loaded. If a board needs the legacy image
435 format support in this case, enable it using
436 CONFIG_LEGACY_IMAGE_FORMAT.
438 config FIT_SIGNATURE_MAX_SIZE
439 hex "Max size of signed FIT structures"
440 depends on FIT_SIGNATURE
443 This option sets a max size in bytes for verified FIT uImages.
444 A sane value of 256MB protects corrupted DTB structures from overlapping
445 device memory. Assure this size does not extend past expected storage
448 config FIT_ENABLE_RSASSA_PSS_SUPPORT
449 bool "Support rsassa-pss signature scheme of FIT image contents"
450 depends on FIT_SIGNATURE
453 Enable this to support the pss padding algorithm as described
454 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
457 bool "Enable ciphering data in a FIT uImages"
461 Enable the feature of data ciphering/unciphering in the tool mkimage
462 and in the u-boot support of the FIT image.
465 bool "Show verbose messages when FIT images fail"
467 Generally a system will have valid FIT images so debug messages
468 are a waste of code space. If you are debugging your images then
469 you can enable this option to get more verbose information about
472 config FIT_BEST_MATCH
473 bool "Select the best match for the kernel device tree"
475 When no configuration is explicitly selected, default to the
476 one whose fdt's compatibility field best matches that of
477 U-Boot itself. A match is considered "best" if it matches the
478 most specific compatibility entry of U-Boot's fdt's root node.
479 The order of entries in the configuration's fdt is ignored.
481 config FIT_IMAGE_POST_PROCESS
482 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
483 depends on TI_SECURE_DEVICE
485 Allows doing any sort of manipulation to blobs after they got extracted
486 from FIT images like stripping off headers or modifying the size of the
487 blob, verification, authentication, decryption etc. in a platform or
488 board specific way. In order to use this feature a platform or board-
489 specific implementation of board_fit_image_post_process() must be
490 provided. Also, anything done during this post-processing step would
491 need to be comprehended in how the images were prepared before being
492 injected into the FIT creation (i.e. the blobs would have been pre-
493 processed before being added to the FIT image).
498 bool "Support Flattened Image Tree within SPL"
503 bool "Support FIT printing within SPL"
506 Support printing the content of the fitImage in a verbose manner in SPL.
508 config SPL_FIT_SIGNATURE
509 bool "Enable signature verification of FIT firmware within SPL"
512 select SPL_CRYPTO_SUPPORT
513 select SPL_HASH_SUPPORT
515 select SPL_RSA_VERIFY
516 select SPL_IMAGE_SIGN_INFO
519 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
522 Normally with the SPL framework a legacy image is generated as part
523 of the build. This contains U-Boot along with information as to
524 where it should be loaded. This option instead enables generation
525 of a FIT (Flat Image Tree) which provides more flexibility. In
526 particular it can handle selecting from multiple device tree
527 and passing the correct one to U-Boot.
529 config SPL_LOAD_FIT_ADDRESS
530 hex "load address of fit image"
531 depends on SPL_LOAD_FIT
534 Specify the load address of the fit image that will be loaded
537 config SPL_LOAD_FIT_APPLY_OVERLAY
538 bool "Enable SPL applying DT overlays from FIT"
539 depends on SPL_LOAD_FIT
540 select OF_LIBFDT_OVERLAY
542 The device tree is loaded from the FIT image. Allow the SPL is to
543 also load device-tree overlays from the FIT image an apply them
544 over the device tree.
546 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
547 depends on SPL_LOAD_FIT_APPLY_OVERLAY
549 hex "size of temporary buffer used to load the overlays"
551 The size of the area where the overlays will be loaded and
552 uncompress. Must be at least as large as biggest overlay
555 config SPL_LOAD_FIT_FULL
556 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
559 Normally with the SPL framework a legacy image is generated as part
560 of the build. This contains U-Boot along with information as to
561 where it should be loaded. This option instead enables generation
562 of a FIT (Flat Image Tree) which provides more flexibility. In
563 particular it can handle selecting from multiple device tree
564 and passing the correct one to U-Boot.
566 config SPL_FIT_IMAGE_POST_PROCESS
567 bool "Enable post-processing of FIT artifacts after loading by the SPL"
568 depends on SPL_LOAD_FIT
570 Allows doing any sort of manipulation to blobs after they got extracted
571 from the U-Boot FIT image like stripping off headers or modifying the
572 size of the blob, verification, authentication, decryption etc. in a
573 platform or board specific way. In order to use this feature a platform
574 or board-specific implementation of board_fit_image_post_process() must
575 be provided. Also, anything done during this post-processing step would
576 need to be comprehended in how the images were prepared before being
577 injected into the FIT creation (i.e. the blobs would have been pre-
578 processed before being added to the FIT image).
580 config SPL_FIT_SOURCE
581 string ".its source file for U-Boot FIT image"
584 Specifies a (platform specific) FIT source file to generate the
585 U-Boot FIT image. This could specify further image to load and/or
588 config SPL_FIT_GENERATOR
589 string ".its file generator script for U-Boot FIT image"
591 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
592 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
593 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
594 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
596 Specifies a (platform specific) script file to generate the FIT
597 source file used to build the U-Boot FIT image file. This gets
598 passed a list of supported device tree file stub names to
599 include in the generated image.
605 config LEGACY_IMAGE_FORMAT
606 bool "Enable support for the legacy image format"
607 default y if !FIT_SIGNATURE
609 This option enables the legacy image format. It is enabled by
610 default for backward compatibility, unless FIT_SIGNATURE is
611 set where it is disabled so that unsigned images cannot be
612 loaded. If a board needs the legacy image format support in this
613 case, enable it here.
615 config OF_BOARD_SETUP
616 bool "Set up board-specific details in device tree before boot"
619 This causes U-Boot to call ft_board_setup() before booting into
620 the Operating System. This function can set up various
621 board-specific information in the device tree for use by the OS.
622 The device tree is then passed to the OS.
624 config OF_SYSTEM_SETUP
625 bool "Set up system-specific details in device tree before boot"
628 This causes U-Boot to call ft_system_setup() before booting into
629 the Operating System. This function can set up various
630 system-specific information in the device tree for use by the OS.
631 The device tree is then passed to the OS.
633 config OF_STDOUT_VIA_ALIAS
634 bool "Update the device-tree stdout alias from U-Boot"
637 This uses U-Boot's serial alias from the aliases node to update
638 the device tree passed to the OS. The "linux,stdout-path" property
639 in the chosen node is set to point to the correct serial node.
640 This option currently references CONFIG_CONS_INDEX, which is
641 incorrect when used with device tree as this option does not
642 exist / should not be used.
644 config SYS_EXTRA_OPTIONS
645 string "Extra Options (DEPRECATED)"
647 The old configuration infrastructure (= mkconfig + boards.cfg)
648 provided the extra options field. If you have something like
649 "HAS_BAR,BAZ=64", the optional options
651 #define CONFIG_BAZ 64
652 will be defined in include/config.h.
653 This option was prepared for the smooth migration from the old
654 configuration to Kconfig. Since this option will be removed sometime,
655 new boards should not use this option.
657 config HAVE_SYS_TEXT_BASE
659 depends on !NIOS2 && !XTENSA
664 depends on HAVE_SYS_TEXT_BASE
665 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
666 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
667 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
668 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
671 The address in memory that U-Boot will be running from, initially.
674 depends on ARC || ARCH_SUNXI || MPC83xx
675 int "CPU clock frequency"
677 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
679 config ARCH_FIXUP_FDT_MEMORY
680 bool "Enable arch_fixup_memory_banks() call"
683 Enable FDT memory map syncup before OS boot. This feature can be
684 used for booting OS with different memory setup where the part of
685 the memory location should be used for different purpose.
687 endmenu # Boot images
691 source "common/Kconfig"
695 source "disk/Kconfig"
703 source "drivers/Kconfig"
709 source "test/Kconfig"