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 endmenu         # General setup
 257
 258 menu "Boot images"
 259
 260 config ANDROID_BOOT_IMAGE
 261         bool "Enable support for Android Boot Images"
 262         default y if FASTBOOT
 263         help
 264           This enables support for booting images which use the Android
 265           image format header.
 266
 267 config FIT
 268         bool "Support Flattened Image Tree"
 269         select MD5
 270         select SHA1
 271         help
 272           This option allows you to boot the new uImage structure,
 273           Flattened Image Tree.  FIT is formally a FDT, which can include
 274           images of various types (kernel, FDT blob, ramdisk, etc.)
 275           in a single blob.  To boot this new uImage structure,
 276           pass the address of the blob to the "bootm" command.
 277           FIT is very flexible, supporting compression, multiple images,
 278           multiple configurations, verification through hashing and also
 279           verified boot (secure boot using RSA).
 280
 281 if FIT
 282
 283 config FIT_EXTERNAL_OFFSET
 284         hex "FIT external data offset"
 285         default 0x0
 286         help
 287           This specifies a data offset in fit image.
 288           The offset is from data payload offset to the beginning of
 289           fit image header. When specifies a offset, specific data
 290           could be put in the hole between data payload and fit image
 291           header, such as CSF data on i.MX platform.
 292
 293 config FIT_ENABLE_SHA256_SUPPORT
 294         bool "Support SHA256 checksum of FIT image contents"
 295         default y
 296         select SHA256
 297         help
 298           Enable this to support SHA256 checksum of FIT image contents. A
 299           SHA256 checksum is a 256-bit (32-byte) hash value used to check that
 300           the image contents have not been corrupted. SHA256 is recommended
 301           for use in secure applications since (as at 2016) there is no known
 302           feasible attack that could produce a 'collision' with differing
 303           input data. Use this for the highest security. Note that only the
 304           SHA256 variant is supported: SHA512 and others are not currently
 305           supported in U-Boot.
 306
 307 config FIT_SIGNATURE
 308         bool "Enable signature verification of FIT uImages"
 309         depends on DM
 310         select HASH
 311         select RSA
 312         help
 313           This option enables signature verification of FIT uImages,
 314           using a hash signed and verified using RSA. If
 315           CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
 316           hashing is available using hardware, then the RSA library will use
 317           it. See doc/uImage.FIT/signature.txt for more details.
 318
 319           WARNING: When relying on signed FIT images with a required signature
 320           check the legacy image format is disabled by default, so that
 321           unsigned images cannot be loaded. If a board needs the legacy image
 322           format support in this case, enable it using
 323           CONFIG_IMAGE_FORMAT_LEGACY.
 324
 325 config FIT_SIGNATURE_MAX_SIZE
 326         hex "Max size of signed FIT structures"
 327         depends on FIT_SIGNATURE
 328         default 0x10000000
 329         help
 330           This option sets a max size in bytes for verified FIT uImages.
 331           A sane value of 256MB protects corrupted DTB structures from overlapping
 332           device memory. Assure this size does not extend past expected storage
 333           space.
 334
 335 config FIT_ENABLE_RSASSA_PSS_SUPPORT
 336         bool "Support rsassa-pss signature scheme of FIT image contents"
 337         depends on FIT_SIGNATURE
 338         default n
 339         help
 340           Enable this to support the pss padding algorithm as described
 341           in the rfc8017 (https://tools.ietf.org/html/rfc8017).
 342
 343 config FIT_VERBOSE
 344         bool "Show verbose messages when FIT images fail"
 345         help
 346           Generally a system will have valid FIT images so debug messages
 347           are a waste of code space. If you are debugging your images then
 348           you can enable this option to get more verbose information about
 349           failures.
 350
 351 config FIT_BEST_MATCH
 352         bool "Select the best match for the kernel device tree"
 353         help
 354           When no configuration is explicitly selected, default to the
 355           one whose fdt's compatibility field best matches that of
 356           U-Boot itself. A match is considered "best" if it matches the
 357           most specific compatibility entry of U-Boot's fdt's root node.
 358           The order of entries in the configuration's fdt is ignored.
 359
 360 config FIT_IMAGE_POST_PROCESS
 361         bool "Enable post-processing of FIT artifacts after loading by U-Boot"
 362         depends on TI_SECURE_DEVICE
 363         help
 364           Allows doing any sort of manipulation to blobs after they got extracted
 365           from FIT images like stripping off headers or modifying the size of the
 366           blob, verification, authentication, decryption etc. in a platform or
 367           board specific way. In order to use this feature a platform or board-
 368           specific implementation of board_fit_image_post_process() must be
 369           provided. Also, anything done during this post-processing step would
 370           need to be comprehended in how the images were prepared before being
 371           injected into the FIT creation (i.e. the blobs would have been pre-
 372           processed before being added to the FIT image).
 373
 374 if SPL
 375
 376 config SPL_FIT
 377         bool "Support Flattened Image Tree within SPL"
 378         depends on SPL
 379         select SPL_OF_LIBFDT
 380
 381 config SPL_FIT_PRINT
 382         bool "Support FIT printing within SPL"
 383         depends on SPL_FIT
 384         help
 385           Support printing the content of the fitImage in a verbose manner in SPL.
 386
 387 config SPL_FIT_SIGNATURE
 388         bool "Enable signature verification of FIT firmware within SPL"
 389         depends on SPL_DM
 390         select SPL_FIT
 391         select SPL_RSA
 392
 393 config SPL_LOAD_FIT
 394         bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
 395         select SPL_FIT
 396         help
 397           Normally with the SPL framework a legacy image is generated as part
 398           of the build. This contains U-Boot along with information as to
 399           where it should be loaded. This option instead enables generation
 400           of a FIT (Flat Image Tree) which provides more flexibility. In
 401           particular it can handle selecting from multiple device tree
 402           and passing the correct one to U-Boot.
 403
 404 config SPL_LOAD_FIT_FULL
 405         bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
 406         select SPL_FIT
 407         help
 408           Normally with the SPL framework a legacy image is generated as part
 409           of the build. This contains U-Boot along with information as to
 410           where it should be loaded. This option instead enables generation
 411           of a FIT (Flat Image Tree) which provides more flexibility. In
 412           particular it can handle selecting from multiple device tree
 413           and passing the correct one to U-Boot.
 414
 415 config SPL_FIT_IMAGE_POST_PROCESS
 416         bool "Enable post-processing of FIT artifacts after loading by the SPL"
 417         depends on SPL_LOAD_FIT
 418         help
 419           Allows doing any sort of manipulation to blobs after they got extracted
 420           from the U-Boot FIT image like stripping off headers or modifying the
 421           size of the blob, verification, authentication, decryption etc. in a
 422           platform or board specific way. In order to use this feature a platform
 423           or board-specific implementation of board_fit_image_post_process() must
 424           be provided. Also, anything done during this post-processing step would
 425           need to be comprehended in how the images were prepared before being
 426           injected into the FIT creation (i.e. the blobs would have been pre-
 427           processed before being added to the FIT image).
 428
 429 config SPL_FIT_SOURCE
 430         string ".its source file for U-Boot FIT image"
 431         depends on SPL_FIT
 432         help
 433           Specifies a (platform specific) FIT source file to generate the
 434           U-Boot FIT image. This could specify further image to load and/or
 435           execute.
 436
 437 config SPL_FIT_GENERATOR
 438         string ".its file generator script for U-Boot FIT image"
 439         depends on SPL_FIT
 440         default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
 441         default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
 442         help
 443           Specifies a (platform specific) script file to generate the FIT
 444           source file used to build the U-Boot FIT image file. This gets
 445           passed a list of supported device tree file stub names to
 446           include in the generated image.
 447
 448 endif # SPL
 449
 450 endif # FIT
 451
 452 config IMAGE_FORMAT_LEGACY
 453         bool "Enable support for the legacy image format"
 454         default y if !FIT_SIGNATURE
 455         help
 456           This option enables the legacy image format. It is enabled by
 457           default for backward compatibility, unless FIT_SIGNATURE is
 458           set where it is disabled so that unsigned images cannot be
 459           loaded. If a board needs the legacy image format support in this
 460           case, enable it here.
 461
 462 config OF_BOARD_SETUP
 463         bool "Set up board-specific details in device tree before boot"
 464         depends on OF_LIBFDT
 465         help
 466           This causes U-Boot to call ft_board_setup() before booting into
 467           the Operating System. This function can set up various
 468           board-specific information in the device tree for use by the OS.
 469           The device tree is then passed to the OS.
 470
 471 config OF_SYSTEM_SETUP
 472         bool "Set up system-specific details in device tree before boot"
 473         depends on OF_LIBFDT
 474         help
 475           This causes U-Boot to call ft_system_setup() before booting into
 476           the Operating System. This function can set up various
 477           system-specific information in the device tree for use by the OS.
 478           The device tree is then passed to the OS.
 479
 480 config OF_STDOUT_VIA_ALIAS
 481         bool "Update the device-tree stdout alias from U-Boot"
 482         depends on OF_LIBFDT
 483         help
 484           This uses U-Boot's serial alias from the aliases node to update
 485           the device tree passed to the OS. The "linux,stdout-path" property
 486           in the chosen node is set to point to the correct serial node.
 487           This option currently references CONFIG_CONS_INDEX, which is
 488           incorrect when used with device tree as this option does not
 489           exist / should not be used.
 490
 491 config SYS_EXTRA_OPTIONS
 492         string "Extra Options (DEPRECATED)"
 493         help
 494           The old configuration infrastructure (= mkconfig + boards.cfg)
 495           provided the extra options field. If you have something like
 496           "HAS_BAR,BAZ=64", the optional options
 497             #define CONFIG_HAS
 498             #define CONFIG_BAZ  64
 499           will be defined in include/config.h.
 500           This option was prepared for the smooth migration from the old
 501           configuration to Kconfig. Since this option will be removed sometime,
 502           new boards should not use this option.
 503
 504 config SYS_TEXT_BASE
 505         depends on !NIOS2 && !XTENSA
 506         depends on !EFI_APP
 507         default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
 508         default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
 509         default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
 510         default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
 511         hex "Text Base"
 512         help
 513           The address in memory that U-Boot will be running from, initially.
 514
 515
 516
 517 config SYS_CLK_FREQ
 518         depends on ARC || ARCH_SUNXI || MPC83xx
 519         int "CPU clock frequency"
 520         help
 521           TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
 522
 523 config ARCH_FIXUP_FDT_MEMORY
 524         bool "Enable arch_fixup_memory_banks() call"
 525         default y
 526         help
 527           Enable FDT memory map syncup before OS boot. This feature can be
 528           used for booting OS with different memory setup where the part of
 529           the memory location should be used for different purpose.
 530
 531 endmenu         # Boot images
 532
 533 source "api/Kconfig"
 534
 535 source "common/Kconfig"
 536
 537 source "cmd/Kconfig"
 538
 539 source "disk/Kconfig"
 540
 541 source "dts/Kconfig"
 542
 543 source "env/Kconfig"
 544
 545 source "net/Kconfig"
 546
 547 source "drivers/Kconfig"
 548
 549 source "fs/Kconfig"
 550
 551 source "lib/Kconfig"
 552
 553 source "test/Kconfig"