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 TPL_BOOTSTAGE
  31         bool "Boot timing and reported in TPL"
  32         depends on BOOTSTAGE
  33         help
  34           Enable recording of boot time in SPL. To make this visible to U-Boot
  35           proper, enable BOOTSTAGE_STASH as well. This will stash the timing
  36           information when TPL finishes and load it when U-Boot proper starts
  37           up.
  38
  39 config BOOTSTAGE_REPORT
  40         bool "Display a detailed boot timing report before booting the OS"
  41         depends on BOOTSTAGE
  42         help
  43           Enable output of a boot time report just before the OS is booted.
  44           This shows how long it took U-Boot to go through each stage of the
  45           boot process. The report looks something like this:
  46
  47                 Timer summary in microseconds:
  48                        Mark    Elapsed  Stage
  49                           0          0  reset
  50                   3,575,678  3,575,678  board_init_f start
  51                   3,575,695         17  arch_cpu_init A9
  52                   3,575,777         82  arch_cpu_init done
  53                   3,659,598     83,821  board_init_r start
  54                   3,910,375    250,777  main_loop
  55                  29,916,167 26,005,792  bootm_start
  56                  30,361,327    445,160  start_kernel
  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 SPL_BOOTSTAGE_RECORD_COUNT
  66         int "Number of boot stage records to store for SPL"
  67         default 5
  68         help
  69           This is the size of the bootstage record list and is the maximum
  70           number of bootstage records that can be recorded.
  71
  72 config BOOTSTAGE_FDT
  73         bool "Store boot timing information in the OS device tree"
  74         depends on BOOTSTAGE
  75         help
  76           Stash the bootstage information in the FDT. A root 'bootstage'
  77           node is created with each bootstage id as a child. Each child
  78           has a 'name' property and either 'mark' containing the
  79           mark time in microseconds, or 'accum' containing the
  80           accumulated time for that bootstage id in microseconds.
  81           For example:
  82
  83                 bootstage {
  84                         154 {
  85                                 name = "board_init_f";
  86                                 mark = <3575678>;
  87                         };
  88                         170 {
  89                                 name = "lcd";
  90                                 accum = <33482>;
  91                         };
  92                 };
  93
  94           Code in the Linux kernel can find this in /proc/devicetree.
  95
  96 config BOOTSTAGE_STASH
  97         bool "Stash the boot timing information in memory before booting OS"
  98         depends on BOOTSTAGE
  99         help
 100           Some OSes do not support device tree. Bootstage can instead write
 101           the boot timing information in a binary format at a given address.
 102           This happens through a call to bootstage_stash(), typically in
 103           the CPU's cleanup_before_linux() function. You can use the
 104           'bootstage stash' and 'bootstage unstash' commands to do this on
 105           the command line.
 106
 107 config BOOTSTAGE_STASH_ADDR
 108         hex "Address to stash boot timing information"
 109         default 0
 110         help
 111           Provide an address which will not be overwritten by the OS when it
 112           starts, so that it can read this information when ready.
 113
 114 config BOOTSTAGE_STASH_SIZE
 115         hex "Size of boot timing stash region"
 116         default 0x1000
 117         help
 118           This should be large enough to hold the bootstage stash. A value of
 119           4096 (4KiB) is normally plenty.
 120
 121 endmenu
 122
 123 menu "Boot media"
 124
 125 config NOR_BOOT
 126         bool "Support for booting from NOR flash"
 127         depends on NOR
 128         help
 129           Enabling this will make a U-Boot binary that is capable of being
 130           booted via NOR.  In this case we will enable certain pinmux early
 131           as the ROM only partially sets up pinmux.  We also default to using
 132           NOR for environment.
 133
 134 config NAND_BOOT
 135         bool "Support for booting from NAND flash"
 136         default n
 137         imply NAND
 138         help
 139           Enabling this will make a U-Boot binary that is capable of being
 140           booted via NAND flash. This is not a must, some SoCs need this,
 141           some not.
 142
 143 config ONENAND_BOOT
 144         bool "Support for booting from ONENAND"
 145         default n
 146         imply NAND
 147         help
 148           Enabling this will make a U-Boot binary that is capable of being
 149           booted via ONENAND. This is not a must, some SoCs need this,
 150           some not.
 151
 152 config QSPI_BOOT
 153         bool "Support for booting from QSPI flash"
 154         default n
 155         help
 156           Enabling this will make a U-Boot binary that is capable of being
 157           booted via QSPI flash. This is not a must, some SoCs need this,
 158           some not.
 159
 160 config SATA_BOOT
 161         bool "Support for booting from SATA"
 162         default n
 163         help
 164           Enabling this will make a U-Boot binary that is capable of being
 165           booted via SATA. This is not a must, some SoCs need this,
 166           some not.
 167
 168 config SD_BOOT
 169         bool "Support for booting from SD/EMMC"
 170         default n
 171         help
 172           Enabling this will make a U-Boot binary that is capable of being
 173           booted via SD/EMMC. This is not a must, some SoCs need this,
 174           some not.
 175
 176 config SPI_BOOT
 177         bool "Support for booting from SPI flash"
 178         default n
 179         help
 180           Enabling this will make a U-Boot binary that is capable of being
 181           booted via SPI flash. This is not a must, some SoCs need this,
 182           some not.
 183
 184 endmenu
 185
 186 config BOOTDELAY
 187         int "delay in seconds before automatically booting"
 188         default 2
 189         depends on AUTOBOOT
 190         help
 191           Delay before automatically running bootcmd;
 192           set to 0 to autoboot with no delay, but you can stop it by key input.
 193           set to -1 to disable autoboot.
 194           set to -2 to autoboot with no delay and not check for abort
 195
 196           If this value is >= 0 then it is also used for the default delay
 197           before starting the default entry in bootmenu. If it is < 0 then
 198           a default value of 10s is used.
 199
 200           See doc/README.autoboot for details.
 201
 202 config USE_BOOTARGS
 203         bool "Enable boot arguments"
 204         help
 205           Provide boot arguments to bootm command. Boot arguments are specified
 206           in CONFIG_BOOTARGS option. Enable this option to be able to specify
 207           CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
 208           will be undefined and won't take any space in U-Boot image.
 209
 210 config BOOTARGS
 211         string "Boot arguments"
 212         depends on USE_BOOTARGS
 213         help
 214           This can be used to pass arguments to the bootm command. The value of
 215           CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
 216           this value will also override the "chosen" node in FDT blob.
 217
 218 config USE_BOOTCOMMAND
 219         bool "Enable a default value for bootcmd"
 220         help
 221           Provide a default value for the bootcmd entry in the environment.  If
 222           autoboot is enabled this is what will be run automatically.  Enable
 223           this option to be able to specify CONFIG_BOOTCOMMAND as a string.  If
 224           this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
 225           won't take any space in U-Boot image.
 226
 227 config BOOTCOMMAND
 228         string "bootcmd value"
 229         depends on USE_BOOTCOMMAND
 230         default "run distro_bootcmd" if DISTRO_DEFAULTS
 231         help
 232           This is the string of commands that will be used as bootcmd and if
 233           AUTOBOOT is set, automatically run.
 234
 235 config USE_PREBOOT
 236         bool "Enable preboot"
 237         help
 238           When this option is enabled, the existence of the environment
 239           variable "preboot" will be checked immediately before starting the
 240           CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
 241           entering interactive mode.
 242
 243           This feature is especially useful when "preboot" is automatically
 244           generated or modified. For example, the boot code can modify the
 245           "preboot" when a user holds down a certain combination of keys.
 246
 247 config PREBOOT
 248         string "preboot default value"
 249         depends on USE_PREBOOT
 250         default ""
 251         help
 252           This is the default of "preboot" environment variable.
 253
 254 menu "Console"
 255
 256 config MENU
 257         bool
 258         help
 259           This is the library functionality to provide a text-based menu of
 260           choices for the user to make choices with.
 261
 262 config CONSOLE_RECORD
 263         bool "Console recording"
 264         help
 265           This provides a way to record console output (and provide console
 266           input) through circular buffers. This is mostly useful for testing.
 267           Console output is recorded even when the console is silent.
 268           To enable console recording, call console_record_reset_enable()
 269           from your code.
 270
 271 config CONSOLE_RECORD_OUT_SIZE
 272         hex "Output buffer size"
 273         depends on CONSOLE_RECORD
 274         default 0x400 if CONSOLE_RECORD
 275         help
 276           Set the size of the console output buffer. When this fills up, no
 277           more data will be recorded until some is removed. The buffer is
 278           allocated immediately after the malloc() region is ready.
 279
 280 config CONSOLE_RECORD_IN_SIZE
 281         hex "Input buffer size"
 282         depends on CONSOLE_RECORD
 283         default 0x100 if CONSOLE_RECORD
 284         help
 285           Set the size of the console input buffer. When this contains data,
 286           tstc() and getc() will use this in preference to real device input.
 287           The buffer is allocated immediately after the malloc() region is
 288           ready.
 289
 290 config DISABLE_CONSOLE
 291         bool "Add functionality to disable console completely"
 292         help
 293                 Disable console (in & out).
 294
 295 config IDENT_STRING
 296         string "Board specific string to be added to uboot version string"
 297         help
 298           This options adds the board specific name to u-boot version.
 299
 300 config LOGLEVEL
 301         int "loglevel"
 302         default 4
 303         range 0 8
 304         help
 305           All Messages with a loglevel smaller than the console loglevel will
 306           be compiled in. The loglevels are defined as follows:
 307
 308             0 - emergency
 309             1 - alert
 310             2 - critical
 311             3 - error
 312             4 - warning
 313             5 - note
 314             6 - info
 315             7 - debug
 316             8 - debug content
 317             9 - debug hardware I/O
 318
 319 config SPL_LOGLEVEL
 320         int
 321         default LOGLEVEL
 322
 323 config TPL_LOGLEVEL
 324         int
 325         default LOGLEVEL
 326
 327 config SILENT_CONSOLE
 328         bool "Support a silent console"
 329         help
 330           This option allows the console to be silenced, meaning that no
 331           output will appear on the console devices. This is controlled by
 332           setting the environment variable 'silent' to a non-empty value.
 333           Note this also silences the console when booting Linux.
 334
 335           When the console is set up, the variable is checked, and the
 336           GD_FLG_SILENT flag is set. Changing the environment variable later
 337           will update the flag.
 338
 339 config SILENT_U_BOOT_ONLY
 340         bool "Only silence the U-Boot console"
 341         depends on SILENT_CONSOLE
 342         help
 343           Normally when the U-Boot console is silenced, Linux's console is
 344           also silenced (assuming the board boots into Linux). This option
 345           allows the linux console to operate normally, even if U-Boot's
 346           is silenced.
 347
 348 config SILENT_CONSOLE_UPDATE_ON_SET
 349         bool "Changes to the 'silent' environment variable update immediately"
 350         depends on SILENT_CONSOLE
 351         default y if SILENT_CONSOLE
 352         help
 353           When the 'silent' environment variable is changed, update the
 354           console silence flag immediately. This allows 'setenv' to be used
 355           to silence or un-silence the console.
 356
 357           The effect is that any change to the variable will affect the
 358           GD_FLG_SILENT flag.
 359
 360 config SILENT_CONSOLE_UPDATE_ON_RELOC
 361         bool "Allow flags to take effect on relocation"
 362         depends on SILENT_CONSOLE
 363         help
 364           In some cases the environment is not available until relocation
 365           (e.g. NAND). This option makes the value of the 'silent'
 366           environment variable take effect at relocation.
 367
 368 config PRE_CONSOLE_BUFFER
 369         bool "Buffer characters before the console is available"
 370         help
 371           Prior to the console being initialised (i.e. serial UART
 372           initialised etc) all console output is silently discarded.
 373           Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
 374           buffer any console messages prior to the console being
 375           initialised to a buffer. The buffer is a circular buffer, so
 376           if it overflows, earlier output is discarded.
 377
 378           Note that this is not currently supported in SPL. It would be
 379           useful to be able to share the pre-console buffer with SPL.
 380
 381 config PRE_CON_BUF_SZ
 382         int "Sets the size of the pre-console buffer"
 383         depends on PRE_CONSOLE_BUFFER
 384         default 4096
 385         help
 386           The size of the pre-console buffer affects how much console output
 387           can be held before it overflows and starts discarding earlier
 388           output. Normally there is very little output at this early stage,
 389           unless debugging is enabled, so allow enough for ~10 lines of
 390           text.
 391
 392           This is a useful feature if you are using a video console and
 393           want to see the full boot output on the console. Without this
 394           option only the post-relocation output will be displayed.
 395
 396 config PRE_CON_BUF_ADDR
 397         hex "Address of the pre-console buffer"
 398         depends on PRE_CONSOLE_BUFFER
 399         default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
 400         default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
 401         help
 402           This sets the start address of the pre-console buffer. This must
 403           be in available memory and is accessed before relocation and
 404           possibly before DRAM is set up. Therefore choose an address
 405           carefully.
 406
 407           We should consider removing this option and allocating the memory
 408           in board_init_f_init_reserve() instead.
 409
 410 config CONSOLE_MUX
 411         bool "Enable console multiplexing"
 412         default y if DM_VIDEO || VIDEO || LCD
 413         help
 414           This allows multiple devices to be used for each console 'file'.
 415           For example, stdout can be set to go to serial and video.
 416           Similarly, stdin can be set to come from serial and keyboard.
 417           Input can be provided from either source. Console multiplexing
 418           adds a small amount of size to U-Boot.  Changes to the environment
 419           variables stdout, stdin and stderr will take effect immediately.
 420
 421 config SYS_CONSOLE_IS_IN_ENV
 422         bool "Select console devices from the environment"
 423         default y if CONSOLE_MUX
 424         help
 425           This allows multiple input/output devices to be set at boot time.
 426           For example, if stdout is set to "serial,video" then output will
 427           be sent to both the serial and video devices on boot. The
 428           environment variables can be updated after boot to change the
 429           input/output devices.
 430
 431 config SYS_CONSOLE_OVERWRITE_ROUTINE
 432         bool "Allow board control over console overwriting"
 433         help
 434           If this is enabled, and the board-specific function
 435           overwrite_console() returns 1, the stdin, stderr and stdout are
 436           switched to the serial port, else the settings in the environment
 437           are used. If this is not enabled, the console will not be switched
 438           to serial.
 439
 440 config SYS_CONSOLE_ENV_OVERWRITE
 441         bool "Update environment variables during console init"
 442         help
 443           The console environment variables (stdout, stdin, stderr) can be
 444           used to determine the correct console devices on start-up. This
 445           option writes the console devices to these variables on console
 446           start-up (after relocation). This causes the environment to be
 447           updated to match the console devices actually chosen.
 448
 449 config SYS_CONSOLE_INFO_QUIET
 450         bool "Don't display the console devices on boot"
 451         help
 452           Normally U-Boot displays the current settings for stdout, stdin
 453           and stderr on boot when the post-relocation console is set up.
 454           Enable this option to suppress this output. It can be obtained by
 455           calling stdio_print_current_devices() from board code.
 456
 457 config SYS_STDIO_DEREGISTER
 458         bool "Allow deregistering stdio devices"
 459         default y if USB_KEYBOARD
 460         help
 461           Generally there is no need to deregister stdio devices since they
 462           are never deactivated. But if a stdio device is used which can be
 463           removed (for example a USB keyboard) then this option can be
 464           enabled to ensure this is handled correctly.
 465
 466 endmenu
 467
 468 menu "Logging"
 469
 470 config LOG
 471         bool "Enable logging support"
 472         depends on DM
 473         help
 474           This enables support for logging of status and debug messages. These
 475           can be displayed on the console, recorded in a memory buffer, or
 476           discarded if not needed. Logging supports various categories and
 477           levels of severity.
 478
 479 config SPL_LOG
 480         bool "Enable logging support in SPL"
 481         depends on LOG
 482         help
 483           This enables support for logging of status and debug messages. These
 484           can be displayed on the console, recorded in a memory buffer, or
 485           discarded if not needed. Logging supports various categories and
 486           levels of severity.
 487
 488 config TPL_LOG
 489         bool "Enable logging support in TPL"
 490         depends on LOG
 491         help
 492           This enables support for logging of status and debug messages. These
 493           can be displayed on the console, recorded in a memory buffer, or
 494           discarded if not needed. Logging supports various categories and
 495           levels of severity.
 496
 497 config LOG_MAX_LEVEL
 498         int "Maximum log level to record"
 499         depends on LOG
 500         default 5
 501         help
 502           This selects the maximum log level that will be recorded. Any value
 503           higher than this will be ignored. If possible log statements below
 504           this level will be discarded at build time. Levels:
 505
 506             0 - emergency
 507             1 - alert
 508             2 - critical
 509             3 - error
 510             4 - warning
 511             5 - note
 512             6 - info
 513             7 - debug
 514             8 - debug content
 515             9 - debug hardware I/O
 516
 517 config SPL_LOG_MAX_LEVEL
 518         int "Maximum log level to record in SPL"
 519         depends on SPL_LOG
 520         default 3
 521         help
 522           This selects the maximum log level that will be recorded. Any value
 523           higher than this will be ignored. If possible log statements below
 524           this level will be discarded at build time. Levels:
 525
 526             0 - emergency
 527             1 - alert
 528             2 - critical
 529             3 - error
 530             4 - warning
 531             5 - note
 532             6 - info
 533             7 - debug
 534             8 - debug content
 535             9 - debug hardware I/O
 536
 537 config TPL_LOG_MAX_LEVEL
 538         int "Maximum log level to record in TPL"
 539         depends on TPL_LOG
 540         default 3
 541         help
 542           This selects the maximum log level that will be recorded. Any value
 543           higher than this will be ignored. If possible log statements below
 544           this level will be discarded at build time. Levels:
 545
 546             0 - emergency
 547             1 - alert
 548             2 - critical
 549             3 - error
 550             4 - warning
 551             5 - note
 552             6 - info
 553             7 - debug
 554             8 - debug content
 555             9 - debug hardware I/O
 556
 557 config LOG_DEFAULT_LEVEL
 558         int "Default logging level to display"
 559         default 6
 560         help
 561           This is the default logging level set when U-Boot starts. It can
 562           be adjusted later using the 'log level' command. Note that setting
 563           this to a value above LOG_MAX_LEVEL will be ineffective, since the
 564           higher levels are not compiled in to U-Boot.
 565
 566             0 - emergency
 567             1 - alert
 568             2 - critical
 569             3 - error
 570             4 - warning
 571             5 - note
 572             6 - info
 573             7 - debug
 574             8 - debug content
 575             9 - debug hardware I/O
 576
 577 config LOG_CONSOLE
 578         bool "Allow log output to the console"
 579         depends on LOG
 580         default y
 581         help
 582           Enables a log driver which writes log records to the console.
 583           Generally the console is the serial port or LCD display. Only the
 584           log message is shown - other details like level, category, file and
 585           line number are omitted.
 586
 587 config SPL_LOG_CONSOLE
 588         bool "Allow log output to the console in SPL"
 589         depends on SPL_LOG
 590         default y
 591         help
 592           Enables a log driver which writes log records to the console.
 593           Generally the console is the serial port or LCD display. Only the
 594           log message is shown - other details like level, category, file and
 595           line number are omitted.
 596
 597 config TPL_LOG_CONSOLE
 598         bool "Allow log output to the console in SPL"
 599         depends on TPL_LOG
 600         default y
 601         help
 602           Enables a log driver which writes log records to the console.
 603           Generally the console is the serial port or LCD display. Only the
 604           log message is shown - other details like level, category, file and
 605           line number are omitted.
 606
 607 config LOG_TEST
 608         bool "Provide a test for logging"
 609         depends on LOG
 610         default y if SANDBOX
 611         help
 612           This enables a 'log test' command to test logging. It is normally
 613           executed from a pytest and simply outputs logging information
 614           in various different ways to test that the logging system works
 615           correctly with various settings.
 616
 617 config LOG_ERROR_RETURN
 618         bool "Log all functions which return an error"
 619         depends on LOG
 620         help
 621           When an error is returned in U-Boot it is sometimes difficult to
 622           figure out the root cause. For example, reading from SPI flash may
 623           fail due to a problem in the SPI controller or due to the flash part
 624           not returning the expected information. This option changes
 625           log_ret() to log any errors it sees. With this option disabled,
 626           log_ret() is a nop.
 627
 628           You can add log_ret() to all functions which return an error code.
 629
 630 endmenu
 631
 632 config SUPPORT_RAW_INITRD
 633         bool "Enable raw initrd images"
 634         help
 635           Note, defining the SUPPORT_RAW_INITRD allows user to supply
 636           kernel with raw initrd images. The syntax is slightly different, the
 637           address of the initrd must be augmented by it's size, in the following
 638           format: "<initrd address>:<initrd size>".
 639
 640 config DEFAULT_FDT_FILE
 641         string "Default fdt file"
 642         help
 643           This option is used to set the default fdt file to boot OS.
 644
 645 config MISC_INIT_R
 646         bool "Execute Misc Init"
 647         default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
 648         default y if ARCH_OMAP2PLUS && !AM33XX
 649         help
 650           Enabling this option calls 'misc_init_r' function
 651
 652 config VERSION_VARIABLE
 653         bool "add U-Boot environment variable vers"
 654         default n
 655         help
 656           If this variable is defined, an environment variable
 657           named "ver" is created by U-Boot showing the U-Boot
 658           version as printed by the "version" command.
 659           Any change to this variable will be reverted at the
 660           next reset.
 661
 662 config BOARD_LATE_INIT
 663         bool "Execute Board late init"
 664         help
 665           Sometimes board require some initialization code that might
 666           require once the actual init done, example saving board specific env,
 667           boot-modes etc. which eventually done at late.
 668
 669           So this config enable the late init code with the help of board_late_init
 670           function which should defined on respective boards.
 671
 672 config DISPLAY_CPUINFO
 673         bool "Display information about the CPU during start up"
 674         default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
 675         help
 676           Display information about the CPU that U-Boot is running on
 677           when U-Boot starts up. The function print_cpuinfo() is called
 678           to do this.
 679
 680 config DISPLAY_BOARDINFO
 681         bool "Display information about the board during early start up"
 682         default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
 683         help
 684           Display information about the board that U-Boot is running on
 685           when U-Boot starts up. The board function checkboard() is called
 686           to do this.
 687
 688 config DISPLAY_BOARDINFO_LATE
 689         bool "Display information about the board during late start up"
 690         help
 691           Display information about the board that U-Boot is running on after
 692           the relocation phase. The board function checkboard() is called to do
 693           this.
 694
 695 config BOUNCE_BUFFER
 696         bool "Include bounce buffer API"
 697         help
 698           Some peripherals support DMA from a subset of physically
 699           addressable memory only.  To support such peripherals, the
 700           bounce buffer API uses a temporary buffer: it copies data
 701           to/from DMA regions while managing cache operations.
 702
 703           A second possible use of bounce buffers is their ability to
 704           provide aligned buffers for DMA operations.
 705
 706 config BOARD_TYPES
 707         bool "Call get_board_type() to get and display the board type"
 708         help
 709           If this option is enabled, checkboard() will call get_board_type()
 710           to get a string containing the board type and this will be
 711           displayed immediately after the model is shown on the console
 712           early in boot.
 713
 714 menu "Start-up hooks"
 715
 716 config ARCH_EARLY_INIT_R
 717         bool "Call arch-specific init soon after relocation"
 718         help
 719           With this option U-Boot will call arch_early_init_r() soon after
 720           relocation. Driver model is running by this point, and the cache
 721           is on. Note that board_early_init_r() is called first, if
 722           enabled. This can be used to set up architecture-specific devices.
 723
 724 config ARCH_MISC_INIT
 725         bool "Call arch-specific init after relocation, when console is ready"
 726         help
 727           With this option U-Boot will call arch_misc_init() after
 728           relocation to allow miscellaneous arch-dependent initialisation
 729           to be performed. This function should be defined by the board
 730           and will be called after the console is set up, after relocation.
 731
 732 config BOARD_EARLY_INIT_F
 733         bool "Call board-specific init before relocation"
 734         help
 735           Some boards need to perform initialisation as soon as possible
 736           after boot. With this option, U-Boot calls board_early_init_f()
 737           after driver model is ready in the pre-relocation init sequence.
 738           Note that the normal serial console is not yet set up, but the
 739           debug UART will be available if enabled.
 740
 741 config BOARD_EARLY_INIT_R
 742         bool "Call board-specific init after relocation"
 743         help
 744           Some boards need to perform initialisation as directly after
 745           relocation. With this option, U-Boot calls board_early_init_r()
 746           in the post-relocation init sequence.
 747
 748 config LAST_STAGE_INIT
 749         bool "Call board-specific as last setup step"
 750         help
 751           Some boards need to perform initialisation immediately before control
 752           is passed to the command-line interpreter (e.g. for initializations
 753           that depend on later phases in the init sequence). With this option,
 754           U-Boot calls last_stage_init() before the command-line interpreter is
 755           started.
 756
 757 endmenu
 758
 759 menu "Security support"
 760
 761 config HASH
 762         bool # "Support hashing API (SHA1, SHA256, etc.)"
 763         help
 764           This provides a way to hash data in memory using various supported
 765           algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
 766           and the algorithms it supports are defined in common/hash.c. See
 767           also CMD_HASH for command-line access.
 768
 769 config AVB_VERIFY
 770         bool "Build Android Verified Boot operations"
 771         depends on LIBAVB && FASTBOOT
 772         depends on PARTITION_UUIDS
 773         help
 774           This option enables compilation of bootloader-dependent operations,
 775           used by Android Verified Boot 2.0 library (libavb). Includes:
 776             * Helpers to process strings in order to build OS bootargs.
 777             * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
 778             * Helpers to alloc/init/free avb ops.
 779
 780 config SPL_HASH
 781         bool # "Support hashing API (SHA1, SHA256, etc.)"
 782         help
 783           This provides a way to hash data in memory using various supported
 784           algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
 785           and the algorithms it supports are defined in common/hash.c. See
 786           also CMD_HASH for command-line access.
 787
 788 config TPL_HASH
 789         bool # "Support hashing API (SHA1, SHA256, etc.)"
 790         help
 791           This provides a way to hash data in memory using various supported
 792           algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
 793           and the algorithms it supports are defined in common/hash.c. See
 794           also CMD_HASH for command-line access.
 795
 796 endmenu
 797
 798 menu "Update support"
 799
 800 config UPDATE_TFTP
 801         bool "Auto-update using fitImage via TFTP"
 802         depends on FIT
 803         help
 804           This option allows performing update of NOR with data in fitImage
 805           sent via TFTP boot.
 806
 807 config UPDATE_TFTP_CNT_MAX
 808         int "The number of connection retries during auto-update"
 809         default 0
 810         depends on UPDATE_TFTP
 811
 812 config UPDATE_TFTP_MSEC_MAX
 813         int "Delay in mSec to wait for the TFTP server during auto-update"
 814         default 100
 815         depends on UPDATE_TFTP
 816
 817 endmenu
 818
 819 menu "Blob list"
 820
 821 config BLOBLIST
 822         bool "Support for a bloblist"
 823         help
 824           This enables support for a bloblist in U-Boot, which can be passed
 825           from TPL to SPL to U-Boot proper (and potentially to Linux). The
 826           blob list supports multiple binary blobs of data, each with a tag,
 827           so that different U-Boot components can store data which can survive
 828           through to the next stage of the boot.
 829
 830 config SPL_BLOBLIST
 831         bool "Support for a bloblist in SPL"
 832         depends on BLOBLIST
 833         default y if SPL
 834         help
 835           This enables a bloblist in SPL. If this is the first part of U-Boot
 836           to run, then the bloblist is set up in SPL and passed to U-Boot
 837           proper. If TPL also has a bloblist, then SPL uses the one from there.
 838
 839 config TPL_BLOBLIST
 840         bool "Support for a bloblist in TPL"
 841         depends on BLOBLIST
 842         default y if TPL
 843         help
 844           This enables a bloblist in TPL. The bloblist is set up in TPL and
 845           passed to SPL and U-Boot proper.
 846
 847 config BLOBLIST_SIZE
 848         hex "Size of bloblist"
 849         depends on BLOBLIST
 850         default 0x400
 851         help
 852           Sets the size of the bloblist in bytes. This must include all
 853           overhead (alignment, bloblist header, record header). The bloblist
 854           is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
 855           proper), and this sane bloblist is used for subsequent stages.
 856
 857 config BLOBLIST_ADDR
 858         hex "Address of bloblist"
 859         depends on BLOBLIST
 860         default 0xe000 if SANDBOX
 861         help
 862           Sets the address of the bloblist, set up by the first part of U-Boot
 863           which runs. Subsequent U-Boot stages typically use the same address.
 864
 865 endmenu
 866
 867 source "common/spl/Kconfig"