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