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