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 menuconfig EXPERT
  99         bool "Configure standard U-Boot features (expert users)"
 100         default y
 101         help
 102           This option allows certain base U-Boot options and settings
 103           to be disabled or tweaked. This is for specialized
 104           environments which can tolerate a "non-standard" U-Boot.
 105           Use this only if you really know what you are doing.
 106
 107 if EXPERT
 108         config SYS_MALLOC_CLEAR_ON_INIT
 109         bool "Init with zeros the memory reserved for malloc (slow)"
 110         default y
 111         help
 112           This setting is enabled by default. The reserved malloc
 113           memory is initialized with zeros, so first malloc calls
 114           will return the pointer to the zeroed memory. But this
 115           slows the boot time.
 116
 117           It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
 118           value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
 119           Then the boot time can be significantly reduced.
 120           Warning:
 121           When disabling this, please check if malloc calls, maybe
 122           should be replaced by calloc - if one expects zeroed memory.
 123
 124 config TOOLS_DEBUG
 125         bool "Enable debug information for tools"
 126         help
 127           Enable generation of debug information for tools such as mkimage.
 128           This can be used for debugging purposes. With debug information
 129           it is possible to set breakpoints on particular lines, single-step
 130           debug through the source code, etc.
 131
 132 endif # EXPERT
 133
 134 config PHYS_64BIT
 135         bool "64bit physical address support"
 136         help
 137           Say Y here to support 64bit physical memory address.
 138           This can be used not only for 64bit SoCs, but also for
 139           large physical address extention on 32bit SoCs.
 140
 141 endmenu         # General setup
 142
 143 menu "Boot images"
 144
 145 config FIT
 146         bool "Support Flattened Image Tree"
 147         select MD5
 148         help
 149           This option allows you to boot the new uImage structure,
 150           Flattened Image Tree.  FIT is formally a FDT, which can include
 151           images of various types (kernel, FDT blob, ramdisk, etc.)
 152           in a single blob.  To boot this new uImage structure,
 153           pass the address of the blob to the "bootm" command.
 154           FIT is very flexible, supporting compression, multiple images,
 155           multiple configurations, verification through hashing and also
 156           verified boot (secure boot using RSA).
 157
 158 if FIT
 159
 160 config FIT_SIGNATURE
 161         bool "Enable signature verification of FIT uImages"
 162         depends on DM
 163         select RSA
 164         help
 165           This option enables signature verification of FIT uImages,
 166           using a hash signed and verified using RSA. If
 167           CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
 168           hashing is available using hardware, then the RSA library will use
 169           it. See doc/uImage.FIT/signature.txt for more details.
 170
 171           WARNING: When relying on signed FIT images with a required signature
 172           check the legacy image format is disabled by default, so that
 173           unsigned images cannot be loaded. If a board needs the legacy image
 174           format support in this case, enable it using
 175           CONFIG_IMAGE_FORMAT_LEGACY.
 176
 177 config FIT_VERBOSE
 178         bool "Show verbose messages when FIT images fail"
 179         help
 180           Generally a system will have valid FIT images so debug messages
 181           are a waste of code space. If you are debugging your images then
 182           you can enable this option to get more verbose information about
 183           failures.
 184
 185 config FIT_BEST_MATCH
 186         bool "Select the best match for the kernel device tree"
 187         help
 188           When no configuration is explicitly selected, default to the
 189           one whose fdt's compatibility field best matches that of
 190           U-Boot itself. A match is considered "best" if it matches the
 191           most specific compatibility entry of U-Boot's fdt's root node.
 192           The order of entries in the configuration's fdt is ignored.
 193
 194 config FIT_IMAGE_POST_PROCESS
 195         bool "Enable post-processing of FIT artifacts after loading by U-Boot"
 196         depends on TI_SECURE_DEVICE
 197         help
 198           Allows doing any sort of manipulation to blobs after they got extracted
 199           from FIT images like stripping off headers or modifying the size of the
 200           blob, verification, authentication, decryption etc. in a platform or
 201           board specific way. In order to use this feature a platform or board-
 202           specific implementation of board_fit_image_post_process() must be
 203           provided. Also, anything done during this post-processing step would
 204           need to be comprehended in how the images were prepared before being
 205           injected into the FIT creation (i.e. the blobs would have been pre-
 206           processed before being added to the FIT image).
 207
 208 config SPL_FIT
 209         bool "Support Flattened Image Tree within SPL"
 210         depends on SPL
 211
 212 config SPL_FIT_SIGNATURE
 213         bool "Enable signature verification of FIT firmware within SPL"
 214         depends on SPL_FIT
 215         depends on SPL_DM
 216         select SPL_RSA
 217
 218 config SPL_LOAD_FIT
 219         bool "Enable SPL loading U-Boot as a FIT"
 220         help
 221           Normally with the SPL framework a legacy image is generated as part
 222           of the build. This contains U-Boot along with information as to
 223           where it should be loaded. This option instead enables generation
 224           of a FIT (Flat Image Tree) which provides more flexibility. In
 225           particular it can handle selecting from multiple device tree
 226           and passing the correct one to U-Boot.
 227
 228 config SPL_FIT_IMAGE_POST_PROCESS
 229         bool "Enable post-processing of FIT artifacts after loading by the SPL"
 230         depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
 231         help
 232           Allows doing any sort of manipulation to blobs after they got extracted
 233           from the U-Boot FIT image like stripping off headers or modifying the
 234           size of the blob, verification, authentication, decryption etc. in a
 235           platform or board specific way. In order to use this feature a platform
 236           or board-specific implementation of board_fit_image_post_process() must
 237           be provided. Also, anything done during this post-processing step would
 238           need to be comprehended in how the images were prepared before being
 239           injected into the FIT creation (i.e. the blobs would have been pre-
 240           processed before being added to the FIT image).
 241
 242 endif # FIT
 243
 244 config OF_BOARD_SETUP
 245         bool "Set up board-specific details in device tree before boot"
 246         depends on OF_LIBFDT
 247         help
 248           This causes U-Boot to call ft_board_setup() before booting into
 249           the Operating System. This function can set up various
 250           board-specific information in the device tree for use by the OS.
 251           The device tree is then passed to the OS.
 252
 253 config OF_SYSTEM_SETUP
 254         bool "Set up system-specific details in device tree before boot"
 255         depends on OF_LIBFDT
 256         help
 257           This causes U-Boot to call ft_system_setup() before booting into
 258           the Operating System. This function can set up various
 259           system-specific information in the device tree for use by the OS.
 260           The device tree is then passed to the OS.
 261
 262 config OF_STDOUT_VIA_ALIAS
 263         bool "Update the device-tree stdout alias from U-Boot"
 264         depends on OF_LIBFDT
 265         help
 266           This uses U-Boot's serial alias from the aliases node to update
 267           the device tree passed to the OS. The "linux,stdout-path" property
 268           in the chosen node is set to point to the correct serial node.
 269           This option currently references CONFIG_CONS_INDEX, which is
 270           incorrect when used with device tree as this option does not
 271           exist / should not be used.
 272
 273 config SYS_EXTRA_OPTIONS
 274         string "Extra Options (DEPRECATED)"
 275         help
 276           The old configuration infrastructure (= mkconfig + boards.cfg)
 277           provided the extra options field. If you have something like
 278           "HAS_BAR,BAZ=64", the optional options
 279             #define CONFIG_HAS
 280             #define CONFIG_BAZ  64
 281           will be defined in include/config.h.
 282           This option was prepared for the smooth migration from the old
 283           configuration to Kconfig. Since this option will be removed sometime,
 284           new boards should not use this option.
 285
 286 config SYS_TEXT_BASE
 287         depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
 288                 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
 289                 ARCH_ZYNQ || ARCH_KEYSTONE
 290         depends on !EFI_APP
 291         hex "Text Base"
 292         help
 293           TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
 294
 295
 296 config SYS_CLK_FREQ
 297         depends on ARC || ARCH_SUNXI
 298         int "CPU clock frequency"
 299         help
 300           TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
 301
 302 config ARCH_FIXUP_FDT_MEMORY
 303         bool "Enable arch_fixup_memory_banks() call"
 304         default y
 305         help
 306           Enable FDT memory map syncup before OS boot. This feature can be
 307           used for booting OS with different memory setup where the part of
 308           the memory location should be used for different purpose.
 309
 310 endmenu         # Boot images
 311
 312 source "api/Kconfig"
 313
 314 source "common/Kconfig"
 315
 316 source "cmd/Kconfig"
 317
 318 source "disk/Kconfig"
 319
 320 source "dts/Kconfig"
 321
 322 source "net/Kconfig"
 323
 324 source "drivers/Kconfig"
 325
 326 source "fs/Kconfig"
 327
 328 source "lib/Kconfig"
 329
 330 source "test/Kconfig"
 331
 332 source "scripts/Kconfig"