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