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_EEPROM
 180         bool "Environment in EEPROM"
 181         depends on !CHAIN_OF_TRUST
 182         help
 183           Use this if you have an EEPROM or similar serial access
 184           device and a driver for it.
 185
 186           - CONFIG_ENV_OFFSET:
 187           - CONFIG_ENV_SIZE:
 188
 189           These two #defines specify the offset and size of the
 190           environment area within the total memory of your EEPROM.
 191
 192           - CONFIG_SYS_I2C_EEPROM_ADDR:
 193           If defined, specified the chip address of the EEPROM device.
 194           The default address is zero.
 195
 196           - CONFIG_SYS_I2C_EEPROM_BUS:
 197           If defined, specified the i2c bus of the EEPROM device.
 198
 199           - CONFIG_SYS_EEPROM_PAGE_WRITE_BITS:
 200           If defined, the number of bits used to address bytes in a
 201           single page in the EEPROM device.  A 64 byte page, for example
 202           would require six bits.
 203
 204           - CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS:
 205           If defined, the number of milliseconds to delay between
 206           page writes.  The default is zero milliseconds.
 207
 208           - CONFIG_SYS_I2C_EEPROM_ADDR_LEN:
 209           The length in bytes of the EEPROM memory array address.  Note
 210           that this is NOT the chip address length!
 211
 212           - CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW:
 213           EEPROM chips that implement "address overflow" are ones
 214           like Catalyst 24WC04/08/16 which has 9/10/11 bits of
 215           address and the extra bits end up in the "chip address" bit
 216           slots. This makes a 24WC08 (1Kbyte) chip look like four 256
 217           byte chips.
 218
 219           Note that we consider the length of the address field to
 220           still be one byte because the extra address bits are hidden
 221           in the chip address.
 222
 223           - CONFIG_SYS_EEPROM_SIZE:
 224           The size in bytes of the EEPROM device.
 225
 226           - CONFIG_ENV_EEPROM_IS_ON_I2C
 227           define this, if you have I2C and SPI activated, and your
 228           EEPROM, which holds the environment, is on the I2C bus.
 229
 230           - CONFIG_I2C_ENV_EEPROM_BUS
 231           if you have an Environment on an EEPROM reached over
 232           I2C muxes, you can define here, how to reach this
 233           EEPROM. For example:
 234
 235           #define CONFIG_I2C_ENV_EEPROM_BUS       1
 236
 237           EEPROM which holds the environment, is reached over
 238           a pca9547 i2c mux with address 0x70, channel 3.
 239
 240 config ENV_IS_IN_FLASH
 241         bool "Environment in flash memory"
 242         depends on !CHAIN_OF_TRUST
 243         help
 244           Define this if you have a flash device which you want to use for the
 245           environment.
 246
 247           a) The environment occupies one whole flash sector, which is
 248            "embedded" in the text segment with the U-Boot code. This
 249            happens usually with "bottom boot sector" or "top boot
 250            sector" type flash chips, which have several smaller
 251            sectors at the start or the end. For instance, such a
 252            layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
 253            such a case you would place the environment in one of the
 254            4 kB sectors - with U-Boot code before and after it. With
 255            "top boot sector" type flash chips, you would put the
 256            environment in one of the last sectors, leaving a gap
 257            between U-Boot and the environment.
 258
 259           CONFIG_ENV_OFFSET:
 260
 261            Offset of environment data (variable area) to the
 262            beginning of flash memory; for instance, with bottom boot
 263            type flash chips the second sector can be used: the offset
 264            for this sector is given here.
 265
 266            CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
 267
 268           CONFIG_ENV_ADDR:
 269
 270            This is just another way to specify the start address of
 271            the flash sector containing the environment (instead of
 272            CONFIG_ENV_OFFSET).
 273
 274           CONFIG_ENV_SECT_SIZE:
 275
 276            Size of the sector containing the environment.
 277
 278
 279           b) Sometimes flash chips have few, equal sized, BIG sectors.
 280            In such a case you don't want to spend a whole sector for
 281            the environment.
 282
 283           CONFIG_ENV_SIZE:
 284
 285            If you use this in combination with CONFIG_ENV_IS_IN_FLASH
 286            and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
 287            of this flash sector for the environment. This saves
 288            memory for the RAM copy of the environment.
 289
 290            It may also save flash memory if you decide to use this
 291            when your environment is "embedded" within U-Boot code,
 292            since then the remainder of the flash sector could be used
 293            for U-Boot code. It should be pointed out that this is
 294            STRONGLY DISCOURAGED from a robustness point of view:
 295            updating the environment in flash makes it always
 296            necessary to erase the WHOLE sector. If something goes
 297            wrong before the contents has been restored from a copy in
 298            RAM, your target system will be dead.
 299
 300           CONFIG_ENV_ADDR_REDUND
 301           CONFIG_ENV_SIZE_REDUND
 302
 303            These settings describe a second storage area used to hold
 304            a redundant copy of the environment data, so that there is
 305            a valid backup copy in case there is a power failure during
 306            a "saveenv" operation.
 307
 308           BE CAREFUL! Any changes to the flash layout, and some changes to the
 309           source code will make it necessary to adapt <board>/u-boot.lds*
 310           accordingly!
 311
 312 config ENV_IS_IN_MMC
 313         bool "Environment in an MMC device"
 314         depends on !CHAIN_OF_TRUST
 315         default y if ARCH_SUNXI
 316         help
 317           Define this if you have an MMC device which you want to use for the
 318           environment.
 319
 320           CONFIG_SYS_MMC_ENV_DEV:
 321
 322           Specifies which MMC device the environment is stored in.
 323
 324           CONFIG_SYS_MMC_ENV_PART (optional):
 325
 326           Specifies which MMC partition the environment is stored in. If not
 327           set, defaults to partition 0, the user area. Common values might be
 328           1 (first MMC boot partition), 2 (second MMC boot partition).
 329
 330           CONFIG_ENV_OFFSET:
 331           CONFIG_ENV_SIZE:
 332
 333           These two #defines specify the offset and size of the environment
 334           area within the specified MMC device.
 335
 336           If offset is positive (the usual case), it is treated as relative to
 337           the start of the MMC partition. If offset is negative, it is treated
 338           as relative to the end of the MMC partition. This can be useful if
 339           your board may be fitted with different MMC devices, which have
 340           different sizes for the MMC partitions, and you always want the
 341           environment placed at the very end of the partition, to leave the
 342           maximum possible space before it, to store other data.
 343
 344           These two values are in units of bytes, but must be aligned to an
 345           MMC sector boundary.
 346
 347           CONFIG_ENV_OFFSET_REDUND (optional):
 348
 349           Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
 350           hold a redundant copy of the environment data. This provides a
 351           valid backup copy in case the other copy is corrupted, e.g. due
 352           to a power failure during a "saveenv" operation.
 353
 354           This value may also be positive or negative; this is handled in the
 355           same way as CONFIG_ENV_OFFSET.
 356
 357           This value is also in units of bytes, but must also be aligned to
 358           an MMC sector boundary.
 359
 360           CONFIG_ENV_SIZE_REDUND (optional):
 361
 362           This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
 363           set. If this value is set, it must be set to the same value as
 364           CONFIG_ENV_SIZE.
 365
 366 config ENV_IS_IN_NAND
 367         bool "Environment in a NAND device"
 368         depends on !CHAIN_OF_TRUST
 369         help
 370           Define this if you have a NAND device which you want to use for the
 371           environment.
 372
 373           - CONFIG_ENV_OFFSET:
 374           - CONFIG_ENV_SIZE:
 375
 376           These two #defines specify the offset and size of the environment
 377           area within the first NAND device.  CONFIG_ENV_OFFSET must be
 378           aligned to an erase block boundary.
 379
 380           - CONFIG_ENV_OFFSET_REDUND (optional):
 381
 382           This setting describes a second storage area of CONFIG_ENV_SIZE
 383           size used to hold a redundant copy of the environment data, so
 384           that there is a valid backup copy in case there is a power failure
 385           during a "saveenv" operation.  CONFIG_ENV_OFFSET_REDUND must be
 386           aligned to an erase block boundary.
 387
 388           - CONFIG_ENV_RANGE (optional):
 389
 390           Specifies the length of the region in which the environment
 391           can be written.  This should be a multiple of the NAND device's
 392           block size.  Specifying a range with more erase blocks than
 393           are needed to hold CONFIG_ENV_SIZE allows bad blocks within
 394           the range to be avoided.
 395
 396           - CONFIG_ENV_OFFSET_OOB (optional):
 397
 398           Enables support for dynamically retrieving the offset of the
 399           environment from block zero's out-of-band data.  The
 400           "nand env.oob" command can be used to record this offset.
 401           Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
 402           using CONFIG_ENV_OFFSET_OOB.
 403
 404 config ENV_IS_IN_NVRAM
 405         bool "Environment in a non-volatile RAM"
 406         depends on !CHAIN_OF_TRUST
 407         help
 408           Define this if you have some non-volatile memory device
 409           (NVRAM, battery buffered SRAM) which you want to use for the
 410           environment.
 411
 412           - CONFIG_ENV_ADDR:
 413           - CONFIG_ENV_SIZE:
 414
 415           These two #defines are used to determine the memory area you
 416           want to use for environment. It is assumed that this memory
 417           can just be read and written to, without any special
 418           provision.
 419
 420 config ENV_IS_IN_UBI
 421         bool "Environment in a UBI volume"
 422         depends on !CHAIN_OF_TRUST
 423         help
 424           Define this if you have an UBI volume that you want to use for the
 425           environment.  This has the benefit of wear-leveling the environment
 426           accesses, which is important on NAND.
 427
 428           - CONFIG_ENV_UBI_PART:
 429
 430           Define this to a string that is the mtd partition containing the UBI.
 431
 432           - CONFIG_ENV_UBI_VOLUME:
 433
 434           Define this to the name of the volume that you want to store the
 435           environment in.
 436
 437           - CONFIG_ENV_UBI_VOLUME_REDUND:
 438
 439           Define this to the name of another volume to store a second copy of
 440           the environment in.  This will enable redundant environments in UBI.
 441           It is assumed that both volumes are in the same MTD partition.
 442
 443           - CONFIG_UBI_SILENCE_MSG
 444           - CONFIG_UBIFS_SILENCE_MSG
 445
 446           You will probably want to define these to avoid a really noisy system
 447           when storing the env in UBI.
 448
 449 config ENV_IS_NOWHERE
 450         bool "Environment is not stored"
 451         help
 452           Define this if you don't want to or can't have an environment stored
 453           on a storage medium
 454
 455 if ARCH_SUNXI
 456
 457 config ENV_OFFSET
 458         hex "Environment Offset"
 459         depends on !ENV_IS_IN_UBI
 460         depends on !ENV_IS_NOWHERE
 461         default 0x88000 if ARCH_SUNXI
 462         help
 463           Offset from the start of the device (or partition)
 464
 465 config ENV_SIZE
 466         hex "Environment Size"
 467         depends on !ENV_IS_NOWHERE
 468         default 0x20000 if ARCH_SUNXI
 469         help
 470           Size of the environment storage area
 471
 472 config ENV_UBI_PART
 473         string "UBI partition name"
 474         depends on ENV_IS_IN_UBI
 475         help
 476           MTD partition containing the UBI device
 477
 478 config ENV_UBI_VOLUME
 479         string "UBI volume name"
 480         depends on ENV_IS_IN_UBI
 481         help
 482           Name of the volume that you want to store the environment in.
 483
 484 endif
 485
 486 endmenu
 487
 488 config BOOTDELAY
 489         int "delay in seconds before automatically booting"
 490         default 2
 491         depends on AUTOBOOT
 492         help
 493           Delay before automatically running bootcmd;
 494           set to 0 to autoboot with no delay, but you can stop it by key input.
 495           set to -1 to disable autoboot.
 496           set to -2 to autoboot with no delay and not check for abort
 497
 498           See doc/README.autoboot for details.
 499
 500 menu "Console"
 501
 502 config MENU
 503         bool
 504         help
 505           This is the library functionality to provide a text-based menu of
 506           choices for the user to make choices with.
 507
 508 config CONSOLE_RECORD
 509         bool "Console recording"
 510         help
 511           This provides a way to record console output (and provide console
 512           input) through circular buffers. This is mostly useful for testing.
 513           Console output is recorded even when the console is silent.
 514           To enable console recording, call console_record_reset_enable()
 515           from your code.
 516
 517 config CONSOLE_RECORD_OUT_SIZE
 518         hex "Output buffer size"
 519         depends on CONSOLE_RECORD
 520         default 0x400 if CONSOLE_RECORD
 521         help
 522           Set the size of the console output buffer. When this fills up, no
 523           more data will be recorded until some is removed. The buffer is
 524           allocated immediately after the malloc() region is ready.
 525
 526 config CONSOLE_RECORD_IN_SIZE
 527         hex "Input buffer size"
 528         depends on CONSOLE_RECORD
 529         default 0x100 if CONSOLE_RECORD
 530         help
 531           Set the size of the console input buffer. When this contains data,
 532           tstc() and getc() will use this in preference to real device input.
 533           The buffer is allocated immediately after the malloc() region is
 534           ready.
 535
 536 config IDENT_STRING
 537         string "Board specific string to be added to uboot version string"
 538         help
 539           This options adds the board specific name to u-boot version.
 540
 541 config SILENT_CONSOLE
 542         bool "Support a silent console"
 543         help
 544           This option allows the console to be silenced, meaning that no
 545           output will appear on the console devices. This is controlled by
 546           setting the environment vaariable 'silent' to a non-empty value.
 547           Note this also silences the console when booting Linux.
 548
 549           When the console is set up, the variable is checked, and the
 550           GD_FLG_SILENT flag is set. Changing the environment variable later
 551           will update the flag.
 552
 553 config SILENT_U_BOOT_ONLY
 554         bool "Only silence the U-Boot console"
 555         depends on SILENT_CONSOLE
 556         help
 557           Normally when the U-Boot console is silenced, Linux's console is
 558           also silenced (assuming the board boots into Linux). This option
 559           allows the linux console to operate normally, even if U-Boot's
 560           is silenced.
 561
 562 config SILENT_CONSOLE_UPDATE_ON_SET
 563         bool "Changes to the 'silent' environment variable update immediately"
 564         depends on SILENT_CONSOLE
 565         default y if SILENT_CONSOLE
 566         help
 567           When the 'silent' environment variable is changed, update the
 568           console silence flag immediately. This allows 'setenv' to be used
 569           to silence or un-silence the console.
 570
 571           The effect is that any change to the variable will affect the
 572           GD_FLG_SILENT flag.
 573
 574 config SILENT_CONSOLE_UPDATE_ON_RELOC
 575         bool "Allow flags to take effect on relocation"
 576         depends on SILENT_CONSOLE
 577         help
 578           In some cases the environment is not available until relocation
 579           (e.g. NAND). This option makes the value of the 'silent'
 580           environment variable take effect at relocation.
 581
 582 config PRE_CONSOLE_BUFFER
 583         bool "Buffer characters before the console is available"
 584         help
 585           Prior to the console being initialised (i.e. serial UART
 586           initialised etc) all console output is silently discarded.
 587           Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
 588           buffer any console messages prior to the console being
 589           initialised to a buffer. The buffer is a circular buffer, so
 590           if it overflows, earlier output is discarded.
 591
 592           Note that this is not currently supported in SPL. It would be
 593           useful to be able to share the pre-console buffer with SPL.
 594
 595 config PRE_CON_BUF_SZ
 596         int "Sets the size of the pre-console buffer"
 597         depends on PRE_CONSOLE_BUFFER
 598         default 4096
 599         help
 600           The size of the pre-console buffer affects how much console output
 601           can be held before it overflows and starts discarding earlier
 602           output. Normally there is very little output at this early stage,
 603           unless debugging is enabled, so allow enough for ~10 lines of
 604           text.
 605
 606           This is a useful feature if you are using a video console and
 607           want to see the full boot output on the console. Without this
 608           option only the post-relocation output will be displayed.
 609
 610 config PRE_CON_BUF_ADDR
 611         hex "Address of the pre-console buffer"
 612         depends on PRE_CONSOLE_BUFFER
 613         default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
 614         default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
 615         help
 616           This sets the start address of the pre-console buffer. This must
 617           be in available memory and is accessed before relocation and
 618           possibly before DRAM is set up. Therefore choose an address
 619           carefully.
 620
 621           We should consider removing this option and allocating the memory
 622           in board_init_f_init_reserve() instead.
 623
 624 config CONSOLE_MUX
 625         bool "Enable console multiplexing"
 626         default y if DM_VIDEO || VIDEO || LCD
 627         help
 628           This allows multiple devices to be used for each console 'file'.
 629           For example, stdout can be set to go to serial and video.
 630           Similarly, stdin can be set to come from serial and keyboard.
 631           Input can be provided from either source. Console multiplexing
 632           adds a small amount of size to U-Boot.  Changes to the environment
 633           variables stdout, stdin and stderr will take effect immediately.
 634
 635 config SYS_CONSOLE_IS_IN_ENV
 636         bool "Select console devices from the environment"
 637         default y if CONSOLE_MUX
 638         help
 639           This allows multiple input/output devices to be set at boot time.
 640           For example, if stdout is set to "serial,video" then output will
 641           be sent to both the serial and video devices on boot. The
 642           environment variables can be updated after boot to change the
 643           input/output devices.
 644
 645 config SYS_CONSOLE_OVERWRITE_ROUTINE
 646         bool "Allow board control over console overwriting"
 647         help
 648           If this is enabled, and the board-specific function
 649           overwrite_console() returns 1, the stdin, stderr and stdout are
 650           switched to the serial port, else the settings in the environment
 651           are used. If this is not enabled, the console will not be switched
 652           to serial.
 653
 654 config SYS_CONSOLE_ENV_OVERWRITE
 655         bool "Update environment variables during console init"
 656         help
 657           The console environment variables (stdout, stdin, stderr) can be
 658           used to determine the correct console devices on start-up. This
 659           option writes the console devices to these variables on console
 660           start-up (after relocation). This causes the environment to be
 661           updated to match the console devices actually chosen.
 662
 663 config SYS_CONSOLE_INFO_QUIET
 664         bool "Don't display the console devices on boot"
 665         help
 666           Normally U-Boot displays the current settings for stdout, stdin
 667           and stderr on boot when the post-relocation console is set up.
 668           Enable this option to supress this output. It can be obtained by
 669           calling stdio_print_current_devices() from board code.
 670
 671 config SYS_STDIO_DEREGISTER
 672         bool "Allow deregistering stdio devices"
 673         default y if USB_KEYBOARD
 674         help
 675           Generally there is no need to deregister stdio devices since they
 676           are never deactivated. But if a stdio device is used which can be
 677           removed (for example a USB keyboard) then this option can be
 678           enabled to ensure this is handled correctly.
 679
 680 endmenu
 681
 682 config DTB_RESELECT
 683         bool "Support swapping dtbs at a later point in boot"
 684         depends on FIT_EMBED
 685         help
 686           It is possible during initial boot you may need to use a generic
 687           dtb until you can fully determine the board your running on. This
 688           config allows boards to implement a function at a later point
 689           during boot to switch to the "correct" dtb.
 690
 691 config FIT_EMBED
 692         bool "Support a FIT image embedded in the U-boot image"
 693         help
 694           This option provides hooks to allow U-boot to parse an
 695           appended FIT image and enable board specific code to then select
 696           the correct DTB to be used.
 697
 698 config DEFAULT_FDT_FILE
 699         string "Default fdt file"
 700         help
 701           This option is used to set the default fdt file to boot OS.
 702
 703 config VERSION_VARIABLE
 704         bool "add U-Boot environment variable vers"
 705         default n
 706         help
 707           If this variable is defined, an environment variable
 708           named "ver" is created by U-Boot showing the U-Boot
 709           version as printed by the "version" command.
 710           Any change to this variable will be reverted at the
 711           next reset.
 712
 713 config BOARD_LATE_INIT
 714         bool
 715         help
 716           Sometimes board require some initialization code that might
 717           require once the actual init done, example saving board specific env,
 718           boot-modes etc. which eventually done at late.
 719
 720           So this config enable the late init code with the help of board_late_init
 721           function which should defined on respective boards.
 722
 723 config DISPLAY_CPUINFO
 724         bool "Display information about the CPU during start up"
 725         default y if ARM || NIOS2 || X86 || XTENSA
 726         help
 727           Display information about the CPU that U-Boot is running on
 728           when U-Boot starts up. The function print_cpuinfo() is called
 729           to do this.
 730
 731 config DISPLAY_BOARDINFO
 732         bool "Display information about the board during start up"
 733         default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
 734         help
 735           Display information about the board that U-Boot is running on
 736           when U-Boot starts up. The board function checkboard() is called
 737           to do this.
 738
 739 menu "Start-up hooks"
 740
 741 config ARCH_EARLY_INIT_R
 742         bool "Call arch-specific init soon after relocation"
 743         default y if X86
 744         help
 745           With this option U-Boot will call arch_early_init_r() soon after
 746           relocation. Driver model is running by this point, and the cache
 747           is on. Note that board_early_init_r() is called first, if
 748           enabled. This can be used to set up architecture-specific devices.
 749
 750 config ARCH_MISC_INIT
 751         bool "Call arch-specific init after relocation, when console is ready"
 752         help
 753           With this option U-Boot will call arch_misc_init() after
 754           relocation to allow miscellaneous arch-dependent initialisation
 755           to be performed. This function should be defined by the board
 756           and will be called after the console is set up, after relocaiton.
 757
 758 config BOARD_EARLY_INIT_F
 759         bool "Call board-specific init before relocation"
 760         default y if X86
 761         help
 762           Some boards need to perform initialisation as soon as possible
 763           after boot. With this option, U-Boot calls board_early_init_f()
 764           after driver model is ready in the pre-relocation init sequence.
 765           Note that the normal serial console is not yet set up, but the
 766           debug UART will be available if enabled.
 767
 768 endmenu
 769
 770 menu "Security support"
 771
 772 config HASH
 773         bool # "Support hashing API (SHA1, SHA256, etc.)"
 774         help
 775           This provides a way to hash data in memory using various supported
 776           algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
 777           and the algorithms it supports are defined in common/hash.c. See
 778           also CMD_HASH for command-line access.
 779
 780 endmenu
 781
 782 source "common/spl/Kconfig"