1 source "common/Kconfig.boot"
8 This is the library functionality to provide a text-based menu of
9 choices for the user to make choices with.
12 bool "Console recording"
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()
20 config CONSOLE_RECORD_OUT_SIZE
21 hex "Output buffer size"
22 depends on CONSOLE_RECORD
23 default 0x400 if CONSOLE_RECORD
25 Set the size of the console output buffer. When this fills up, no
26 more data will be recorded until some is removed. The buffer is
27 allocated immediately after the malloc() region is ready.
29 config CONSOLE_RECORD_IN_SIZE
30 hex "Input buffer size"
31 depends on CONSOLE_RECORD
32 default 0x100 if CONSOLE_RECORD
34 Set the size of the console input buffer. When this contains data,
35 tstc() and getc() will use this in preference to real device input.
36 The buffer is allocated immediately after the malloc() region is
39 config DISABLE_CONSOLE
40 bool "Add functionality to disable console completely"
42 Disable console (in & out).
45 string "Board specific string to be added to uboot version string"
47 This options adds the board specific name to u-boot version.
54 All Messages with a loglevel smaller than the console loglevel will
55 be compiled in. The loglevels are defined as follows:
66 9 - debug hardware I/O
77 bool "Support a silent console"
79 This option allows the console to be silenced, meaning that no
80 output will appear on the console devices. This is controlled by
81 setting the environment variable 'silent' to a non-empty value.
82 Note this also silences the console when booting Linux.
84 When the console is set up, the variable is checked, and the
85 GD_FLG_SILENT flag is set. Changing the environment variable later
88 config SILENT_U_BOOT_ONLY
89 bool "Only silence the U-Boot console"
90 depends on SILENT_CONSOLE
92 Normally when the U-Boot console is silenced, Linux's console is
93 also silenced (assuming the board boots into Linux). This option
94 allows the linux console to operate normally, even if U-Boot's
97 config SILENT_CONSOLE_UPDATE_ON_SET
98 bool "Changes to the 'silent' environment variable update immediately"
99 depends on SILENT_CONSOLE
100 default y if SILENT_CONSOLE
102 When the 'silent' environment variable is changed, update the
103 console silence flag immediately. This allows 'setenv' to be used
104 to silence or un-silence the console.
106 The effect is that any change to the variable will affect the
109 config SILENT_CONSOLE_UPDATE_ON_RELOC
110 bool "Allow flags to take effect on relocation"
111 depends on SILENT_CONSOLE
113 In some cases the environment is not available until relocation
114 (e.g. NAND). This option makes the value of the 'silent'
115 environment variable take effect at relocation.
117 config PRE_CONSOLE_BUFFER
118 bool "Buffer characters before the console is available"
120 Prior to the console being initialised (i.e. serial UART
121 initialised etc) all console output is silently discarded.
122 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
123 buffer any console messages prior to the console being
124 initialised to a buffer. The buffer is a circular buffer, so
125 if it overflows, earlier output is discarded.
127 Note that this is not currently supported in SPL. It would be
128 useful to be able to share the pre-console buffer with SPL.
130 config PRE_CON_BUF_SZ
131 int "Sets the size of the pre-console buffer"
132 depends on PRE_CONSOLE_BUFFER
135 The size of the pre-console buffer affects how much console output
136 can be held before it overflows and starts discarding earlier
137 output. Normally there is very little output at this early stage,
138 unless debugging is enabled, so allow enough for ~10 lines of
141 This is a useful feature if you are using a video console and
142 want to see the full boot output on the console. Without this
143 option only the post-relocation output will be displayed.
145 config PRE_CON_BUF_ADDR
146 hex "Address of the pre-console buffer"
147 depends on PRE_CONSOLE_BUFFER
148 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
149 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
150 default 0x0f000000 if ROCKCHIP_RK3288
151 default 0x0f200000 if ROCKCHIP_RK3399
153 This sets the start address of the pre-console buffer. This must
154 be in available memory and is accessed before relocation and
155 possibly before DRAM is set up. Therefore choose an address
158 We should consider removing this option and allocating the memory
159 in board_init_f_init_reserve() instead.
162 bool "Enable console multiplexing"
163 default y if DM_VIDEO || VIDEO || LCD
165 This allows multiple devices to be used for each console 'file'.
166 For example, stdout can be set to go to serial and video.
167 Similarly, stdin can be set to come from serial and keyboard.
168 Input can be provided from either source. Console multiplexing
169 adds a small amount of size to U-Boot. Changes to the environment
170 variables stdout, stdin and stderr will take effect immediately.
172 config SYS_CONSOLE_IS_IN_ENV
173 bool "Select console devices from the environment"
174 default y if CONSOLE_MUX
176 This allows multiple input/output devices to be set at boot time.
177 For example, if stdout is set to "serial,video" then output will
178 be sent to both the serial and video devices on boot. The
179 environment variables can be updated after boot to change the
180 input/output devices.
182 config SYS_CONSOLE_OVERWRITE_ROUTINE
183 bool "Allow board control over console overwriting"
185 If this is enabled, and the board-specific function
186 overwrite_console() returns 1, the stdin, stderr and stdout are
187 switched to the serial port, else the settings in the environment
188 are used. If this is not enabled, the console will not be switched
191 config SYS_CONSOLE_ENV_OVERWRITE
192 bool "Update environment variables during console init"
194 The console environment variables (stdout, stdin, stderr) can be
195 used to determine the correct console devices on start-up. This
196 option writes the console devices to these variables on console
197 start-up (after relocation). This causes the environment to be
198 updated to match the console devices actually chosen.
200 config SYS_CONSOLE_INFO_QUIET
201 bool "Don't display the console devices on boot"
203 Normally U-Boot displays the current settings for stdout, stdin
204 and stderr on boot when the post-relocation console is set up.
205 Enable this option to suppress this output. It can be obtained by
206 calling stdio_print_current_devices() from board code.
208 config SYS_STDIO_DEREGISTER
209 bool "Allow deregistering stdio devices"
210 default y if USB_KEYBOARD
212 Generally there is no need to deregister stdio devices since they
213 are never deactivated. But if a stdio device is used which can be
214 removed (for example a USB keyboard) then this option can be
215 enabled to ensure this is handled correctly.
217 config SPL_SYS_STDIO_DEREGISTER
218 bool "Allow deregistering stdio devices in SPL"
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. This is very rarely
226 config SYS_DEVICE_NULLDEV
227 bool "Enable a null device for stdio"
228 default y if SPLASH_SCREEN || SYS_STDIO_DEREGISTER
230 Enable creation of a "nulldev" stdio device. This allows silent
231 operation of the console by setting stdout to "nulldev". Enable
232 this to use a serial console under board control.
239 bool "Enable logging support"
242 This enables support for logging of status and debug messages. These
243 can be displayed on the console, recorded in a memory buffer, or
244 discarded if not needed. Logging supports various categories and
250 int "Maximum log level to record"
254 This selects the maximum log level that will be recorded. Any value
255 higher than this will be ignored. If possible log statements below
256 this level will be discarded at build time. Levels:
267 9 - debug hardware I/O
269 config LOG_DEFAULT_LEVEL
270 int "Default logging level to display"
271 default LOG_MAX_LEVEL
272 range 0 LOG_MAX_LEVEL
274 This is the default logging level set when U-Boot starts. It can
275 be adjusted later using the 'log level' command. Note that setting
276 this to a value above LOG_MAX_LEVEL will be ineffective, since the
277 higher levels are not compiled in to U-Boot.
288 9 - debug hardware I/O
291 bool "Allow log output to the console"
294 Enables a log driver which writes log records to the console.
295 Generally the console is the serial port or LCD display. Only the
296 log message is shown - other details like level, category, file and
297 line number are omitted.
300 bool "Show source file name in log messages by default"
302 Show the source file name in log messages by default. This value
303 can be overridden using the 'log format' command.
306 bool "Show source line number in log messages by default"
308 Show the source line number in log messages by default. This value
309 can be overridden using the 'log format' command.
312 bool "Show function name in log messages by default"
314 Show the function name in log messages by default. This value can
315 be overridden using the 'log format' command.
318 bool "Log output to syslog server"
321 Enables a log driver which broadcasts log records via UDP port 514
325 bool "Enable logging support in SPL"
328 This enables support for logging of status and debug messages. These
329 can be displayed on the console, recorded in a memory buffer, or
330 discarded if not needed. Logging supports various categories and
335 config SPL_LOG_MAX_LEVEL
336 int "Maximum log level to record in SPL"
341 This selects the maximum log level that will be recorded. Any value
342 higher than this will be ignored. If possible log statements below
343 this level will be discarded at build time. Levels:
354 9 - debug hardware I/O
356 config SPL_LOG_CONSOLE
357 bool "Allow log output to the console in SPL"
360 Enables a log driver which writes log records to the console.
361 Generally the console is the serial port or LCD display. Only the
362 log message is shown - other details like level, category, file and
363 line number are omitted.
368 bool "Enable logging support in TPL"
371 This enables support for logging of status and debug messages. These
372 can be displayed on the console, recorded in a memory buffer, or
373 discarded if not needed. Logging supports various categories and
378 config TPL_LOG_MAX_LEVEL
379 int "Maximum log level to record in TPL"
384 This selects the maximum log level that will be recorded. Any value
385 higher than this will be ignored. If possible log statements below
386 this level will be discarded at build time. Levels:
397 9 - debug hardware I/O
399 config TPL_LOG_CONSOLE
400 bool "Allow log output to the console in TPL"
403 Enables a log driver which writes log records to the console.
404 Generally the console is the serial port or LCD display. Only the
405 log message is shown - other details like level, category, file and
406 line number are omitted.
410 config LOG_ERROR_RETURN
411 bool "Log all functions which return an error"
413 When an error is returned in U-Boot it is sometimes difficult to
414 figure out the root cause. For example, reading from SPI flash may
415 fail due to a problem in the SPI controller or due to the flash part
416 not returning the expected information. This option changes
417 log_ret() to log any errors it sees. With this option disabled,
420 You can add log_ret() to all functions which return an error code.
423 bool "Provide a test for logging"
427 This enables a 'log test' command to test logging. It is normally
428 executed from a pytest and simply outputs logging information
429 in various different ways to test that the logging system works
430 correctly with various settings.
438 config DISPLAY_CPUINFO
439 bool "Display information about the CPU during start up"
440 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
442 Display information about the CPU that U-Boot is running on
443 when U-Boot starts up. The function print_cpuinfo() is called
446 config DISPLAY_BOARDINFO
447 bool "Display information about the board during early start up"
448 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
450 Display information about the board that U-Boot is running on
451 when U-Boot starts up. The board function checkboard() is called
454 config DISPLAY_BOARDINFO_LATE
455 bool "Display information about the board during late start up"
457 Display information about the board that U-Boot is running on after
458 the relocation phase. The board function checkboard() is called to do
461 menu "Start-up hooks"
463 config ARCH_EARLY_INIT_R
464 bool "Call arch-specific init soon after relocation"
466 With this option U-Boot will call arch_early_init_r() soon after
467 relocation. Driver model is running by this point, and the cache
468 is on. Note that board_early_init_r() is called first, if
469 enabled. This can be used to set up architecture-specific devices.
471 config ARCH_MISC_INIT
472 bool "Call arch-specific init after relocation, when console is ready"
474 With this option U-Boot will call arch_misc_init() after
475 relocation to allow miscellaneous arch-dependent initialisation
476 to be performed. This function should be defined by the board
477 and will be called after the console is set up, after relocation.
479 config BOARD_EARLY_INIT_F
480 bool "Call board-specific init before relocation"
482 Some boards need to perform initialisation as soon as possible
483 after boot. With this option, U-Boot calls board_early_init_f()
484 after driver model is ready in the pre-relocation init sequence.
485 Note that the normal serial console is not yet set up, but the
486 debug UART will be available if enabled.
488 config BOARD_EARLY_INIT_R
489 bool "Call board-specific init after relocation"
491 Some boards need to perform initialisation as directly after
492 relocation. With this option, U-Boot calls board_early_init_r()
493 in the post-relocation init sequence.
495 config BOARD_LATE_INIT
496 bool "Execute Board late init"
498 Sometimes board require some initialization code that might
499 require once the actual init done, example saving board specific env,
500 boot-modes etc. which eventually done at late.
502 So this config enable the late init code with the help of board_late_init
503 function which should defined on respective boards.
505 config LAST_STAGE_INIT
506 bool "Call board-specific as last setup step"
508 Some boards need to perform initialisation immediately before control
509 is passed to the command-line interpreter (e.g. for initializations
510 that depend on later phases in the init sequence). With this option,
511 U-Boot calls last_stage_init() before the command-line interpreter is
515 bool "Execute Misc Init"
516 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
517 default y if ARCH_OMAP2PLUS && !AM33XX
519 Enabling this option calls 'misc_init_r' function
522 bool "Enumerate PCI buses during init"
526 With this option U-Boot will call pci_init() soon after relocation,
527 which will enumerate PCI buses. This is needed, for instance, in the
528 case of DM PCI-based Ethernet devices, which will not be detected
529 without having the enumeration performed earlier.
533 endmenu # Init options
536 bool "Include bounce buffer API"
538 Some peripherals support DMA from a subset of physically
539 addressable memory only. To support such peripherals, the
540 bounce buffer API uses a temporary buffer: it copies data
541 to/from DMA regions while managing cache operations.
543 A second possible use of bounce buffers is their ability to
544 provide aligned buffers for DMA operations.
547 bool "Call get_board_type() to get and display the board type"
549 If this option is enabled, checkboard() will call get_board_type()
550 to get a string containing the board type and this will be
551 displayed immediately after the model is shown on the console
554 menu "Security support"
557 bool # "Support hashing API (SHA1, SHA256, etc.)"
559 This provides a way to hash data in memory using various supported
560 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
561 and the algorithms it supports are defined in common/hash.c. See
562 also CMD_HASH for command-line access.
565 bool "Build Android Verified Boot operations"
567 depends on PARTITION_UUIDS
569 This option enables compilation of bootloader-dependent operations,
570 used by Android Verified Boot 2.0 library (libavb). Includes:
571 * Helpers to process strings in order to build OS bootargs.
572 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
573 * Helpers to alloc/init/free avb ops.
578 hex "Define AVB buffer address"
579 default FASTBOOT_BUF_ADDR
581 AVB requires a buffer for memory transactions. This variable defines the
585 hex "Define AVB buffer SIZE"
586 default FASTBOOT_BUF_SIZE
588 AVB requires a buffer for memory transactions. This variable defines the
594 bool # "Support hashing API (SHA1, SHA256, etc.)"
596 This provides a way to hash data in memory using various supported
597 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
598 and the algorithms it supports are defined in common/hash.c. See
599 also CMD_HASH for command-line access.
602 bool # "Support hashing API (SHA1, SHA256, etc.)"
604 This provides a way to hash data in memory using various supported
605 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
606 and the algorithms it supports are defined in common/hash.c. See
607 also CMD_HASH for command-line access.
611 menu "Update support"
614 bool "Auto-update using fitImage via TFTP"
617 This option allows performing update of NOR with data in fitImage
620 config UPDATE_TFTP_CNT_MAX
621 int "The number of connection retries during auto-update"
623 depends on UPDATE_TFTP
625 config UPDATE_TFTP_MSEC_MAX
626 int "Delay in mSec to wait for the TFTP server during auto-update"
628 depends on UPDATE_TFTP
631 bool "Android A/B updates"
634 If enabled, adds support for the new Android A/B update model. This
635 allows the bootloader to select which slot to boot from based on the
636 information provided by userspace via the Android boot_ctrl HAL. This
637 allows a bootloader to try a new version of the system but roll back
638 to previous version if the new one didn't boot all the way.
645 bool "Support for a bloblist"
647 This enables support for a bloblist in U-Boot, which can be passed
648 from TPL to SPL to U-Boot proper (and potentially to Linux). The
649 blob list supports multiple binary blobs of data, each with a tag,
650 so that different U-Boot components can store data which can survive
651 through to the next stage of the boot.
654 bool "Support for a bloblist in SPL"
658 This enables a bloblist in SPL. If this is the first part of U-Boot
659 to run, then the bloblist is set up in SPL and passed to U-Boot
660 proper. If TPL also has a bloblist, then SPL uses the one from there.
663 bool "Support for a bloblist in TPL"
667 This enables a bloblist in TPL. The bloblist is set up in TPL and
668 passed to SPL and U-Boot proper.
671 hex "Size of bloblist"
675 Sets the size of the bloblist in bytes. This must include all
676 overhead (alignment, bloblist header, record header). The bloblist
677 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
678 proper), and this sane bloblist is used for subsequent stages.
681 hex "Address of bloblist"
683 default 0xe000 if SANDBOX
685 Sets the address of the bloblist, set up by the first part of U-Boot
686 which runs. Subsequent U-Boot stages typically use the same address.
690 source "common/spl/Kconfig"
692 config IMAGE_SIGN_INFO
697 Enable image_sign_info helper functions.
701 config SPL_IMAGE_SIGN_INFO
706 Enable image_sign_info helper functions in SPL.