12 config SPL_DFU_NO_RESET
17 depends on SUPPORT_SPL
20 If you want to build SPL as well as the normal image, say Y.
23 bool "Support SPL based upon the common SPL framework"
27 Enable the SPL framework under common/spl/. This framework
28 supports MMC, NAND and YMODEM and other methods loading of U-Boot
29 and the Linux Kernel. If unsure, say Y.
31 config SPL_FRAMEWORK_BOARD_INIT_F
32 bool "Define a generic function board_init_f"
33 depends on SPL_FRAMEWORK
35 Define a generic function board_init_f that:
36 - initialize the spl (spl_early_init)
37 - initialize the serial (preloader_console_init)
38 Unless you want to provide your own board_init_f, you should say Y.
41 hex "Maximum size of SPL image"
43 default 0x11000 if ARCH_MX6 && !MX6_OCRAM_256KB
44 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
47 Specifies the maximum length of the U-Boot SPL image.
48 If this value is zero, it is ignored.
50 config SPL_SIZE_LIMIT_SUBTRACT_GD
51 bool "SPL image size check: provide space for global data"
52 depends on SPL_SIZE_LIMIT > 0
54 If enabled, aligned size of global data is reserved in
55 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
56 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
57 pre-reloc global data is put into this SRAM, too.
59 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
60 bool "SPL image size check: provide space for malloc() pool before relocation"
61 depends on SPL_SIZE_LIMIT > 0
63 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
64 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
65 describes the size of SRAM available for SPL when pre-reloc malloc
66 pool is put into this SRAM, too.
68 config SPL_SIZE_LIMIT_PROVIDE_STACK
69 hex "SPL image size check: provide stack space before relocation"
70 depends on SPL_SIZE_LIMIT > 0
73 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
74 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
75 of SRAM available for SPL when the stack required before reolcation
79 hex "Maximum size of the SPL image, excluding BSS"
80 default 0x30000 if ARCH_MX6 && MX6_OCRAM_256KB
81 default 0x1b000 if AM33XX && !TI_SECURE_DEVICE
82 default 0x10000 if ARCH_MX6 && !MX6_OCRAM_256KB
83 default 0x7fa0 if SUNXI_SRAM_ADDRESS = 0x10000
84 default 0x7fa0 if SUNXI_SRAM_ADDRESS = 0x20000 && !MACH_SUN50I_H616
85 default 0x7000 if RCAR_GEN3
86 default 0x5fa0 if SUNXI_SRAM_ADDRESS = 0x0
89 Maximum size of the SPL image (text, data, rodata, and linker lists
90 sections), BSS excluded. When defined, the linker checks that the
91 actual size does not exceed it.
94 hex "Offset to which the SPL should be padded before appending the SPL payload"
95 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
96 default 0x11000 if ARCH_MX7 || (ARCH_MX6 && !MX6_OCRAM_256KB)
97 default 0x10000 if ARCH_KEYSTONE
98 default 0x8000 if ARCH_SUNXI && !MACH_SUN50I_H616
99 default TPL_MAX_SIZE if TPL_MAX_SIZE > SPL_MAX_SIZE
102 Image offset to which the SPL should be padded before appending the
103 SPL payload. By default, this is defined as CONFIG_SPL_MAX_SIZE, or 0 if
104 CONFIG_SPL_MAX_SIZE is undefined. CONFIG_SPL_PAD_TO must be either
105 0, meaning to append the SPL payload without any padding, or >=
109 prompt "Enforce SPL BSS limit"
110 depends on SPL && !PPC
111 default SPL_BSS_LIMIT
113 In some platforms we only want to enforce a limit on the size of the
114 BSS in memory. On other platforms we need to enforce a limit on the
115 whole of the memory allocation as we're strictly limited to a small
116 typically non-DRAM location. Finally, other platforms do not enforce
117 a memory limit within SPL.
119 config SPL_NO_BSS_LIMIT
120 bool "Do not enforce a build time limit on the size of the BSS"
123 bool "Enforce a limit on the size of the BSS only"
125 config SPL_FOOTPRINT_LIMIT
126 bool "Enforce a limit on the whole of memory allocated to SPL, BSS included"
130 config SPL_BSS_MAX_SIZE
131 hex "Maximum size in memory allocated to the SPL BSS"
132 depends on SPL_BSS_LIMIT
133 default 0x100000 if ARCH_MX6 || RISCV
134 default 0x80000 if ARCH_OMAP2PLUS || ARCH_SUNXI
136 When non-zero, the linker checks that the actual memory used by SPL
137 from __bss_start to __bss_end does not exceed it.
139 config SPL_MAX_FOOTPRINT
140 hex "Maximum size in memory allocated to the SPL, BSS included"
141 depends on SPL_FOOTPRINT_LIMIT
143 When non-zero, the linker checks that the actual memory used by SPL
144 from _start to __bss_end does not exceed it.
146 config SPL_SYS_STACK_F_CHECK_BYTE
150 Constant used to check the stack
152 config SPL_SYS_REPORT_STACK_F_USAGE
153 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
154 bool "Check and report stack usage in SPL before relocation"
156 If this option is enabled, the initial SPL stack is filled with 0xaa
157 very early, up to the size configured with
158 SPL_SIZE_LIMIT_PROVIDE_STACK.
159 Later when SPL is done using this initial stack and switches to a
160 stack in DRAM, the actually used size of this initial stack is
161 reported by examining the memory and searching for the lowest
162 occurrence of non 0xaa bytes.
163 This default implementation works for stacks growing down only.
165 config SPL_SHOW_ERRORS
166 bool "Show more information when something goes wrong"
168 This enabled more verbose error messages and checking when something
169 goes wrong in SPL. For example, it shows the error code when U-Boot
170 cannot be located. This can help to diagnose the problem and figure
171 out a fix, particularly during development.
173 This adds a small amount to SPL code size, perhaps 100 bytes.
175 config SPL_BINMAN_SYMBOLS
176 bool "Declare binman symbols in SPL"
177 depends on SPL_FRAMEWORK && BINMAN
180 This enables use of symbols in SPL which refer to U-Boot, enabling SPL
181 to obtain the location of U-Boot simply by calling spl_get_image_pos()
182 and spl_get_image_size().
184 For this to work, you must have a U-Boot image in the binman image, so
185 binman can update SPL with the location of it.
187 menu "PowerPC and LayerScape SPL Boot options"
190 bool "Load SPL from NAND flash"
191 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
194 bool "Load SPL from SD Card / eMMC"
195 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
198 bool "Load SPL from SPI flash"
199 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
202 bool "Create SPL in Freescale PBI format"
203 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
206 Create boot binary having SPL binary in PBI format concatenated with
211 menu "PowerPC SPL specific options"
212 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
214 config SPL_INIT_MINIMAL
215 bool "Arch init code will be built for a very small image"
217 config SPL_FLUSH_IMAGE
218 bool "Clean dcache and invalidate icache after loading the image"
220 config SPL_SKIP_RELOCATE
221 bool "Skip relocating SPL"
226 bool "Pass hand-off information from SPL to U-Boot proper"
227 depends on SPL && BLOBLIST
229 It is useful to be able to pass information from SPL to U-Boot
230 proper to preserve state that is known in SPL and is needed in U-Boot.
231 Enable this to locate the handoff information in U-Boot proper, early
232 in boot. It is available in gd->handoff. The state state is set up
233 in SPL (or TPL if that is being used).
238 bool "Pass hand-off information from SPL to U-Boot proper"
239 depends on HANDOFF && SPL_BLOBLIST
242 This option enables SPL to write handoff information. This can be
243 used to pass information like the size of SDRAM from SPL to U-Boot
244 proper. Also SPL can receive information from TPL in the same place
248 string "Linker script for the SPL stage"
249 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
251 The SPL stage will usually require a different linker-script
252 (as it runs from a different memory region) than the regular
253 U-Boot stage. Set this to the path of the linker-script to
258 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
259 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
260 default 0x20060 if SUN50I_GEN_H6
261 default 0x00060 if ARCH_SUNXI
262 default 0xfffc0000 if ARCH_ZYNQMP
265 The address in memory that SPL will be running from.
267 config SPL_BOARD_INIT
268 bool "Call board-specific initialization in SPL"
270 If this option is enabled, U-Boot will call the function
271 spl_board_init() from board_init_r(). This function should be
272 provided by the board.
274 config VPL_BOARD_INIT
275 bool "Call board-specific initialization in VPL"
277 If this option is enabled, U-Boot will call the function
278 spl_board_init() from board_init_r(). This function should be
279 provided by the board.
281 config SPL_BOOTROM_SUPPORT
282 bool "Support returning to the BOOTROM"
284 Some platforms (e.g. the Rockchip RK3368) provide support in their
285 ROM for loading the next boot-stage after performing basic setup
288 Enable this option, to return to the BOOTROM through the
289 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
290 boot device list, if not implemented for a given board)
292 config SPL_BOOTCOUNT_LIMIT
293 bool "Support bootcount in SPL"
294 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
296 On some boards, which use 'falcon' mode, it is necessary to check
297 and increment the number of boot attempts. Such boards do not
298 use proper U-Boot for normal boot flow and hence needs those
299 adjustments to be done in the SPL.
301 config SPL_RAW_IMAGE_SUPPORT
302 bool "Support SPL loading and booting of RAW images"
303 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
305 depends on !TI_SECURE_DEVICE
307 SPL will support loading and booting a RAW image when this option
308 is y. If this is not set, SPL will move on to other available
309 boot media to find a suitable image.
311 config SPL_LEGACY_IMAGE_FORMAT
312 bool "Support SPL loading and booting of Legacy images"
313 default y if !SPL_LOAD_FIT
314 depends on !TI_SECURE_DEVICE
316 SPL will support loading and booting Legacy images when this option
317 is y. If this is not set, SPL will move on to other available
318 boot media to find a suitable image.
320 config SPL_LEGACY_IMAGE_CRC_CHECK
321 bool "Check CRC of Legacy images"
322 depends on SPL_LEGACY_IMAGE_FORMAT
325 Enable this to check the CRC of Legacy images. While this increases
326 reliability, it affects both code size and boot duration.
327 If disabled, Legacy images are booted if the image magic and size
328 are correct, without further integrity checks.
330 config SPL_SYS_MALLOC_SIMPLE
332 prompt "Only use malloc_simple functions in the SPL"
334 Say Y here to only use the *_simple malloc functions from
335 malloc_simple.c, rather then using the versions from dlmalloc.c;
336 this will make the SPL binary smaller at the cost of more heap
337 usage as the *_simple malloc functions do not re-use free-ed mem.
339 config TPL_SYS_MALLOC_SIMPLE
341 prompt "Only use malloc_simple functions in the TPL"
344 Say Y here to only use the *_simple malloc functions from
345 malloc_simple.c, rather then using the versions from dlmalloc.c;
346 this will make the TPL binary smaller at the cost of more heap
347 usage as the *_simple malloc functions do not re-use free-ed mem.
350 bool "Enable SDRAM location for SPL stack"
352 SPL starts off execution in SRAM and thus typically has only a small
353 stack available. Since SPL sets up DRAM while in its board_init_f()
354 function, it is possible for the stack to move there before
355 board_init_r() is reached. This option enables a special SDRAM
356 location for the SPL stack. U-Boot SPL switches to this after
357 board_init_f() completes, and before board_init_r() starts.
359 config SPL_STACK_R_ADDR
360 depends on SPL_STACK_R
361 hex "SDRAM location for SPL stack"
362 default 0x82000000 if ARCH_OMAP2PLUS
364 Specify the address in SDRAM for the SPL stack. This will be set up
365 before board_init_r() is called.
367 config SPL_STACK_R_MALLOC_SIMPLE_LEN
368 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
369 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
372 Specify the amount of the stack to use as memory pool for
373 malloc_simple after switching the stack to DRAM. This may be set
374 to give board_init_r() a larger heap then the initial heap in
375 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
377 config SPL_SEPARATE_BSS
378 bool "BSS section is in a different memory region from text"
380 Some platforms need a large BSS region in SPL and can provide this
381 because RAM is already set up. In this case BSS can be moved to RAM.
382 This option should then be enabled so that the correct device tree
383 location is used. Normally we put the device tree at the end of BSS
384 but with this option enabled, it goes at _image_binary_end.
388 depends on SPL_OF_PLATDATA
389 # Bind cannot be supported because the udevice structs are in read-only
390 # memory so we cannot update the linked lists.
391 select SPL_OF_PLATDATA_NO_BIND
392 select SPL_OF_PLATDATA_RT
394 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
395 section of memory. This means that of-platdata must make a copy (in
396 writeable memory) of anything it wants to modify, such as
399 config TPL_SEPARATE_BSS
400 bool "BSS section is in a different memory region from text"
401 default y if SPL_SEPARATE_BSS
403 Some platforms need a large BSS region in TPL and can provide this
404 because RAM is already set up. In this case BSS can be moved to RAM.
405 This option should then be enabled so that the correct device tree
406 location is used. Normally we put the device tree at the end of BSS
407 but with this option enabled, it goes at _image_binary_end.
409 config SPL_BANNER_PRINT
410 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
413 If this option is enabled, SPL will print the banner with version
414 info. Disabling this option could be useful to reduce SPL boot time
415 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
417 config TPL_BANNER_PRINT
418 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
422 If this option is enabled, TPL will print the banner with version
423 info. Disabling this option could be useful to reduce TPL boot time
424 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
427 depends on ARM && !ARM64
428 bool "Allows initializing BSS early before entering board_init_f"
430 On some platform we have sufficient memory available early on to
431 allow setting up and using a basic BSS prior to entering
432 board_init_f. Activating this option will also de-activate the
433 clearing of BSS during the SPL relocation process, thus allowing
434 to carry state from board_init_f to board_init_r by way of BSS.
436 config SPL_DISPLAY_PRINT
437 bool "Display a board-specific message in SPL"
439 If this option is enabled, U-Boot will call the function
440 spl_display_print() immediately after displaying the SPL console
441 banner ("U-Boot SPL ..."). This function should be provided by
444 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
445 bool "MMC raw mode: by sector"
446 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
447 ARCH_MX6 || ARCH_MX7 || \
448 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
449 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
450 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
451 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
453 Use sector number for specifying U-Boot location on MMC/SD in
456 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
457 hex "Address on the MMC to load U-Boot from"
458 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
459 default 0x40 if ARCH_SUNXI
460 default 0x75 if ARCH_DAVINCI
461 default 0x8a if ARCH_MX6 || ARCH_MX7
462 default 0x100 if ARCH_UNIPHIER
463 default 0x0 if ARCH_MVEBU
464 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
465 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
466 OMAP54XX || AM33XX || AM43XX || ARCH_K3
467 default 0x4000 if ARCH_ROCKCHIP
468 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
470 Address on the MMC to load U-Boot from, when the MMC is being used
471 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
473 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
474 hex "U-Boot main hardware partition image offset"
475 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
476 default 0x10 if ARCH_SUNXI
479 On some platforms SPL location depends on hardware partition. The ROM
480 code skips the MBR sector when loading SPL from main hardware data
481 partition. This adds offset to the main U-Boot image. Set this symbol
482 to the number of skipped sectors.
484 If unsure, leave the default.
486 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
487 bool "MMC Raw mode: by partition"
489 Use a partition for loading U-Boot when using MMC/SD in raw mode.
491 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
492 hex "Partition to use to load U-Boot from"
493 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
496 Partition on the MMC to load U-Boot from when the MMC is being
499 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
500 bool "MMC raw mode: by partition type"
501 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
503 Use partition type for specifying U-Boot partition on MMC/SD in
504 raw mode. U-Boot will be loaded from the first partition of this
507 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
508 hex "Partition Type on the MMC to load U-Boot from"
509 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
511 Partition Type on the MMC to load U-Boot from, when the MMC is being
514 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
515 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
516 depends on SUPPORT_EMMC_BOOT
518 eMMC boot partition is normally configured by the bits of the EXT_CSD
519 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
520 cases it might be required in SPL to load the image from different
521 partition than the partition selected by EXT_CSC_PART_CONFIG register.
522 Enable this option if you intend to use an eMMC boot partition other
523 then selected via EXT_CSC_PART_CONFIG register and specify the custom
524 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
527 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
528 int "Number of the eMMC boot partition to use"
529 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
532 eMMC boot partition number to use when the eMMC in raw mode and
533 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
534 by user defined partition number.
538 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
539 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
541 Enable this to support CRC32 in uImages or FIT images within SPL.
542 This is a 32-bit checksum value that can be used to verify images.
543 For FIT images, this is the least secure type of checksum, suitable
544 for detected accidental image corruption. For secure applications you
545 should consider SHA1 or SHA256.
551 Enable this to support MD5 in FIT images within SPL. An MD5
552 checksum is a 128-bit hash value used to check that the image
553 contents have not been corrupted. Note that MD5 is not considered
554 secure as it is possible (with a brute-force attack) to adjust the
555 image while still retaining the same MD5 hash value. For secure
556 applications where images may be changed maliciously, you should
557 consider SHA256 or SHA384.
559 config SPL_FIT_IMAGE_TINY
560 bool "Remove functionality from SPL FIT loading to reduce size"
562 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
563 default y if ARCH_IMX8M
565 Enable this to reduce the size of the FIT image loading code
566 in SPL, if space for the SPL binary is very tight.
568 This skips the recording of each loaded payload
569 (i.e. loadable) into the FDT (modifying the loaded FDT to
570 ensure this information is available to the next image
574 bool "Support CACHE drivers"
576 Enable CACHE drivers in SPL. These drivers can keep data so that
577 future requests for that data can be served faster. Enable this option
578 to build the drivers in drivers/cache as part of an SPL build.
581 bool "Support CPU drivers"
583 Enable this to support CPU drivers in SPL. These drivers can set
584 up CPUs and provide information about them such as the model and
585 name. This can be useful in SPL since setting up the CPUs earlier
586 may improve boot performance. Enable this option to build the
587 drivers in drivers/cpu as part of an SPL build.
590 bool "Support crypto drivers"
592 Enable crypto drivers in SPL. These drivers can be used to
593 accelerate secure boot processing in secure applications. Enable
594 this option to build the drivers in drivers/crypto as part of an
598 bool "Support DMA drivers"
600 Enable DMA (direct-memory-access) drivers in SPL. These drivers
601 can be used to handle memory-to-peripheral data transfer without
602 the CPU moving the data. Enable this option to build the drivers
603 in drivers/dma as part of an SPL build.
605 config SPL_DRIVERS_MISC
606 bool "Support misc drivers"
608 Enable miscellaneous drivers in SPL. These drivers perform various
609 tasks that don't fall nicely into other categories, Enable this
610 option to build the drivers in drivers/misc as part of an SPL
611 build, for those that support building in SPL (not all drivers do).
613 config SPL_ENV_SUPPORT
614 bool "Support an environment"
616 Enable environment support in SPL. The U-Boot environment provides
617 a number of settings (essentially name/value pairs) which can
618 control many aspects of U-Boot's operation. Normally this is not
619 needed in SPL as it has a much simpler task with less
620 configuration. But some boards use this to support 'Falcon' boot
621 on EXT2 and FAT, where SPL boots directly into Linux without
622 starting U-Boot first. Enabling this option will make env_get()
623 and env_set() available in SPL.
626 bool "Support save environment"
627 depends on SPL_ENV_SUPPORT
628 select SPL_MMC_WRITE if ENV_IS_IN_MMC
630 Enable save environment support in SPL after setenv. By default
631 the saveenv option is not provided in SPL, but some boards need
632 this support in 'Falcon' boot, where SPL need to boot from
633 different images based on environment variable set by OS. For
634 example OS may set "reboot_image" environment variable to
635 "recovery" inorder to boot recovery image by SPL. The SPL read
636 "reboot_image" and act accordingly and change the reboot_image
637 to default mode using setenv and save the environment.
640 bool "Support Ethernet"
641 depends on SPL_ENV_SUPPORT
644 Enable access to the network subsystem and associated Ethernet
645 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
646 link rather than from an on-board peripheral. Environment support
647 is required since the network stack uses a number of environment
648 variables. See also SPL_NET.
651 bool "Support EXT filesystems"
653 Enable support for EXT2/3/4 filesystems with SPL. This permits
654 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
655 filesystem from within SPL. Support for the underlying block
656 device (e.g. MMC or USB) must be enabled separately.
658 config SPL_FS_SQUASHFS
659 bool "Support SquashFS filesystems"
662 Enable support for SquashFS filesystems with SPL. This permits
663 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
664 filesystem from within SPL. Support for the underlying block
665 device (e.g. MMC or USB) must be enabled separately.
668 bool "Support FAT filesystems"
671 Enable support for FAT and VFAT filesystems with SPL. This
672 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
673 filesystem from within SPL. Support for the underlying block
674 device (e.g. MMC or USB) must be enabled separately.
676 config SPL_FS_LOAD_PAYLOAD_NAME
677 string "File to load for U-Boot from the filesystem"
678 depends on SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS
679 default "tispl.bin" if SYS_K3_SPL_ATF
680 default "u-boot.itb" if SPL_LOAD_FIT
683 Filename to read to load U-Boot when reading from filesystem.
685 config SPL_FS_LOAD_KERNEL_NAME
686 string "File to load for the OS kernel from the filesystem"
687 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
690 Filename to read to load for the OS kernel when reading from the
693 config SPL_FS_LOAD_ARGS_NAME
694 string "File to load for the OS kernel argument parameters from the filesystem"
695 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
698 Filename to read to load for the OS kernel argument parameters from
702 bool "Support write for FAT filesystems"
704 Enable write support for FAT and VFAT filesystems with SPL.
705 Support for the underlying block device (e.g. MMC or USB) must be
711 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
712 provide software-configurable hardware which is typically used to
713 implement peripherals (such as UARTs, LCD displays, MMC) or
714 accelerate custom processing functions, such as image processing
715 or machine learning. Sometimes it is useful to program the FPGA
716 as early as possible during boot, and this option can enable that
720 bool "Support GPIO in SPL"
722 Enable support for GPIOs (General-purpose Input/Output) in SPL.
723 GPIOs allow U-Boot to read the state of an input line (high or
724 low) and set the state of an output line. This can be used to
725 drive LEDs, control power to various system parts and read user
726 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
727 for example. Enable this option to build the drivers in
728 drivers/gpio as part of an SPL build.
733 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
734 I2C works with a clock and data line which can be driven by a
735 one or more masters or slaves. It is a fairly complex bus but is
736 widely used as it only needs two lines for communication. Speeds of
737 400kbps are typical but up to 3.4Mbps is supported by some
738 hardware. I2C can be useful in SPL to configure power management
739 ICs (PMICs) before raising the CPU clock speed, for example.
740 Enable this option to build the drivers in drivers/i2c as part of
743 config SPL_LIBCOMMON_SUPPORT
744 bool "Support common libraries"
746 Enable support for common U-Boot libraries within SPL. These
747 libraries include common code to deal with U-Boot images,
748 environment and USB, for example. This option is enabled on many
749 boards. Enable this option to build the code in common/ as part of
752 config SPL_LIBDISK_SUPPORT
753 bool "Support disk partitions"
756 Enable support for disk partitions within SPL. 'Disk' is something
757 of a misnomer as it includes non-spinning media such as flash (as
758 used in MMC and USB sticks). Partitions provide a way for a disk
759 to be split up into separate regions, with a partition table placed
760 at the start or end which describes the location and size of each
761 'partition'. These partitions are typically uses as individual block
762 devices, typically with an EXT2 or FAT filesystem in each. This
763 option enables whatever partition support has been enabled in
764 U-Boot to also be used in SPL. It brings in the code in disk/.
766 config SPL_LIBGENERIC_SUPPORT
767 bool "Support generic libraries"
769 Enable support for generic U-Boot libraries within SPL. These
770 libraries include generic code to deal with device tree, hashing,
771 printf(), compression and the like. This option is enabled on many
772 boards. Enable this option to build the code in lib/ as part of an
775 config SPL_DM_MAILBOX
776 bool "Support Mailbox"
778 Enable support for Mailbox within SPL. This enable the inter
779 processor communication protocols tobe used within SPL. Enable
780 this option to build the drivers in drivers/mailbox as part of
786 select HAVE_BLOCK_DEVICE
788 Enable support for MMC (Multimedia Card) within SPL. This enables
789 the MMC protocol implementation and allows any enabled drivers to
790 be used within SPL. MMC can be used with or without disk partition
791 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
792 this option to build the drivers in drivers/mmc as part of an SPL
795 config SYS_MMCSD_FS_BOOT_PARTITION
796 int "MMC Boot Partition"
799 Partition on the MMC to load U-Boot from when the MMC is being
801 Use -1 as a special value to use the first bootable partition.
804 bool "Tiny MMC framework in SPL"
807 Enable MMC framework tinification support. This option is useful if
808 if your SPL is extremely size constrained. Heed the warning, enable
809 this option if and only if you know exactly what you are doing, if
810 you are reading this help text, you most likely have no idea :-)
812 The MMC framework is reduced to bare minimum to be useful. No malloc
813 support is needed for the MMC framework operation with this option
814 enabled. The framework supports exactly one MMC device and exactly
815 one MMC driver. The MMC driver can be adjusted to avoid any malloc
816 operations too, which can remove the need for malloc support in SPL
817 and thus further reduce footprint.
820 bool "MMC/SD/SDIO card support for write operations in SPL"
823 Enable write access to MMC and SD Cards in SPL
826 config SPL_MPC8XXX_INIT_DDR
827 bool "Support MPC8XXX DDR init"
829 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
830 random-access memory) on the MPC8XXX family within SPL. This
831 allows DRAM to be set up before loading U-Boot into that DRAM,
834 config SPL_MTD_SUPPORT
835 bool "Support MTD drivers"
837 Enable support for MTD (Memory Technology Device) within SPL. MTD
838 provides a block interface over raw NAND and can also be used with
839 SPI flash. This allows SPL to load U-Boot from supported MTD
840 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
841 to enable specific MTD drivers.
844 bool "Support new Mentor Graphics USB"
846 Enable support for Mentor Graphics USB in SPL. This is a new
847 driver used by some boards. Enable this option to build
848 the drivers in drivers/usb/musb-new as part of an SPL build. The
849 old drivers are in drivers/usb/musb.
851 config SPL_NAND_SUPPORT
852 bool "Support NAND flash"
854 Enable support for NAND (Negative AND) flash in SPL. NAND flash
855 can be used to allow SPL to load U-Boot from supported devices.
856 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
859 config SPL_NAND_RAW_ONLY
860 bool "Support to boot only raw u-boot.bin images"
861 depends on SPL_NAND_SUPPORT
863 Use this only if you need to save space.
865 config SPL_NAND_DRIVERS
866 bool "Use standard NAND driver"
868 SPL uses normal NAND drivers, not minimal drivers.
871 bool "Include standard ECC in SPL"
873 config SPL_NAND_SOFTECC
874 bool "Use software ECC in SPL"
875 depends on SPL_NAND_ECC
877 config SPL_NAND_SIMPLE
878 bool "Support simple NAND drivers in SPL"
880 Support for NAND boot using simple NAND drivers that
881 expose the cmd_ctrl() interface.
884 depends on SPL_NAND_DRIVERS
885 bool "Use Base NAND Driver"
887 Include nand_base.c in the SPL.
889 config SPL_NAND_IDENT
890 depends on SPL_NAND_BASE
891 bool "Use chip ID to identify NAND flash"
893 SPL uses the chip ID list to identify the NAND flash.
898 Enable support for loading payloads from UBI. See
899 README.ubispl for more info.
903 bool "Support SPI DM drivers in SPL"
905 Enable support for SPI DM drivers in SPL.
907 config SPL_DM_SPI_FLASH
908 bool "Support SPI DM FLASH drivers in SPL"
910 Enable support for SPI DM flash drivers in SPL.
914 config SPL_UBI_LOAD_BY_VOLNAME
915 bool "Support loading volumes by name"
917 This enables support for loading UBI volumes by name. When this
918 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
919 configure the volume name from which to load U-Boot.
921 config SPL_UBI_MAX_VOL_LEBS
922 int "Maximum number of LEBs per volume"
925 The maximum number of logical eraseblocks which a static volume
926 to load can contain. Used for sizing the scan data structure.
928 config SPL_UBI_MAX_PEB_SIZE
929 int "Maximum PEB size"
932 The maximum physical erase block size.
934 config SPL_UBI_MAX_PEBS
935 int "Maximum number of PEBs"
938 The maximum physical erase block size. If not overridden by
939 board code, this value will be used as the actual number of PEBs.
941 config SPL_UBI_PEB_OFFSET
942 int "Offset to first UBI PEB"
945 The offset in number of PEBs from the start of flash to the first
946 PEB part of the UBI image.
948 config SPL_UBI_VID_OFFSET
949 int "Offset to VID header"
952 config SPL_UBI_LEB_START
953 int "Offset to LEB in PEB"
956 The offset in bytes to the LEB within a PEB.
958 config SPL_UBI_INFO_ADDR
959 hex "Address to place UBI scan info"
962 Address for ubispl to place the scan info. Read README.ubispl to
963 determine the required size
965 config SPL_UBI_VOL_IDS
966 int "Maximum volume id"
969 The maximum volume id which can be loaded. Used for sizing the
972 config SPL_UBI_LOAD_MONITOR_ID
973 int "id of U-Boot volume"
976 The UBI volume id from which to load U-Boot
978 config SPL_UBI_LOAD_MONITOR_VOLNAME
979 string "volume name of U-Boot volume"
980 depends on SPL_UBI_LOAD_BY_VOLNAME
982 The UBI volume name from which to load U-Boot
984 config SPL_UBI_LOAD_KERNEL_ID
985 int "id of kernel volume"
986 depends on SPL_OS_BOOT && SPL_UBI
988 The UBI volume id from which to load the kernel
990 config SPL_UBI_LOAD_ARGS_ID
991 int "id of kernel args volume"
992 depends on SPL_OS_BOOT && SPL_UBI
994 The UBI volume id from which to load the device tree
996 config UBI_SPL_SILENCE_MSG
997 bool "silence UBI SPL messages"
999 Disable messages from UBI SPL. This leaves warnings
1005 bool "Support networking"
1007 Enable support for network devices (such as Ethernet) in SPL.
1008 This permits SPL to load U-Boot over a network link rather than
1009 from an on-board peripheral. Environment support is required since
1010 the network stack uses a number of environment variables. See also
1014 config SPL_NET_VCI_STRING
1015 string "BOOTP Vendor Class Identifier string sent by SPL"
1017 As defined by RFC 2132 the vendor class identifier field can be
1018 sent by the client to identify the vendor type and configuration
1019 of a client. This is often used in practice to allow for the DHCP
1020 server to specify different files to load depending on if the ROM,
1021 SPL or U-Boot itself makes the request
1024 config SPL_NO_CPU_SUPPORT
1025 bool "Drop CPU code in SPL"
1027 This is specific to the ARM926EJ-S CPU. It disables the standard
1028 start.S start-up code, presumably so that a replacement can be
1029 used on that CPU. You should not enable it unless you know what
1032 config SPL_NOR_SUPPORT
1033 bool "Support NOR flash"
1035 Enable support for loading U-Boot from memory-mapped NOR (Negative
1036 OR) flash in SPL. NOR flash is slow to write but fast to read, and
1037 a memory-mapped device makes it very easy to access. Loading from
1038 NOR is typically achieved with just a memcpy().
1040 config SPL_XIP_SUPPORT
1044 Enable support for execute in place of U-Boot or kernel image. There
1045 is no need to copy image from flash to ram if flash supports execute
1046 in place. Its very useful in systems having enough flash but not
1047 enough ram to load the image.
1049 config SPL_ONENAND_SUPPORT
1050 bool "Support OneNAND flash"
1052 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
1053 a type of NAND flash and therefore can be used to allow SPL to
1054 load U-Boot from supported devices. This enables the drivers in
1055 drivers/mtd/onenand as part of an SPL build.
1058 bool "Activate Falcon Mode"
1059 depends on !TI_SECURE_DEVICE
1061 Enable booting directly to an OS from SPL.
1062 for more info read doc/README.falcon
1066 hex "addr, where OS is found"
1067 depends on SPL_NOR_SUPPORT
1069 Specify the address, where the OS image is found, which
1074 config SPL_FALCON_BOOT_MMCSD
1075 bool "Enable Falcon boot from MMC or SD media"
1076 depends on SPL_OS_BOOT && SPL_MMC
1078 Select this if the Falcon mode OS image mode is on MMC or SD media.
1080 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
1081 hex "Falcon mode: Sector to load kernel uImage from MMC"
1082 depends on SPL_FALCON_BOOT_MMCSD
1084 When Falcon mode is used with an MMC or SD media, SPL needs to know
1085 where to look for the kernel uImage. The image is expected to begin
1086 at the raw MMC specified in this config.
1087 Note that the Falcon mode image can also be a FIT, if FIT support is
1091 string "SPL payload"
1092 default "tpl/u-boot-with-tpl.bin" if TPL
1093 default "u-boot.bin"
1095 Payload for SPL boot. For backward compatibility, default to
1096 u-boot.bin, i.e. RAW image without any header. In case of
1097 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
1101 bool "Support PCI drivers"
1103 Enable support for PCI in SPL. For platforms that need PCI to boot,
1104 or must perform some init using PCI in SPL, this provides the
1105 necessary driver support. This enables the drivers in drivers/pci
1106 as part of an SPL build.
1109 bool "Support PCH drivers"
1111 Enable support for PCH (Platform Controller Hub) devices in SPL.
1112 These are used to set up GPIOs and the SPI peripheral early in
1113 boot. This enables the drivers in drivers/pch as part of an SPL
1116 config SPL_POST_MEM_SUPPORT
1117 bool "Support POST drivers"
1119 Enable support for POST (Power-on Self Test) in SPL. POST is a
1120 procedure that checks that the hardware (CPU or board) appears to
1121 be functionally correctly. It is a sanity check that can be
1122 performed before booting. This enables the drivers in post/drivers
1123 as part of an SPL build.
1126 bool "Support reset drivers"
1129 Enable support for reset control in SPL.
1130 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1131 by using the generic reset API provided by driver model.
1132 This enables the drivers in drivers/reset as part of an SPL build.
1135 bool "Support power drivers"
1137 Enable support for power control in SPL. This includes support
1138 for PMICs (Power-management Integrated Circuits) and some of the
1139 features provided by PMICs. In particular, voltage regulators can
1140 be used to enable/disable power and vary its voltage. That can be
1141 useful in SPL to turn on boot peripherals and adjust CPU voltage
1142 so that the clock speed can be increased. This enables the drivers
1143 in drivers/power, drivers/power/pmic and drivers/power/regulator
1144 as part of an SPL build.
1146 config SPL_POWER_DOMAIN
1147 bool "Support power domain drivers"
1150 Enable support for power domain control in SPL. Many SoCs allow
1151 power to be applied to or removed from portions of the SoC (power
1152 domains). This may be used to save power. This API provides the
1153 means to control such power management hardware. This enables
1154 the drivers in drivers/power/domain as part of a SPL build.
1156 config SPL_RAM_SUPPORT
1157 bool "Support booting from RAM"
1158 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1160 Enable booting of an image in RAM. The image can be preloaded or
1161 it can be loaded by SPL directly into RAM (e.g. using USB).
1163 config SPL_RAM_DEVICE
1164 bool "Support booting from preloaded image in RAM"
1165 depends on SPL_RAM_SUPPORT
1166 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1168 Enable booting of an image already loaded in RAM. The image has to
1169 be already in memory when SPL takes over, e.g. loaded by the boot
1172 config SPL_REMOTEPROC
1173 bool "Support REMOTEPROCS"
1175 Enable support for REMOTEPROCs in SPL. This permits to load
1176 a remote processor firmware in SPL.
1179 bool "Support RTC drivers"
1181 Enable RTC (Real-time Clock) support in SPL. This includes support
1182 for reading and setting the time. Some RTC devices also have some
1183 non-volatile (battery-backed) memory which is accessible if
1184 needed. This enables the drivers in drivers/rtc as part of an SPL
1188 bool "Support loading from SATA"
1190 Enable support for SATA (Serial AT attachment) in SPL. This allows
1191 use of SATA devices such as hard drives and flash drivers for
1192 loading U-Boot. SATA is used in higher-end embedded systems and
1193 can provide higher performance than MMC , at somewhat higher
1194 expense and power consumption. This enables loading from SATA
1195 using a configured device.
1197 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1198 bool "SATA raw mode: by sector"
1200 default y if ARCH_MVEBU
1202 Use sector number for specifying U-Boot location on SATA disk in
1205 config SPL_SATA_RAW_U_BOOT_SECTOR
1206 hex "Sector on the SATA disk to load U-Boot from"
1207 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1208 default 0x1 if ARCH_MVEBU
1210 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1211 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1214 bool "Support serial"
1218 Enable support for serial in SPL. This allows use of a serial UART
1219 for displaying messages while SPL is running. It also brings in
1220 printf() and panic() functions. This should normally be enabled
1221 unless there are space reasons not to. Even then, consider
1222 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1225 bool "Support SPI drivers"
1227 Enable support for using SPI in SPL. This is used for connecting
1228 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1229 more details on that. The SPI driver provides the transport for
1230 data between the SPI flash and the CPU. This option can be used to
1231 enable SPI drivers that are needed for other purposes also, such
1234 config SPL_SPI_FLASH_SUPPORT
1235 bool "Support SPI flash drivers"
1238 Enable support for using SPI flash in SPL, and loading U-Boot from
1239 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1240 the SPI bus that is used to connect it to a system. It is a simple
1241 but fast bidirectional 4-wire bus (clock, chip select and two data
1242 lines). This enables the drivers in drivers/mtd/spi as part of an
1243 SPL build. This normally requires SPL_SPI.
1245 if SPL_SPI_FLASH_SUPPORT
1247 config SPL_SPI_FLASH_TINY
1248 bool "Enable low footprint SPL SPI Flash support"
1249 depends on !SPI_FLASH_BAR
1250 default y if SPI_FLASH
1252 Enable lightweight SPL SPI Flash support that supports just reading
1253 data/images from flash. No support to write/erase flash. Enable
1254 this if you have SPL size limitations and don't need full
1255 fledged SPI flash support.
1257 config SPL_SPI_FLASH_SFDP_SUPPORT
1258 bool "SFDP table parsing support for SPI NOR flashes"
1259 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1261 Enable support for parsing and auto discovery of parameters for
1262 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1263 tables as per JESD216 standard in SPL.
1265 config SPL_SPI_FLASH_MTD
1266 bool "Support for SPI flash MTD drivers in SPL"
1268 Enable support for SPI flash MTD drivers in SPL.
1271 bool "Support loading from SPI flash"
1273 Enable support for loading next stage, U-Boot or otherwise, from
1274 SPI NOR in U-Boot SPL.
1276 endif # SPL_SPI_FLASH_SUPPORT
1278 config SYS_SPI_U_BOOT_OFFS
1279 hex "address of u-boot payload in SPI flash"
1280 default 0x8000 if ARCH_SUNXI
1282 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1284 Address within SPI-Flash from where the u-boot payload is fetched
1288 bool "Driver support for thermal devices"
1290 Enable support for temperature-sensing devices. Some SoCs have on-chip
1291 temperature sensors to permit warnings, speed throttling or even
1292 automatic power-off when the temperature gets too high or low. Other
1293 devices may be discrete but connected on a suitable bus.
1296 bool "Support USB host drivers"
1297 select HAVE_BLOCK_DEVICE
1299 Enable access to USB (Universal Serial Bus) host devices so that
1300 SPL can load U-Boot from a connected USB peripheral, such as a USB
1301 flash stick. While USB takes a little longer to start up than most
1302 buses, it is very flexible since many different types of storage
1303 device can be attached. This option enables the drivers in
1304 drivers/usb/host as part of an SPL build.
1306 config SPL_USB_STORAGE
1307 bool "Support loading from USB"
1308 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1310 Enable support for USB devices in SPL. This allows use of USB
1311 devices such as hard drives and flash drivers for loading U-Boot.
1312 The actual drivers are enabled separately using the normal U-Boot
1313 config options. This enables loading from USB using a configured
1316 config SPL_USB_GADGET
1317 bool "Suppport USB Gadget drivers"
1319 Enable USB Gadget API which allows to enable USB device functions
1324 config SPL_USB_ETHER
1325 bool "Support USB Ethernet drivers"
1328 Enable access to the USB network subsystem and associated
1329 drivers in SPL. This permits SPL to load U-Boot over a
1330 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1331 than from an onboard peripheral. Environment support is required
1332 since the network stack uses a number of environment variables.
1333 See also SPL_NET and SPL_ETH.
1336 bool "Support DFU (Device Firmware Upgrade)"
1338 select SPL_DFU_NO_RESET
1339 depends on SPL_RAM_SUPPORT
1341 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1342 RAM memory device support. The ROM code will load and execute
1343 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1344 selected device partition from host-pc using dfu-utils.
1345 This feature is useful to flash the binaries to factory or bare-metal
1346 boards using USB interface.
1349 bool "DFU device selection"
1354 depends on SPL_DFU && SPL_RAM_SUPPORT
1356 select RAM/DDR memory device for loading binary images
1357 (u-boot/kernel) to the selected device partition using
1358 DFU and execute the u-boot/kernel from RAM.
1362 config SPL_USB_SDP_SUPPORT
1363 bool "Support SDP (Serial Download Protocol)"
1364 depends on SPL_SERIAL
1366 Enable Serial Download Protocol (SDP) device support in SPL. This
1367 allows to download images into memory and execute (jump to) them
1368 using the same protocol as implemented by the i.MX family's boot ROM.
1370 config SPL_SDP_USB_DEV
1371 int "SDP USB controller index"
1373 depends on SPL_USB_SDP_SUPPORT
1375 Some boards have USB controller other than 0. Define this option
1376 so it can be used in compiled environment.
1380 bool "Support watchdog drivers"
1381 imply SPL_WDT if !HW_WATCHDOG
1383 Enable support for watchdog drivers in SPL. A watchdog is
1384 typically a hardware peripheral which can reset the system when it
1385 detects no activity for a while (such as a software crash). This
1386 enables the drivers in drivers/watchdog as part of an SPL build.
1388 config SPL_YMODEM_SUPPORT
1389 bool "Support loading using Ymodem"
1390 depends on SPL_SERIAL
1392 While loading from serial is slow it can be a useful backup when
1393 there is no other option. The Ymodem protocol provides a reliable
1394 means of transmitting U-Boot over a serial line for using in SPL,
1395 with a checksum to ensure correctness.
1398 bool "Support ARM Trusted Firmware"
1399 depends on ARM64 && SPL_FIT
1401 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1402 is loaded by SPL (which is considered as BL2 in ATF terminology).
1403 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1405 config SPL_ATF_LOAD_IMAGE_V2
1406 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1409 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1411 If you want to load a bl31 image from the SPL and need the new
1414 config SPL_ATF_NO_PLATFORM_PARAM
1415 bool "Pass no platform parameter"
1418 While we expect to call a pointer to a valid FDT (or NULL)
1419 as the platform parameter to an ATF, some ATF versions are
1420 not U-Boot aware and have an insufficiently robust parameter
1421 validation to gracefully reject a FDT being passed.
1423 If this option is enabled, the spl_atf os-type handler will
1424 always pass NULL for the platform parameter.
1426 If your ATF is affected, say Y.
1428 config SPL_AM33XX_ENABLE_RTC32K_OSC
1429 bool "Enable the RTC32K OSC on AM33xx based platforms"
1432 Enable access to the AM33xx RTC and select the external 32kHz clock
1435 config SPL_OPTEE_IMAGE
1436 bool "Support OP-TEE Trusted OS image in SPL"
1439 OP-TEE is an open source Trusted OS which is loaded by SPL.
1440 More detail at: https://github.com/OP-TEE/optee_os
1443 bool "Support RISC-V OpenSBI"
1444 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1446 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1447 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1448 firmware. It is loaded and started by U-Boot SPL.
1450 More details are available at https://github.com/riscv/opensbi and
1451 https://github.com/riscv/riscv-sbi-doc
1453 config SPL_OPENSBI_LOAD_ADDR
1454 hex "OpenSBI load address"
1455 depends on SPL_OPENSBI
1457 Load address of the OpenSBI binary.
1461 depends on SUPPORT_TPL
1464 If you want to build TPL as well as the normal image and SPL, say Y.
1468 config TPL_SIZE_LIMIT
1469 hex "Maximum size of TPL image"
1473 Specifies the maximum length of the U-Boot TPL image.
1474 If this value is zero, it is ignored.
1476 config TPL_BINMAN_SYMBOLS
1477 bool "Declare binman symbols in TPL"
1478 depends on SPL_FRAMEWORK && BINMAN
1481 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1482 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1483 and spl_get_image_size().
1485 For this to work, you must have a U-Boot image in the binman image, so
1486 binman can update TPL with the location of it.
1488 config TPL_FRAMEWORK
1489 bool "Support TPL based upon the common SPL framework"
1490 default y if SPL_FRAMEWORK
1492 Enable the SPL framework under common/spl/ for TPL builds.
1493 This framework supports MMC, NAND and YMODEM and other methods
1494 loading of U-Boot's SPL stage. If unsure, say Y.
1497 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1498 depends on HANDOFF && TPL_BLOBLIST
1501 This option enables TPL to write handoff information. This can be
1502 used to pass information like the size of SDRAM from TPL to U-Boot
1503 proper. The information is also available to SPL if it is useful
1506 config TPL_BOARD_INIT
1507 bool "Call board-specific initialization in TPL"
1509 If this option is enabled, U-Boot will call the function
1510 spl_board_init() from board_init_r(). This function should be
1511 provided by the board.
1513 config TPL_BOOTCOUNT_LIMIT
1514 bool "Support bootcount in TPL"
1515 depends on TPL_ENV_SUPPORT
1517 If this option is enabled, the TPL will support bootcount.
1518 For example, it may be useful to choose the device to boot.
1521 string "Linker script for the TPL stage"
1523 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1524 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1526 The TPL stage will usually require a different linker-script
1527 (as it runs from a different memory region) than the regular
1528 U-Boot stage. Set this to the path of the linker-script to
1531 May be left empty to trigger the Makefile infrastructure to
1532 fall back to the linker-script used for the SPL stage.
1534 config TPL_NEEDS_SEPARATE_STACK
1535 bool "TPL needs a separate initial stack-pointer"
1538 Enable, if the TPL stage should not inherit its initial
1539 stack-pointer from the settings for the SPL stage.
1542 bool "Support power drivers"
1544 Enable support for power control in TPL. This includes support
1545 for PMICs (Power-management Integrated Circuits) and some of the
1546 features provided by PMICs. In particular, voltage regulators can
1547 be used to enable/disable power and vary its voltage. That can be
1548 useful in TPL to turn on boot peripherals and adjust CPU voltage
1549 so that the clock speed can be increased. This enables the drivers
1550 in drivers/power, drivers/power/pmic and drivers/power/regulator
1551 as part of an TPL build.
1553 config TPL_TEXT_BASE
1554 hex "Base address for the .text section of the TPL stage"
1557 The base address for the .text section of the TPL stage.
1560 hex "Maximum size (in bytes) for the TPL stage"
1561 default 0x2e000 if ROCKCHIP_RK3399
1562 default 0x8000 if ROCKCHIP_RK3288
1563 default 0x7000 if ROCKCHIP_RK322X || ROCKCHIP_RK3328 || ROCKCHIP_RK3368
1564 default 0x2800 if ROCKCHIP_PX30
1567 The maximum size (in bytes) of the TPL stage.
1570 hex "Offset to which the TPL should be padded before appending the TPL payload"
1571 depends on !TPL_FRAMEWORK && PPC
1572 default TPL_MAX_SIZE
1574 Image offset to which the TPL should be padded before appending the
1575 TPL payload. By default, this is defined as CONFIG_TPL_MAX_SIZE, or 0 if
1576 CONFIG_TPL_MAX_SIZE is undefined. CONFIG_TPL_PAD_TO must be either
1577 0, meaning to append the TPL payload without any padding, or >=
1578 CONFIG_TPL_MAX_SIZE.
1581 hex "Address of the initial stack-pointer for the TPL stage"
1582 depends on TPL_NEEDS_SEPARATE_STACK
1584 The address of the initial stack-pointer for the TPL stage.
1585 Usually this will be the (aligned) top-of-stack.
1587 config TPL_READ_ONLY
1589 depends on TPL_OF_PLATDATA
1590 select TPL_OF_PLATDATA_NO_BIND
1591 select TPL_OF_PLATDATA_RT
1593 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1594 section of memory. This means that of-platdata must make a copy (in
1595 writeable memory) of anything it wants to modify, such as
1596 device-private data.
1598 config TPL_BOOTROM_SUPPORT
1599 bool "Support returning to the BOOTROM (from TPL)"
1601 Some platforms (e.g. the Rockchip RK3368) provide support in their
1602 ROM for loading the next boot-stage after performing basic setup
1605 Enable this option, to return to the BOOTROM through the
1606 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1607 boot device list, if not implemented for a given board)
1610 bool "Support CRC32 in TPL"
1611 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1613 Enable this to support CRC32 in uImages or FIT images within SPL.
1614 This is a 32-bit checksum value that can be used to verify images.
1615 For FIT images, this is the least secure type of checksum, suitable
1616 for detected accidental image corruption. For secure applications you
1617 should consider SHA1 or SHA256.
1619 config TPL_DRIVERS_MISC
1620 bool "Support misc drivers in TPL"
1622 Enable miscellaneous drivers in TPL. These drivers perform various
1623 tasks that don't fall nicely into other categories, Enable this
1624 option to build the drivers in drivers/misc as part of an TPL
1625 build, for those that support building in TPL (not all drivers do).
1627 config TPL_ENV_SUPPORT
1628 bool "Support an environment"
1630 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1633 bool "Support GPIO in TPL"
1635 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1636 GPIOs allow U-Boot to read the state of an input line (high or
1637 low) and set the state of an output line. This can be used to
1638 drive LEDs, control power to various system parts and read user
1639 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1640 for example. Enable this option to build the drivers in
1641 drivers/gpio as part of an TPL build.
1646 Enable support for the I2C bus in TPL. See SPL_I2C for
1649 config TPL_LIBCOMMON_SUPPORT
1650 bool "Support common libraries"
1652 Enable support for common U-Boot libraries within TPL. See
1653 SPL_LIBCOMMON_SUPPORT for details.
1655 config TPL_LIBGENERIC_SUPPORT
1656 bool "Support generic libraries"
1658 Enable support for generic U-Boot libraries within TPL. See
1659 SPL_LIBGENERIC_SUPPORT for details.
1661 config TPL_MPC8XXX_INIT_DDR
1662 bool "Support MPC8XXX DDR init"
1664 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1665 SPL_MPC8XXX_INIT_DDR for details.
1671 Enable support for MMC within TPL. See SPL_MMC for details.
1673 config TPL_NAND_SUPPORT
1674 bool "Support NAND flash"
1676 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1679 bool "Support PCI drivers"
1681 Enable support for PCI in TPL. For platforms that need PCI to boot,
1682 or must perform some init using PCI in SPL, this provides the
1683 necessary driver support. This enables the drivers in drivers/pci
1684 as part of a TPL build.
1687 bool "Support PCH drivers"
1689 Enable support for PCH (Platform Controller Hub) devices in TPL.
1690 These are used to set up GPIOs and the SPI peripheral early in
1691 boot. This enables the drivers in drivers/pch as part of a TPL
1694 config TPL_RAM_SUPPORT
1695 bool "Support booting from RAM"
1697 Enable booting of an image in RAM. The image can be preloaded or
1698 it can be loaded by TPL directly into RAM (e.g. using USB).
1700 config TPL_RAM_DEVICE
1701 bool "Support booting from preloaded image in RAM"
1702 depends on TPL_RAM_SUPPORT
1704 Enable booting of an image already loaded in RAM. The image has to
1705 be already in memory when TPL takes over, e.g. loaded by the boot
1709 bool "Support RTC drivers"
1711 Enable RTC (Real-time Clock) support in TPL. This includes support
1712 for reading and setting the time. Some RTC devices also have some
1713 non-volatile (battery-backed) memory which is accessible if
1714 needed. This enables the drivers in drivers/rtc as part of an TPL
1718 bool "Support serial"
1722 Enable support for serial in TPL. See SPL_SERIAL for
1725 config TPL_SPI_FLASH_SUPPORT
1726 bool "Support SPI flash drivers"
1728 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1731 config TPL_SPI_FLASH_TINY
1732 bool "Enable low footprint TPL SPI Flash support"
1733 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1734 default y if SPI_FLASH
1736 Enable lightweight TPL SPI Flash support that supports just reading
1737 data/images from flash. No support to write/erase flash. Enable
1738 this if you have TPL size limitations and don't need full-fledged
1742 bool "Support loading from SPI flash"
1743 depends on TPL_SPI_FLASH_SUPPORT
1745 Enable support for loading next stage, U-Boot or otherwise, from
1746 SPI NOR in U-Boot TPL.
1749 bool "Support SPI drivers"
1751 Enable support for using SPI in TPL. See SPL_SPI for
1755 bool "Support SPI DM drivers in TPL"
1757 Enable support for SPI DM drivers in TPL.
1759 config TPL_DM_SPI_FLASH
1760 bool "Support SPI DM FLASH drivers in TPL"
1762 Enable support for SPI DM flash drivers in TPL.
1764 config TPL_YMODEM_SUPPORT
1765 bool "Support loading using Ymodem"
1766 depends on TPL_SERIAL
1768 While loading from serial is slow it can be a useful backup when
1769 there is no other option. The Ymodem protocol provides a reliable
1770 means of transmitting U-Boot over a serial line for using in TPL,
1771 with a checksum to ensure correctness.
1777 depends on SUPPORT_SPL
1780 If you want to build VPL as well as the normal image, TPL and SPL,
1785 config VPL_BANNER_PRINT
1786 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1790 If this option is enabled, VPL will print the banner with version
1791 info. Disabling this option could be useful to reduce VPL boot time
1792 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1794 config VPL_BOARD_INIT
1795 bool "Call board-specific initialization in VPL"
1797 If this option is enabled, U-Boot will call the function
1798 spl_board_init() from board_init_r(). This function should be
1799 provided by the board.
1803 bool "Support cache drivers in VPL"
1805 Enable support for cache drivers in VPL.
1808 bool "Support CRC32 in VPL"
1809 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1811 Enable this to support CRC32 in uImages or FIT images within VPL.
1812 This is a 32-bit checksum value that can be used to verify images.
1813 For FIT images, this is the least secure type of checksum, suitable
1814 for detected accidental image corruption. For secure applications you
1815 should consider SHA1 or SHA256.
1818 bool "Support SPI DM drivers in VPL"
1820 Enable support for SPI DM drivers in VPL.
1822 config VPL_DM_SPI_FLASH
1823 bool "Support SPI DM FLASH drivers in VPL"
1825 Enable support for SPI DM flash drivers in VPL.
1827 config VPL_FRAMEWORK
1828 bool "Support VPL based upon the common SPL framework"
1831 Enable the SPL framework under common/spl/ for VPL builds.
1832 This framework supports MMC, NAND and YMODEM and other methods
1833 loading of U-Boot's next stage. If unsure, say Y.
1836 bool "Pass hand-off information from VPL to SPL"
1837 depends on HANDOFF && VPL_BLOBLIST
1840 This option enables VPL to write handoff information. This can be
1841 used to pass information like the size of SDRAM from VPL to SPL. Also
1842 VPL can receive information from TPL in the same place if that is
1845 config VPL_LIBCOMMON_SUPPORT
1846 bool "Support common libraries"
1847 default y if SPL_LIBCOMMON_SUPPORT
1849 Enable support for common U-Boot libraries within VPL. See
1850 SPL_LIBCOMMON_SUPPORT for details.
1852 config VPL_LIBGENERIC_SUPPORT
1853 bool "Support generic libraries"
1854 default y if SPL_LIBGENERIC_SUPPORT
1856 Enable support for generic U-Boot libraries within VPL. These
1857 libraries include generic code to deal with device tree, hashing,
1858 printf(), compression and the like. This option is enabled on many
1859 boards. Enable this option to build the code in lib/ as part of a
1862 config VPL_DRIVERS_MISC
1863 bool "Support misc drivers"
1864 default y if TPL_DRIVERS_MISC
1866 Enable miscellaneous drivers in VPL. These drivers perform various
1867 tasks that don't fall nicely into other categories, Enable this
1868 option to build the drivers in drivers/misc as part of a VPL
1869 build, for those that support building in VPL (not all drivers do).
1871 config VPL_ENV_SUPPORT
1872 bool "Support an environment"
1874 Enable environment support in VPL. The U-Boot environment provides
1875 a number of settings (essentially name/value pairs) which can
1876 control many aspects of U-Boot's operation. Enabling this option will
1877 make env_get() and env_set() available in VSPL.
1880 bool "Support GPIO in VPL"
1881 default y if SPL_GPIO
1883 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1884 GPIOs allow U-Boot to read the state of an input line (high or
1885 low) and set the state of an output line. This can be used to
1886 drive LEDs, control power to various system parts and read user
1887 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1888 for example. Enable this option to build the drivers in
1889 drivers/gpio as part of a VPL build.
1892 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1893 depends on HANDOFF && VPL_BLOBLIST
1896 This option enables VPL to write handoff information. This can be
1897 used to pass information like the size of SDRAM from VPL to U-Boot
1898 proper. The information is also available to VPL if it is useful
1902 bool "Support hashing drivers in VPL"
1907 Enable hashing drivers in VPL. These drivers can be used to
1908 accelerate secure boot processing in secure applications. Enable
1909 this option to build system-specific drivers for hash acceleration
1910 as part of a VPL build.
1912 config VPL_I2C_SUPPORT
1913 bool "Support I2C in VPL"
1914 default y if SPL_I2C_SUPPORT
1916 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1919 config VPL_PCH_SUPPORT
1920 bool "Support PCH drivers"
1921 default y if TPL_PCH_SUPPORT
1923 Enable support for PCH (Platform Controller Hub) devices in VPL.
1924 These are used to set up GPIOs and the SPI peripheral early in
1925 boot. This enables the drivers in drivers/pch as part of a VPL
1929 bool "Support PCI drivers"
1930 default y if SPL_PCI
1932 Enable support for PCI in VPL. For platforms that need PCI to boot,
1933 or must perform some init using PCI in VPL, this provides the
1934 necessary driver support. This enables the drivers in drivers/pci
1935 as part of a VPL build.
1938 bool "Support RTC drivers"
1940 Enable RTC (Real-time Clock) support in VPL. This includes support
1941 for reading and setting the time. Some RTC devices also have some
1942 non-volatile (battery-backed) memory which is accessible if
1943 needed. This enables the drivers in drivers/rtc as part of a VPL
1947 bool "Support serial"
1948 default y if TPL_SERIAL
1952 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1955 config VPL_SIZE_LIMIT
1956 hex "Maximum size of VPL image"
1960 Specifies the maximum length of the U-Boot VPL image.
1961 If this value is zero, it is ignored.
1964 bool "Support SPI drivers"
1966 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
1969 config VPL_SPI_FLASH_SUPPORT
1970 bool "Support SPI flash drivers"
1972 Enable support for using SPI flash in VPL, and loading U-Boot from
1973 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1974 the SPI bus that is used to connect it to a system. It is a simple
1975 but fast bidirectional 4-wire bus (clock, chip select and two data
1976 lines). This enables the drivers in drivers/mtd/spi as part of a
1977 VPL build. This normally requires VPL_SPI_SUPPORT.
1979 config VPL_TEXT_BASE
1983 The address in memory that VPL will be running from.
1987 config SPL_AT91_MCK_BYPASS
1988 bool "Use external clock signal as a source of main clock for AT91 platforms"
1989 depends on ARCH_AT91
1991 Use external 8 to 24 Mhz clock signal as source of main clock instead
1992 of an external crystal oscillator.
1993 This option disables the internal driving on the XOUT pin.
1994 The external source has to provide a stable clock on the XIN pin.
1995 If this option is disabled, the SoC expects a crystal oscillator
1996 that needs driving on both XIN and XOUT lines.