common/Kconfig

   1 menu "Boot timing"
   2
   3 config BOOTSTAGE
   4         bool "Boot timing and reporting"
   5         help
   6           Enable recording of boot time while booting. To use it, insert
   7           calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
   8           bootstage.h. Only a single entry is recorded for each ID. You can
   9           give the entry a name with bootstage_mark_name(). You can also
  10           record elapsed time in a particular stage using bootstage_start()
  11           before starting and bootstage_accum() when finished. Bootstage will
  12           add up all the accumulated time and report it.
  13
  14           Normally, IDs are defined in bootstage.h but a small number of
  15           additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
  16           as the ID.
  17
  18           Calls to show_boot_progress() will also result in log entries but
  19           these will not have names.
  20
  21 config SPL_BOOTSTAGE
  22         bool "Boot timing and reported in SPL"
  23         depends on BOOTSTAGE
  24         help
  25           Enable recording of boot time in SPL. To make this visible to U-Boot
  26           proper, enable BOOTSTAGE_STASH as well. This will stash the timing
  27           information when SPL finishes and load it when U-Boot proper starts
  28           up.
  29
  30 config BOOTSTAGE_REPORT
  31         bool "Display a detailed boot timing report before booting the OS"
  32         depends on BOOTSTAGE
  33         help
  34           Enable output of a boot time report just before the OS is booted.
  35           This shows how long it took U-Boot to go through each stage of the
  36           boot process. The report looks something like this:
  37
  38                 Timer summary in microseconds:
  39                        Mark    Elapsed  Stage
  40                           0          0  reset
  41                   3,575,678  3,575,678  board_init_f start
  42                   3,575,695         17  arch_cpu_init A9
  43                   3,575,777         82  arch_cpu_init done
  44                   3,659,598     83,821  board_init_r start
  45                   3,910,375    250,777  main_loop
  46                  29,916,167 26,005,792  bootm_start
  47                  30,361,327    445,160  start_kernel
  48
  49 config BOOTSTAGE_RECORD_COUNT
  50         int "Number of boot stage records to store"
  51         default 30
  52         help
  53           This is the size of the bootstage record list and is the maximum
  54           number of bootstage records that can be recorded.
  55
  56 config BOOTSTAGE_FDT
  57         bool "Store boot timing information in the OS device tree"
  58         depends on BOOTSTAGE
  59         help
  60           Stash the bootstage information in the FDT. A root 'bootstage'
  61           node is created with each bootstage id as a child. Each child
  62           has a 'name' property and either 'mark' containing the
  63           mark time in microseconds, or 'accum' containing the
  64           accumulated time for that bootstage id in microseconds.
  65           For example:
  66
  67                 bootstage {
  68                         154 {
  69                                 name = "board_init_f";
  70                                 mark = <3575678>;
  71                         };
  72                         170 {
  73                                 name = "lcd";
  74                                 accum = <33482>;
  75                         };
  76                 };
  77
  78           Code in the Linux kernel can find this in /proc/devicetree.
  79
  80 config BOOTSTAGE_STASH
  81         bool "Stash the boot timing information in memory before booting OS"
  82         depends on BOOTSTAGE
  83         help
  84           Some OSes do not support device tree. Bootstage can instead write
  85           the boot timing information in a binary format at a given address.
  86           This happens through a call to bootstage_stash(), typically in
  87           the CPU's cleanup_before_linux() function. You can use the
  88           'bootstage stash' and 'bootstage unstash' commands to do this on
  89           the command line.
  90
  91 config BOOTSTAGE_STASH_ADDR
  92         hex "Address to stash boot timing information"
  93         default 0
  94         help
  95           Provide an address which will not be overwritten by the OS when it
  96           starts, so that it can read this information when ready.
  97
  98 config BOOTSTAGE_STASH_SIZE
  99         hex "Size of boot timing stash region"
 100         default 0x1000
 101         help
 102           This should be large enough to hold the bootstage stash. A value of
 103           4096 (4KiB) is normally plenty.
 104
 105 endmenu
 106
 107 menu "Boot media"
 108
 109 config NOR_BOOT
 110         bool "Support for booting from NOR flash"
 111         depends on NOR
 112         help
 113           Enabling this will make a U-Boot binary that is capable of being
 114           booted via NOR.  In this case we will enable certain pinmux early
 115           as the ROM only partially sets up pinmux.  We also default to using
 116           NOR for environment.
 117
 118 config NAND_BOOT
 119         bool "Support for booting from NAND flash"
 120         default n
 121         help
 122           Enabling this will make a U-Boot binary that is capable of being
 123           booted via NAND flash. This is not a must, some SoCs need this,
 124           some not.
 125
 126 config ONENAND_BOOT
 127         bool "Support for booting from ONENAND"
 128         default n
 129         help
 130           Enabling this will make a U-Boot binary that is capable of being
 131           booted via ONENAND. This is not a must, some SoCs need this,
 132           some not.
 133
 134 config QSPI_BOOT
 135         bool "Support for booting from QSPI flash"
 136         default n
 137         help
 138           Enabling this will make a U-Boot binary that is capable of being
 139           booted via QSPI flash. This is not a must, some SoCs need this,
 140           some not.
 141
 142 config SATA_BOOT
 143         bool "Support for booting from SATA"
 144         default n
 145         help
 146           Enabling this will make a U-Boot binary that is capable of being
 147           booted via SATA. This is not a must, some SoCs need this,
 148           some not.
 149
 150 config SD_BOOT
 151         bool "Support for booting from SD/EMMC"
 152         default n
 153         help
 154           Enabling this will make a U-Boot binary that is capable of being
 155           booted via SD/EMMC. This is not a must, some SoCs need this,
 156           some not.
 157
 158 config SPI_BOOT
 159         bool "Support for booting from SPI flash"
 160         default n
 161         help
 162           Enabling this will make a U-Boot binary that is capable of being
 163           booted via SPI flash. This is not a must, some SoCs need this,
 164           some not.
 165
 166 endmenu
 167
 168 config BOOTDELAY
 169         int "delay in seconds before automatically booting"
 170         default 2
 171         depends on AUTOBOOT
 172         help
 173           Delay before automatically running bootcmd;
 174           set to 0 to autoboot with no delay, but you can stop it by key input.
 175           set to -1 to disable autoboot.
 176           set to -2 to autoboot with no delay and not check for abort
 177
 178           See doc/README.autoboot for details.
 179
 180 config USE_BOOTARGS
 181         bool "Enable boot arguments"
 182         help
 183           Provide boot arguments to bootm command. Boot arguments are specified
 184           in CONFIG_BOOTARGS option. Enable this option to be able to specify
 185           CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
 186           will be undefined and won't take any space in U-Boot image.
 187
 188 config BOOTARGS
 189         string "Boot arguments"
 190         depends on USE_BOOTARGS
 191         help
 192           This can be used to pass arguments to the bootm command. The value of
 193           CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
 194           this value will also override the "chosen" node in FDT blob.
 195
 196 menu "Console"
 197
 198 config MENU
 199         bool
 200         help
 201           This is the library functionality to provide a text-based menu of
 202           choices for the user to make choices with.
 203
 204 config CONSOLE_RECORD
 205         bool "Console recording"
 206         help
 207           This provides a way to record console output (and provide console
 208           input) through circular buffers. This is mostly useful for testing.
 209           Console output is recorded even when the console is silent.
 210           To enable console recording, call console_record_reset_enable()
 211           from your code.
 212
 213 config CONSOLE_RECORD_OUT_SIZE
 214         hex "Output buffer size"
 215         depends on CONSOLE_RECORD
 216         default 0x400 if CONSOLE_RECORD
 217         help
 218           Set the size of the console output buffer. When this fills up, no
 219           more data will be recorded until some is removed. The buffer is
 220           allocated immediately after the malloc() region is ready.
 221
 222 config CONSOLE_RECORD_IN_SIZE
 223         hex "Input buffer size"
 224         depends on CONSOLE_RECORD
 225         default 0x100 if CONSOLE_RECORD
 226         help
 227           Set the size of the console input buffer. When this contains data,
 228           tstc() and getc() will use this in preference to real device input.
 229           The buffer is allocated immediately after the malloc() region is
 230           ready.
 231
 232 config IDENT_STRING
 233         string "Board specific string to be added to uboot version string"
 234         help
 235           This options adds the board specific name to u-boot version.
 236
 237 config SILENT_CONSOLE
 238         bool "Support a silent console"
 239         help
 240           This option allows the console to be silenced, meaning that no
 241           output will appear on the console devices. This is controlled by
 242           setting the environment vaariable 'silent' to a non-empty value.
 243           Note this also silences the console when booting Linux.
 244
 245           When the console is set up, the variable is checked, and the
 246           GD_FLG_SILENT flag is set. Changing the environment variable later
 247           will update the flag.
 248
 249 config SILENT_U_BOOT_ONLY
 250         bool "Only silence the U-Boot console"
 251         depends on SILENT_CONSOLE
 252         help
 253           Normally when the U-Boot console is silenced, Linux's console is
 254           also silenced (assuming the board boots into Linux). This option
 255           allows the linux console to operate normally, even if U-Boot's
 256           is silenced.
 257
 258 config SILENT_CONSOLE_UPDATE_ON_SET
 259         bool "Changes to the 'silent' environment variable update immediately"
 260         depends on SILENT_CONSOLE
 261         default y if SILENT_CONSOLE
 262         help
 263           When the 'silent' environment variable is changed, update the
 264           console silence flag immediately. This allows 'setenv' to be used
 265           to silence or un-silence the console.
 266
 267           The effect is that any change to the variable will affect the
 268           GD_FLG_SILENT flag.
 269
 270 config SILENT_CONSOLE_UPDATE_ON_RELOC
 271         bool "Allow flags to take effect on relocation"
 272         depends on SILENT_CONSOLE
 273         help
 274           In some cases the environment is not available until relocation
 275           (e.g. NAND). This option makes the value of the 'silent'
 276           environment variable take effect at relocation.
 277
 278 config PRE_CONSOLE_BUFFER
 279         bool "Buffer characters before the console is available"
 280         help
 281           Prior to the console being initialised (i.e. serial UART
 282           initialised etc) all console output is silently discarded.
 283           Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
 284           buffer any console messages prior to the console being
 285           initialised to a buffer. The buffer is a circular buffer, so
 286           if it overflows, earlier output is discarded.
 287
 288           Note that this is not currently supported in SPL. It would be
 289           useful to be able to share the pre-console buffer with SPL.
 290
 291 config PRE_CON_BUF_SZ
 292         int "Sets the size of the pre-console buffer"
 293         depends on PRE_CONSOLE_BUFFER
 294         default 4096
 295         help
 296           The size of the pre-console buffer affects how much console output
 297           can be held before it overflows and starts discarding earlier
 298           output. Normally there is very little output at this early stage,
 299           unless debugging is enabled, so allow enough for ~10 lines of
 300           text.
 301
 302           This is a useful feature if you are using a video console and
 303           want to see the full boot output on the console. Without this
 304           option only the post-relocation output will be displayed.
 305
 306 config PRE_CON_BUF_ADDR
 307         hex "Address of the pre-console buffer"
 308         depends on PRE_CONSOLE_BUFFER
 309         default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
 310         default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
 311         help
 312           This sets the start address of the pre-console buffer. This must
 313           be in available memory and is accessed before relocation and
 314           possibly before DRAM is set up. Therefore choose an address
 315           carefully.
 316
 317           We should consider removing this option and allocating the memory
 318           in board_init_f_init_reserve() instead.
 319
 320 config CONSOLE_MUX
 321         bool "Enable console multiplexing"
 322         default y if DM_VIDEO || VIDEO || LCD
 323         help
 324           This allows multiple devices to be used for each console 'file'.
 325           For example, stdout can be set to go to serial and video.
 326           Similarly, stdin can be set to come from serial and keyboard.
 327           Input can be provided from either source. Console multiplexing
 328           adds a small amount of size to U-Boot.  Changes to the environment
 329           variables stdout, stdin and stderr will take effect immediately.
 330
 331 config SYS_CONSOLE_IS_IN_ENV
 332         bool "Select console devices from the environment"
 333         default y if CONSOLE_MUX
 334         help
 335           This allows multiple input/output devices to be set at boot time.
 336           For example, if stdout is set to "serial,video" then output will
 337           be sent to both the serial and video devices on boot. The
 338           environment variables can be updated after boot to change the
 339           input/output devices.
 340
 341 config SYS_CONSOLE_OVERWRITE_ROUTINE
 342         bool "Allow board control over console overwriting"
 343         help
 344           If this is enabled, and the board-specific function
 345           overwrite_console() returns 1, the stdin, stderr and stdout are
 346           switched to the serial port, else the settings in the environment
 347           are used. If this is not enabled, the console will not be switched
 348           to serial.
 349
 350 config SYS_CONSOLE_ENV_OVERWRITE
 351         bool "Update environment variables during console init"
 352         help
 353           The console environment variables (stdout, stdin, stderr) can be
 354           used to determine the correct console devices on start-up. This
 355           option writes the console devices to these variables on console
 356           start-up (after relocation). This causes the environment to be
 357           updated to match the console devices actually chosen.
 358
 359 config SYS_CONSOLE_INFO_QUIET
 360         bool "Don't display the console devices on boot"
 361         help
 362           Normally U-Boot displays the current settings for stdout, stdin
 363           and stderr on boot when the post-relocation console is set up.
 364           Enable this option to supress this output. It can be obtained by
 365           calling stdio_print_current_devices() from board code.
 366
 367 config SYS_STDIO_DEREGISTER
 368         bool "Allow deregistering stdio devices"
 369         default y if USB_KEYBOARD
 370         help
 371           Generally there is no need to deregister stdio devices since they
 372           are never deactivated. But if a stdio device is used which can be
 373           removed (for example a USB keyboard) then this option can be
 374           enabled to ensure this is handled correctly.
 375
 376 endmenu
 377
 378 config DTB_RESELECT
 379         bool "Support swapping dtbs at a later point in boot"
 380         depends on FIT_EMBED
 381         help
 382           It is possible during initial boot you may need to use a generic
 383           dtb until you can fully determine the board your running on. This
 384           config allows boards to implement a function at a later point
 385           during boot to switch to the "correct" dtb.
 386
 387 config FIT_EMBED
 388         bool "Support a FIT image embedded in the U-boot image"
 389         help
 390           This option provides hooks to allow U-boot to parse an
 391           appended FIT image and enable board specific code to then select
 392           the correct DTB to be used.
 393
 394 config DEFAULT_FDT_FILE
 395         string "Default fdt file"
 396         help
 397           This option is used to set the default fdt file to boot OS.
 398
 399 config VERSION_VARIABLE
 400         bool "add U-Boot environment variable vers"
 401         default n
 402         help
 403           If this variable is defined, an environment variable
 404           named "ver" is created by U-Boot showing the U-Boot
 405           version as printed by the "version" command.
 406           Any change to this variable will be reverted at the
 407           next reset.
 408
 409 config BOARD_LATE_INIT
 410         bool
 411         help
 412           Sometimes board require some initialization code that might
 413           require once the actual init done, example saving board specific env,
 414           boot-modes etc. which eventually done at late.
 415
 416           So this config enable the late init code with the help of board_late_init
 417           function which should defined on respective boards.
 418
 419 config DISPLAY_CPUINFO
 420         bool "Display information about the CPU during start up"
 421         default y if ARM || NIOS2 || X86 || XTENSA
 422         help
 423           Display information about the CPU that U-Boot is running on
 424           when U-Boot starts up. The function print_cpuinfo() is called
 425           to do this.
 426
 427 config DISPLAY_BOARDINFO
 428         bool "Display information about the board during start up"
 429         default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
 430         help
 431           Display information about the board that U-Boot is running on
 432           when U-Boot starts up. The board function checkboard() is called
 433           to do this.
 434
 435 menu "Start-up hooks"
 436
 437 config ARCH_EARLY_INIT_R
 438         bool "Call arch-specific init soon after relocation"
 439         help
 440           With this option U-Boot will call arch_early_init_r() soon after
 441           relocation. Driver model is running by this point, and the cache
 442           is on. Note that board_early_init_r() is called first, if
 443           enabled. This can be used to set up architecture-specific devices.
 444
 445 config ARCH_MISC_INIT
 446         bool "Call arch-specific init after relocation, when console is ready"
 447         help
 448           With this option U-Boot will call arch_misc_init() after
 449           relocation to allow miscellaneous arch-dependent initialisation
 450           to be performed. This function should be defined by the board
 451           and will be called after the console is set up, after relocaiton.
 452
 453 config BOARD_EARLY_INIT_F
 454         bool "Call board-specific init before relocation"
 455         help
 456           Some boards need to perform initialisation as soon as possible
 457           after boot. With this option, U-Boot calls board_early_init_f()
 458           after driver model is ready in the pre-relocation init sequence.
 459           Note that the normal serial console is not yet set up, but the
 460           debug UART will be available if enabled.
 461
 462 endmenu
 463
 464 menu "Security support"
 465
 466 config HASH
 467         bool # "Support hashing API (SHA1, SHA256, etc.)"
 468         help
 469           This provides a way to hash data in memory using various supported
 470           algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
 471           and the algorithms it supports are defined in common/hash.c. See
 472           also CMD_HASH for command-line access.
 473
 474 endmenu
 475
 476 source "common/spl/Kconfig"