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