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