1source "common/Kconfig.boot"
2
3menu "Console"
4
5config MENU
6 bool
7 help
8 This is the library functionality to provide a text-based menu of
9 choices for the user to make choices with.
10
11config CONSOLE_RECORD
12 bool "Console recording"
13 help
14 This provides a way to record console output (and provide console
15 input) through circular buffers. This is mostly useful for testing.
16 Console output is recorded even when the console is silent.
17 To enable console recording, call console_record_reset_enable()
18 from your code.
19
20config CONSOLE_RECORD_INIT_F
21 bool "Enable console recording during pre-relocation init"
22 depends on CONSOLE_RECORD && SYS_MALLOC_F
23 default y
24 help
25 This option enables console recording during pre-relocation init.
26 CONFIG_SYS_MALLOC_F must be enabled to use this feature.
27
28config CONSOLE_RECORD_OUT_SIZE
29 hex "Output buffer size"
30 depends on CONSOLE_RECORD
31 default 0x400 if CONSOLE_RECORD
32 help
33 Set the size of the console output buffer. When this fills up, no
34 more data will be recorded until some is removed. The buffer is
35 allocated immediately after the malloc() region is ready.
36
37config CONSOLE_RECORD_IN_SIZE
38 hex "Input buffer size"
39 depends on CONSOLE_RECORD
40 default 0x100 if CONSOLE_RECORD
41 help
42 Set the size of the console input buffer. When this contains data,
43 tstc() and getc() will use this in preference to real device input.
44 The buffer is allocated immediately after the malloc() region is
45 ready.
46
47config DISABLE_CONSOLE
48 bool "Add functionality to disable console completely"
49 help
50 Disable console (in & out).
51
52config IDENT_STRING
53 string "Board specific string to be added to uboot version string"
54 help
55 This options adds the board specific name to u-boot version.
56
57config LOGLEVEL
58 int "loglevel"
59 default 4
60 range 0 10
61 help
62 All Messages with a loglevel smaller than the console loglevel will
63 be compiled in. The loglevels are defined as follows:
64
65 0 - emergency
66 1 - alert
67 2 - critical
68 3 - error
69 4 - warning
70 5 - note
71 6 - info
72 7 - debug
73 8 - debug content
74 9 - debug hardware I/O
75
76config SPL_LOGLEVEL
77 int
78 default LOGLEVEL
79
80config TPL_LOGLEVEL
81 int
82 default LOGLEVEL
83
84config SILENT_CONSOLE
85 bool "Support a silent console"
86 help
87 This option allows the console to be silenced, meaning that no
88 output will appear on the console devices. This is controlled by
89 setting the environment variable 'silent' to a non-empty value.
90 Note this also silences the console when booting Linux.
91
92 When the console is set up, the variable is checked, and the
93 GD_FLG_SILENT flag is set. Changing the environment variable later
94 will update the flag.
95
96config SILENT_U_BOOT_ONLY
97 bool "Only silence the U-Boot console"
98 depends on SILENT_CONSOLE
99 help
100 Normally when the U-Boot console is silenced, Linux's console is
101 also silenced (assuming the board boots into Linux). This option
102 allows the linux console to operate normally, even if U-Boot's
103 is silenced.
104
105config SILENT_CONSOLE_UPDATE_ON_SET
106 bool "Changes to the 'silent' environment variable update immediately"
107 depends on SILENT_CONSOLE
108 default y if SILENT_CONSOLE
109 help
110 When the 'silent' environment variable is changed, update the
111 console silence flag immediately. This allows 'setenv' to be used
112 to silence or un-silence the console.
113
114 The effect is that any change to the variable will affect the
115 GD_FLG_SILENT flag.
116
117config SILENT_CONSOLE_UPDATE_ON_RELOC
118 bool "Allow flags to take effect on relocation"
119 depends on SILENT_CONSOLE
120 help
121 In some cases the environment is not available until relocation
122 (e.g. NAND). This option makes the value of the 'silent'
123 environment variable take effect at relocation.
124
125config PRE_CONSOLE_BUFFER
126 bool "Buffer characters before the console is available"
127 help
128 Prior to the console being initialised (i.e. serial UART
129 initialised etc) all console output is silently discarded.
130 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
131 buffer any console messages prior to the console being
132 initialised to a buffer. The buffer is a circular buffer, so
133 if it overflows, earlier output is discarded.
134
135 Note that this is not currently supported in SPL. It would be
136 useful to be able to share the pre-console buffer with SPL.
137
138config PRE_CON_BUF_SZ
139 int "Sets the size of the pre-console buffer"
140 depends on PRE_CONSOLE_BUFFER
141 default 4096
142 help
143 The size of the pre-console buffer affects how much console output
144 can be held before it overflows and starts discarding earlier
145 output. Normally there is very little output at this early stage,
146 unless debugging is enabled, so allow enough for ~10 lines of
147 text.
148
149 This is a useful feature if you are using a video console and
150 want to see the full boot output on the console. Without this
151 option only the post-relocation output will be displayed.
152
153config PRE_CON_BUF_ADDR
154 hex "Address of the pre-console buffer"
155 depends on PRE_CONSOLE_BUFFER
156 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
157 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
158 default 0x0f000000 if ROCKCHIP_RK3288
159 default 0x0f200000 if ROCKCHIP_RK3399
160 help
161 This sets the start address of the pre-console buffer. This must
162 be in available memory and is accessed before relocation and
163 possibly before DRAM is set up. Therefore choose an address
164 carefully.
165
166 We should consider removing this option and allocating the memory
167 in board_init_f_init_reserve() instead.
168
169config CONSOLE_MUX
170 bool "Enable console multiplexing"
171 default y if DM_VIDEO || VIDEO || LCD
172 help
173 This allows multiple devices to be used for each console 'file'.
174 For example, stdout can be set to go to serial and video.
175 Similarly, stdin can be set to come from serial and keyboard.
176 Input can be provided from either source. Console multiplexing
177 adds a small amount of size to U-Boot. Changes to the environment
178 variables stdout, stdin and stderr will take effect immediately.
179
180config SYS_CONSOLE_IS_IN_ENV
181 bool "Select console devices from the environment"
182 default y if CONSOLE_MUX
183 help
184 This allows multiple input/output devices to be set at boot time.
185 For example, if stdout is set to "serial,video" then output will
186 be sent to both the serial and video devices on boot. The
187 environment variables can be updated after boot to change the
188 input/output devices.
189
190config SYS_CONSOLE_OVERWRITE_ROUTINE
191 bool "Allow board control over console overwriting"
192 help
193 If this is enabled, and the board-specific function
194 overwrite_console() returns 1, the stdin, stderr and stdout are
195 switched to the serial port, else the settings in the environment
196 are used. If this is not enabled, the console will not be switched
197 to serial.
198
199config SYS_CONSOLE_ENV_OVERWRITE
200 bool "Update environment variables during console init"
201 help
202 The console environment variables (stdout, stdin, stderr) can be
203 used to determine the correct console devices on start-up. This
204 option writes the console devices to these variables on console
205 start-up (after relocation). This causes the environment to be
206 updated to match the console devices actually chosen.
207
208config SYS_CONSOLE_INFO_QUIET
209 bool "Don't display the console devices on boot"
210 help
211 Normally U-Boot displays the current settings for stdout, stdin
212 and stderr on boot when the post-relocation console is set up.
213 Enable this option to suppress this output. It can be obtained by
214 calling stdio_print_current_devices() from board code.
215
216config SYS_STDIO_DEREGISTER
217 bool "Allow deregistering stdio devices"
218 default y if USB_KEYBOARD
219 help
220 Generally there is no need to deregister stdio devices since they
221 are never deactivated. But if a stdio device is used which can be
222 removed (for example a USB keyboard) then this option can be
223 enabled to ensure this is handled correctly.
224
225config SPL_SYS_STDIO_DEREGISTER
226 bool "Allow deregistering stdio devices in SPL"
227 help
228 Generally there is no need to deregister stdio devices since they
229 are never deactivated. But if a stdio device is used which can be
230 removed (for example a USB keyboard) then this option can be
231 enabled to ensure this is handled correctly. This is very rarely
232 needed in SPL.
233
234config SYS_DEVICE_NULLDEV
235 bool "Enable a null device for stdio"
236 default y if SPLASH_SCREEN || SYS_STDIO_DEREGISTER
237 help
238 Enable creation of a "nulldev" stdio device. This allows silent
239 operation of the console by setting stdout to "nulldev". Enable
240 this to use a serial console under board control.
241
242endmenu
243
244menu "Logging"
245
246config LOG
247 bool "Enable logging support"
248 depends on DM
249 help
250 This enables support for logging of status and debug messages. These
251 can be displayed on the console, recorded in a memory buffer, or
252 discarded if not needed. Logging supports various categories and
253 levels of severity.
254
255if LOG
256
257config LOG_MAX_LEVEL
258 int "Maximum log level to record"
259 default 6
260 range 0 9
261 help
262 This selects the maximum log level that will be recorded. Any value
263 higher than this will be ignored. If possible log statements below
264 this level will be discarded at build time. Levels:
265
266 0 - emergency
267 1 - alert
268 2 - critical
269 3 - error
270 4 - warning
271 5 - note
272 6 - info
273 7 - debug
274 8 - debug content
275 9 - debug hardware I/O
276
277config LOG_DEFAULT_LEVEL
278 int "Default logging level to display"
279 default LOG_MAX_LEVEL
280 range 0 LOG_MAX_LEVEL
281 help
282 This is the default logging level set when U-Boot starts. It can
283 be adjusted later using the 'log level' command. Note that setting
284 this to a value above LOG_MAX_LEVEL will be ineffective, since the
285 higher levels are not compiled in to U-Boot.
286
287 0 - emergency
288 1 - alert
289 2 - critical
290 3 - error
291 4 - warning
292 5 - note
293 6 - info
294 7 - debug
295 8 - debug content
296 9 - debug hardware I/O
297
298config LOG_CONSOLE
299 bool "Allow log output to the console"
300 default y
301 help
302 Enables a log driver which writes log records to the console.
303 Generally the console is the serial port or LCD display. Only the
304 log message is shown - other details like level, category, file and
305 line number are omitted.
306
307config LOGF_FILE
308 bool "Show source file name in log messages by default"
309 help
310 Show the source file name in log messages by default. This value
311 can be overridden using the 'log format' command.
312
313config LOGF_LINE
314 bool "Show source line number in log messages by default"
315 help
316 Show the source line number in log messages by default. This value
317 can be overridden using the 'log format' command.
318
319config LOGF_FUNC
320 bool "Show function name in log messages by default"
321 help
322 Show the function name in log messages by default. This value can
323 be overridden using the 'log format' command.
324
325config LOGF_FUNC_PAD
326 int "Number of characters to use for function"
327 default 20
328 help
329 Sets the field width to use when showing the function. Set this to
330 a larger value if you have lots of long function names, and want
331 things to line up.
332
333config LOG_SYSLOG
334 bool "Log output to syslog server"
335 depends on NET
336 help
337 Enables a log driver which broadcasts log records via UDP port 514
338 to syslog servers.
339
340config SPL_LOG
341 bool "Enable logging support in SPL"
342 depends on LOG
343 help
344 This enables support for logging of status and debug messages. These
345 can be displayed on the console, recorded in a memory buffer, or
346 discarded if not needed. Logging supports various categories and
347 levels of severity.
348
349if SPL_LOG
350
351config SPL_LOG_MAX_LEVEL
352 int "Maximum log level to record in SPL"
353 depends on SPL_LOG
354 default 3
355 range 0 9
356 help
357 This selects the maximum log level that will be recorded. Any value
358 higher than this will be ignored. If possible log statements below
359 this level will be discarded at build time. Levels:
360
361 0 - emergency
362 1 - alert
363 2 - critical
364 3 - error
365 4 - warning
366 5 - note
367 6 - info
368 7 - debug
369 8 - debug content
370 9 - debug hardware I/O
371
372config SPL_LOG_CONSOLE
373 bool "Allow log output to the console in SPL"
374 default y
375 help
376 Enables a log driver which writes log records to the console.
377 Generally the console is the serial port or LCD display. Only the
378 log message is shown - other details like level, category, file and
379 line number are omitted.
380
381endif
382
383config TPL_LOG
384 bool "Enable logging support in TPL"
385 depends on LOG
386 help
387 This enables support for logging of status and debug messages. These
388 can be displayed on the console, recorded in a memory buffer, or
389 discarded if not needed. Logging supports various categories and
390 levels of severity.
391
392if TPL_LOG
393
394config TPL_LOG_MAX_LEVEL
395 int "Maximum log level to record in TPL"
396 depends on TPL_LOG
397 default 3
398 range 0 9
399 help
400 This selects the maximum log level that will be recorded. Any value
401 higher than this will be ignored. If possible log statements below
402 this level will be discarded at build time. Levels:
403
404 0 - emergency
405 1 - alert
406 2 - critical
407 3 - error
408 4 - warning
409 5 - note
410 6 - info
411 7 - debug
412 8 - debug content
413 9 - debug hardware I/O
414
415config TPL_LOG_CONSOLE
416 bool "Allow log output to the console in TPL"
417 default y
418 help
419 Enables a log driver which writes log records to the console.
420 Generally the console is the serial port or LCD display. Only the
421 log message is shown - other details like level, category, file and
422 line number are omitted.
423
424endif
425
426config LOG_ERROR_RETURN
427 bool "Log all functions which return an error"
428 help
429 When an error is returned in U-Boot it is sometimes difficult to
430 figure out the root cause. For example, reading from SPI flash may
431 fail due to a problem in the SPI controller or due to the flash part
432 not returning the expected information. This option changes
433 log_ret() to log any errors it sees. With this option disabled,
434 log_ret() is a nop.
435
436 You can add log_ret() to all functions which return an error code.
437
438config LOG_TEST
439 bool "Provide a test for logging"
440 depends on UNIT_TEST
441 default y if SANDBOX
442 help
443 This enables a 'log test' command to test logging. It is normally
444 executed from a pytest and simply outputs logging information
445 in various different ways to test that the logging system works
446 correctly with various settings.
447
448endif
449
450endmenu
451
452menu "Init options"
453
454config BOARD_TYPES
455 bool "Call get_board_type() to get and display the board type"
456 help
457 If this option is enabled, checkboard() will call get_board_type()
458 to get a string containing the board type and this will be
459 displayed immediately after the model is shown on the console
460 early in boot.
461
462config DISPLAY_CPUINFO
463 bool "Display information about the CPU during start up"
464 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
465 help
466 Display information about the CPU that U-Boot is running on
467 when U-Boot starts up. The function print_cpuinfo() is called
468 to do this.
469
470config DISPLAY_BOARDINFO
471 bool "Display information about the board during early start up"
472 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
473 help
474 Display information about the board that U-Boot is running on
475 when U-Boot starts up. The board function checkboard() is called
476 to do this.
477
478config DISPLAY_BOARDINFO_LATE
479 bool "Display information about the board during late start up"
480 help
481 Display information about the board that U-Boot is running on after
482 the relocation phase. The board function checkboard() is called to do
483 this.
484
485menu "Start-up hooks"
486
487config ARCH_EARLY_INIT_R
488 bool "Call arch-specific init soon after relocation"
489 help
490 With this option U-Boot will call arch_early_init_r() soon after
491 relocation. Driver model is running by this point, and the cache
492 is on. Note that board_early_init_r() is called first, if
493 enabled. This can be used to set up architecture-specific devices.
494
495config ARCH_MISC_INIT
496 bool "Call arch-specific init after relocation, when console is ready"
497 help
498 With this option U-Boot will call arch_misc_init() after
499 relocation to allow miscellaneous arch-dependent initialisation
500 to be performed. This function should be defined by the board
501 and will be called after the console is set up, after relocation.
502
503config BOARD_EARLY_INIT_F
504 bool "Call board-specific init before relocation"
505 help
506 Some boards need to perform initialisation as soon as possible
507 after boot. With this option, U-Boot calls board_early_init_f()
508 after driver model is ready in the pre-relocation init sequence.
509 Note that the normal serial console is not yet set up, but the
510 debug UART will be available if enabled.
511
512config BOARD_EARLY_INIT_R
513 bool "Call board-specific init after relocation"
514 help
515 Some boards need to perform initialisation as directly after
516 relocation. With this option, U-Boot calls board_early_init_r()
517 in the post-relocation init sequence.
518
519config BOARD_LATE_INIT
520 bool "Execute Board late init"
521 help
522 Sometimes board require some initialization code that might
523 require once the actual init done, example saving board specific env,
524 boot-modes etc. which eventually done at late.
525
526 So this config enable the late init code with the help of board_late_init
527 function which should defined on respective boards.
528
529config LAST_STAGE_INIT
530 bool "Call board-specific as last setup step"
531 help
532 Some boards need to perform initialisation immediately before control
533 is passed to the command-line interpreter (e.g. for initializations
534 that depend on later phases in the init sequence). With this option,
535 U-Boot calls last_stage_init() before the command-line interpreter is
536 started.
537
538config MISC_INIT_F
539 bool "Execute pre-relocation misc init"
540 help
541 Enabling this option calls the 'misc_init_f' function in the init
542 sequence just before DRAM is inited.
543
544config MISC_INIT_R
545 bool "Execute Misc Init"
546 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
547 default y if ARCH_OMAP2PLUS && !AM33XX
548 help
549 Enabling this option calls 'misc_init_r' function
550
551config PCI_INIT_R
552 bool "Enumerate PCI buses during init"
553 depends on PCI
554 help
555 With this option U-Boot will call pci_init() soon after relocation,
556 which will enumerate PCI buses. This is needed, for instance, in the
557 case of DM PCI-based Ethernet devices, which will not be detected
558 without having the enumeration performed earlier.
559
560endmenu
561
562endmenu
563
564menu "Security support"
565
566config HASH
567 bool
568 help
569 This provides a way to hash data in memory using various supported
570 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
571 and the algorithms it supports are defined in common/hash.c. See
572 also CMD_HASH for command-line access.
573
574config AVB_VERIFY
575 bool "Build Android Verified Boot operations"
576 depends on LIBAVB
577 depends on MMC
578 depends on PARTITION_UUIDS
579 help
580 This option enables compilation of bootloader-dependent operations,
581 used by Android Verified Boot 2.0 library (libavb). Includes:
582 * Helpers to process strings in order to build OS bootargs.
583 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
584 * Helpers to alloc/init/free avb ops.
585
586if AVB_VERIFY
587
588config AVB_BUF_ADDR
589 hex "Define AVB buffer address"
590 default FASTBOOT_BUF_ADDR
591 help
592 AVB requires a buffer for memory transactions. This variable defines the
593 buffer address.
594
595config AVB_BUF_SIZE
596 hex "Define AVB buffer SIZE"
597 default FASTBOOT_BUF_SIZE
598 help
599 AVB requires a buffer for memory transactions. This variable defines the
600 buffer size.
601
602endif
603
604config SCP03
605 bool "Build SCP03 - Secure Channel Protocol O3 - controls"
606 depends on OPTEE || SANDBOX
607 depends on TEE
608 help
609 This option allows U-Boot to enable and or provision SCP03 on an OPTEE
610 controlled Secured Element.
611
612config SPL_HASH
613 bool
614 help
615 This provides a way to hash data in memory using various supported
616 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
617 and the algorithms it supports are defined in common/hash.c. See
618 also CMD_HASH for command-line access.
619
620config TPL_HASH
621 bool
622 help
623 This provides a way to hash data in memory using various supported
624 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
625 and the algorithms it supports are defined in common/hash.c. See
626 also CMD_HASH for command-line access.
627
628config STACKPROTECTOR
629 bool "Stack Protector buffer overflow detection"
630 default n
631 help
632 Enable stack smash detection through compiler's stack-protector
633 canary logic
634
635config SPL_STACKPROTECTOR
636 bool "Stack Protector buffer overflow detection for SPL"
637 depends on STACKPROTECTOR && SPL
638 default n
639
640config TPL_STACKPROTECTOR
641 bool "Stack Protector buffer overflow detection for TPL"
642 depends on STACKPROTECTOR && TPL
643 default n
644
645endmenu
646
647menu "Update support"
648
649config UPDATE_COMMON
650 bool
651 default n
652 select DFU_WRITE_ALT
653
654config UPDATE_TFTP
655 bool "Auto-update using fitImage via TFTP"
656 depends on FIT
657 select UPDATE_COMMON
658 help
659 This option allows performing update of NOR with data in fitImage
660 sent via TFTP boot.
661
662config UPDATE_TFTP_CNT_MAX
663 int "The number of connection retries during auto-update"
664 default 0
665 depends on UPDATE_TFTP
666
667config UPDATE_TFTP_MSEC_MAX
668 int "Delay in mSec to wait for the TFTP server during auto-update"
669 default 100
670 depends on UPDATE_TFTP
671
672config UPDATE_FIT
673 bool "Firmware update using fitImage"
674 depends on FIT
675 depends on DFU
676 select UPDATE_COMMON
677 help
678 This option allows performing update of DFU-capable storage with
679 data in fitImage.
680
681config ANDROID_AB
682 bool "Android A/B updates"
683 default n
684 help
685 If enabled, adds support for the new Android A/B update model. This
686 allows the bootloader to select which slot to boot from based on the
687 information provided by userspace via the Android boot_ctrl HAL. This
688 allows a bootloader to try a new version of the system but roll back
689 to previous version if the new one didn't boot all the way.
690
691endmenu
692
693menu "Blob list"
694
695config BLOBLIST
696 bool "Support for a bloblist"
697 help
698 This enables support for a bloblist in U-Boot, which can be passed
699 from TPL to SPL to U-Boot proper (and potentially to Linux). The
700 blob list supports multiple binary blobs of data, each with a tag,
701 so that different U-Boot components can store data which can survive
702 through to the next stage of the boot.
703
704config SPL_BLOBLIST
705 bool "Support for a bloblist in SPL"
706 depends on BLOBLIST
707 default y if SPL
708 help
709 This enables a bloblist in SPL. If this is the first part of U-Boot
710 to run, then the bloblist is set up in SPL and passed to U-Boot
711 proper. If TPL also has a bloblist, then SPL uses the one from there.
712
713config TPL_BLOBLIST
714 bool "Support for a bloblist in TPL"
715 depends on BLOBLIST
716 default y if TPL
717 help
718 This enables a bloblist in TPL. The bloblist is set up in TPL and
719 passed to SPL and U-Boot proper.
720
721config BLOBLIST_SIZE
722 hex "Size of bloblist"
723 depends on BLOBLIST
724 default 0x400
725 help
726 Sets the size of the bloblist in bytes. This must include all
727 overhead (alignment, bloblist header, record header). The bloblist
728 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
729 proper), and this sane bloblist is used for subsequent stages.
730
731config BLOBLIST_ADDR
732 hex "Address of bloblist"
733 depends on BLOBLIST
734 default 0xc000 if SANDBOX
735 help
736 Sets the address of the bloblist, set up by the first part of U-Boot
737 which runs. Subsequent U-Boot stages typically use the same address.
738
739config BLOBLIST_SIZE_RELOC
740 hex "Size of bloblist after relocation"
741 depends on BLOBLIST
742 default BLOBLIST_SIZE
743 help
744 Sets the size of the bloblist in bytes after relocation. Since U-Boot
745 has a lot more memory available then, it is possible to use a larger
746 size than the one set up by SPL. This bloblist is set up during the
747 relocation process.
748
749endmenu
750
751source "common/spl/Kconfig"
752
753config IMAGE_SIGN_INFO
754 bool
755 select SHA1
756 select SHA256
757 help
758 Enable image_sign_info helper functions.
759
760if IMAGE_SIGN_INFO
761
762config SPL_IMAGE_SIGN_INFO
763 bool
764 select SHA1
765 select SHA256
766 help
767 Enable image_sign_info helper functions in SPL.
768
769endif
770