]>
Commit | Line | Data |
---|---|---|
ee2b2434 SG |
1 | menu "Boot timing" |
2 | ||
3 | config 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 | |
57247d9c | 12 | add up all the accumulated time and report it. |
ee2b2434 SG |
13 | |
14 | Normally, IDs are defined in bootstage.h but a small number of | |
57247d9c | 15 | additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC |
ee2b2434 SG |
16 | as the ID. |
17 | ||
57247d9c | 18 | Calls to show_boot_progress() will also result in log entries but |
ee2b2434 SG |
19 | these will not have names. |
20 | ||
824bb1b4 SG |
21 | config 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 | ||
ee2b2434 SG |
30 | config 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 | ||
49 | config BOOTSTAGE_USER_COUNT | |
5a0e275c | 50 | int "Number of boot ID numbers available for user use" |
ee2b2434 SG |
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 | ||
03ecac31 SG |
58 | config 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 | ||
ee2b2434 SG |
65 | config 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 | |
57247d9c | 72 | mark time in microseconds, or 'accum' containing the |
ee2b2434 SG |
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 | ||
89 | config 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 | ||
100 | config 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 | ||
107 | config BOOTSTAGE_STASH_SIZE | |
108 | hex "Size of boot timing stash region" | |
fad6a2b7 | 109 | default 0x1000 |
ee2b2434 SG |
110 | help |
111 | This should be large enough to hold the bootstage stash. A value of | |
112 | 4096 (4KiB) is normally plenty. | |
113 | ||
114 | endmenu | |
115 | ||
d14739ff PF |
116 | menu "Boot media" |
117 | ||
118 | config 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 | ||
faaef73f PF |
127 | config 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, | |
57247d9c | 133 | some not. |
faaef73f PF |
134 | |
135 | config 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, | |
57247d9c | 141 | some not. |
faaef73f PF |
142 | |
143 | config 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, | |
57247d9c | 149 | some not. |
faaef73f PF |
150 | |
151 | config 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, | |
57247d9c | 157 | some not. |
faaef73f PF |
158 | |
159 | config 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, | |
57247d9c | 165 | some not. |
faaef73f PF |
166 | |
167 | config 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, | |
57247d9c | 173 | some not. |
faaef73f | 174 | |
d14739ff PF |
175 | endmenu |
176 | ||
bb597c0e HS |
177 | config BOOTDELAY |
178 | int "delay in seconds before automatically booting" | |
5e4e8741 | 179 | default 2 |
41598c82 | 180 | depends on AUTOBOOT |
bb597c0e HS |
181 | help |
182 | Delay before automatically running bootcmd; | |
2fbb8462 | 183 | set to 0 to autoboot with no delay, but you can stop it by key input. |
bb597c0e HS |
184 | set to -1 to disable autoboot. |
185 | set to -2 to autoboot with no delay and not check for abort | |
bb597c0e | 186 | |
9060970f MY |
187 | See doc/README.autoboot for details. |
188 | ||
5abc1a45 SP |
189 | config 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 | ||
197 | config 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 | ||
98af8799 SG |
205 | menu "Console" |
206 | ||
4880b026 TR |
207 | config 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 | ||
9854a874 SG |
213 | config CONSOLE_RECORD |
214 | bool "Console recording" | |
215 | help | |
216 | This provides a way to record console output (and provide console | |
57247d9c | 217 | input) through circular buffers. This is mostly useful for testing. |
9854a874 SG |
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 | ||
222 | config 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 | ||
231 | config 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. | |
4d25507f | 240 | |
a4d88920 SDPP |
241 | config 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 | ||
98af8799 SG |
246 | config SILENT_CONSOLE |
247 | bool "Support a silent console" | |
248 | help | |
249 | This option allows the console to be silenced, meaning that no | |
250 | output will appear on the console devices. This is controlled by | |
251 | setting the environment vaariable 'silent' to a non-empty value. | |
252 | Note this also silences the console when booting Linux. | |
253 | ||
254 | When the console is set up, the variable is checked, and the | |
255 | GD_FLG_SILENT flag is set. Changing the environment variable later | |
256 | will update the flag. | |
257 | ||
258 | config SILENT_U_BOOT_ONLY | |
259 | bool "Only silence the U-Boot console" | |
260 | depends on SILENT_CONSOLE | |
261 | help | |
262 | Normally when the U-Boot console is silenced, Linux's console is | |
263 | also silenced (assuming the board boots into Linux). This option | |
264 | allows the linux console to operate normally, even if U-Boot's | |
265 | is silenced. | |
266 | ||
267 | config SILENT_CONSOLE_UPDATE_ON_SET | |
268 | bool "Changes to the 'silent' environment variable update immediately" | |
269 | depends on SILENT_CONSOLE | |
270 | default y if SILENT_CONSOLE | |
271 | help | |
272 | When the 'silent' environment variable is changed, update the | |
273 | console silence flag immediately. This allows 'setenv' to be used | |
274 | to silence or un-silence the console. | |
275 | ||
276 | The effect is that any change to the variable will affect the | |
277 | GD_FLG_SILENT flag. | |
278 | ||
279 | config SILENT_CONSOLE_UPDATE_ON_RELOC | |
280 | bool "Allow flags to take effect on relocation" | |
281 | depends on SILENT_CONSOLE | |
282 | help | |
283 | In some cases the environment is not available until relocation | |
284 | (e.g. NAND). This option makes the value of the 'silent' | |
285 | environment variable take effect at relocation. | |
286 | ||
8f925584 SG |
287 | config PRE_CONSOLE_BUFFER |
288 | bool "Buffer characters before the console is available" | |
289 | help | |
290 | Prior to the console being initialised (i.e. serial UART | |
291 | initialised etc) all console output is silently discarded. | |
292 | Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to | |
293 | buffer any console messages prior to the console being | |
294 | initialised to a buffer. The buffer is a circular buffer, so | |
295 | if it overflows, earlier output is discarded. | |
296 | ||
297 | Note that this is not currently supported in SPL. It would be | |
298 | useful to be able to share the pre-console buffer with SPL. | |
299 | ||
300 | config PRE_CON_BUF_SZ | |
301 | int "Sets the size of the pre-console buffer" | |
302 | depends on PRE_CONSOLE_BUFFER | |
303 | default 4096 | |
304 | help | |
305 | The size of the pre-console buffer affects how much console output | |
306 | can be held before it overflows and starts discarding earlier | |
307 | output. Normally there is very little output at this early stage, | |
308 | unless debugging is enabled, so allow enough for ~10 lines of | |
309 | text. | |
310 | ||
311 | This is a useful feature if you are using a video console and | |
312 | want to see the full boot output on the console. Without this | |
313 | option only the post-relocation output will be displayed. | |
314 | ||
315 | config PRE_CON_BUF_ADDR | |
316 | hex "Address of the pre-console buffer" | |
317 | depends on PRE_CONSOLE_BUFFER | |
318 | default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I | |
319 | default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I | |
320 | help | |
321 | This sets the start address of the pre-console buffer. This must | |
322 | be in available memory and is accessed before relocation and | |
323 | possibly before DRAM is set up. Therefore choose an address | |
324 | carefully. | |
325 | ||
326 | We should consider removing this option and allocating the memory | |
327 | in board_init_f_init_reserve() instead. | |
328 | ||
ef26d603 SG |
329 | config CONSOLE_MUX |
330 | bool "Enable console multiplexing" | |
331 | default y if DM_VIDEO || VIDEO || LCD | |
332 | help | |
333 | This allows multiple devices to be used for each console 'file'. | |
334 | For example, stdout can be set to go to serial and video. | |
335 | Similarly, stdin can be set to come from serial and keyboard. | |
336 | Input can be provided from either source. Console multiplexing | |
337 | adds a small amount of size to U-Boot. Changes to the environment | |
338 | variables stdout, stdin and stderr will take effect immediately. | |
339 | ||
340 | config SYS_CONSOLE_IS_IN_ENV | |
341 | bool "Select console devices from the environment" | |
342 | default y if CONSOLE_MUX | |
343 | help | |
344 | This allows multiple input/output devices to be set at boot time. | |
345 | For example, if stdout is set to "serial,video" then output will | |
346 | be sent to both the serial and video devices on boot. The | |
347 | environment variables can be updated after boot to change the | |
348 | input/output devices. | |
349 | ||
84f2a5d0 SG |
350 | config SYS_CONSOLE_OVERWRITE_ROUTINE |
351 | bool "Allow board control over console overwriting" | |
352 | help | |
353 | If this is enabled, and the board-specific function | |
354 | overwrite_console() returns 1, the stdin, stderr and stdout are | |
355 | switched to the serial port, else the settings in the environment | |
356 | are used. If this is not enabled, the console will not be switched | |
357 | to serial. | |
358 | ||
3505bc55 SG |
359 | config SYS_CONSOLE_ENV_OVERWRITE |
360 | bool "Update environment variables during console init" | |
361 | help | |
362 | The console environment variables (stdout, stdin, stderr) can be | |
363 | used to determine the correct console devices on start-up. This | |
364 | option writes the console devices to these variables on console | |
365 | start-up (after relocation). This causes the environment to be | |
366 | updated to match the console devices actually chosen. | |
367 | ||
f3f3efff SG |
368 | config SYS_CONSOLE_INFO_QUIET |
369 | bool "Don't display the console devices on boot" | |
370 | help | |
371 | Normally U-Boot displays the current settings for stdout, stdin | |
372 | and stderr on boot when the post-relocation console is set up. | |
373 | Enable this option to supress this output. It can be obtained by | |
374 | calling stdio_print_current_devices() from board code. | |
375 | ||
869588de SG |
376 | config SYS_STDIO_DEREGISTER |
377 | bool "Allow deregistering stdio devices" | |
378 | default y if USB_KEYBOARD | |
379 | help | |
380 | Generally there is no need to deregister stdio devices since they | |
381 | are never deactivated. But if a stdio device is used which can be | |
382 | removed (for example a USB keyboard) then this option can be | |
383 | enabled to ensure this is handled correctly. | |
384 | ||
98af8799 SG |
385 | endmenu |
386 | ||
af9e6ad4 CJF |
387 | config DTB_RESELECT |
388 | bool "Support swapping dtbs at a later point in boot" | |
389 | depends on FIT_EMBED | |
390 | help | |
391 | It is possible during initial boot you may need to use a generic | |
392 | dtb until you can fully determine the board your running on. This | |
393 | config allows boards to implement a function at a later point | |
394 | during boot to switch to the "correct" dtb. | |
395 | ||
92926bc8 CJF |
396 | config FIT_EMBED |
397 | bool "Support a FIT image embedded in the U-boot image" | |
398 | help | |
399 | This option provides hooks to allow U-boot to parse an | |
400 | appended FIT image and enable board specific code to then select | |
401 | the correct DTB to be used. | |
402 | ||
d259c008 JT |
403 | config DEFAULT_FDT_FILE |
404 | string "Default fdt file" | |
405 | help | |
406 | This option is used to set the default fdt file to boot OS. | |
407 | ||
9dd1d0aa HS |
408 | config VERSION_VARIABLE |
409 | bool "add U-Boot environment variable vers" | |
410 | default n | |
411 | help | |
412 | If this variable is defined, an environment variable | |
413 | named "ver" is created by U-Boot showing the U-Boot | |
414 | version as printed by the "version" command. | |
415 | Any change to this variable will be reverted at the | |
416 | next reset. | |
c2ae7d82 | 417 | |
de70fefb | 418 | config BOARD_LATE_INIT |
e5ec4815 | 419 | bool |
de70fefb JT |
420 | help |
421 | Sometimes board require some initialization code that might | |
422 | require once the actual init done, example saving board specific env, | |
423 | boot-modes etc. which eventually done at late. | |
424 | ||
425 | So this config enable the late init code with the help of board_late_init | |
426 | function which should defined on respective boards. | |
427 | ||
19a97475 LV |
428 | config DISPLAY_CPUINFO |
429 | bool "Display information about the CPU during start up" | |
064b55cf | 430 | default y if ARM || NIOS2 || X86 || XTENSA |
19a97475 LV |
431 | help |
432 | Display information about the CPU that U-Boot is running on | |
433 | when U-Boot starts up. The function print_cpuinfo() is called | |
434 | to do this. | |
435 | ||
84351792 LV |
436 | config DISPLAY_BOARDINFO |
437 | bool "Display information about the board during start up" | |
d63b5b4f | 438 | default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA |
84351792 LV |
439 | help |
440 | Display information about the board that U-Boot is running on | |
441 | when U-Boot starts up. The board function checkboard() is called | |
442 | to do this. | |
443 | ||
a421192f SG |
444 | menu "Start-up hooks" |
445 | ||
446 | config ARCH_EARLY_INIT_R | |
447 | bool "Call arch-specific init soon after relocation" | |
a421192f SG |
448 | help |
449 | With this option U-Boot will call arch_early_init_r() soon after | |
450 | relocation. Driver model is running by this point, and the cache | |
451 | is on. Note that board_early_init_r() is called first, if | |
452 | enabled. This can be used to set up architecture-specific devices. | |
453 | ||
4585601a SG |
454 | config ARCH_MISC_INIT |
455 | bool "Call arch-specific init after relocation, when console is ready" | |
456 | help | |
457 | With this option U-Boot will call arch_misc_init() after | |
458 | relocation to allow miscellaneous arch-dependent initialisation | |
459 | to be performed. This function should be defined by the board | |
460 | and will be called after the console is set up, after relocaiton. | |
461 | ||
a5d67547 SG |
462 | config BOARD_EARLY_INIT_F |
463 | bool "Call board-specific init before relocation" | |
a5d67547 SG |
464 | help |
465 | Some boards need to perform initialisation as soon as possible | |
466 | after boot. With this option, U-Boot calls board_early_init_f() | |
467 | after driver model is ready in the pre-relocation init sequence. | |
468 | Note that the normal serial console is not yet set up, but the | |
469 | debug UART will be available if enabled. | |
470 | ||
a421192f SG |
471 | endmenu |
472 | ||
d70f919e SG |
473 | menu "Security support" |
474 | ||
475 | config HASH | |
476 | bool # "Support hashing API (SHA1, SHA256, etc.)" | |
477 | help | |
478 | This provides a way to hash data in memory using various supported | |
479 | algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h | |
480 | and the algorithms it supports are defined in common/hash.c. See | |
481 | also CMD_HASH for command-line access. | |
482 | ||
483 | endmenu | |
484 | ||
c2ae7d82 | 485 | source "common/spl/Kconfig" |