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