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