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