Blame view
common/Kconfig
20.8 KB
ee2b24340 Kconfig: Move CON... |
1 2 3 4 5 6 7 8 9 10 11 |
menu "Boot timing" config BOOTSTAGE bool "Boot timing and reporting" help Enable recording of boot time while booting. To use it, insert calls to bootstage_mark() with a suitable BOOTSTAGE_ID from bootstage.h. Only a single entry is recorded for each ID. You can give the entry a name with bootstage_mark_name(). You can also record elapsed time in a particular stage using bootstage_start() before starting and bootstage_accum() when finished. Bootstage will |
57247d9cb common/Kconfig: F... |
12 |
add up all the accumulated time and report it. |
ee2b24340 Kconfig: Move CON... |
13 14 |
Normally, IDs are defined in bootstage.h but a small number of |
57247d9cb common/Kconfig: F... |
15 |
additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC |
ee2b24340 Kconfig: Move CON... |
16 |
as the ID. |
57247d9cb common/Kconfig: F... |
17 |
Calls to show_boot_progress() will also result in log entries but |
ee2b24340 Kconfig: Move CON... |
18 |
these will not have names. |
824bb1b45 bootstage: Suppor... |
19 20 21 22 23 24 25 26 |
config SPL_BOOTSTAGE bool "Boot timing and reported in SPL" depends on BOOTSTAGE help Enable recording of boot time in SPL. To make this visible to U-Boot proper, enable BOOTSTAGE_STASH as well. This will stash the timing information when SPL finishes and load it when U-Boot proper starts up. |
ee2b24340 Kconfig: Move CON... |
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 |
config BOOTSTAGE_REPORT bool "Display a detailed boot timing report before booting the OS" depends on BOOTSTAGE help Enable output of a boot time report just before the OS is booted. This shows how long it took U-Boot to go through each stage of the boot process. The report looks something like this: Timer summary in microseconds: Mark Elapsed Stage 0 0 reset 3,575,678 3,575,678 board_init_f start 3,575,695 17 arch_cpu_init A9 3,575,777 82 arch_cpu_init done 3,659,598 83,821 board_init_r start 3,910,375 250,777 main_loop 29,916,167 26,005,792 bootm_start 30,361,327 445,160 start_kernel |
03ecac314 bootstage: Use re... |
45 46 47 48 49 50 |
config BOOTSTAGE_RECORD_COUNT int "Number of boot stage records to store" default 30 help This is the size of the bootstage record list and is the maximum number of bootstage records that can be recorded. |
d69bb0ecb bootstage: Provid... |
51 52 53 54 55 56 |
config SPL_BOOTSTAGE_RECORD_COUNT int "Number of boot stage records to store for SPL" default 5 help This is the size of the bootstage record list and is the maximum number of bootstage records that can be recorded. |
ee2b24340 Kconfig: Move CON... |
57 58 59 60 61 62 63 |
config BOOTSTAGE_FDT bool "Store boot timing information in the OS device tree" depends on BOOTSTAGE help Stash the bootstage information in the FDT. A root 'bootstage' node is created with each bootstage id as a child. Each child has a 'name' property and either 'mark' containing the |
57247d9cb common/Kconfig: F... |
64 |
mark time in microseconds, or 'accum' containing the |
ee2b24340 Kconfig: Move CON... |
65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 |
accumulated time for that bootstage id in microseconds. For example: bootstage { 154 { name = "board_init_f"; mark = <3575678>; }; 170 { name = "lcd"; accum = <33482>; }; }; Code in the Linux kernel can find this in /proc/devicetree. config BOOTSTAGE_STASH bool "Stash the boot timing information in memory before booting OS" depends on BOOTSTAGE help Some OSes do not support device tree. Bootstage can instead write the boot timing information in a binary format at a given address. This happens through a call to bootstage_stash(), typically in the CPU's cleanup_before_linux() function. You can use the 'bootstage stash' and 'bootstage unstash' commands to do this on the command line. config BOOTSTAGE_STASH_ADDR hex "Address to stash boot timing information" default 0 help Provide an address which will not be overwritten by the OS when it starts, so that it can read this information when ready. config BOOTSTAGE_STASH_SIZE hex "Size of boot timing stash region" |
fad6a2b77 common, kconfig: ... |
101 |
default 0x1000 |
ee2b24340 Kconfig: Move CON... |
102 103 104 105 106 |
help This should be large enough to hold the bootstage stash. A value of 4096 (4KiB) is normally plenty. endmenu |
d14739ffe Kconfig: make NOR... |
107 108 109 110 111 112 113 114 115 116 |
menu "Boot media" config NOR_BOOT bool "Support for booting from NOR flash" depends on NOR help Enabling this will make a U-Boot binary that is capable of being booted via NOR. In this case we will enable certain pinmux early as the ROM only partially sets up pinmux. We also default to using NOR for environment. |
faaef73f7 common: add new b... |
117 118 119 120 121 122 |
config NAND_BOOT bool "Support for booting from NAND flash" default n help Enabling this will make a U-Boot binary that is capable of being booted via NAND flash. This is not a must, some SoCs need this, |
57247d9cb common/Kconfig: F... |
123 |
some not. |
faaef73f7 common: add new b... |
124 125 126 127 128 129 130 |
config ONENAND_BOOT bool "Support for booting from ONENAND" default n help Enabling this will make a U-Boot binary that is capable of being booted via ONENAND. This is not a must, some SoCs need this, |
57247d9cb common/Kconfig: F... |
131 |
some not. |
faaef73f7 common: add new b... |
132 133 134 135 136 137 138 |
config QSPI_BOOT bool "Support for booting from QSPI flash" default n help Enabling this will make a U-Boot binary that is capable of being booted via QSPI flash. This is not a must, some SoCs need this, |
57247d9cb common/Kconfig: F... |
139 |
some not. |
faaef73f7 common: add new b... |
140 141 142 143 144 145 146 |
config SATA_BOOT bool "Support for booting from SATA" default n help Enabling this will make a U-Boot binary that is capable of being booted via SATA. This is not a must, some SoCs need this, |
57247d9cb common/Kconfig: F... |
147 |
some not. |
faaef73f7 common: add new b... |
148 149 150 151 152 153 154 |
config SD_BOOT bool "Support for booting from SD/EMMC" default n help Enabling this will make a U-Boot binary that is capable of being booted via SD/EMMC. This is not a must, some SoCs need this, |
57247d9cb common/Kconfig: F... |
155 |
some not. |
faaef73f7 common: add new b... |
156 157 158 159 160 161 162 |
config SPI_BOOT bool "Support for booting from SPI flash" default n help Enabling this will make a U-Boot binary that is capable of being booted via SPI flash. This is not a must, some SoCs need this, |
57247d9cb common/Kconfig: F... |
163 |
some not. |
faaef73f7 common: add new b... |
164 |
|
d14739ffe Kconfig: make NOR... |
165 |
endmenu |
bb597c0ee common: bootdelay... |
166 167 |
config BOOTDELAY int "delay in seconds before automatically booting" |
5e4e87418 common/Kconfig: C... |
168 |
default 2 |
41598c825 autoboot: add CON... |
169 |
depends on AUTOBOOT |
bb597c0ee common: bootdelay... |
170 171 |
help Delay before automatically running bootcmd; |
2fbb8462b autoboot: remove ... |
172 |
set to 0 to autoboot with no delay, but you can stop it by key input. |
bb597c0ee common: bootdelay... |
173 174 |
set to -1 to disable autoboot. set to -2 to autoboot with no delay and not check for abort |
bb597c0ee common: bootdelay... |
175 |
|
9060970f4 doc: bootdelay: d... |
176 |
See doc/README.autoboot for details. |
5abc1a452 common: Move CONF... |
177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 |
config USE_BOOTARGS bool "Enable boot arguments" help Provide boot arguments to bootm command. Boot arguments are specified in CONFIG_BOOTARGS option. Enable this option to be able to specify CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS will be undefined and won't take any space in U-Boot image. config BOOTARGS string "Boot arguments" depends on USE_BOOTARGS help This can be used to pass arguments to the bootm command. The value of CONFIG_BOOTARGS goes into the environment value "bootargs". Note that this value will also override the "chosen" node in FDT blob. |
b6251db8c Kconfig: Introduc... |
192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 |
config USE_BOOTCOMMAND bool "Enable a default value for bootcmd" help Provide a default value for the bootcmd entry in the environment. If autoboot is enabled this is what will be run automatically. Enable this option to be able to specify CONFIG_BOOTCOMMAND as a string. If this option is disabled, CONFIG_BOOTCOMMAND will be undefined and won't take any space in U-Boot image. config BOOTCOMMAND string "bootcmd value" depends on USE_BOOTCOMMAND default "run distro_bootcmd" if DISTRO_DEFAULTS help This is the string of commands that will be used as bootcmd and if AUTOBOOT is set, automatically run. |
98af87997 Convert SILENT_CO... |
208 |
menu "Console" |
4880b026e cmd: Convert CMD_... |
209 210 211 212 213 |
config MENU bool help This is the library functionality to provide a text-based menu of choices for the user to make choices with. |
9854a8748 console: Add a co... |
214 215 216 217 |
config CONSOLE_RECORD bool "Console recording" help This provides a way to record console output (and provide console |
57247d9cb common/Kconfig: F... |
218 |
input) through circular buffers. This is mostly useful for testing. |
9854a8748 console: Add a co... |
219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 |
Console output is recorded even when the console is silent. To enable console recording, call console_record_reset_enable() from your code. config CONSOLE_RECORD_OUT_SIZE hex "Output buffer size" depends on CONSOLE_RECORD default 0x400 if CONSOLE_RECORD help Set the size of the console output buffer. When this fills up, no more data will be recorded until some is removed. The buffer is allocated immediately after the malloc() region is ready. config CONSOLE_RECORD_IN_SIZE hex "Input buffer size" depends on CONSOLE_RECORD default 0x100 if CONSOLE_RECORD help Set the size of the console input buffer. When this contains data, tstc() and getc() will use this in preference to real device input. The buffer is allocated immediately after the malloc() region is ready. |
4d25507f3 Kconfig: Move opt... |
241 |
|
a4d88920e Kconfig: Move con... |
242 243 244 245 |
config IDENT_STRING string "Board specific string to be added to uboot version string" help This options adds the board specific name to u-boot version. |
b44b30260 printk: collect p... |
246 247 |
config LOGLEVEL int "loglevel" |
6a3e65dea common: Drop LOGL... |
248 |
default 4 |
b44b30260 printk: collect p... |
249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 |
range 0 8 help All Messages with a loglevel smaller than the console loglevel will be compiled in. The loglevels are defined as follows: 0 (KERN_EMERG) system is unusable 1 (KERN_ALERT) action must be taken immediately 2 (KERN_CRIT) critical conditions 3 (KERN_ERR) error conditions 4 (KERN_WARNING) warning conditions 5 (KERN_NOTICE) normal but significant condition 6 (KERN_INFO) informational 7 (KERN_DEBUG) debug-level messages config SPL_LOGLEVEL int default LOGLEVEL |
98af87997 Convert SILENT_CO... |
266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 |
config SILENT_CONSOLE bool "Support a silent console" help This option allows the console to be silenced, meaning that no output will appear on the console devices. This is controlled by setting the environment vaariable 'silent' to a non-empty value. Note this also silences the console when booting Linux. When the console is set up, the variable is checked, and the GD_FLG_SILENT flag is set. Changing the environment variable later will update the flag. config SILENT_U_BOOT_ONLY bool "Only silence the U-Boot console" depends on SILENT_CONSOLE help Normally when the U-Boot console is silenced, Linux's console is also silenced (assuming the board boots into Linux). This option allows the linux console to operate normally, even if U-Boot's is silenced. config SILENT_CONSOLE_UPDATE_ON_SET bool "Changes to the 'silent' environment variable update immediately" depends on SILENT_CONSOLE default y if SILENT_CONSOLE help When the 'silent' environment variable is changed, update the console silence flag immediately. This allows 'setenv' to be used to silence or un-silence the console. The effect is that any change to the variable will affect the GD_FLG_SILENT flag. config SILENT_CONSOLE_UPDATE_ON_RELOC bool "Allow flags to take effect on relocation" depends on SILENT_CONSOLE help In some cases the environment is not available until relocation (e.g. NAND). This option makes the value of the 'silent' environment variable take effect at relocation. |
8f9255841 Convert CONSOLE_P... |
306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 |
config PRE_CONSOLE_BUFFER bool "Buffer characters before the console is available" help Prior to the console being initialised (i.e. serial UART initialised etc) all console output is silently discarded. Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to buffer any console messages prior to the console being initialised to a buffer. The buffer is a circular buffer, so if it overflows, earlier output is discarded. Note that this is not currently supported in SPL. It would be useful to be able to share the pre-console buffer with SPL. config PRE_CON_BUF_SZ int "Sets the size of the pre-console buffer" depends on PRE_CONSOLE_BUFFER default 4096 help The size of the pre-console buffer affects how much console output can be held before it overflows and starts discarding earlier output. Normally there is very little output at this early stage, unless debugging is enabled, so allow enough for ~10 lines of text. This is a useful feature if you are using a video console and want to see the full boot output on the console. Without this option only the post-relocation output will be displayed. config PRE_CON_BUF_ADDR hex "Address of the pre-console buffer" depends on PRE_CONSOLE_BUFFER default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I help This sets the start address of the pre-console buffer. This must be in available memory and is accessed before relocation and possibly before DRAM is set up. Therefore choose an address carefully. We should consider removing this option and allocating the memory in board_init_f_init_reserve() instead. |
ef26d6039 Convert CONFIG_SY... |
347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 |
config CONSOLE_MUX bool "Enable console multiplexing" default y if DM_VIDEO || VIDEO || LCD help This allows multiple devices to be used for each console 'file'. For example, stdout can be set to go to serial and video. Similarly, stdin can be set to come from serial and keyboard. Input can be provided from either source. Console multiplexing adds a small amount of size to U-Boot. Changes to the environment variables stdout, stdin and stderr will take effect immediately. config SYS_CONSOLE_IS_IN_ENV bool "Select console devices from the environment" default y if CONSOLE_MUX help This allows multiple input/output devices to be set at boot time. For example, if stdout is set to "serial,video" then output will be sent to both the serial and video devices on boot. The environment variables can be updated after boot to change the input/output devices. |
84f2a5d0a Convert CONFIG_SY... |
367 368 369 370 371 372 373 374 |
config SYS_CONSOLE_OVERWRITE_ROUTINE bool "Allow board control over console overwriting" help If this is enabled, and the board-specific function overwrite_console() returns 1, the stdin, stderr and stdout are switched to the serial port, else the settings in the environment are used. If this is not enabled, the console will not be switched to serial. |
3505bc556 Convert CONFIG_SY... |
375 376 377 378 379 380 381 382 |
config SYS_CONSOLE_ENV_OVERWRITE bool "Update environment variables during console init" help The console environment variables (stdout, stdin, stderr) can be used to determine the correct console devices on start-up. This option writes the console devices to these variables on console start-up (after relocation). This causes the environment to be updated to match the console devices actually chosen. |
f3f3efff9 Convert CONFIG_SY... |
383 384 385 386 387 388 389 |
config SYS_CONSOLE_INFO_QUIET bool "Don't display the console devices on boot" help Normally U-Boot displays the current settings for stdout, stdin and stderr on boot when the post-relocation console is set up. Enable this option to supress this output. It can be obtained by calling stdio_print_current_devices() from board code. |
869588dec Convert CONFIG_SY... |
390 391 392 393 394 395 396 397 |
config SYS_STDIO_DEREGISTER bool "Allow deregistering stdio devices" default y if USB_KEYBOARD help Generally there is no need to deregister stdio devices since they are never deactivated. But if a stdio device is used which can be removed (for example a USB keyboard) then this option can be enabled to ensure this is handled correctly. |
98af87997 Convert SILENT_CO... |
398 |
endmenu |
e9c8d49d5 log: Add an imple... |
399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 |
menu "Logging" config LOG bool "Enable logging support" help This enables support for logging of status and debug messages. These can be displayed on the console, recorded in a memory buffer, or discarded if not needed. Logging supports various categories and levels of severity. config SPL_LOG bool "Enable logging support in SPL" help This enables support for logging of status and debug messages. These can be displayed on the console, recorded in a memory buffer, or discarded if not needed. Logging supports various categories and levels of severity. config LOG_MAX_LEVEL int "Maximum log level to record" depends on LOG default 5 help This selects the maximum log level that will be recorded. Any value higher than this will be ignored. If possible log statements below this level will be discarded at build time. Levels: 0 - panic 1 - critical 2 - error 3 - warning 4 - note 5 - info 6 - detail 7 - debug config SPL_LOG_MAX_LEVEL int "Maximum log level to record in SPL" depends on SPL_LOG default 3 help This selects the maximum log level that will be recorded. Any value higher than this will be ignored. If possible log statements below this level will be discarded at build time. Levels: 0 - panic 1 - critical 2 - error 3 - warning 4 - note 5 - info 6 - detail 7 - debug |
c6d47535d log: Add a consol... |
452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 |
config LOG_CONSOLE bool "Allow log output to the console" depends on LOG default y help Enables a log driver which writes log records to the console. Generally the console is the serial port or LCD display. Only the log message is shown - other details like level, category, file and line number are omitted. config LOG_SPL_CONSOLE bool "Allow log output to the console in SPL" depends on LOG_SPL default y help Enables a log driver which writes log records to the console. Generally the console is the serial port or LCD display. Only the log message is shown - other details like level, category, file and line number are omitted. |
ef11ed823 log: Add a test c... |
471 472 473 474 475 476 477 478 479 |
config LOG_TEST bool "Provide a test for logging" depends on LOG default y if SANDBOX help This enables a 'log test' command to test logging. It is normally executed from a pytest and simply outputs logging information in various different ways to test that the logging system works correctly with varoius settings. |
3707c6ee0 log: Add a way to... |
480 481 482 483 484 485 486 487 488 489 490 491 |
config LOG_ERROR_RETURN bool "Log all functions which return an error" depends on LOG help When an error is returned in U-Boot it is sometimes difficult to figure out the root cause. For eaxmple, reading from SPI flash may fail due to a problem in the SPI controller or due to the flash part not returning the expected information. This option changes log_ret() to log any errors it sees. With this option disabled, log_ret() is a nop. You can add log_ret() to all functions which return an error code. |
e9c8d49d5 log: Add an imple... |
492 |
endmenu |
d021e9421 Convert CONFIG_BO... |
493 494 495 496 497 498 499 |
config SUPPORT_RAW_INITRD bool "Enable raw initrd images" help Note, defining the SUPPORT_RAW_INITRD allows user to supply kernel with raw initrd images. The syntax is slightly different, the address of the initrd must be augmented by it's size, in the following format: "<initrd address>:<initrd size>". |
d259c0084 config: Move CONF... |
500 501 502 503 |
config DEFAULT_FDT_FILE string "Default fdt file" help This option is used to set the default fdt file to boot OS. |
9dd1d0aa4 common, kconfig: ... |
504 505 506 507 508 509 510 511 512 |
config VERSION_VARIABLE bool "add U-Boot environment variable vers" default n help If this variable is defined, an environment variable named "ver" is created by U-Boot showing the U-Boot version as printed by the "version" command. Any change to this variable will be reverted at the next reset. |
c2ae7d822 Kconfig: Move SPL... |
513 |
|
de70fefb1 common: Kconfig: ... |
514 |
config BOARD_LATE_INIT |
e5ec48152 Kconfig: Migrate ... |
515 |
bool |
de70fefb1 common: Kconfig: ... |
516 517 518 519 520 521 522 |
help Sometimes board require some initialization code that might require once the actual init done, example saving board specific env, boot-modes etc. which eventually done at late. So this config enable the late init code with the help of board_late_init function which should defined on respective boards. |
19a974753 common/Kconfig: A... |
523 524 |
config DISPLAY_CPUINFO bool "Display information about the CPU during start up" |
b9153fe30 common/board_f.c:... |
525 |
default y if ARM || NIOS2 || X86 || XTENSA || M68K |
19a974753 common/Kconfig: A... |
526 527 528 529 |
help Display information about the CPU that U-Boot is running on when U-Boot starts up. The function print_cpuinfo() is called to do this. |
843517927 common: Add DISPL... |
530 531 |
config DISPLAY_BOARDINFO bool "Display information about the board during start up" |
d63b5b4fb sandbox: Enable m... |
532 |
default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA |
843517927 common: Add DISPL... |
533 534 535 536 |
help Display information about the board that U-Boot is running on when U-Boot starts up. The board function checkboard() is called to do this. |
a421192fb Convert CONFIG_AR... |
537 538 539 540 |
menu "Start-up hooks" config ARCH_EARLY_INIT_R bool "Call arch-specific init soon after relocation" |
a421192fb Convert CONFIG_AR... |
541 542 543 544 545 |
help With this option U-Boot will call arch_early_init_r() soon after relocation. Driver model is running by this point, and the cache is on. Note that board_early_init_r() is called first, if enabled. This can be used to set up architecture-specific devices. |
4585601ae Convert CONFIG_AR... |
546 547 548 549 550 551 552 |
config ARCH_MISC_INIT bool "Call arch-specific init after relocation, when console is ready" help With this option U-Boot will call arch_misc_init() after relocation to allow miscellaneous arch-dependent initialisation to be performed. This function should be defined by the board and will be called after the console is set up, after relocaiton. |
a5d67547d Convert CONFIG_BO... |
553 554 |
config BOARD_EARLY_INIT_F bool "Call board-specific init before relocation" |
a5d67547d Convert CONFIG_BO... |
555 556 557 558 559 560 |
help Some boards need to perform initialisation as soon as possible after boot. With this option, U-Boot calls board_early_init_f() after driver model is ready in the pre-relocation init sequence. Note that the normal serial console is not yet set up, but the debug UART will be available if enabled. |
a421192fb Convert CONFIG_AR... |
561 |
endmenu |
d70f919e4 Kconfig: Add CONF... |
562 563 564 565 566 567 568 569 570 571 572 |
menu "Security support" config HASH bool # "Support hashing API (SHA1, SHA256, etc.)" help This provides a way to hash data in memory using various supported algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h and the algorithms it supports are defined in common/hash.c. See also CMD_HASH for command-line access. endmenu |
b254c5291 cmd: fitupd: Conv... |
573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 |
menu "Update support" config UPDATE_TFTP bool "Auto-update using fitImage via TFTP" depends on FIT help This option allows performing update of NOR with data in fitImage sent via TFTP boot. config UPDATE_TFTP_CNT_MAX int "The number of connection retries during auto-update" default 0 depends on UPDATE_TFTP config UPDATE_TFTP_MSEC_MAX int "Delay in mSec to wait for the TFTP server during auto-update" default 100 depends on UPDATE_TFTP endmenu |
c2ae7d822 Kconfig: Move SPL... |
593 |
source "common/spl/Kconfig" |