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