1menu "Boot timing" 2 3config 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 21config 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 30config 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 39config 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 58config 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 65config 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 72config 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 96config 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 107config 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 114config 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 121endmenu 122 123menu "Boot media" 124 125config 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 134config 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 143config 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 152config 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 160config 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 168config 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 176config 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 184endmenu 185 186config 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 202config 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 210config 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 218config 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 227config 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 235menu "Console" 236 237config MENU 238 bool 239 help 240 This is the library functionality to provide a text-based menu of 241 choices for the user to make choices with. 242 243config CONSOLE_RECORD 244 bool "Console recording" 245 help 246 This provides a way to record console output (and provide console 247 input) through circular buffers. This is mostly useful for testing. 248 Console output is recorded even when the console is silent. 249 To enable console recording, call console_record_reset_enable() 250 from your code. 251 252config CONSOLE_RECORD_OUT_SIZE 253 hex "Output buffer size" 254 depends on CONSOLE_RECORD 255 default 0x400 if CONSOLE_RECORD 256 help 257 Set the size of the console output buffer. When this fills up, no 258 more data will be recorded until some is removed. The buffer is 259 allocated immediately after the malloc() region is ready. 260 261config CONSOLE_RECORD_IN_SIZE 262 hex "Input buffer size" 263 depends on CONSOLE_RECORD 264 default 0x100 if CONSOLE_RECORD 265 help 266 Set the size of the console input buffer. When this contains data, 267 tstc() and getc() will use this in preference to real device input. 268 The buffer is allocated immediately after the malloc() region is 269 ready. 270 271config DISABLE_CONSOLE 272 bool "Add functionality to disable console completely" 273 help 274 Disable console (in & out). 275 276config IDENT_STRING 277 string "Board specific string to be added to uboot version string" 278 help 279 This options adds the board specific name to u-boot version. 280 281config LOGLEVEL 282 int "loglevel" 283 default 4 284 range 0 8 285 help 286 All Messages with a loglevel smaller than the console loglevel will 287 be compiled in. The loglevels are defined as follows: 288 289 0 (KERN_EMERG) system is unusable 290 1 (KERN_ALERT) action must be taken immediately 291 2 (KERN_CRIT) critical conditions 292 3 (KERN_ERR) error conditions 293 4 (KERN_WARNING) warning conditions 294 5 (KERN_NOTICE) normal but significant condition 295 6 (KERN_INFO) informational 296 7 (KERN_DEBUG) debug-level messages 297 298config SPL_LOGLEVEL 299 int 300 default LOGLEVEL 301 302config SILENT_CONSOLE 303 bool "Support a silent console" 304 help 305 This option allows the console to be silenced, meaning that no 306 output will appear on the console devices. This is controlled by 307 setting the environment vaariable 'silent' to a non-empty value. 308 Note this also silences the console when booting Linux. 309 310 When the console is set up, the variable is checked, and the 311 GD_FLG_SILENT flag is set. Changing the environment variable later 312 will update the flag. 313 314config SILENT_U_BOOT_ONLY 315 bool "Only silence the U-Boot console" 316 depends on SILENT_CONSOLE 317 help 318 Normally when the U-Boot console is silenced, Linux's console is 319 also silenced (assuming the board boots into Linux). This option 320 allows the linux console to operate normally, even if U-Boot's 321 is silenced. 322 323config SILENT_CONSOLE_UPDATE_ON_SET 324 bool "Changes to the 'silent' environment variable update immediately" 325 depends on SILENT_CONSOLE 326 default y if SILENT_CONSOLE 327 help 328 When the 'silent' environment variable is changed, update the 329 console silence flag immediately. This allows 'setenv' to be used 330 to silence or un-silence the console. 331 332 The effect is that any change to the variable will affect the 333 GD_FLG_SILENT flag. 334 335config SILENT_CONSOLE_UPDATE_ON_RELOC 336 bool "Allow flags to take effect on relocation" 337 depends on SILENT_CONSOLE 338 help 339 In some cases the environment is not available until relocation 340 (e.g. NAND). This option makes the value of the 'silent' 341 environment variable take effect at relocation. 342 343config PRE_CONSOLE_BUFFER 344 bool "Buffer characters before the console is available" 345 help 346 Prior to the console being initialised (i.e. serial UART 347 initialised etc) all console output is silently discarded. 348 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to 349 buffer any console messages prior to the console being 350 initialised to a buffer. The buffer is a circular buffer, so 351 if it overflows, earlier output is discarded. 352 353 Note that this is not currently supported in SPL. It would be 354 useful to be able to share the pre-console buffer with SPL. 355 356config PRE_CON_BUF_SZ 357 int "Sets the size of the pre-console buffer" 358 depends on PRE_CONSOLE_BUFFER 359 default 4096 360 help 361 The size of the pre-console buffer affects how much console output 362 can be held before it overflows and starts discarding earlier 363 output. Normally there is very little output at this early stage, 364 unless debugging is enabled, so allow enough for ~10 lines of 365 text. 366 367 This is a useful feature if you are using a video console and 368 want to see the full boot output on the console. Without this 369 option only the post-relocation output will be displayed. 370 371config PRE_CON_BUF_ADDR 372 hex "Address of the pre-console buffer" 373 depends on PRE_CONSOLE_BUFFER 374 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I 375 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I 376 help 377 This sets the start address of the pre-console buffer. This must 378 be in available memory and is accessed before relocation and 379 possibly before DRAM is set up. Therefore choose an address 380 carefully. 381 382 We should consider removing this option and allocating the memory 383 in board_init_f_init_reserve() instead. 384 385config CONSOLE_MUX 386 bool "Enable console multiplexing" 387 default y if DM_VIDEO || VIDEO || LCD 388 help 389 This allows multiple devices to be used for each console 'file'. 390 For example, stdout can be set to go to serial and video. 391 Similarly, stdin can be set to come from serial and keyboard. 392 Input can be provided from either source. Console multiplexing 393 adds a small amount of size to U-Boot. Changes to the environment 394 variables stdout, stdin and stderr will take effect immediately. 395 396config SYS_CONSOLE_IS_IN_ENV 397 bool "Select console devices from the environment" 398 default y if CONSOLE_MUX 399 help 400 This allows multiple input/output devices to be set at boot time. 401 For example, if stdout is set to "serial,video" then output will 402 be sent to both the serial and video devices on boot. The 403 environment variables can be updated after boot to change the 404 input/output devices. 405 406config SYS_CONSOLE_OVERWRITE_ROUTINE 407 bool "Allow board control over console overwriting" 408 help 409 If this is enabled, and the board-specific function 410 overwrite_console() returns 1, the stdin, stderr and stdout are 411 switched to the serial port, else the settings in the environment 412 are used. If this is not enabled, the console will not be switched 413 to serial. 414 415config SYS_CONSOLE_ENV_OVERWRITE 416 bool "Update environment variables during console init" 417 help 418 The console environment variables (stdout, stdin, stderr) can be 419 used to determine the correct console devices on start-up. This 420 option writes the console devices to these variables on console 421 start-up (after relocation). This causes the environment to be 422 updated to match the console devices actually chosen. 423 424config SYS_CONSOLE_INFO_QUIET 425 bool "Don't display the console devices on boot" 426 help 427 Normally U-Boot displays the current settings for stdout, stdin 428 and stderr on boot when the post-relocation console is set up. 429 Enable this option to supress this output. It can be obtained by 430 calling stdio_print_current_devices() from board code. 431 432config SYS_STDIO_DEREGISTER 433 bool "Allow deregistering stdio devices" 434 default y if USB_KEYBOARD 435 help 436 Generally there is no need to deregister stdio devices since they 437 are never deactivated. But if a stdio device is used which can be 438 removed (for example a USB keyboard) then this option can be 439 enabled to ensure this is handled correctly. 440 441endmenu 442 443menu "Logging" 444 445config LOG 446 bool "Enable logging support" 447 depends on DM 448 help 449 This enables support for logging of status and debug messages. These 450 can be displayed on the console, recorded in a memory buffer, or 451 discarded if not needed. Logging supports various categories and 452 levels of severity. 453 454config SPL_LOG 455 bool "Enable logging support in SPL" 456 depends on LOG 457 help 458 This enables support for logging of status and debug messages. These 459 can be displayed on the console, recorded in a memory buffer, or 460 discarded if not needed. Logging supports various categories and 461 levels of severity. 462 463config TPL_LOG 464 bool "Enable logging support in TPL" 465 depends on LOG 466 help 467 This enables support for logging of status and debug messages. These 468 can be displayed on the console, recorded in a memory buffer, or 469 discarded if not needed. Logging supports various categories and 470 levels of severity. 471 472config LOG_MAX_LEVEL 473 int "Maximum log level to record" 474 depends on LOG 475 default 5 476 help 477 This selects the maximum log level that will be recorded. Any value 478 higher than this will be ignored. If possible log statements below 479 this level will be discarded at build time. Levels: 480 481 0 - panic 482 1 - critical 483 2 - error 484 3 - warning 485 4 - note 486 5 - info 487 6 - detail 488 7 - debug 489 490config SPL_LOG_MAX_LEVEL 491 int "Maximum log level to record in SPL" 492 depends on SPL_LOG 493 default 3 494 help 495 This selects the maximum log level that will be recorded. Any value 496 higher than this will be ignored. If possible log statements below 497 this level will be discarded at build time. Levels: 498 499 0 - panic 500 1 - critical 501 2 - error 502 3 - warning 503 4 - note 504 5 - info 505 6 - detail 506 7 - debug 507 508config LOG_CONSOLE 509 bool "Allow log output to the console" 510 depends on LOG 511 default y 512 help 513 Enables a log driver which writes log records to the console. 514 Generally the console is the serial port or LCD display. Only the 515 log message is shown - other details like level, category, file and 516 line number are omitted. 517 518config LOG_SPL_CONSOLE 519 bool "Allow log output to the console in SPL" 520 depends on LOG_SPL 521 default y 522 help 523 Enables a log driver which writes log records to the console. 524 Generally the console is the serial port or LCD display. Only the 525 log message is shown - other details like level, category, file and 526 line number are omitted. 527 528config LOG_TEST 529 bool "Provide a test for logging" 530 depends on LOG 531 default y if SANDBOX 532 help 533 This enables a 'log test' command to test logging. It is normally 534 executed from a pytest and simply outputs logging information 535 in various different ways to test that the logging system works 536 correctly with varoius settings. 537 538config LOG_ERROR_RETURN 539 bool "Log all functions which return an error" 540 depends on LOG 541 help 542 When an error is returned in U-Boot it is sometimes difficult to 543 figure out the root cause. For eaxmple, reading from SPI flash may 544 fail due to a problem in the SPI controller or due to the flash part 545 not returning the expected information. This option changes 546 log_ret() to log any errors it sees. With this option disabled, 547 log_ret() is a nop. 548 549 You can add log_ret() to all functions which return an error code. 550 551endmenu 552 553config SUPPORT_RAW_INITRD 554 bool "Enable raw initrd images" 555 help 556 Note, defining the SUPPORT_RAW_INITRD allows user to supply 557 kernel with raw initrd images. The syntax is slightly different, the 558 address of the initrd must be augmented by it's size, in the following 559 format: "<initrd address>:<initrd size>". 560 561config DEFAULT_FDT_FILE 562 string "Default fdt file" 563 help 564 This option is used to set the default fdt file to boot OS. 565 566config MISC_INIT_R 567 bool "Execute Misc Init" 568 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx 569 default y if ARCH_OMAP2PLUS && !AM33XX 570 help 571 Enabling this option calls 'misc_init_r' function 572 573config VERSION_VARIABLE 574 bool "add U-Boot environment variable vers" 575 default n 576 help 577 If this variable is defined, an environment variable 578 named "ver" is created by U-Boot showing the U-Boot 579 version as printed by the "version" command. 580 Any change to this variable will be reverted at the 581 next reset. 582 583config BOARD_LATE_INIT 584 bool "Execute Board late init" 585 help 586 Sometimes board require some initialization code that might 587 require once the actual init done, example saving board specific env, 588 boot-modes etc. which eventually done at late. 589 590 So this config enable the late init code with the help of board_late_init 591 function which should defined on respective boards. 592 593config DISPLAY_CPUINFO 594 bool "Display information about the CPU during start up" 595 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K 596 help 597 Display information about the CPU that U-Boot is running on 598 when U-Boot starts up. The function print_cpuinfo() is called 599 to do this. 600 601config DISPLAY_BOARDINFO 602 bool "Display information about the board during early start up" 603 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA 604 help 605 Display information about the board that U-Boot is running on 606 when U-Boot starts up. The board function checkboard() is called 607 to do this. 608 609config DISPLAY_BOARDINFO_LATE 610 bool "Display information about the board during late start up" 611 help 612 Display information about the board that U-Boot is running on after 613 the relocation phase. The board function checkboard() is called to do 614 this. 615 616menu "Start-up hooks" 617 618config ARCH_EARLY_INIT_R 619 bool "Call arch-specific init soon after relocation" 620 help 621 With this option U-Boot will call arch_early_init_r() soon after 622 relocation. Driver model is running by this point, and the cache 623 is on. Note that board_early_init_r() is called first, if 624 enabled. This can be used to set up architecture-specific devices. 625 626config ARCH_MISC_INIT 627 bool "Call arch-specific init after relocation, when console is ready" 628 help 629 With this option U-Boot will call arch_misc_init() after 630 relocation to allow miscellaneous arch-dependent initialisation 631 to be performed. This function should be defined by the board 632 and will be called after the console is set up, after relocaiton. 633 634config BOARD_EARLY_INIT_F 635 bool "Call board-specific init before relocation" 636 help 637 Some boards need to perform initialisation as soon as possible 638 after boot. With this option, U-Boot calls board_early_init_f() 639 after driver model is ready in the pre-relocation init sequence. 640 Note that the normal serial console is not yet set up, but the 641 debug UART will be available if enabled. 642 643config BOARD_EARLY_INIT_R 644 bool "Call board-specific init after relocation" 645 help 646 Some boards need to perform initialisation as directly after 647 relocation. With this option, U-Boot calls board_early_init_r() 648 in the post-relocation init sequence. 649 650config LAST_STAGE_INIT 651 bool "Call board-specific as last setup step" 652 help 653 Some boards need to perform initialisation immediately before control 654 is passed to the command-line interpreter (e.g. for initializations 655 that depend on later phases in the init sequence). With this option, 656 U-Boot calls last_stage_init() before the command-line interpreter is 657 started. 658 659endmenu 660 661menu "Security support" 662 663config HASH 664 bool # "Support hashing API (SHA1, SHA256, etc.)" 665 help 666 This provides a way to hash data in memory using various supported 667 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h 668 and the algorithms it supports are defined in common/hash.c. See 669 also CMD_HASH for command-line access. 670 671config AVB_VERIFY 672 bool "Build Android Verified Boot operations" 673 depends on LIBAVB && FASTBOOT 674 depends on PARTITION_UUIDS 675 help 676 This option enables compilation of bootloader-dependent operations, 677 used by Android Verified Boot 2.0 library (libavb). Includes: 678 * Helpers to process strings in order to build OS bootargs. 679 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c. 680 * Helpers to alloc/init/free avb ops. 681 682config SPL_HASH 683 bool # "Support hashing API (SHA1, SHA256, etc.)" 684 help 685 This provides a way to hash data in memory using various supported 686 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h 687 and the algorithms it supports are defined in common/hash.c. See 688 also CMD_HASH for command-line access. 689 690config TPL_HASH 691 bool # "Support hashing API (SHA1, SHA256, etc.)" 692 help 693 This provides a way to hash data in memory using various supported 694 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h 695 and the algorithms it supports are defined in common/hash.c. See 696 also CMD_HASH for command-line access. 697 698endmenu 699 700menu "Update support" 701 702config UPDATE_TFTP 703 bool "Auto-update using fitImage via TFTP" 704 depends on FIT 705 help 706 This option allows performing update of NOR with data in fitImage 707 sent via TFTP boot. 708 709config UPDATE_TFTP_CNT_MAX 710 int "The number of connection retries during auto-update" 711 default 0 712 depends on UPDATE_TFTP 713 714config UPDATE_TFTP_MSEC_MAX 715 int "Delay in mSec to wait for the TFTP server during auto-update" 716 default 100 717 depends on UPDATE_TFTP 718 719endmenu 720 721source "common/spl/Kconfig" 722