]> git.ipfire.org Git - thirdparty/u-boot.git/blob - Kconfig
Merge tag 'u-boot-rockchip-20191110' of https://gitlab.denx.de/u-boot/custodians...
[thirdparty/u-boot.git] / Kconfig
1 #
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.
5 #
6 mainmenu "U-Boot $UBOOTVERSION Configuration"
7
8 config UBOOTVERSION
9 string
10 option env="UBOOTVERSION"
11
12 # Allow defaults in arch-specific code to override any given here
13 source "arch/Kconfig"
14
15 menu "General setup"
16
17 config BROKEN
18 bool
19 help
20 This option cannot be enabled. It is used as dependency
21 for broken and incomplete features.
22
23 config DEPRECATED
24 bool
25 help
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.
29
30 config LOCALVERSION
31 string "Local version - append to U-Boot release"
32 help
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.
39
40 config LOCALVERSION_AUTO
41 bool "Automatically append version information to the version string"
42 default y
43 help
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
46 top of tree revision.
47
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.
52
53 (The actual string used here is the first eight characters produced
54 by running the command:
55
56 $ git rev-parse --verify HEAD
57
58 which is done within the script "scripts/setlocalversion".)
59
60 config CC_OPTIMIZE_FOR_SIZE
61 bool "Optimize for size"
62 default y
63 help
64 Enabling this option will pass "-Os" instead of "-O2" to gcc
65 resulting in a smaller U-Boot image.
66
67 This option is enabled by default for U-Boot.
68
69 config CC_COVERAGE
70 bool "Enable code coverage analysis"
71 depends on SANDBOX
72 help
73 Enabling this option will pass "--coverage" to gcc to compile
74 and link code instrumented for coverage analysis.
75
76 config DISTRO_DEFAULTS
77 bool "Select defaults suitable for booting general purpose Linux distributions"
78 select AUTO_COMPLETE
79 select CMDLINE_EDITING
80 select CMD_BOOTI if ARM64
81 select CMD_BOOTZ if ARM && !ARM64
82 select CMD_DHCP if CMD_NET
83 select CMD_ENV_EXISTS
84 select CMD_EXT2
85 select CMD_EXT4
86 select CMD_FAT
87 select CMD_FS_GENERIC
88 select CMD_PART if PARTITIONS
89 select CMD_PING if CMD_NET
90 select CMD_PXE if NET
91 select ENV_VARS_UBOOT_CONFIG
92 select HUSH_PARSER
93 select SUPPORT_RAW_INITRD
94 select SYS_LONGHELP
95 imply CMD_MII if NET
96 imply USB_STORAGE
97 imply USE_BOOTCOMMAND
98 help
99 Select this to enable various options and commands which are suitable
100 for building u-boot for booting general purpose Linux distributions.
101
102 config ENV_VARS_UBOOT_CONFIG
103 bool "Add arch, board, vendor and soc variables to default environment"
104 help
105 Define this in order to add variables describing the
106 U-Boot build configuration to the default environment.
107 These will be named arch, cpu, board, vendor, and soc.
108 Enabling this option will cause the following to be defined:
109 - CONFIG_SYS_ARCH
110 - CONFIG_SYS_CPU
111 - CONFIG_SYS_BOARD
112 - CONFIG_SYS_VENDOR
113 - CONFIG_SYS_SOC
114
115 config NR_DRAM_BANKS
116 int "Number of DRAM banks"
117 default 4
118 help
119 This defines the number of DRAM banks.
120
121 config SYS_BOOT_GET_CMDLINE
122 bool "Enable kernel command line setup"
123 help
124 Enables allocating and saving kernel cmdline in space between
125 "bootm_low" and "bootm_low" + BOOTMAPSZ.
126
127 config SYS_BOOT_GET_KBD
128 bool "Enable kernel board information setup"
129 help
130 Enables allocating and saving a kernel copy of the bd_info in
131 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
132
133 config SYS_MALLOC_F
134 bool "Enable malloc() pool before relocation"
135 default y if DM
136
137 help
138 Before relocation, memory is very limited on many platforms. Still,
139 we can provide a small malloc() pool if needed. Driver model in
140 particular needs this to operate, so that it can allocate the
141 initial serial device and any others that are needed.
142
143 config SYS_MALLOC_F_LEN
144 hex "Size of malloc() pool before relocation"
145 depends on SYS_MALLOC_F
146 default 0x1000 if AM33XX
147 default 0x2800 if SANDBOX
148 default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
149 ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5)
150 default 0x400
151 help
152 Before relocation, memory is very limited on many platforms. Still,
153 we can provide a small malloc() pool if needed. Driver model in
154 particular needs this to operate, so that it can allocate the
155 initial serial device and any others that are needed.
156
157 config SYS_MALLOC_LEN
158 hex "Define memory for Dynamic allocation"
159 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
160 default 0x2000000 if ARCH_ROCKCHIP
161 help
162 This defines memory to be allocated for Dynamic allocation
163 TODO: Use for other architectures
164
165 config SPL_SYS_MALLOC_F_LEN
166 hex "Size of malloc() pool in SPL before relocation"
167 depends on SYS_MALLOC_F && SPL
168 default 0x2800 if RCAR_GEN3
169 default SYS_MALLOC_F_LEN
170 help
171 Before relocation, memory is very limited on many platforms. Still,
172 we can provide a small malloc() pool if needed. Driver model in
173 particular needs this to operate, so that it can allocate the
174 initial serial device and any others that are needed.
175
176 config TPL_SYS_MALLOC_F_LEN
177 hex "Size of malloc() pool in TPL before relocation"
178 depends on SYS_MALLOC_F && TPL
179 default SYS_MALLOC_F_LEN
180 help
181 Before relocation, memory is very limited on many platforms. Still,
182 we can provide a small malloc() pool if needed. Driver model in
183 particular needs this to operate, so that it can allocate the
184 initial serial device and any others that are needed.
185
186 menuconfig EXPERT
187 bool "Configure standard U-Boot features (expert users)"
188 default y
189 help
190 This option allows certain base U-Boot options and settings
191 to be disabled or tweaked. This is for specialized
192 environments which can tolerate a "non-standard" U-Boot.
193 Use this only if you really know what you are doing.
194
195 if EXPERT
196 config SYS_MALLOC_CLEAR_ON_INIT
197 bool "Init with zeros the memory reserved for malloc (slow)"
198 default y
199 help
200 This setting is enabled by default. The reserved malloc
201 memory is initialized with zeros, so first malloc calls
202 will return the pointer to the zeroed memory. But this
203 slows the boot time.
204
205 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
206 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
207 Then the boot time can be significantly reduced.
208 Warning:
209 When disabling this, please check if malloc calls, maybe
210 should be replaced by calloc - if one expects zeroed memory.
211
212 config TOOLS_DEBUG
213 bool "Enable debug information for tools"
214 help
215 Enable generation of debug information for tools such as mkimage.
216 This can be used for debugging purposes. With debug information
217 it is possible to set breakpoints on particular lines, single-step
218 debug through the source code, etc.
219
220 endif # EXPERT
221
222 config PHYS_64BIT
223 bool "64bit physical address support"
224 help
225 Say Y here to support 64bit physical memory address.
226 This can be used not only for 64bit SoCs, but also for
227 large physical address extension on 32bit SoCs.
228
229 config BUILD_ROM
230 bool "Build U-Boot as BIOS replacement"
231 depends on X86
232 help
233 This option allows to build a ROM version of U-Boot.
234 The build process generally requires several binary blobs
235 which are not shipped in the U-Boot source tree.
236 Please, see doc/README.x86 for details.
237
238 config SPL_IMAGE
239 string "SPL image used in the combined SPL+U-Boot image"
240 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
241 default "spl/u-boot-spl.bin"
242 depends on SPL
243 help
244 Select the SPL build target that shall be generated by the SPL
245 build process (default spl/u-boot-spl.bin). This image will be
246 used to generate a combined image with SPL and main U-Boot
247 proper as one single image.
248
249 config BUILD_TARGET
250 string "Build target special images"
251 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
252 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
253 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
254 default "u-boot-elf.srec" if RCAR_GEN3
255 default "u-boot.itb" if SPL_LOAD_FIT && (ROCKCHIP_RK3399 || \
256 ARCH_SUNXI || RISCV)
257 default "u-boot.kwb" if KIRKWOOD
258 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
259 default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
260 help
261 Some SoCs need special image types (e.g. U-Boot binary
262 with a special header) as build targets. By defining
263 CONFIG_BUILD_TARGET in the SoC / board header, this
264 special image will be automatically built upon calling
265 make / buildman.
266
267 config SYS_CUSTOM_LDSCRIPT
268 bool "Use a custom location for the U-Boot linker script"
269 help
270 Normally when linking U-Boot we will look in the board directory,
271 the CPU directory and finally the "cpu" directory of the architecture
272 for the ile "u-boot.lds" and use that as our linker. However, in
273 some cases we need to provide a different linker script. To do so,
274 enable this option and then provide the location under
275 CONFIG_SYS_LDSCRIPT.
276
277 config SYS_LDSCRIPT
278 depends on SYS_CUSTOM_LDSCRIPT
279 string "Custom ldscript location"
280 help
281 Path within the source tree to the linker script to use for the
282 main U-Boot binary.
283
284 config ERR_PTR_OFFSET
285 hex
286 default 0x0
287 help
288 Some U-Boot pointers have redundant information, so we can use a
289 scheme where we can return either an error code or a pointer with the
290 same return value. The default implementation just casts the pointer
291 to a number, however, this may fail on platforms where the end of the
292 address range is used for valid pointers (e.g. 0xffffff00 is a valid
293 heap pointer in socfpga SPL).
294 For such platforms, this value provides an upper range of those error
295 pointer values - up to 'MAX_ERRNO' bytes below this value must be
296 unused/invalid addresses.
297
298 endmenu # General setup
299
300 menu "Boot images"
301
302 config ANDROID_BOOT_IMAGE
303 bool "Enable support for Android Boot Images"
304 default y if FASTBOOT
305 help
306 This enables support for booting images which use the Android
307 image format header.
308
309 config FIT
310 bool "Support Flattened Image Tree"
311 select MD5
312 select SHA1
313 help
314 This option allows you to boot the new uImage structure,
315 Flattened Image Tree. FIT is formally a FDT, which can include
316 images of various types (kernel, FDT blob, ramdisk, etc.)
317 in a single blob. To boot this new uImage structure,
318 pass the address of the blob to the "bootm" command.
319 FIT is very flexible, supporting compression, multiple images,
320 multiple configurations, verification through hashing and also
321 verified boot (secure boot using RSA).
322
323 if FIT
324
325 config FIT_EXTERNAL_OFFSET
326 hex "FIT external data offset"
327 default 0x0
328 help
329 This specifies a data offset in fit image.
330 The offset is from data payload offset to the beginning of
331 fit image header. When specifies a offset, specific data
332 could be put in the hole between data payload and fit image
333 header, such as CSF data on i.MX platform.
334
335 config FIT_ENABLE_SHA256_SUPPORT
336 bool "Support SHA256 checksum of FIT image contents"
337 default y
338 select SHA256
339 help
340 Enable this to support SHA256 checksum of FIT image contents. A
341 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
342 the image contents have not been corrupted. SHA256 is recommended
343 for use in secure applications since (as at 2016) there is no known
344 feasible attack that could produce a 'collision' with differing
345 input data. Use this for the highest security. Note that only the
346 SHA256 variant is supported: SHA512 and others are not currently
347 supported in U-Boot.
348
349 config FIT_SIGNATURE
350 bool "Enable signature verification of FIT uImages"
351 depends on DM
352 select HASH
353 select RSA
354 help
355 This option enables signature verification of FIT uImages,
356 using a hash signed and verified using RSA. If
357 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
358 hashing is available using hardware, then the RSA library will use
359 it. See doc/uImage.FIT/signature.txt for more details.
360
361 WARNING: When relying on signed FIT images with a required signature
362 check the legacy image format is disabled by default, so that
363 unsigned images cannot be loaded. If a board needs the legacy image
364 format support in this case, enable it using
365 CONFIG_LEGACY_IMAGE_FORMAT.
366
367 config FIT_SIGNATURE_MAX_SIZE
368 hex "Max size of signed FIT structures"
369 depends on FIT_SIGNATURE
370 default 0x10000000
371 help
372 This option sets a max size in bytes for verified FIT uImages.
373 A sane value of 256MB protects corrupted DTB structures from overlapping
374 device memory. Assure this size does not extend past expected storage
375 space.
376
377 config FIT_ENABLE_RSASSA_PSS_SUPPORT
378 bool "Support rsassa-pss signature scheme of FIT image contents"
379 depends on FIT_SIGNATURE
380 default n
381 help
382 Enable this to support the pss padding algorithm as described
383 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
384
385 config FIT_VERBOSE
386 bool "Show verbose messages when FIT images fail"
387 help
388 Generally a system will have valid FIT images so debug messages
389 are a waste of code space. If you are debugging your images then
390 you can enable this option to get more verbose information about
391 failures.
392
393 config FIT_BEST_MATCH
394 bool "Select the best match for the kernel device tree"
395 help
396 When no configuration is explicitly selected, default to the
397 one whose fdt's compatibility field best matches that of
398 U-Boot itself. A match is considered "best" if it matches the
399 most specific compatibility entry of U-Boot's fdt's root node.
400 The order of entries in the configuration's fdt is ignored.
401
402 config FIT_IMAGE_POST_PROCESS
403 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
404 depends on TI_SECURE_DEVICE
405 help
406 Allows doing any sort of manipulation to blobs after they got extracted
407 from FIT images like stripping off headers or modifying the size of the
408 blob, verification, authentication, decryption etc. in a platform or
409 board specific way. In order to use this feature a platform or board-
410 specific implementation of board_fit_image_post_process() must be
411 provided. Also, anything done during this post-processing step would
412 need to be comprehended in how the images were prepared before being
413 injected into the FIT creation (i.e. the blobs would have been pre-
414 processed before being added to the FIT image).
415
416 if SPL
417
418 config SPL_FIT
419 bool "Support Flattened Image Tree within SPL"
420 depends on SPL
421 select SPL_OF_LIBFDT
422
423 config SPL_FIT_PRINT
424 bool "Support FIT printing within SPL"
425 depends on SPL_FIT
426 help
427 Support printing the content of the fitImage in a verbose manner in SPL.
428
429 config SPL_FIT_SIGNATURE
430 bool "Enable signature verification of FIT firmware within SPL"
431 depends on SPL_DM
432 select SPL_FIT
433 select SPL_RSA
434
435 config SPL_LOAD_FIT
436 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
437 select SPL_FIT
438 help
439 Normally with the SPL framework a legacy image is generated as part
440 of the build. This contains U-Boot along with information as to
441 where it should be loaded. This option instead enables generation
442 of a FIT (Flat Image Tree) which provides more flexibility. In
443 particular it can handle selecting from multiple device tree
444 and passing the correct one to U-Boot.
445
446 config SPL_LOAD_FIT_FULL
447 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
448 select SPL_FIT
449 help
450 Normally with the SPL framework a legacy image is generated as part
451 of the build. This contains U-Boot along with information as to
452 where it should be loaded. This option instead enables generation
453 of a FIT (Flat Image Tree) which provides more flexibility. In
454 particular it can handle selecting from multiple device tree
455 and passing the correct one to U-Boot.
456
457 config SPL_FIT_IMAGE_POST_PROCESS
458 bool "Enable post-processing of FIT artifacts after loading by the SPL"
459 depends on SPL_LOAD_FIT
460 help
461 Allows doing any sort of manipulation to blobs after they got extracted
462 from the U-Boot FIT image like stripping off headers or modifying the
463 size of the blob, verification, authentication, decryption etc. in a
464 platform or board specific way. In order to use this feature a platform
465 or board-specific implementation of board_fit_image_post_process() must
466 be provided. Also, anything done during this post-processing step would
467 need to be comprehended in how the images were prepared before being
468 injected into the FIT creation (i.e. the blobs would have been pre-
469 processed before being added to the FIT image).
470
471 config SPL_FIT_SOURCE
472 string ".its source file for U-Boot FIT image"
473 depends on SPL_FIT
474 help
475 Specifies a (platform specific) FIT source file to generate the
476 U-Boot FIT image. This could specify further image to load and/or
477 execute.
478
479 config SPL_FIT_GENERATOR
480 string ".its file generator script for U-Boot FIT image"
481 depends on SPL_FIT
482 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
483 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
484 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
485 help
486 Specifies a (platform specific) script file to generate the FIT
487 source file used to build the U-Boot FIT image file. This gets
488 passed a list of supported device tree file stub names to
489 include in the generated image.
490
491 endif # SPL
492
493 endif # FIT
494
495 config LEGACY_IMAGE_FORMAT
496 bool "Enable support for the legacy image format"
497 default y if !FIT_SIGNATURE
498 help
499 This option enables the legacy image format. It is enabled by
500 default for backward compatibility, unless FIT_SIGNATURE is
501 set where it is disabled so that unsigned images cannot be
502 loaded. If a board needs the legacy image format support in this
503 case, enable it here.
504
505 config OF_BOARD_SETUP
506 bool "Set up board-specific details in device tree before boot"
507 depends on OF_LIBFDT
508 help
509 This causes U-Boot to call ft_board_setup() before booting into
510 the Operating System. This function can set up various
511 board-specific information in the device tree for use by the OS.
512 The device tree is then passed to the OS.
513
514 config OF_SYSTEM_SETUP
515 bool "Set up system-specific details in device tree before boot"
516 depends on OF_LIBFDT
517 help
518 This causes U-Boot to call ft_system_setup() before booting into
519 the Operating System. This function can set up various
520 system-specific information in the device tree for use by the OS.
521 The device tree is then passed to the OS.
522
523 config OF_STDOUT_VIA_ALIAS
524 bool "Update the device-tree stdout alias from U-Boot"
525 depends on OF_LIBFDT
526 help
527 This uses U-Boot's serial alias from the aliases node to update
528 the device tree passed to the OS. The "linux,stdout-path" property
529 in the chosen node is set to point to the correct serial node.
530 This option currently references CONFIG_CONS_INDEX, which is
531 incorrect when used with device tree as this option does not
532 exist / should not be used.
533
534 config SYS_EXTRA_OPTIONS
535 string "Extra Options (DEPRECATED)"
536 help
537 The old configuration infrastructure (= mkconfig + boards.cfg)
538 provided the extra options field. If you have something like
539 "HAS_BAR,BAZ=64", the optional options
540 #define CONFIG_HAS
541 #define CONFIG_BAZ 64
542 will be defined in include/config.h.
543 This option was prepared for the smooth migration from the old
544 configuration to Kconfig. Since this option will be removed sometime,
545 new boards should not use this option.
546
547 config SYS_TEXT_BASE
548 depends on !NIOS2 && !XTENSA
549 depends on !EFI_APP
550 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
551 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
552 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
553 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
554 hex "Text Base"
555 help
556 The address in memory that U-Boot will be running from, initially.
557
558
559
560 config SYS_CLK_FREQ
561 depends on ARC || ARCH_SUNXI || MPC83xx
562 int "CPU clock frequency"
563 help
564 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
565
566 config ARCH_FIXUP_FDT_MEMORY
567 bool "Enable arch_fixup_memory_banks() call"
568 default y
569 help
570 Enable FDT memory map syncup before OS boot. This feature can be
571 used for booting OS with different memory setup where the part of
572 the memory location should be used for different purpose.
573
574 endmenu # Boot images
575
576 source "api/Kconfig"
577
578 source "common/Kconfig"
579
580 source "cmd/Kconfig"
581
582 source "disk/Kconfig"
583
584 source "dts/Kconfig"
585
586 source "env/Kconfig"
587
588 source "net/Kconfig"
589
590 source "drivers/Kconfig"
591
592 source "fs/Kconfig"
593
594 source "lib/Kconfig"
595
596 source "test/Kconfig"