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