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 LOCALVERSION
  18         string "Local version - append to U-Boot release"
  19         help
  20           Append an extra string to the end of your U-Boot version.
  21           This will show up in your boot log, for example.
  22           The string you set here will be appended after the contents of
  23           any files with a filename matching localversion* in your
  24           object and source tree, in that order.  Your total string can
  25           be a maximum of 64 characters.
  26
  27 config LOCALVERSION_AUTO
  28         bool "Automatically append version information to the version string"
  29         default y
  30         help
  31           This will try to automatically determine if the current tree is a
  32           release tree by looking for Git tags that belong to the current
  33           top of tree revision.
  34
  35           A string of the format -gxxxxxxxx will be added to the localversion
  36           if a Git-based tree is found.  The string generated by this will be
  37           appended after any matching localversion* files, and after the value
  38           set in CONFIG_LOCALVERSION.
  39
  40           (The actual string used here is the first eight characters produced
  41           by running the command:
  42
  43             $ git rev-parse --verify HEAD
  44
  45           which is done within the script "scripts/setlocalversion".)
  46
  47 config CC_OPTIMIZE_FOR_SIZE
  48         bool "Optimize for size"
  49         default y
  50         help
  51           Enabling this option will pass "-Os" instead of "-O2" to gcc
  52           resulting in a smaller U-Boot image.
  53
  54           This option is enabled by default for U-Boot.
  55
  56 config DISTRO_DEFAULTS
  57         bool "Select defaults suitable for booting general purpose Linux distributions"
  58         default y if ARCH_SUNXI || TEGRA
  59         default y if ARCH_LS2080A
  60         default y if ARCH_MESON
  61         default y if ARCH_ROCKCHIP
  62         default n
  63         select CMD_BOOTZ if ARM && !ARM64
  64         select CMD_BOOTI if ARM64
  65         select CMD_DHCP
  66         select CMD_PXE
  67         select CMD_EXT2
  68         select CMD_EXT4
  69         select CMD_FAT
  70         select CMD_FS_GENERIC
  71         select CMD_MII
  72         select CMD_PING
  73         select CMD_PART
  74         select HUSH_PARSER
  75         help
  76           Select this to enable various options and commands which are suitable
  77           for building u-boot for booting general purpose Linux distributions.
  78
  79 config SYS_MALLOC_F
  80         bool "Enable malloc() pool before relocation"
  81         default y if DM
  82         help
  83           Before relocation, memory is very limited on many platforms. Still,
  84           we can provide a small malloc() pool if needed. Driver model in
  85           particular needs this to operate, so that it can allocate the
  86           initial serial device and any others that are needed.
  87
  88 config SYS_MALLOC_F_LEN
  89         hex "Size of malloc() pool before relocation"
  90         depends on SYS_MALLOC_F
  91         default 0x400
  92         help
  93           Before relocation, memory is very limited on many platforms. Still,
  94           we can provide a small malloc() pool if needed. Driver model in
  95           particular needs this to operate, so that it can allocate the
  96           initial serial device and any others that are needed.
  97
  98 config SPL_SYS_MALLOC_F_LEN
  99         hex "Size of malloc() pool in SPL before relocation"
 100         depends on SYS_MALLOC_F
 101         default SYS_MALLOC_F_LEN
 102         help
 103           Before relocation, memory is very limited on many platforms. Still,
 104           we can provide a small malloc() pool if needed. Driver model in
 105           particular needs this to operate, so that it can allocate the
 106           initial serial device and any others that are needed.
 107
 108 config TPL_SYS_MALLOC_F_LEN
 109         hex "Size of malloc() pool in TPL before relocation"
 110         depends on SYS_MALLOC_F
 111         default SYS_MALLOC_F_LEN
 112         help
 113           Before relocation, memory is very limited on many platforms. Still,
 114           we can provide a small malloc() pool if needed. Driver model in
 115           particular needs this to operate, so that it can allocate the
 116           initial serial device and any others that are needed.
 117
 118 menuconfig EXPERT
 119         bool "Configure standard U-Boot features (expert users)"
 120         default y
 121         help
 122           This option allows certain base U-Boot options and settings
 123           to be disabled or tweaked. This is for specialized
 124           environments which can tolerate a "non-standard" U-Boot.
 125           Use this only if you really know what you are doing.
 126
 127 if EXPERT
 128         config SYS_MALLOC_CLEAR_ON_INIT
 129         bool "Init with zeros the memory reserved for malloc (slow)"
 130         default y
 131         help
 132           This setting is enabled by default. The reserved malloc
 133           memory is initialized with zeros, so first malloc calls
 134           will return the pointer to the zeroed memory. But this
 135           slows the boot time.
 136
 137           It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
 138           value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
 139           Then the boot time can be significantly reduced.
 140           Warning:
 141           When disabling this, please check if malloc calls, maybe
 142           should be replaced by calloc - if one expects zeroed memory.
 143
 144 config TOOLS_DEBUG
 145         bool "Enable debug information for tools"
 146         help
 147           Enable generation of debug information for tools such as mkimage.
 148           This can be used for debugging purposes. With debug information
 149           it is possible to set breakpoints on particular lines, single-step
 150           debug through the source code, etc.
 151
 152 endif # EXPERT
 153
 154 config PHYS_64BIT
 155         bool "64bit physical address support"
 156         help
 157           Say Y here to support 64bit physical memory address.
 158           This can be used not only for 64bit SoCs, but also for
 159           large physical address extention on 32bit SoCs.
 160
 161 endmenu         # General setup
 162
 163 menu "Boot images"
 164
 165 config FIT
 166         bool "Support Flattened Image Tree"
 167         select MD5
 168         select SHA1
 169         help
 170           This option allows you to boot the new uImage structure,
 171           Flattened Image Tree.  FIT is formally a FDT, which can include
 172           images of various types (kernel, FDT blob, ramdisk, etc.)
 173           in a single blob.  To boot this new uImage structure,
 174           pass the address of the blob to the "bootm" command.
 175           FIT is very flexible, supporting compression, multiple images,
 176           multiple configurations, verification through hashing and also
 177           verified boot (secure boot using RSA).
 178
 179 if FIT
 180
 181 config FIT_ENABLE_SHA256_SUPPORT
 182         bool "Support SHA256 checksum of FIT image contents"
 183         select SHA256
 184         default y
 185         help
 186           Enable this to support SHA256 checksum of FIT image contents. A
 187           SHA256 checksum is a 256-bit (32-byte) hash value used to check that
 188           the image contents have not been corrupted. SHA256 is recommended
 189           for use in secure applications since (as at 2016) there is no known
 190           feasible attack that could produce a 'collision' with differing
 191           input data. Use this for the highest security. Note that only the
 192           SHA256 variant is supported: SHA512 and others are not currently
 193           supported in U-Boot.
 194
 195 config FIT_SIGNATURE
 196         bool "Enable signature verification of FIT uImages"
 197         depends on DM
 198         select RSA
 199         help
 200           This option enables signature verification of FIT uImages,
 201           using a hash signed and verified using RSA. If
 202           CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
 203           hashing is available using hardware, then the RSA library will use
 204           it. See doc/uImage.FIT/signature.txt for more details.
 205
 206           WARNING: When relying on signed FIT images with a required signature
 207           check the legacy image format is disabled by default, so that
 208           unsigned images cannot be loaded. If a board needs the legacy image
 209           format support in this case, enable it using
 210           CONFIG_IMAGE_FORMAT_LEGACY.
 211
 212 config FIT_VERBOSE
 213         bool "Show verbose messages when FIT images fail"
 214         help
 215           Generally a system will have valid FIT images so debug messages
 216           are a waste of code space. If you are debugging your images then
 217           you can enable this option to get more verbose information about
 218           failures.
 219
 220 config FIT_BEST_MATCH
 221         bool "Select the best match for the kernel device tree"
 222         help
 223           When no configuration is explicitly selected, default to the
 224           one whose fdt's compatibility field best matches that of
 225           U-Boot itself. A match is considered "best" if it matches the
 226           most specific compatibility entry of U-Boot's fdt's root node.
 227           The order of entries in the configuration's fdt is ignored.
 228
 229 config FIT_IMAGE_POST_PROCESS
 230         bool "Enable post-processing of FIT artifacts after loading by U-Boot"
 231         depends on TI_SECURE_DEVICE
 232         help
 233           Allows doing any sort of manipulation to blobs after they got extracted
 234           from FIT images like stripping off headers or modifying the size of the
 235           blob, verification, authentication, decryption etc. in a platform or
 236           board specific way. In order to use this feature a platform or board-
 237           specific implementation of board_fit_image_post_process() must be
 238           provided. Also, anything done during this post-processing step would
 239           need to be comprehended in how the images were prepared before being
 240           injected into the FIT creation (i.e. the blobs would have been pre-
 241           processed before being added to the FIT image).
 242
 243 if SPL
 244
 245 config SPL_FIT
 246         bool "Support Flattened Image Tree within SPL"
 247         depends on SPL
 248         select SPL_OF_LIBFDT
 249
 250 config SPL_FIT_SIGNATURE
 251         bool "Enable signature verification of FIT firmware within SPL"
 252         depends on SPL_DM
 253         select SPL_FIT
 254         select SPL_RSA
 255
 256 config SPL_LOAD_FIT
 257         bool "Enable SPL loading U-Boot as a FIT"
 258         select SPL_FIT
 259         help
 260           Normally with the SPL framework a legacy image is generated as part
 261           of the build. This contains U-Boot along with information as to
 262           where it should be loaded. This option instead enables generation
 263           of a FIT (Flat Image Tree) which provides more flexibility. In
 264           particular it can handle selecting from multiple device tree
 265           and passing the correct one to U-Boot.
 266
 267 config SPL_FIT_IMAGE_POST_PROCESS
 268         bool "Enable post-processing of FIT artifacts after loading by the SPL"
 269         depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
 270         help
 271           Allows doing any sort of manipulation to blobs after they got extracted
 272           from the U-Boot FIT image like stripping off headers or modifying the
 273           size of the blob, verification, authentication, decryption etc. in a
 274           platform or board specific way. In order to use this feature a platform
 275           or board-specific implementation of board_fit_image_post_process() must
 276           be provided. Also, anything done during this post-processing step would
 277           need to be comprehended in how the images were prepared before being
 278           injected into the FIT creation (i.e. the blobs would have been pre-
 279           processed before being added to the FIT image).
 280
 281 config SPL_FIT_SOURCE
 282         string ".its source file for U-Boot FIT image"
 283         depends on SPL_FIT
 284         help
 285           Specifies a (platform specific) FIT source file to generate the
 286           U-Boot FIT image. This could specify further image to load and/or
 287           execute.
 288
 289 config SPL_FIT_GENERATOR
 290         string ".its file generator script for U-Boot FIT image"
 291         depends on SPL_FIT
 292         default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
 293         help
 294           Specifies a (platform specific) script file to generate the FIT
 295           source file used to build the U-Boot FIT image file. This gets
 296           passed a list of supported device tree file stub names to
 297           include in the generated image.
 298
 299 endif # SPL
 300
 301 endif # FIT
 302
 303 config OF_BOARD_SETUP
 304         bool "Set up board-specific details in device tree before boot"
 305         depends on OF_LIBFDT
 306         help
 307           This causes U-Boot to call ft_board_setup() before booting into
 308           the Operating System. This function can set up various
 309           board-specific information in the device tree for use by the OS.
 310           The device tree is then passed to the OS.
 311
 312 config OF_SYSTEM_SETUP
 313         bool "Set up system-specific details in device tree before boot"
 314         depends on OF_LIBFDT
 315         help
 316           This causes U-Boot to call ft_system_setup() before booting into
 317           the Operating System. This function can set up various
 318           system-specific information in the device tree for use by the OS.
 319           The device tree is then passed to the OS.
 320
 321 config OF_STDOUT_VIA_ALIAS
 322         bool "Update the device-tree stdout alias from U-Boot"
 323         depends on OF_LIBFDT
 324         help
 325           This uses U-Boot's serial alias from the aliases node to update
 326           the device tree passed to the OS. The "linux,stdout-path" property
 327           in the chosen node is set to point to the correct serial node.
 328           This option currently references CONFIG_CONS_INDEX, which is
 329           incorrect when used with device tree as this option does not
 330           exist / should not be used.
 331
 332 config SYS_EXTRA_OPTIONS
 333         string "Extra Options (DEPRECATED)"
 334         help
 335           The old configuration infrastructure (= mkconfig + boards.cfg)
 336           provided the extra options field. If you have something like
 337           "HAS_BAR,BAZ=64", the optional options
 338             #define CONFIG_HAS
 339             #define CONFIG_BAZ  64
 340           will be defined in include/config.h.
 341           This option was prepared for the smooth migration from the old
 342           configuration to Kconfig. Since this option will be removed sometime,
 343           new boards should not use this option.
 344
 345 config SYS_TEXT_BASE
 346         depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
 347                 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
 348                 ARCH_ZYNQ || ARCH_KEYSTONE || ARCH_OMAP2PLUS
 349         depends on !EFI_APP
 350         hex "Text Base"
 351         help
 352           TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
 353
 354         default 0x80800000 if ARCH_OMAP2PLUS
 355
 356
 357 config SYS_CLK_FREQ
 358         depends on ARC || ARCH_SUNXI
 359         int "CPU clock frequency"
 360         help
 361           TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
 362
 363 config ARCH_FIXUP_FDT_MEMORY
 364         bool "Enable arch_fixup_memory_banks() call"
 365         default y
 366         help
 367           Enable FDT memory map syncup before OS boot. This feature can be
 368           used for booting OS with different memory setup where the part of
 369           the memory location should be used for different purpose.
 370
 371 endmenu         # Boot images
 372
 373 source "api/Kconfig"
 374
 375 source "common/Kconfig"
 376
 377 source "cmd/Kconfig"
 378
 379 source "disk/Kconfig"
 380
 381 source "dts/Kconfig"
 382
 383 source "env/Kconfig"
 384
 385 source "net/Kconfig"
 386
 387 source "drivers/Kconfig"
 388
 389 source "fs/Kconfig"
 390
 391 source "lib/Kconfig"
 392
 393 source "test/Kconfig"
 394
 395 source "scripts/Kconfig"