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