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 accumated time and report it.
14 Normally, IDs are defined in bootstage.h but a small number of
15 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
18 Calls to show_boot_progress() wil also result in log entries but
19 these will not have names.
21 config BOOTSTAGE_REPORT
22 bool "Display a detailed boot timing report before booting the OS"
25 Enable output of a boot time report just before the OS is booted.
26 This shows how long it took U-Boot to go through each stage of the
27 boot process. The report looks something like this:
29 Timer summary in microseconds:
32 3,575,678 3,575,678 board_init_f start
33 3,575,695 17 arch_cpu_init A9
34 3,575,777 82 arch_cpu_init done
35 3,659,598 83,821 board_init_r start
36 3,910,375 250,777 main_loop
37 29,916,167 26,005,792 bootm_start
38 30,361,327 445,160 start_kernel
40 config BOOTSTAGE_USER_COUNT
41 hex "Number of boot ID numbers available for user use"
44 This is the number of available user bootstage records.
45 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
46 a new ID will be allocated from this stash. If you exceed
47 the limit, recording will stop.
50 bool "Store boot timing information in the OS device tree"
53 Stash the bootstage information in the FDT. A root 'bootstage'
54 node is created with each bootstage id as a child. Each child
55 has a 'name' property and either 'mark' containing the
56 mark time in microsecond, or 'accum' containing the
57 accumulated time for that bootstage id in microseconds.
62 name = "board_init_f";
71 Code in the Linux kernel can find this in /proc/devicetree.
73 config BOOTSTAGE_STASH
74 bool "Stash the boot timing information in memory before booting OS"
77 Some OSes do not support device tree. Bootstage can instead write
78 the boot timing information in a binary format at a given address.
79 This happens through a call to bootstage_stash(), typically in
80 the CPU's cleanup_before_linux() function. You can use the
81 'bootstage stash' and 'bootstage unstash' commands to do this on
84 config BOOTSTAGE_STASH_ADDR
85 hex "Address to stash boot timing information"
88 Provide an address which will not be overwritten by the OS when it
89 starts, so that it can read this information when ready.
91 config BOOTSTAGE_STASH_SIZE
92 hex "Size of boot timing stash region"
95 This should be large enough to hold the bootstage stash. A value of
96 4096 (4KiB) is normally plenty.
101 int "delay in seconds before automatically booting"
105 Delay before automatically running bootcmd;
106 set to -1 to disable autoboot.
107 set to -2 to autoboot with no delay and not check for abort
108 (even when CONFIG_ZERO_BOOTDELAY_CHECK is defined).
110 config CONSOLE_RECORD
111 bool "Console recording"
113 This provides a way to record console output (and provide console
114 input) through cirular buffers. This is mostly useful for testing.
115 Console output is recorded even when the console is silent.
116 To enable console recording, call console_record_reset_enable()
119 config CONSOLE_RECORD_OUT_SIZE
120 hex "Output buffer size"
121 depends on CONSOLE_RECORD
122 default 0x400 if CONSOLE_RECORD
124 Set the size of the console output buffer. When this fills up, no
125 more data will be recorded until some is removed. The buffer is
126 allocated immediately after the malloc() region is ready.
128 config CONSOLE_RECORD_IN_SIZE
129 hex "Input buffer size"
130 depends on CONSOLE_RECORD
131 default 0x100 if CONSOLE_RECORD
133 Set the size of the console input buffer. When this contains data,
134 tstc() and getc() will use this in preference to real device input.
135 The buffer is allocated immediately after the malloc() region is