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