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