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.
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 microseconds, 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.
103 bool "Support for booting from NOR flash"
106 Enabling this will make a U-Boot binary that is capable of being
107 booted via NOR. In this case we will enable certain pinmux early
108 as the ROM only partially sets up pinmux. We also default to using
112 bool "Support for booting from NAND flash"
115 Enabling this will make a U-Boot binary that is capable of being
116 booted via NAND flash. This is not a must, some SoCs need this,
120 bool "Support for booting from ONENAND"
123 Enabling this will make a U-Boot binary that is capable of being
124 booted via ONENAND. This is not a must, some SoCs need this,
128 bool "Support for booting from QSPI flash"
131 Enabling this will make a U-Boot binary that is capable of being
132 booted via QSPI flash. This is not a must, some SoCs need this,
136 bool "Support for booting from SATA"
139 Enabling this will make a U-Boot binary that is capable of being
140 booted via SATA. This is not a must, some SoCs need this,
144 bool "Support for booting from SD/EMMC"
147 Enabling this will make a U-Boot binary that is capable of being
148 booted via SD/EMMC. This is not a must, some SoCs need this,
152 bool "Support for booting from SPI flash"
155 Enabling this will make a U-Boot binary that is capable of being
156 booted via SPI flash. This is not a must, some SoCs need this,
162 int "delay in seconds before automatically booting"
166 Delay before automatically running bootcmd;
167 set to 0 to autoboot with no delay, but you can stop it by key input.
168 set to -1 to disable autoboot.
169 set to -2 to autoboot with no delay and not check for abort
171 See doc/README.autoboot for details.
173 config CONSOLE_RECORD
174 bool "Console recording"
176 This provides a way to record console output (and provide console
177 input) through circular buffers. This is mostly useful for testing.
178 Console output is recorded even when the console is silent.
179 To enable console recording, call console_record_reset_enable()
182 config CONSOLE_RECORD_OUT_SIZE
183 hex "Output buffer size"
184 depends on CONSOLE_RECORD
185 default 0x400 if CONSOLE_RECORD
187 Set the size of the console output buffer. When this fills up, no
188 more data will be recorded until some is removed. The buffer is
189 allocated immediately after the malloc() region is ready.
191 config CONSOLE_RECORD_IN_SIZE
192 hex "Input buffer size"
193 depends on CONSOLE_RECORD
194 default 0x100 if CONSOLE_RECORD
196 Set the size of the console input buffer. When this contains data,
197 tstc() and getc() will use this in preference to real device input.
198 The buffer is allocated immediately after the malloc() region is
202 string "Board specific string to be added to uboot version string"
204 This options adds the board specific name to u-boot version.
207 bool "Disable support for parallel NOR flash"
210 This option is used to disable support for parallel NOR flash.
212 config VERSION_VARIABLE
213 bool "add U-Boot environment variable vers"
216 If this variable is defined, an environment variable
217 named "ver" is created by U-Boot showing the U-Boot
218 version as printed by the "version" command.
219 Any change to this variable will be reverted at the
222 source "common/spl/Kconfig"