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_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 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 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 89config 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 100config 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 107config 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 114config BOOTSTAGE_PRINTF_TIMESTAMP 115 bool "Support printf timestamp" 116 help 117 Enabling this will support printf timestamp. 118endmenu 119 120menu "Boot media" 121 122config NOR_BOOT 123 bool "Support for booting from NOR flash" 124 depends on NOR 125 help 126 Enabling this will make a U-Boot binary that is capable of being 127 booted via NOR. In this case we will enable certain pinmux early 128 as the ROM only partially sets up pinmux. We also default to using 129 NOR for environment. 130 131config NAND_BOOT 132 bool "Support for booting from NAND flash" 133 default n 134 help 135 Enabling this will make a U-Boot binary that is capable of being 136 booted via NAND flash. This is not a must, some SoCs need this, 137 some not. 138 139config ONENAND_BOOT 140 bool "Support for booting from ONENAND" 141 default n 142 help 143 Enabling this will make a U-Boot binary that is capable of being 144 booted via ONENAND. This is not a must, some SoCs need this, 145 some not. 146 147config QSPI_BOOT 148 bool "Support for booting from QSPI flash" 149 default n 150 help 151 Enabling this will make a U-Boot binary that is capable of being 152 booted via QSPI flash. This is not a must, some SoCs need this, 153 some not. 154 155config SATA_BOOT 156 bool "Support for booting from SATA" 157 default n 158 help 159 Enabling this will make a U-Boot binary that is capable of being 160 booted via SATA. This is not a must, some SoCs need this, 161 some not. 162 163config SD_BOOT 164 bool "Support for booting from SD/EMMC" 165 default n 166 help 167 Enabling this will make a U-Boot binary that is capable of being 168 booted via SD/EMMC. This is not a must, some SoCs need this, 169 some not. 170 171config SPI_BOOT 172 bool "Support for booting from SPI flash" 173 default n 174 help 175 Enabling this will make a U-Boot binary that is capable of being 176 booted via SPI flash. This is not a must, some SoCs need this, 177 some not. 178 179endmenu 180 181config BOOTDELAY 182 int "delay in seconds before automatically booting" 183 default 2 184 depends on AUTOBOOT 185 help 186 Delay before automatically running bootcmd; 187 set to 0 to autoboot with no delay, but you can stop it by key input. 188 set to -1 to disable autoboot. 189 set to -2 to autoboot with no delay and not check for abort 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 209menu "Console" 210 211config MENU 212 bool 213 help 214 This is the library functionality to provide a text-based menu of 215 choices for the user to make choices with. 216 217config CONSOLE_RECORD 218 bool "Console recording" 219 help 220 This provides a way to record console output (and provide console 221 input) through circular buffers. This is mostly useful for testing. 222 Console output is recorded even when the console is silent. 223 To enable console recording, call console_record_reset_enable() 224 from your code. 225 226config CONSOLE_RECORD_OUT_SIZE 227 hex "Output buffer size" 228 depends on CONSOLE_RECORD 229 default 0x400 if CONSOLE_RECORD 230 help 231 Set the size of the console output buffer. When this fills up, no 232 more data will be recorded until some is removed. The buffer is 233 allocated immediately after the malloc() region is ready. 234 235config CONSOLE_RECORD_IN_SIZE 236 hex "Input buffer size" 237 depends on CONSOLE_RECORD 238 default 0x100 if CONSOLE_RECORD 239 help 240 Set the size of the console input buffer. When this contains data, 241 tstc() and getc() will use this in preference to real device input. 242 The buffer is allocated immediately after the malloc() region is 243 ready. 244 245config IDENT_STRING 246 string "Board specific string to be added to uboot version string" 247 help 248 This options adds the board specific name to u-boot version. 249 250config LOGLEVEL 251 int "loglevel" 252 default 4 253 range 0 8 254 help 255 All Messages with a loglevel smaller than the console loglevel will 256 be compiled in. The loglevels are defined as follows: 257 258 0 (KERN_EMERG) system is unusable 259 1 (KERN_ALERT) action must be taken immediately 260 2 (KERN_CRIT) critical conditions 261 3 (KERN_ERR) error conditions 262 4 (KERN_WARNING) warning conditions 263 5 (KERN_NOTICE) normal but significant condition 264 6 (KERN_INFO) informational 265 7 (KERN_DEBUG) debug-level messages 266 267config SPL_LOGLEVEL 268 int 269 default LOGLEVEL 270 271config SILENT_CONSOLE 272 bool "Support a silent console" 273 help 274 This option allows the console to be silenced, meaning that no 275 output will appear on the console devices. This is controlled by 276 setting the environment vaariable 'silent' to a non-empty value. 277 Note this also silences the console when booting Linux. 278 279 When the console is set up, the variable is checked, and the 280 GD_FLG_SILENT flag is set. Changing the environment variable later 281 will update the flag. 282 283config SILENT_U_BOOT_ONLY 284 bool "Only silence the U-Boot console" 285 depends on SILENT_CONSOLE 286 help 287 Normally when the U-Boot console is silenced, Linux's console is 288 also silenced (assuming the board boots into Linux). This option 289 allows the linux console to operate normally, even if U-Boot's 290 is silenced. 291 292config SILENT_CONSOLE_UPDATE_ON_SET 293 bool "Changes to the 'silent' environment variable update immediately" 294 depends on SILENT_CONSOLE 295 default y if SILENT_CONSOLE 296 help 297 When the 'silent' environment variable is changed, update the 298 console silence flag immediately. This allows 'setenv' to be used 299 to silence or un-silence the console. 300 301 The effect is that any change to the variable will affect the 302 GD_FLG_SILENT flag. 303 304config SILENT_CONSOLE_UPDATE_ON_RELOC 305 bool "Allow flags to take effect on relocation" 306 depends on SILENT_CONSOLE 307 help 308 In some cases the environment is not available until relocation 309 (e.g. NAND). This option makes the value of the 'silent' 310 environment variable take effect at relocation. 311 312config PRE_CONSOLE_BUFFER 313 bool "Buffer characters before the console is available" 314 help 315 Prior to the console being initialised (i.e. serial UART 316 initialised etc) all console output is silently discarded. 317 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to 318 buffer any console messages prior to the console being 319 initialised to a buffer. The buffer is a circular buffer, so 320 if it overflows, earlier output is discarded. 321 322 Note that this is not currently supported in SPL. It would be 323 useful to be able to share the pre-console buffer with SPL. 324 325config PRE_CON_BUF_SZ 326 int "Sets the size of the pre-console buffer" 327 depends on PRE_CONSOLE_BUFFER 328 default 4096 329 help 330 The size of the pre-console buffer affects how much console output 331 can be held before it overflows and starts discarding earlier 332 output. Normally there is very little output at this early stage, 333 unless debugging is enabled, so allow enough for ~10 lines of 334 text. 335 336 This is a useful feature if you are using a video console and 337 want to see the full boot output on the console. Without this 338 option only the post-relocation output will be displayed. 339 340config PRE_CON_BUF_ADDR 341 hex "Address of the pre-console buffer" 342 depends on PRE_CONSOLE_BUFFER 343 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I 344 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I 345 help 346 This sets the start address of the pre-console buffer. This must 347 be in available memory and is accessed before relocation and 348 possibly before DRAM is set up. Therefore choose an address 349 carefully. 350 351 We should consider removing this option and allocating the memory 352 in board_init_f_init_reserve() instead. 353 354config CONSOLE_MUX 355 bool "Enable console multiplexing" 356 default y if DM_VIDEO || VIDEO || LCD 357 help 358 This allows multiple devices to be used for each console 'file'. 359 For example, stdout can be set to go to serial and video. 360 Similarly, stdin can be set to come from serial and keyboard. 361 Input can be provided from either source. Console multiplexing 362 adds a small amount of size to U-Boot. Changes to the environment 363 variables stdout, stdin and stderr will take effect immediately. 364 365config SYS_CONSOLE_IS_IN_ENV 366 bool "Select console devices from the environment" 367 default y if CONSOLE_MUX 368 help 369 This allows multiple input/output devices to be set at boot time. 370 For example, if stdout is set to "serial,video" then output will 371 be sent to both the serial and video devices on boot. The 372 environment variables can be updated after boot to change the 373 input/output devices. 374 375config SYS_CONSOLE_OVERWRITE_ROUTINE 376 bool "Allow board control over console overwriting" 377 help 378 If this is enabled, and the board-specific function 379 overwrite_console() returns 1, the stdin, stderr and stdout are 380 switched to the serial port, else the settings in the environment 381 are used. If this is not enabled, the console will not be switched 382 to serial. 383 384config SYS_CONSOLE_ENV_OVERWRITE 385 bool "Update environment variables during console init" 386 help 387 The console environment variables (stdout, stdin, stderr) can be 388 used to determine the correct console devices on start-up. This 389 option writes the console devices to these variables on console 390 start-up (after relocation). This causes the environment to be 391 updated to match the console devices actually chosen. 392 393config SYS_CONSOLE_INFO_QUIET 394 bool "Don't display the console devices on boot" 395 help 396 Normally U-Boot displays the current settings for stdout, stdin 397 and stderr on boot when the post-relocation console is set up. 398 Enable this option to supress this output. It can be obtained by 399 calling stdio_print_current_devices() from board code. 400 401config SYS_STDIO_DEREGISTER 402 bool "Allow deregistering stdio devices" 403 default y if USB_KEYBOARD 404 help 405 Generally there is no need to deregister stdio devices since they 406 are never deactivated. But if a stdio device is used which can be 407 removed (for example a USB keyboard) then this option can be 408 enabled to ensure this is handled correctly. 409 410endmenu 411 412menu "Logging" 413 414config LOG 415 bool "Enable logging support" 416 help 417 This enables support for logging of status and debug messages. These 418 can be displayed on the console, recorded in a memory buffer, or 419 discarded if not needed. Logging supports various categories and 420 levels of severity. 421 422config SPL_LOG 423 bool "Enable logging support in SPL" 424 help 425 This enables support for logging of status and debug messages. These 426 can be displayed on the console, recorded in a memory buffer, or 427 discarded if not needed. Logging supports various categories and 428 levels of severity. 429 430config LOG_MAX_LEVEL 431 int "Maximum log level to record" 432 depends on LOG 433 default 5 434 help 435 This selects the maximum log level that will be recorded. Any value 436 higher than this will be ignored. If possible log statements below 437 this level will be discarded at build time. Levels: 438 439 0 - panic 440 1 - critical 441 2 - error 442 3 - warning 443 4 - note 444 5 - info 445 6 - detail 446 7 - debug 447 448config SPL_LOG_MAX_LEVEL 449 int "Maximum log level to record in SPL" 450 depends on SPL_LOG 451 default 3 452 help 453 This selects the maximum log level that will be recorded. Any value 454 higher than this will be ignored. If possible log statements below 455 this level will be discarded at build time. Levels: 456 457 0 - panic 458 1 - critical 459 2 - error 460 3 - warning 461 4 - note 462 5 - info 463 6 - detail 464 7 - debug 465 466config LOG_CONSOLE 467 bool "Allow log output to the console" 468 depends on LOG 469 default y 470 help 471 Enables a log driver which writes log records to the console. 472 Generally the console is the serial port or LCD display. Only the 473 log message is shown - other details like level, category, file and 474 line number are omitted. 475 476config LOG_SPL_CONSOLE 477 bool "Allow log output to the console in SPL" 478 depends on LOG_SPL 479 default y 480 help 481 Enables a log driver which writes log records to the console. 482 Generally the console is the serial port or LCD display. Only the 483 log message is shown - other details like level, category, file and 484 line number are omitted. 485 486config LOG_TEST 487 bool "Provide a test for logging" 488 depends on LOG 489 default y if SANDBOX 490 help 491 This enables a 'log test' command to test logging. It is normally 492 executed from a pytest and simply outputs logging information 493 in various different ways to test that the logging system works 494 correctly with varoius settings. 495 496endmenu 497 498config DEFAULT_FDT_FILE 499 string "Default fdt file" 500 help 501 This option is used to set the default fdt file to boot OS. 502 503config VERSION_VARIABLE 504 bool "add U-Boot environment variable vers" 505 default n 506 help 507 If this variable is defined, an environment variable 508 named "ver" is created by U-Boot showing the U-Boot 509 version as printed by the "version" command. 510 Any change to this variable will be reverted at the 511 next reset. 512 513config BOARD_LATE_INIT 514 bool 515 help 516 Sometimes board require some initialization code that might 517 require once the actual init done, example saving board specific env, 518 boot-modes etc. which eventually done at late. 519 520 So this config enable the late init code with the help of board_late_init 521 function which should defined on respective boards. 522 523config DISPLAY_CPUINFO 524 bool "Display information about the CPU during start up" 525 default y if ARM || NIOS2 || X86 || XTENSA 526 help 527 Display information about the CPU that U-Boot is running on 528 when U-Boot starts up. The function print_cpuinfo() is called 529 to do this. 530 531config DISPLAY_BOARDINFO 532 bool "Display information about the board during start up" 533 default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA 534 help 535 Display information about the board that U-Boot is running on 536 when U-Boot starts up. The board function checkboard() is called 537 to do this. 538 539menu "Start-up hooks" 540 541config ARCH_EARLY_INIT_R 542 bool "Call arch-specific init soon after relocation" 543 help 544 With this option U-Boot will call arch_early_init_r() soon after 545 relocation. Driver model is running by this point, and the cache 546 is on. Note that board_early_init_r() is called first, if 547 enabled. This can be used to set up architecture-specific devices. 548 549config ARCH_MISC_INIT 550 bool "Call arch-specific init after relocation, when console is ready" 551 help 552 With this option U-Boot will call arch_misc_init() after 553 relocation to allow miscellaneous arch-dependent initialisation 554 to be performed. This function should be defined by the board 555 and will be called after the console is set up, after relocaiton. 556 557config BOARD_EARLY_INIT_F 558 bool "Call board-specific init before relocation" 559 help 560 Some boards need to perform initialisation as soon as possible 561 after boot. With this option, U-Boot calls board_early_init_f() 562 after driver model is ready in the pre-relocation init sequence. 563 Note that the normal serial console is not yet set up, but the 564 debug UART will be available if enabled. 565 566endmenu 567config ANDROID_BOOTLOADER 568 bool "Support for Android Bootloader boot flow" 569 default n 570 depends on ANDROID_BOOT_IMAGE 571 help 572 If enabled, adds support to boot an Android device following the 573 Android Bootloader boot flow. This flow requires an Android Bootloader 574 to handle the Android Bootloader Message stored in the Boot Control 575 Block (BCB), normally in the "misc" partition of an Android device. 576 The BCB is used to determine the boot mode of the device (normal mode, 577 recovery mode or bootloader mode) and, if enabled, the slot to boot 578 from in devices with multiple boot slots (A/B devices). 579 580config ANDROID_AB 581 bool "Support for Android A/B updates" 582 default n 583 help 584 If enabled, adds support for the new Android A/B update model. This 585 allows the bootloader to select which slot to boot from based on the 586 information provided by userspace via the Android boot_ctrl HAL. This 587 allows a bootloader to try a new version of the system but roll back 588 to previous version if the new one didn't boot all the way. 589 590config ANDROID_AVB 591 bool"Support Android Verified Boot" 592 default n 593 help 594 If enabled, adds support the android verified boot. The avb get the 595 digital signature and key from vemeta. Then use the RSA2048 and sha256 596 to verify the boot images. The vbmeta must be matched with images, 597 if not, verify failed. 598 599config ANDROID_BOOT_IMAGE 600 bool "Enable support for Android Boot Images" 601 help 602 This enables support for booting images which use the Android 603 image format header. 604 605menu "Security support" 606 607config HASH 608 bool # "Support hashing API (SHA1, SHA256, etc.)" 609 help 610 This provides a way to hash data in memory using various supported 611 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h 612 and the algorithms it supports are defined in common/hash.c. See 613 also CMD_HASH for command-line access. 614 615endmenu 616 617source "common/spl/Kconfig" 618