4 bool "Boot timing and reporting"
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.
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
18 Calls to show_boot_progress() will also result in log entries but
19 these will not have names.
22 bool "Boot timing and reported in SPL"
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
30 config BOOTSTAGE_REPORT
31 bool "Display a detailed boot timing report before booting the OS"
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:
38 Timer summary in microseconds:
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
49 config BOOTSTAGE_USER_COUNT
50 int "Number of boot ID numbers available for user use"
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.
58 config BOOTSTAGE_RECORD_COUNT
59 int "Number of boot stage records to store"
62 This is the size of the bootstage record list and is the maximum
63 number of bootstage records that can be recorded.
66 bool "Store boot timing information in the OS device tree"
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.
78 name = "board_init_f";
87 Code in the Linux kernel can find this in /proc/devicetree.
89 config BOOTSTAGE_STASH
90 bool "Stash the boot timing information in memory before booting OS"
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
100 config BOOTSTAGE_STASH_ADDR
101 hex "Address to stash boot timing information"
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.
107 config BOOTSTAGE_STASH_SIZE
108 hex "Size of boot timing stash region"
111 This should be large enough to hold the bootstage stash. A value of
112 4096 (4KiB) is normally plenty.
119 bool "Support for booting from NOR flash"
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
128 bool "Support for booting from NAND flash"
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,
136 bool "Support for booting from ONENAND"
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,
144 bool "Support for booting from QSPI flash"
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,
152 bool "Support for booting from SATA"
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,
160 bool "Support for booting from SD/EMMC"
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,
168 bool "Support for booting from SPI flash"
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,
182 prompt "Environment Device"
183 default ENV_IS_IN_MMC if ARCH_SUNXI
186 bool "Environment in an MMC device"
189 Define this if you have an MMC device which you want to use for the
192 config ENV_IS_IN_NAND
193 bool "Environment in a NAND device"
196 Define this if you have a NAND device which you want to use for the
200 bool "Environment in a UBI volume"
202 depends on CMD_MTDPARTS
204 Define this if you have a UBI volume which you want to use for the
207 config ENV_IS_NOWHERE
208 bool "Environment is not stored"
210 Define this if you don't want to or can't have an environment stored
216 hex "Environment Offset"
217 depends on !ENV_IS_IN_UBI
218 depends on !ENV_IS_NOWHERE
219 default 0x88000 if ARCH_SUNXI
221 Offset from the start of the device (or partition)
224 hex "Environment Size"
225 depends on !ENV_IS_NOWHERE
226 default 0x20000 if ARCH_SUNXI
228 Size of the environment storage area
231 string "UBI partition name"
232 depends on ENV_IS_IN_UBI
234 MTD partition containing the UBI device
236 config ENV_UBI_VOLUME
237 string "UBI volume name"
238 depends on ENV_IS_IN_UBI
240 Name of the volume that you want to store the environment in.
247 int "delay in seconds before automatically booting"
251 Delay before automatically running bootcmd;
252 set to 0 to autoboot with no delay, but you can stop it by key input.
253 set to -1 to disable autoboot.
254 set to -2 to autoboot with no delay and not check for abort
256 See doc/README.autoboot for details.
263 This is the library functionality to provide a text-based menu of
264 choices for the user to make choices with.
266 config CONSOLE_RECORD
267 bool "Console recording"
269 This provides a way to record console output (and provide console
270 input) through circular buffers. This is mostly useful for testing.
271 Console output is recorded even when the console is silent.
272 To enable console recording, call console_record_reset_enable()
275 config CONSOLE_RECORD_OUT_SIZE
276 hex "Output buffer size"
277 depends on CONSOLE_RECORD
278 default 0x400 if CONSOLE_RECORD
280 Set the size of the console output buffer. When this fills up, no
281 more data will be recorded until some is removed. The buffer is
282 allocated immediately after the malloc() region is ready.
284 config CONSOLE_RECORD_IN_SIZE
285 hex "Input buffer size"
286 depends on CONSOLE_RECORD
287 default 0x100 if CONSOLE_RECORD
289 Set the size of the console input buffer. When this contains data,
290 tstc() and getc() will use this in preference to real device input.
291 The buffer is allocated immediately after the malloc() region is
295 string "Board specific string to be added to uboot version string"
297 This options adds the board specific name to u-boot version.
299 config SILENT_CONSOLE
300 bool "Support a silent console"
302 This option allows the console to be silenced, meaning that no
303 output will appear on the console devices. This is controlled by
304 setting the environment vaariable 'silent' to a non-empty value.
305 Note this also silences the console when booting Linux.
307 When the console is set up, the variable is checked, and the
308 GD_FLG_SILENT flag is set. Changing the environment variable later
309 will update the flag.
311 config SILENT_U_BOOT_ONLY
312 bool "Only silence the U-Boot console"
313 depends on SILENT_CONSOLE
315 Normally when the U-Boot console is silenced, Linux's console is
316 also silenced (assuming the board boots into Linux). This option
317 allows the linux console to operate normally, even if U-Boot's
320 config SILENT_CONSOLE_UPDATE_ON_SET
321 bool "Changes to the 'silent' environment variable update immediately"
322 depends on SILENT_CONSOLE
323 default y if SILENT_CONSOLE
325 When the 'silent' environment variable is changed, update the
326 console silence flag immediately. This allows 'setenv' to be used
327 to silence or un-silence the console.
329 The effect is that any change to the variable will affect the
332 config SILENT_CONSOLE_UPDATE_ON_RELOC
333 bool "Allow flags to take effect on relocation"
334 depends on SILENT_CONSOLE
336 In some cases the environment is not available until relocation
337 (e.g. NAND). This option makes the value of the 'silent'
338 environment variable take effect at relocation.
340 config PRE_CONSOLE_BUFFER
341 bool "Buffer characters before the console is available"
343 Prior to the console being initialised (i.e. serial UART
344 initialised etc) all console output is silently discarded.
345 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
346 buffer any console messages prior to the console being
347 initialised to a buffer. The buffer is a circular buffer, so
348 if it overflows, earlier output is discarded.
350 Note that this is not currently supported in SPL. It would be
351 useful to be able to share the pre-console buffer with SPL.
353 config PRE_CON_BUF_SZ
354 int "Sets the size of the pre-console buffer"
355 depends on PRE_CONSOLE_BUFFER
358 The size of the pre-console buffer affects how much console output
359 can be held before it overflows and starts discarding earlier
360 output. Normally there is very little output at this early stage,
361 unless debugging is enabled, so allow enough for ~10 lines of
364 This is a useful feature if you are using a video console and
365 want to see the full boot output on the console. Without this
366 option only the post-relocation output will be displayed.
368 config PRE_CON_BUF_ADDR
369 hex "Address of the pre-console buffer"
370 depends on PRE_CONSOLE_BUFFER
371 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
372 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
374 This sets the start address of the pre-console buffer. This must
375 be in available memory and is accessed before relocation and
376 possibly before DRAM is set up. Therefore choose an address
379 We should consider removing this option and allocating the memory
380 in board_init_f_init_reserve() instead.
383 bool "Enable console multiplexing"
384 default y if DM_VIDEO || VIDEO || LCD
386 This allows multiple devices to be used for each console 'file'.
387 For example, stdout can be set to go to serial and video.
388 Similarly, stdin can be set to come from serial and keyboard.
389 Input can be provided from either source. Console multiplexing
390 adds a small amount of size to U-Boot. Changes to the environment
391 variables stdout, stdin and stderr will take effect immediately.
393 config SYS_CONSOLE_IS_IN_ENV
394 bool "Select console devices from the environment"
395 default y if CONSOLE_MUX
397 This allows multiple input/output devices to be set at boot time.
398 For example, if stdout is set to "serial,video" then output will
399 be sent to both the serial and video devices on boot. The
400 environment variables can be updated after boot to change the
401 input/output devices.
403 config SYS_CONSOLE_OVERWRITE_ROUTINE
404 bool "Allow board control over console overwriting"
406 If this is enabled, and the board-specific function
407 overwrite_console() returns 1, the stdin, stderr and stdout are
408 switched to the serial port, else the settings in the environment
409 are used. If this is not enabled, the console will not be switched
412 config SYS_CONSOLE_ENV_OVERWRITE
413 bool "Update environment variables during console init"
415 The console environment variables (stdout, stdin, stderr) can be
416 used to determine the correct console devices on start-up. This
417 option writes the console devices to these variables on console
418 start-up (after relocation). This causes the environment to be
419 updated to match the console devices actually chosen.
421 config SYS_CONSOLE_INFO_QUIET
422 bool "Don't display the console devices on boot"
424 Normally U-Boot displays the current settings for stdout, stdin
425 and stderr on boot when the post-relocation console is set up.
426 Enable this option to supress this output. It can be obtained by
427 calling stdio_print_current_devices() from board code.
429 config SYS_STDIO_DEREGISTER
430 bool "Allow deregistering stdio devices"
431 default y if USB_KEYBOARD
433 Generally there is no need to deregister stdio devices since they
434 are never deactivated. But if a stdio device is used which can be
435 removed (for example a USB keyboard) then this option can be
436 enabled to ensure this is handled correctly.
440 config DEFAULT_FDT_FILE
441 string "Default fdt file"
443 This option is used to set the default fdt file to boot OS.
445 config VERSION_VARIABLE
446 bool "add U-Boot environment variable vers"
449 If this variable is defined, an environment variable
450 named "ver" is created by U-Boot showing the U-Boot
451 version as printed by the "version" command.
452 Any change to this variable will be reverted at the
455 config BOARD_LATE_INIT
458 Sometimes board require some initialization code that might
459 require once the actual init done, example saving board specific env,
460 boot-modes etc. which eventually done at late.
462 So this config enable the late init code with the help of board_late_init
463 function which should defined on respective boards.
465 config DISPLAY_CPUINFO
466 bool "Display information about the CPU during start up"
467 default y if ARM || NIOS2 || X86 || XTENSA || MPC5xxx
469 Display information about the CPU that U-Boot is running on
470 when U-Boot starts up. The function print_cpuinfo() is called
473 config DISPLAY_BOARDINFO
474 bool "Display information about the board during start up"
475 default y if ARM || M68K || MIPS || PPC || XTENSA
477 Display information about the board that U-Boot is running on
478 when U-Boot starts up. The board function checkboard() is called
481 menu "Start-up hooks"
483 config ARCH_EARLY_INIT_R
484 bool "Call arch-specific init soon after relocation"
487 With this option U-Boot will call arch_early_init_r() soon after
488 relocation. Driver model is running by this point, and the cache
489 is on. Note that board_early_init_r() is called first, if
490 enabled. This can be used to set up architecture-specific devices.
492 config ARCH_MISC_INIT
493 bool "Call arch-specific init after relocation, when console is ready"
495 With this option U-Boot will call arch_misc_init() after
496 relocation to allow miscellaneous arch-dependent initialisation
497 to be performed. This function should be defined by the board
498 and will be called after the console is set up, after relocaiton.
500 config BOARD_EARLY_INIT_F
501 bool "Call board-specific init before relocation"
504 Some boards need to perform initialisation as soon as possible
505 after boot. With this option, U-Boot calls board_early_init_f()
506 after driver model is ready in the pre-relocation init sequence.
507 Note that the normal serial console is not yet set up, but the
508 debug UART will be available if enabled.
512 menu "Security support"
515 bool # "Support hashing API (SHA1, SHA256, etc.)"
517 This provides a way to hash data in memory using various supported
518 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
519 and the algorithms it supports are defined in common/hash.c. See
520 also CMD_HASH for command-line access.
524 source "common/spl/Kconfig"