xref: /openbmc/u-boot/common/Kconfig (revision d754254f)
1menu "Boot timing"
2
3config 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
12	  add up all the accumulated time and report it.
13
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
16	  as the ID.
17
18	  Calls to show_boot_progress() will also result in log entries but
19	  these will not have names.
20
21config 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
30config 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
49config BOOTSTAGE_USER_COUNT
50	int "Number of boot ID numbers available for user use"
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
58config 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
65config 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
72	  mark time in microseconds, or 'accum' containing the
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
89config 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
100config 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
107config BOOTSTAGE_STASH_SIZE
108	hex "Size of boot timing stash region"
109	default 0x1000
110	help
111	  This should be large enough to hold the bootstage stash. A value of
112	  4096 (4KiB) is normally plenty.
113
114endmenu
115
116menu "Boot media"
117
118config 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
127config 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,
133	  some not.
134
135config 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,
141	  some not.
142
143config 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,
149	  some not.
150
151config 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,
157	  some not.
158
159config 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,
165	  some not.
166
167config 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,
173	  some not.
174
175endmenu
176
177menu "Environment"
178
179if ARCH_SUNXI
180
181choice
182	prompt "Environment Device"
183	default ENV_IS_IN_MMC if ARCH_SUNXI
184
185config ENV_IS_IN_MMC
186	bool "Environment in an MMC device"
187	depends on CMD_MMC
188	help
189	  Define this if you have an MMC device which you want to use for the
190	  environment.
191
192config ENV_IS_IN_NAND
193	bool "Environment in a NAND device"
194	depends on CMD_NAND
195	help
196	  Define this if you have a NAND device which you want to use for the
197	  environment.
198
199config ENV_IS_IN_UBI
200	bool "Environment in a UBI volume"
201	depends on CMD_UBI
202	depends on CMD_MTDPARTS
203	help
204	  Define this if you have a UBI volume which you want to use for the
205	  environment.
206
207config ENV_IS_NOWHERE
208	bool "Environment is not stored"
209	help
210	  Define this if you don't want to or can't have an environment stored
211	  on a storage medium
212
213endchoice
214
215config ENV_OFFSET
216	hex "Environment Offset"
217	depends on !ENV_IS_IN_UBI
218	depends on !ENV_IS_NOWHERE
219	default 0x88000 if ARCH_SUNXI
220	help
221	  Offset from the start of the device (or partition)
222
223config ENV_SIZE
224	hex "Environment Size"
225	depends on !ENV_IS_NOWHERE
226	default 0x20000 if ARCH_SUNXI
227	help
228	  Size of the environment storage area
229
230config ENV_UBI_PART
231	string "UBI partition name"
232	depends on ENV_IS_IN_UBI
233	help
234	  MTD partition containing the UBI device
235
236config ENV_UBI_VOLUME
237	string "UBI volume name"
238	depends on ENV_IS_IN_UBI
239	help
240	  Name of the volume that you want to store the environment in.
241
242endif
243
244endmenu
245
246config BOOTDELAY
247	int "delay in seconds before automatically booting"
248	default 2
249	depends on AUTOBOOT
250	help
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
255
256	  See doc/README.autoboot for details.
257
258menu "Console"
259
260config MENU
261	bool
262	help
263	  This is the library functionality to provide a text-based menu of
264	  choices for the user to make choices with.
265
266config CONSOLE_RECORD
267	bool "Console recording"
268	help
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()
273	  from your code.
274
275config CONSOLE_RECORD_OUT_SIZE
276	hex "Output buffer size"
277	depends on CONSOLE_RECORD
278	default 0x400 if CONSOLE_RECORD
279	help
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.
283
284config CONSOLE_RECORD_IN_SIZE
285	hex "Input buffer size"
286	depends on CONSOLE_RECORD
287	default 0x100 if CONSOLE_RECORD
288	help
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
292	  ready.
293
294config IDENT_STRING
295	string "Board specific string to be added to uboot version string"
296	help
297	  This options adds the board specific name to u-boot version.
298
299config SILENT_CONSOLE
300	bool "Support a silent console"
301	help
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.
306
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.
310
311config SILENT_U_BOOT_ONLY
312	bool "Only silence the U-Boot console"
313	depends on SILENT_CONSOLE
314	help
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
318	  is silenced.
319
320config 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
324	help
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.
328
329	  The effect is that any change to the variable will affect the
330	  GD_FLG_SILENT flag.
331
332config SILENT_CONSOLE_UPDATE_ON_RELOC
333	bool "Allow flags to take effect on relocation"
334	depends on SILENT_CONSOLE
335	help
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.
339
340config PRE_CONSOLE_BUFFER
341	bool "Buffer characters before the console is available"
342	help
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.
349
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.
352
353config PRE_CON_BUF_SZ
354	int "Sets the size of the pre-console buffer"
355	depends on PRE_CONSOLE_BUFFER
356	default 4096
357	help
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
362	  text.
363
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.
367
368config 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
373	help
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
377	  carefully.
378
379	  We should consider removing this option and allocating the memory
380	  in board_init_f_init_reserve() instead.
381
382config CONSOLE_MUX
383	bool "Enable console multiplexing"
384	default y if DM_VIDEO || VIDEO || LCD
385	help
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.
392
393config SYS_CONSOLE_IS_IN_ENV
394	bool "Select console devices from the environment"
395	default y if CONSOLE_MUX
396	help
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.
402
403config SYS_CONSOLE_OVERWRITE_ROUTINE
404	bool "Allow board control over console overwriting"
405	help
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
410	  to serial.
411
412config SYS_CONSOLE_ENV_OVERWRITE
413	bool "Update environment variables during console init"
414	help
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.
420
421config SYS_CONSOLE_INFO_QUIET
422	bool "Don't display the console devices on boot"
423	help
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.
428
429config SYS_STDIO_DEREGISTER
430	bool "Allow deregistering stdio devices"
431	default y if USB_KEYBOARD
432	help
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.
437
438endmenu
439
440config DTB_RESELECT
441	bool "Support swapping dtbs at a later point in boot"
442	depends on FIT_EMBED
443	help
444	  It is possible during initial boot you may need to use a generic
445	  dtb until you can fully determine the board your running on. This
446	  config allows boards to implement a function at a later point
447	  during boot to switch to the "correct" dtb.
448
449config FIT_EMBED
450	bool "Support a FIT image embedded in the U-boot image"
451	help
452	  This option provides hooks to allow U-boot to parse an
453	  appended FIT image and enable board specific code to then select
454	  the correct DTB to be used.
455
456config DEFAULT_FDT_FILE
457	string "Default fdt file"
458	help
459	  This option is used to set the default fdt file to boot OS.
460
461config VERSION_VARIABLE
462	bool "add U-Boot environment variable vers"
463	default n
464	help
465	  If this variable is defined, an environment variable
466	  named "ver" is created by U-Boot showing the U-Boot
467	  version as printed by the "version" command.
468	  Any change to this variable will be reverted at the
469	  next reset.
470
471config BOARD_LATE_INIT
472	bool
473	help
474	  Sometimes board require some initialization code that might
475	  require once the actual init done, example saving board specific env,
476	  boot-modes etc. which eventually done at late.
477
478	  So this config enable the late init code with the help of board_late_init
479	  function which should defined on respective boards.
480
481config DISPLAY_CPUINFO
482	bool "Display information about the CPU during start up"
483	default y if ARM || NIOS2 || X86 || XTENSA
484	help
485	  Display information about the CPU that U-Boot is running on
486	  when U-Boot starts up. The function print_cpuinfo() is called
487	  to do this.
488
489config DISPLAY_BOARDINFO
490	bool "Display information about the board during start up"
491	default y if ARM || M68K || MIPS || PPC || XTENSA
492	help
493	  Display information about the board that U-Boot is running on
494	  when U-Boot starts up. The board function checkboard() is called
495	  to do this.
496
497menu "Start-up hooks"
498
499config ARCH_EARLY_INIT_R
500	bool "Call arch-specific init soon after relocation"
501	default y if X86
502	help
503	  With this option U-Boot will call arch_early_init_r() soon after
504	  relocation. Driver model is running by this point, and the cache
505	  is on. Note that board_early_init_r() is called first, if
506	  enabled. This can be used to set up architecture-specific devices.
507
508config ARCH_MISC_INIT
509	bool "Call arch-specific init after relocation, when console is ready"
510	help
511	  With this option U-Boot will call arch_misc_init() after
512	  relocation to allow miscellaneous arch-dependent initialisation
513	  to be performed. This function should be defined by the board
514	  and will be called after the console is set up, after relocaiton.
515
516config BOARD_EARLY_INIT_F
517	bool "Call board-specific init before relocation"
518	default y if X86
519	help
520	  Some boards need to perform initialisation as soon as possible
521	  after boot. With this option, U-Boot calls board_early_init_f()
522	  after driver model is ready in the pre-relocation init sequence.
523	  Note that the normal serial console is not yet set up, but the
524	  debug UART will be available if enabled.
525
526endmenu
527
528menu "Security support"
529
530config HASH
531	bool # "Support hashing API (SHA1, SHA256, etc.)"
532	help
533	  This provides a way to hash data in memory using various supported
534	  algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
535	  and the algorithms it supports are defined in common/hash.c. See
536	  also CMD_HASH for command-line access.
537
538endmenu
539
540source "common/spl/Kconfig"
541