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 0x400
 142         help
 143           Before relocation, memory is very limited on many platforms. Still,
 144           we can provide a small malloc() pool if needed. Driver model in
 145           particular needs this to operate, so that it can allocate the
 146           initial serial device and any others that are needed.
 147
 148 config SYS_MALLOC_LEN
 149         hex "Define memory for Dynamic allocation"
 150         depends on ARCH_ZYNQ || ARCH_VERSAL
 151         help
 152           This defines memory to be allocated for Dynamic allocation
 153           TODO: Use for other architectures
 154
 155 config SPL_SYS_MALLOC_F_LEN
 156         hex "Size of malloc() pool in SPL before relocation"
 157         depends on SYS_MALLOC_F
 158         default SYS_MALLOC_F_LEN
 159         help
 160           Before relocation, memory is very limited on many platforms. Still,
 161           we can provide a small malloc() pool if needed. Driver model in
 162           particular needs this to operate, so that it can allocate the
 163           initial serial device and any others that are needed.
 164
 165 config TPL_SYS_MALLOC_F_LEN
 166         hex "Size of malloc() pool in TPL before relocation"
 167         depends on SYS_MALLOC_F
 168         default SYS_MALLOC_F_LEN
 169         help
 170           Before relocation, memory is very limited on many platforms. Still,
 171           we can provide a small malloc() pool if needed. Driver model in
 172           particular needs this to operate, so that it can allocate the
 173           initial serial device and any others that are needed.
 174
 175 menuconfig EXPERT
 176         bool "Configure standard U-Boot features (expert users)"
 177         default y
 178         help
 179           This option allows certain base U-Boot options and settings
 180           to be disabled or tweaked. This is for specialized
 181           environments which can tolerate a "non-standard" U-Boot.
 182           Use this only if you really know what you are doing.
 183
 184 if EXPERT
 185         config SYS_MALLOC_CLEAR_ON_INIT
 186         bool "Init with zeros the memory reserved for malloc (slow)"
 187         default y
 188         help
 189           This setting is enabled by default. The reserved malloc
 190           memory is initialized with zeros, so first malloc calls
 191           will return the pointer to the zeroed memory. But this
 192           slows the boot time.
 193
 194           It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
 195           value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
 196           Then the boot time can be significantly reduced.
 197           Warning:
 198           When disabling this, please check if malloc calls, maybe
 199           should be replaced by calloc - if one expects zeroed memory.
 200
 201 config TOOLS_DEBUG
 202         bool "Enable debug information for tools"
 203         help
 204           Enable generation of debug information for tools such as mkimage.
 205           This can be used for debugging purposes. With debug information
 206           it is possible to set breakpoints on particular lines, single-step
 207           debug through the source code, etc.
 208
 209 endif # EXPERT
 210
 211 config PHYS_64BIT
 212         bool "64bit physical address support"
 213         help
 214           Say Y here to support 64bit physical memory address.
 215           This can be used not only for 64bit SoCs, but also for
 216           large physical address extension on 32bit SoCs.
 217
 218 config BUILD_ROM
 219         bool "Build U-Boot as BIOS replacement"
 220         depends on X86
 221         help
 222           This option allows to build a ROM version of U-Boot.
 223           The build process generally requires several binary blobs
 224           which are not shipped in the U-Boot source tree.
 225           Please, see doc/README.x86 for details.
 226
 227 config SPL_IMAGE
 228         string "SPL image used in the combined SPL+U-Boot image"
 229         default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
 230         default "spl/u-boot-spl.bin"
 231         help
 232           Select the SPL build target that shall be generated by the SPL
 233           build process (default spl/u-boot-spl.bin). This image will be
 234           used to generate a combined image with SPL and main U-Boot
 235           proper as one single image.
 236
 237 config BUILD_TARGET
 238         string "Build target special images"
 239         default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
 240         default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
 241         default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
 242         default "u-boot-elf.srec" if RCAR_GEN3
 243         default "u-boot.itb" if SPL_LOAD_FIT && ARCH_SUNXI
 244         default "u-boot.kwb" if KIRKWOOD
 245         default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
 246         help
 247           Some SoCs need special image types (e.g. U-Boot binary
 248           with a special header) as build targets. By defining
 249           CONFIG_BUILD_TARGET in the SoC / board header, this
 250           special image will be automatically built upon calling
 251           make / buildman.
 252
 253 endmenu         # General setup
 254
 255 menu "Boot images"
 256
 257 config ANDROID_BOOT_IMAGE
 258         bool "Enable support for Android Boot Images"
 259         default y if FASTBOOT
 260         help
 261           This enables support for booting images which use the Android
 262           image format header.
 263
 264 config FIT
 265         bool "Support Flattened Image Tree"
 266         select MD5
 267         select SHA1
 268         help
 269           This option allows you to boot the new uImage structure,
 270           Flattened Image Tree.  FIT is formally a FDT, which can include
 271           images of various types (kernel, FDT blob, ramdisk, etc.)
 272           in a single blob.  To boot this new uImage structure,
 273           pass the address of the blob to the "bootm" command.
 274           FIT is very flexible, supporting compression, multiple images,
 275           multiple configurations, verification through hashing and also
 276           verified boot (secure boot using RSA).
 277
 278 if FIT
 279
 280 config FIT_EXTERNAL_OFFSET
 281         hex "Text Base"
 282         default 0x0
 283         help
 284           This specifies a data offset in fit image.
 285           The offset is from data payload offset to the beginning of
 286           fit image header. When specifies a offset, specific data
 287           could be put in the hole between data payload and fit image
 288           header, such as CSF data on i.MX platform.
 289
 290 config FIT_ENABLE_SHA256_SUPPORT
 291         bool "Support SHA256 checksum of FIT image contents"
 292         default y
 293         select SHA256
 294         help
 295           Enable this to support SHA256 checksum of FIT image contents. A
 296           SHA256 checksum is a 256-bit (32-byte) hash value used to check that
 297           the image contents have not been corrupted. SHA256 is recommended
 298           for use in secure applications since (as at 2016) there is no known
 299           feasible attack that could produce a 'collision' with differing
 300           input data. Use this for the highest security. Note that only the
 301           SHA256 variant is supported: SHA512 and others are not currently
 302           supported in U-Boot.
 303
 304 config FIT_SIGNATURE
 305         bool "Enable signature verification of FIT uImages"
 306         depends on DM
 307         select HASH
 308         select RSA
 309         help
 310           This option enables signature verification of FIT uImages,
 311           using a hash signed and verified using RSA. If
 312           CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
 313           hashing is available using hardware, then the RSA library will use
 314           it. See doc/uImage.FIT/signature.txt for more details.
 315
 316           WARNING: When relying on signed FIT images with a required signature
 317           check the legacy image format is disabled by default, so that
 318           unsigned images cannot be loaded. If a board needs the legacy image
 319           format support in this case, enable it using
 320           CONFIG_IMAGE_FORMAT_LEGACY.
 321
 322 config FIT_SIGNATURE_MAX_SIZE
 323         hex "Max size of signed FIT structures"
 324         depends on FIT_SIGNATURE
 325         default 0x10000000
 326         help
 327           This option sets a max size in bytes for verified FIT uImages.
 328           A sane value of 256MB protects corrupted DTB structures from overlapping
 329           device memory. Assure this size does not extend past expected storage
 330           space.
 331
 332 config FIT_ENABLE_RSASSA_PSS_SUPPORT
 333         bool "Support rsassa-pss signature scheme of FIT image contents"
 334         depends on FIT_SIGNATURE
 335         default n
 336         help
 337           Enable this to support the pss padding algorithm as described
 338           in the rfc8017 (https://tools.ietf.org/html/rfc8017).
 339
 340 config FIT_VERBOSE
 341         bool "Show verbose messages when FIT images fail"
 342         help
 343           Generally a system will have valid FIT images so debug messages
 344           are a waste of code space. If you are debugging your images then
 345           you can enable this option to get more verbose information about
 346           failures.
 347
 348 config FIT_BEST_MATCH
 349         bool "Select the best match for the kernel device tree"
 350         help
 351           When no configuration is explicitly selected, default to the
 352           one whose fdt's compatibility field best matches that of
 353           U-Boot itself. A match is considered "best" if it matches the
 354           most specific compatibility entry of U-Boot's fdt's root node.
 355           The order of entries in the configuration's fdt is ignored.
 356
 357 config FIT_IMAGE_POST_PROCESS
 358         bool "Enable post-processing of FIT artifacts after loading by U-Boot"
 359         depends on TI_SECURE_DEVICE
 360         help
 361           Allows doing any sort of manipulation to blobs after they got extracted
 362           from FIT images like stripping off headers or modifying the size of the
 363           blob, verification, authentication, decryption etc. in a platform or
 364           board specific way. In order to use this feature a platform or board-
 365           specific implementation of board_fit_image_post_process() must be
 366           provided. Also, anything done during this post-processing step would
 367           need to be comprehended in how the images were prepared before being
 368           injected into the FIT creation (i.e. the blobs would have been pre-
 369           processed before being added to the FIT image).
 370
 371 if SPL
 372
 373 config SPL_FIT
 374         bool "Support Flattened Image Tree within SPL"
 375         depends on SPL
 376         select SPL_OF_LIBFDT
 377
 378 config SPL_FIT_PRINT
 379         bool "Support FIT printing within SPL"
 380         depends on SPL_FIT
 381         help
 382           Support printing the content of the fitImage in a verbose manner in SPL.
 383
 384 config SPL_FIT_SIGNATURE
 385         bool "Enable signature verification of FIT firmware within SPL"
 386         depends on SPL_DM
 387         select SPL_FIT
 388         select SPL_RSA
 389
 390 config SPL_LOAD_FIT
 391         bool "Enable SPL loading U-Boot as a FIT"
 392         select SPL_FIT
 393         help
 394           Normally with the SPL framework a legacy image is generated as part
 395           of the build. This contains U-Boot along with information as to
 396           where it should be loaded. This option instead enables generation
 397           of a FIT (Flat Image Tree) which provides more flexibility. In
 398           particular it can handle selecting from multiple device tree
 399           and passing the correct one to U-Boot.
 400
 401 config SPL_LOAD_FIT_FULL
 402         bool "Enable SPL loading U-Boot as a FIT"
 403         select SPL_FIT
 404         help
 405           Normally with the SPL framework a legacy image is generated as part
 406           of the build. This contains U-Boot along with information as to
 407           where it should be loaded. This option instead enables generation
 408           of a FIT (Flat Image Tree) which provides more flexibility. In
 409           particular it can handle selecting from multiple device tree
 410           and passing the correct one to U-Boot.
 411
 412 config SPL_FIT_IMAGE_POST_PROCESS
 413         bool "Enable post-processing of FIT artifacts after loading by the SPL"
 414         depends on SPL_LOAD_FIT
 415         help
 416           Allows doing any sort of manipulation to blobs after they got extracted
 417           from the U-Boot FIT image like stripping off headers or modifying the
 418           size of the blob, verification, authentication, decryption etc. in a
 419           platform or board specific way. In order to use this feature a platform
 420           or board-specific implementation of board_fit_image_post_process() must
 421           be provided. Also, anything done during this post-processing step would
 422           need to be comprehended in how the images were prepared before being
 423           injected into the FIT creation (i.e. the blobs would have been pre-
 424           processed before being added to the FIT image).
 425
 426 config SPL_FIT_SOURCE
 427         string ".its source file for U-Boot FIT image"
 428         depends on SPL_FIT
 429         help
 430           Specifies a (platform specific) FIT source file to generate the
 431           U-Boot FIT image. This could specify further image to load and/or
 432           execute.
 433
 434 config SPL_FIT_GENERATOR
 435         string ".its file generator script for U-Boot FIT image"
 436         depends on SPL_FIT
 437         default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
 438         help
 439           Specifies a (platform specific) script file to generate the FIT
 440           source file used to build the U-Boot FIT image file. This gets
 441           passed a list of supported device tree file stub names to
 442           include in the generated image.
 443
 444 endif # SPL
 445
 446 endif # FIT
 447
 448 config IMAGE_FORMAT_LEGACY
 449         bool "Enable support for the legacy image format"
 450         default y if !FIT_SIGNATURE
 451         help
 452           This option enables the legacy image format. It is enabled by
 453           default for backward compatibility, unless FIT_SIGNATURE is
 454           set where it is disabled so that unsigned images cannot be
 455           loaded. If a board needs the legacy image format support in this
 456           case, enable it here.
 457
 458 config OF_BOARD_SETUP
 459         bool "Set up board-specific details in device tree before boot"
 460         depends on OF_LIBFDT
 461         help
 462           This causes U-Boot to call ft_board_setup() before booting into
 463           the Operating System. This function can set up various
 464           board-specific information in the device tree for use by the OS.
 465           The device tree is then passed to the OS.
 466
 467 config OF_SYSTEM_SETUP
 468         bool "Set up system-specific details in device tree before boot"
 469         depends on OF_LIBFDT
 470         help
 471           This causes U-Boot to call ft_system_setup() before booting into
 472           the Operating System. This function can set up various
 473           system-specific information in the device tree for use by the OS.
 474           The device tree is then passed to the OS.
 475
 476 config OF_STDOUT_VIA_ALIAS
 477         bool "Update the device-tree stdout alias from U-Boot"
 478         depends on OF_LIBFDT
 479         help
 480           This uses U-Boot's serial alias from the aliases node to update
 481           the device tree passed to the OS. The "linux,stdout-path" property
 482           in the chosen node is set to point to the correct serial node.
 483           This option currently references CONFIG_CONS_INDEX, which is
 484           incorrect when used with device tree as this option does not
 485           exist / should not be used.
 486
 487 config SYS_EXTRA_OPTIONS
 488         string "Extra Options (DEPRECATED)"
 489         help
 490           The old configuration infrastructure (= mkconfig + boards.cfg)
 491           provided the extra options field. If you have something like
 492           "HAS_BAR,BAZ=64", the optional options
 493             #define CONFIG_HAS
 494             #define CONFIG_BAZ  64
 495           will be defined in include/config.h.
 496           This option was prepared for the smooth migration from the old
 497           configuration to Kconfig. Since this option will be removed sometime,
 498           new boards should not use this option.
 499
 500 config SYS_TEXT_BASE
 501         depends on !NIOS2 && !XTENSA
 502         depends on !EFI_APP
 503         default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
 504         default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
 505         default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
 506         default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
 507         hex "Text Base"
 508         help
 509           The address in memory that U-Boot will be running from, initially.
 510
 511
 512
 513 config SYS_CLK_FREQ
 514         depends on ARC || ARCH_SUNXI
 515         int "CPU clock frequency"
 516         help
 517           TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
 518
 519 config ARCH_FIXUP_FDT_MEMORY
 520         bool "Enable arch_fixup_memory_banks() call"
 521         default y
 522         help
 523           Enable FDT memory map syncup before OS boot. This feature can be
 524           used for booting OS with different memory setup where the part of
 525           the memory location should be used for different purpose.
 526
 527 endmenu         # Boot images
 528
 529 source "api/Kconfig"
 530
 531 source "common/Kconfig"
 532
 533 source "cmd/Kconfig"
 534
 535 source "disk/Kconfig"
 536
 537 source "dts/Kconfig"
 538
 539 source "env/Kconfig"
 540
 541 source "net/Kconfig"
 542
 543 source "drivers/Kconfig"
 544
 545 source "fs/Kconfig"
 546
 547 source "lib/Kconfig"
 548
 549 source "test/Kconfig"