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