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
78 config SPL_SYS_STACK_F_CHECK_BYTE
82 Constant used to check the stack
84 config SPL_SYS_REPORT_STACK_F_USAGE
85 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
86 bool "Check and report stack usage in SPL before relocation"
88 If this option is enabled, the initial SPL stack is filled with 0xaa
89 very early, up to the size configured with
90 SPL_SIZE_LIMIT_PROVIDE_STACK.
91 Later when SPL is done using this initial stack and switches to a
92 stack in DRAM, the actually used size of this initial stack is
93 reported by examining the memory and searching for the lowest
94 occurrence of non 0xaa bytes.
95 This default implementation works for stacks growing down only.
97 config SPL_SHOW_ERRORS
98 bool "Show more information when something goes wrong"
100 This enabled more verbose error messages and checking when something
101 goes wrong in SPL. For example, it shows the error code when U-Boot
102 cannot be located. This can help to diagnose the problem and figure
103 out a fix, particularly during development.
105 This adds a small amount to SPL code size, perhaps 100 bytes.
107 config SPL_BINMAN_SYMBOLS
108 bool "Declare binman symbols in SPL"
109 depends on SPL_FRAMEWORK && BINMAN
112 This enables use of symbols in SPL which refer to U-Boot, enabling SPL
113 to obtain the location of U-Boot simply by calling spl_get_image_pos()
114 and spl_get_image_size().
116 For this to work, you must have a U-Boot image in the binman image, so
117 binman can update SPL with the location of it.
119 menu "PowerPC and LayerScape SPL Boot options"
122 bool "Load SPL from NAND flash"
123 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
126 bool "Load SPL from SD Card / eMMC"
127 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
130 bool "Load SPL from SPI flash"
131 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
134 bool "Create SPL in Freescale PBI format"
135 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
138 Create boot binary having SPL binary in PBI format concatenated with
143 menu "PowerPC SPL specific options"
144 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
146 config SPL_INIT_MINIMAL
147 bool "Arch init code will be built for a very small image"
149 config SPL_FLUSH_IMAGE
150 bool "Clean dcache and invalidate icache after loading the image"
152 config SPL_SKIP_RELOCATE
153 bool "Skip relocating SPL"
158 bool "Pass hand-off information from SPL to U-Boot proper"
159 depends on SPL && BLOBLIST
161 It is useful to be able to pass information from SPL to U-Boot
162 proper to preserve state that is known in SPL and is needed in U-Boot.
163 Enable this to locate the handoff information in U-Boot proper, early
164 in boot. It is available in gd->handoff. The state state is set up
165 in SPL (or TPL if that is being used).
170 bool "Pass hand-off information from SPL to U-Boot proper"
171 depends on HANDOFF && SPL_BLOBLIST
174 This option enables SPL to write handoff information. This can be
175 used to pass information like the size of SDRAM from SPL to U-Boot
176 proper. Also SPL can receive information from TPL in the same place
180 string "Linker script for the SPL stage"
181 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
183 The SPL stage will usually require a different linker-script
184 (as it runs from a different memory region) than the regular
185 U-Boot stage. Set this to the path of the linker-script to
190 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
191 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
192 default 0x20060 if SUN50I_GEN_H6
193 default 0x00060 if ARCH_SUNXI
194 default 0xfffc0000 if ARCH_ZYNQMP
197 The address in memory that SPL will be running from.
199 config SPL_BOARD_INIT
200 bool "Call board-specific initialization in SPL"
202 If this option is enabled, U-Boot will call the function
203 spl_board_init() from board_init_r(). This function should be
204 provided by the board.
206 config VPL_BOARD_INIT
207 bool "Call board-specific initialization in VPL"
209 If this option is enabled, U-Boot will call the function
210 spl_board_init() from board_init_r(). This function should be
211 provided by the board.
213 config SPL_BOOTROM_SUPPORT
214 bool "Support returning to the BOOTROM"
216 Some platforms (e.g. the Rockchip RK3368) provide support in their
217 ROM for loading the next boot-stage after performing basic setup
220 Enable this option, to return to the BOOTROM through the
221 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
222 boot device list, if not implemented for a given board)
224 config SPL_BOOTCOUNT_LIMIT
225 bool "Support bootcount in SPL"
226 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
228 On some boards, which use 'falcon' mode, it is necessary to check
229 and increment the number of boot attempts. Such boards do not
230 use proper U-Boot for normal boot flow and hence needs those
231 adjustments to be done in the SPL.
233 config SPL_RAW_IMAGE_SUPPORT
234 bool "Support SPL loading and booting of RAW images"
235 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
237 depends on !TI_SECURE_DEVICE
239 SPL will support loading and booting a RAW image when this option
240 is y. If this is not set, SPL will move on to other available
241 boot media to find a suitable image.
243 config SPL_LEGACY_IMAGE_FORMAT
244 bool "Support SPL loading and booting of Legacy images"
245 default y if !SPL_LOAD_FIT
246 depends on !TI_SECURE_DEVICE
248 SPL will support loading and booting Legacy images when this option
249 is y. If this is not set, SPL will move on to other available
250 boot media to find a suitable image.
252 config SPL_LEGACY_IMAGE_CRC_CHECK
253 bool "Check CRC of Legacy images"
254 depends on SPL_LEGACY_IMAGE_FORMAT
257 Enable this to check the CRC of Legacy images. While this increases
258 reliability, it affects both code size and boot duration.
259 If disabled, Legacy images are booted if the image magic and size
260 are correct, without further integrity checks.
262 config SPL_SYS_MALLOC_SIMPLE
264 prompt "Only use malloc_simple functions in the SPL"
266 Say Y here to only use the *_simple malloc functions from
267 malloc_simple.c, rather then using the versions from dlmalloc.c;
268 this will make the SPL binary smaller at the cost of more heap
269 usage as the *_simple malloc functions do not re-use free-ed mem.
271 config TPL_SYS_MALLOC_SIMPLE
273 prompt "Only use malloc_simple functions in the TPL"
276 Say Y here to only use the *_simple malloc functions from
277 malloc_simple.c, rather then using the versions from dlmalloc.c;
278 this will make the TPL binary smaller at the cost of more heap
279 usage as the *_simple malloc functions do not re-use free-ed mem.
282 bool "Enable SDRAM location for SPL stack"
284 SPL starts off execution in SRAM and thus typically has only a small
285 stack available. Since SPL sets up DRAM while in its board_init_f()
286 function, it is possible for the stack to move there before
287 board_init_r() is reached. This option enables a special SDRAM
288 location for the SPL stack. U-Boot SPL switches to this after
289 board_init_f() completes, and before board_init_r() starts.
291 config SPL_STACK_R_ADDR
292 depends on SPL_STACK_R
293 hex "SDRAM location for SPL stack"
294 default 0x82000000 if ARCH_OMAP2PLUS
296 Specify the address in SDRAM for the SPL stack. This will be set up
297 before board_init_r() is called.
299 config SPL_STACK_R_MALLOC_SIMPLE_LEN
300 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
301 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
304 Specify the amount of the stack to use as memory pool for
305 malloc_simple after switching the stack to DRAM. This may be set
306 to give board_init_r() a larger heap then the initial heap in
307 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
309 config SPL_SEPARATE_BSS
310 bool "BSS section is in a different memory region from text"
312 Some platforms need a large BSS region in SPL and can provide this
313 because RAM is already set up. In this case BSS can be moved to RAM.
314 This option should then be enabled so that the correct device tree
315 location is used. Normally we put the device tree at the end of BSS
316 but with this option enabled, it goes at _image_binary_end.
320 depends on SPL_OF_PLATDATA
321 # Bind cannot be supported because the udevice structs are in read-only
322 # memory so we cannot update the linked lists.
323 select SPL_OF_PLATDATA_NO_BIND
324 select SPL_OF_PLATDATA_RT
326 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
327 section of memory. This means that of-platdata must make a copy (in
328 writeable memory) of anything it wants to modify, such as
331 config TPL_SEPARATE_BSS
332 bool "BSS section is in a different memory region from text"
333 default y if SPL_SEPARATE_BSS
335 Some platforms need a large BSS region in TPL and can provide this
336 because RAM is already set up. In this case BSS can be moved to RAM.
337 This option should then be enabled so that the correct device tree
338 location is used. Normally we put the device tree at the end of BSS
339 but with this option enabled, it goes at _image_binary_end.
341 config SPL_BANNER_PRINT
342 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
345 If this option is enabled, SPL will print the banner with version
346 info. Disabling this option could be useful to reduce SPL boot time
347 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
349 config TPL_BANNER_PRINT
350 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
354 If this option is enabled, TPL will print the banner with version
355 info. Disabling this option could be useful to reduce TPL boot time
356 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
359 depends on ARM && !ARM64
360 bool "Allows initializing BSS early before entering board_init_f"
362 On some platform we have sufficient memory available early on to
363 allow setting up and using a basic BSS prior to entering
364 board_init_f. Activating this option will also de-activate the
365 clearing of BSS during the SPL relocation process, thus allowing
366 to carry state from board_init_f to board_init_r by way of BSS.
368 config SPL_DISPLAY_PRINT
369 bool "Display a board-specific message in SPL"
371 If this option is enabled, U-Boot will call the function
372 spl_display_print() immediately after displaying the SPL console
373 banner ("U-Boot SPL ..."). This function should be provided by
376 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
377 bool "MMC raw mode: by sector"
378 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
379 ARCH_MX6 || ARCH_MX7 || \
380 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
381 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
382 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
383 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
385 Use sector number for specifying U-Boot location on MMC/SD in
388 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
389 hex "Address on the MMC to load U-Boot from"
390 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
391 default 0x40 if ARCH_SUNXI
392 default 0x75 if ARCH_DAVINCI
393 default 0x8a if ARCH_MX6 || ARCH_MX7
394 default 0x100 if ARCH_UNIPHIER
395 default 0x0 if ARCH_MVEBU
396 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
397 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
398 OMAP54XX || AM33XX || AM43XX || ARCH_K3
399 default 0x4000 if ARCH_ROCKCHIP
400 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
402 Address on the MMC to load U-Boot from, when the MMC is being used
403 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
405 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
406 hex "U-Boot main hardware partition image offset"
407 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
408 default 0x10 if ARCH_SUNXI
411 On some platforms SPL location depends on hardware partition. The ROM
412 code skips the MBR sector when loading SPL from main hardware data
413 partition. This adds offset to the main U-Boot image. Set this symbol
414 to the number of skipped sectors.
416 If unsure, leave the default.
418 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
419 bool "MMC Raw mode: by partition"
421 Use a partition for loading U-Boot when using MMC/SD in raw mode.
423 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
424 hex "Partition to use to load U-Boot from"
425 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
428 Partition on the MMC to load U-Boot from when the MMC is being
431 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
432 bool "MMC raw mode: by partition type"
433 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
435 Use partition type for specifying U-Boot partition on MMC/SD in
436 raw mode. U-Boot will be loaded from the first partition of this
439 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
440 hex "Partition Type on the MMC to load U-Boot from"
441 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
443 Partition Type on the MMC to load U-Boot from, when the MMC is being
446 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
447 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
448 depends on SUPPORT_EMMC_BOOT
450 eMMC boot partition is normally configured by the bits of the EXT_CSD
451 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
452 cases it might be required in SPL to load the image from different
453 partition than the partition selected by EXT_CSC_PART_CONFIG register.
454 Enable this option if you intend to use an eMMC boot partition other
455 then selected via EXT_CSC_PART_CONFIG register and specify the custom
456 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
459 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
460 int "Number of the eMMC boot partition to use"
461 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
464 eMMC boot partition number to use when the eMMC in raw mode and
465 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
466 by user defined partition number.
470 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
471 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
473 Enable this to support CRC32 in uImages or FIT images within SPL.
474 This is a 32-bit checksum value that can be used to verify images.
475 For FIT images, this is the least secure type of checksum, suitable
476 for detected accidental image corruption. For secure applications you
477 should consider SHA1 or SHA256.
483 Enable this to support MD5 in FIT images within SPL. An MD5
484 checksum is a 128-bit hash value used to check that the image
485 contents have not been corrupted. Note that MD5 is not considered
486 secure as it is possible (with a brute-force attack) to adjust the
487 image while still retaining the same MD5 hash value. For secure
488 applications where images may be changed maliciously, you should
489 consider SHA256 or SHA384.
491 config SPL_FIT_IMAGE_TINY
492 bool "Remove functionality from SPL FIT loading to reduce size"
494 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
495 default y if ARCH_IMX8M
497 Enable this to reduce the size of the FIT image loading code
498 in SPL, if space for the SPL binary is very tight.
500 This skips the recording of each loaded payload
501 (i.e. loadable) into the FDT (modifying the loaded FDT to
502 ensure this information is available to the next image
506 bool "Support CACHE drivers"
508 Enable CACHE drivers in SPL. These drivers can keep data so that
509 future requests for that data can be served faster. Enable this option
510 to build the drivers in drivers/cache as part of an SPL build.
513 bool "Support CPU drivers"
515 Enable this to support CPU drivers in SPL. These drivers can set
516 up CPUs and provide information about them such as the model and
517 name. This can be useful in SPL since setting up the CPUs earlier
518 may improve boot performance. Enable this option to build the
519 drivers in drivers/cpu as part of an SPL build.
522 bool "Support crypto drivers"
524 Enable crypto drivers in SPL. These drivers can be used to
525 accelerate secure boot processing in secure applications. Enable
526 this option to build the drivers in drivers/crypto as part of an
530 bool "Support DMA drivers"
532 Enable DMA (direct-memory-access) drivers in SPL. These drivers
533 can be used to handle memory-to-peripheral data transfer without
534 the CPU moving the data. Enable this option to build the drivers
535 in drivers/dma as part of an SPL build.
537 config SPL_DRIVERS_MISC
538 bool "Support misc drivers"
540 Enable miscellaneous drivers in SPL. These drivers perform various
541 tasks that don't fall nicely into other categories, Enable this
542 option to build the drivers in drivers/misc as part of an SPL
543 build, for those that support building in SPL (not all drivers do).
545 config SPL_ENV_SUPPORT
546 bool "Support an environment"
548 Enable environment support in SPL. The U-Boot environment provides
549 a number of settings (essentially name/value pairs) which can
550 control many aspects of U-Boot's operation. Normally this is not
551 needed in SPL as it has a much simpler task with less
552 configuration. But some boards use this to support 'Falcon' boot
553 on EXT2 and FAT, where SPL boots directly into Linux without
554 starting U-Boot first. Enabling this option will make env_get()
555 and env_set() available in SPL.
558 bool "Support save environment"
559 depends on SPL_ENV_SUPPORT
560 select SPL_MMC_WRITE if ENV_IS_IN_MMC
562 Enable save environment support in SPL after setenv. By default
563 the saveenv option is not provided in SPL, but some boards need
564 this support in 'Falcon' boot, where SPL need to boot from
565 different images based on environment variable set by OS. For
566 example OS may set "reboot_image" environment variable to
567 "recovery" inorder to boot recovery image by SPL. The SPL read
568 "reboot_image" and act accordingly and change the reboot_image
569 to default mode using setenv and save the environment.
572 bool "Support Ethernet"
573 depends on SPL_ENV_SUPPORT
576 Enable access to the network subsystem and associated Ethernet
577 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
578 link rather than from an on-board peripheral. Environment support
579 is required since the network stack uses a number of environment
580 variables. See also SPL_NET.
583 bool "Support EXT filesystems"
585 Enable support for EXT2/3/4 filesystems with SPL. This permits
586 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
587 filesystem from within SPL. Support for the underlying block
588 device (e.g. MMC or USB) must be enabled separately.
590 config SPL_FS_SQUASHFS
591 bool "Support SquashFS filesystems"
594 Enable support for SquashFS filesystems with SPL. This permits
595 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
596 filesystem from within SPL. Support for the underlying block
597 device (e.g. MMC or USB) must be enabled separately.
600 bool "Support FAT filesystems"
603 Enable support for FAT and VFAT filesystems with SPL. This
604 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
605 filesystem from within SPL. Support for the underlying block
606 device (e.g. MMC or USB) must be enabled separately.
609 bool "Support write for FAT filesystems"
611 Enable write support for FAT and VFAT filesystems with SPL.
612 Support for the underlying block device (e.g. MMC or USB) must be
618 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
619 provide software-configurable hardware which is typically used to
620 implement peripherals (such as UARTs, LCD displays, MMC) or
621 accelerate custom processing functions, such as image processing
622 or machine learning. Sometimes it is useful to program the FPGA
623 as early as possible during boot, and this option can enable that
627 bool "Support GPIO in SPL"
629 Enable support for GPIOs (General-purpose Input/Output) in SPL.
630 GPIOs allow U-Boot to read the state of an input line (high or
631 low) and set the state of an output line. This can be used to
632 drive LEDs, control power to various system parts and read user
633 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
634 for example. Enable this option to build the drivers in
635 drivers/gpio as part of an SPL build.
640 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
641 I2C works with a clock and data line which can be driven by a
642 one or more masters or slaves. It is a fairly complex bus but is
643 widely used as it only needs two lines for communication. Speeds of
644 400kbps are typical but up to 3.4Mbps is supported by some
645 hardware. I2C can be useful in SPL to configure power management
646 ICs (PMICs) before raising the CPU clock speed, for example.
647 Enable this option to build the drivers in drivers/i2c as part of
650 config SPL_LIBCOMMON_SUPPORT
651 bool "Support common libraries"
653 Enable support for common U-Boot libraries within SPL. These
654 libraries include common code to deal with U-Boot images,
655 environment and USB, for example. This option is enabled on many
656 boards. Enable this option to build the code in common/ as part of
659 config SPL_LIBDISK_SUPPORT
660 bool "Support disk partitions"
663 Enable support for disk partitions within SPL. 'Disk' is something
664 of a misnomer as it includes non-spinning media such as flash (as
665 used in MMC and USB sticks). Partitions provide a way for a disk
666 to be split up into separate regions, with a partition table placed
667 at the start or end which describes the location and size of each
668 'partition'. These partitions are typically uses as individual block
669 devices, typically with an EXT2 or FAT filesystem in each. This
670 option enables whatever partition support has been enabled in
671 U-Boot to also be used in SPL. It brings in the code in disk/.
673 config SPL_LIBGENERIC_SUPPORT
674 bool "Support generic libraries"
676 Enable support for generic U-Boot libraries within SPL. These
677 libraries include generic code to deal with device tree, hashing,
678 printf(), compression and the like. This option is enabled on many
679 boards. Enable this option to build the code in lib/ as part of an
682 config SPL_DM_MAILBOX
683 bool "Support Mailbox"
685 Enable support for Mailbox within SPL. This enable the inter
686 processor communication protocols tobe used within SPL. Enable
687 this option to build the drivers in drivers/mailbox as part of
693 select HAVE_BLOCK_DEVICE
695 Enable support for MMC (Multimedia Card) within SPL. This enables
696 the MMC protocol implementation and allows any enabled drivers to
697 be used within SPL. MMC can be used with or without disk partition
698 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
699 this option to build the drivers in drivers/mmc as part of an SPL
702 config SYS_MMCSD_FS_BOOT_PARTITION
703 int "MMC Boot Partition"
706 Partition on the MMC to load U-Boot from when the MMC is being
708 Use -1 as a special value to use the first bootable partition.
711 bool "Tiny MMC framework in SPL"
714 Enable MMC framework tinification support. This option is useful if
715 if your SPL is extremely size constrained. Heed the warning, enable
716 this option if and only if you know exactly what you are doing, if
717 you are reading this help text, you most likely have no idea :-)
719 The MMC framework is reduced to bare minimum to be useful. No malloc
720 support is needed for the MMC framework operation with this option
721 enabled. The framework supports exactly one MMC device and exactly
722 one MMC driver. The MMC driver can be adjusted to avoid any malloc
723 operations too, which can remove the need for malloc support in SPL
724 and thus further reduce footprint.
727 bool "MMC/SD/SDIO card support for write operations in SPL"
730 Enable write access to MMC and SD Cards in SPL
733 config SPL_MPC8XXX_INIT_DDR
734 bool "Support MPC8XXX DDR init"
736 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
737 random-access memory) on the MPC8XXX family within SPL. This
738 allows DRAM to be set up before loading U-Boot into that DRAM,
741 config SPL_MTD_SUPPORT
742 bool "Support MTD drivers"
744 Enable support for MTD (Memory Technology Device) within SPL. MTD
745 provides a block interface over raw NAND and can also be used with
746 SPI flash. This allows SPL to load U-Boot from supported MTD
747 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
748 to enable specific MTD drivers.
751 bool "Support new Mentor Graphics USB"
753 Enable support for Mentor Graphics USB in SPL. This is a new
754 driver used by some boards. Enable this option to build
755 the drivers in drivers/usb/musb-new as part of an SPL build. The
756 old drivers are in drivers/usb/musb.
758 config SPL_NAND_SUPPORT
759 bool "Support NAND flash"
761 Enable support for NAND (Negative AND) flash in SPL. NAND flash
762 can be used to allow SPL to load U-Boot from supported devices.
763 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
766 config SPL_NAND_DRIVERS
767 bool "Use standard NAND driver"
769 SPL uses normal NAND drivers, not minimal drivers.
772 bool "Include standard software ECC in the SPL"
774 config SPL_NAND_SIMPLE
775 bool "Support simple NAND drivers in SPL"
777 Support for NAND boot using simple NAND drivers that
778 expose the cmd_ctrl() interface.
781 depends on SPL_NAND_DRIVERS
782 bool "Use Base NAND Driver"
784 Include nand_base.c in the SPL.
786 config SPL_NAND_IDENT
787 depends on SPL_NAND_BASE
788 bool "Use chip ID to identify NAND flash"
790 SPL uses the chip ID list to identify the NAND flash.
795 Enable support for loading payloads from UBI. See
796 README.ubispl for more info.
800 bool "Support SPI DM drivers in SPL"
802 Enable support for SPI DM drivers in SPL.
804 config SPL_DM_SPI_FLASH
805 bool "Support SPI DM FLASH drivers in SPL"
807 Enable support for SPI DM flash drivers in SPL.
811 config SPL_UBI_LOAD_BY_VOLNAME
812 bool "Support loading volumes by name"
814 This enables support for loading UBI volumes by name. When this
815 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
816 configure the volume name from which to load U-Boot.
818 config SPL_UBI_MAX_VOL_LEBS
819 int "Maximum number of LEBs per volume"
822 The maximum number of logical eraseblocks which a static volume
823 to load can contain. Used for sizing the scan data structure.
825 config SPL_UBI_MAX_PEB_SIZE
826 int "Maximum PEB size"
829 The maximum physical erase block size.
831 config SPL_UBI_MAX_PEBS
832 int "Maximum number of PEBs"
835 The maximum physical erase block size. If not overridden by
836 board code, this value will be used as the actual number of PEBs.
838 config SPL_UBI_PEB_OFFSET
839 int "Offset to first UBI PEB"
842 The offset in number of PEBs from the start of flash to the first
843 PEB part of the UBI image.
845 config SPL_UBI_VID_OFFSET
846 int "Offset to VID header"
849 config SPL_UBI_LEB_START
850 int "Offset to LEB in PEB"
853 The offset in bytes to the LEB within a PEB.
855 config SPL_UBI_INFO_ADDR
856 hex "Address to place UBI scan info"
859 Address for ubispl to place the scan info. Read README.ubispl to
860 determine the required size
862 config SPL_UBI_VOL_IDS
863 int "Maximum volume id"
866 The maximum volume id which can be loaded. Used for sizing the
869 config SPL_UBI_LOAD_MONITOR_ID
870 int "id of U-Boot volume"
873 The UBI volume id from which to load U-Boot
875 config SPL_UBI_LOAD_MONITOR_VOLNAME
876 string "volume name of U-Boot volume"
877 depends on SPL_UBI_LOAD_BY_VOLNAME
879 The UBI volume name from which to load U-Boot
881 config SPL_UBI_LOAD_KERNEL_ID
882 int "id of kernel volume"
883 depends on SPL_OS_BOOT && SPL_UBI
885 The UBI volume id from which to load the kernel
887 config SPL_UBI_LOAD_ARGS_ID
888 int "id of kernel args volume"
889 depends on SPL_OS_BOOT && SPL_UBI
891 The UBI volume id from which to load the device tree
893 config UBI_SPL_SILENCE_MSG
894 bool "silence UBI SPL messages"
896 Disable messages from UBI SPL. This leaves warnings
902 bool "Support networking"
904 Enable support for network devices (such as Ethernet) in SPL.
905 This permits SPL to load U-Boot over a network link rather than
906 from an on-board peripheral. Environment support is required since
907 the network stack uses a number of environment variables. See also
911 config SPL_NET_VCI_STRING
912 string "BOOTP Vendor Class Identifier string sent by SPL"
914 As defined by RFC 2132 the vendor class identifier field can be
915 sent by the client to identify the vendor type and configuration
916 of a client. This is often used in practice to allow for the DHCP
917 server to specify different files to load depending on if the ROM,
918 SPL or U-Boot itself makes the request
921 config SPL_NO_CPU_SUPPORT
922 bool "Drop CPU code in SPL"
924 This is specific to the ARM926EJ-S CPU. It disables the standard
925 start.S start-up code, presumably so that a replacement can be
926 used on that CPU. You should not enable it unless you know what
929 config SPL_NOR_SUPPORT
930 bool "Support NOR flash"
932 Enable support for loading U-Boot from memory-mapped NOR (Negative
933 OR) flash in SPL. NOR flash is slow to write but fast to read, and
934 a memory-mapped device makes it very easy to access. Loading from
935 NOR is typically achieved with just a memcpy().
937 config SPL_XIP_SUPPORT
941 Enable support for execute in place of U-Boot or kernel image. There
942 is no need to copy image from flash to ram if flash supports execute
943 in place. Its very useful in systems having enough flash but not
944 enough ram to load the image.
946 config SPL_ONENAND_SUPPORT
947 bool "Support OneNAND flash"
949 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
950 a type of NAND flash and therefore can be used to allow SPL to
951 load U-Boot from supported devices. This enables the drivers in
952 drivers/mtd/onenand as part of an SPL build.
955 bool "Activate Falcon Mode"
956 depends on !TI_SECURE_DEVICE
958 Enable booting directly to an OS from SPL.
959 for more info read doc/README.falcon
963 hex "addr, where OS is found"
964 depends on SPL_NOR_SUPPORT
966 Specify the address, where the OS image is found, which
971 config SPL_FALCON_BOOT_MMCSD
972 bool "Enable Falcon boot from MMC or SD media"
973 depends on SPL_OS_BOOT && SPL_MMC
975 Select this if the Falcon mode OS image mode is on MMC or SD media.
977 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
978 hex "Falcon mode: Sector to load kernel uImage from MMC"
979 depends on SPL_FALCON_BOOT_MMCSD
981 When Falcon mode is used with an MMC or SD media, SPL needs to know
982 where to look for the kernel uImage. The image is expected to begin
983 at the raw MMC specified in this config.
984 Note that the Falcon mode image can also be a FIT, if FIT support is
989 default "tpl/u-boot-with-tpl.bin" if TPL
992 Payload for SPL boot. For backward compatibility, default to
993 u-boot.bin, i.e. RAW image without any header. In case of
994 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
998 bool "Support PCI drivers"
1000 Enable support for PCI in SPL. For platforms that need PCI to boot,
1001 or must perform some init using PCI in SPL, this provides the
1002 necessary driver support. This enables the drivers in drivers/pci
1003 as part of an SPL build.
1006 bool "Support PCH drivers"
1008 Enable support for PCH (Platform Controller Hub) devices in SPL.
1009 These are used to set up GPIOs and the SPI peripheral early in
1010 boot. This enables the drivers in drivers/pch as part of an SPL
1013 config SPL_POST_MEM_SUPPORT
1014 bool "Support POST drivers"
1016 Enable support for POST (Power-on Self Test) in SPL. POST is a
1017 procedure that checks that the hardware (CPU or board) appears to
1018 be functionally correctly. It is a sanity check that can be
1019 performed before booting. This enables the drivers in post/drivers
1020 as part of an SPL build.
1023 bool "Support reset drivers"
1026 Enable support for reset control in SPL.
1027 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1028 by using the generic reset API provided by driver model.
1029 This enables the drivers in drivers/reset as part of an SPL build.
1032 bool "Support power drivers"
1034 Enable support for power control in SPL. This includes support
1035 for PMICs (Power-management Integrated Circuits) and some of the
1036 features provided by PMICs. In particular, voltage regulators can
1037 be used to enable/disable power and vary its voltage. That can be
1038 useful in SPL to turn on boot peripherals and adjust CPU voltage
1039 so that the clock speed can be increased. This enables the drivers
1040 in drivers/power, drivers/power/pmic and drivers/power/regulator
1041 as part of an SPL build.
1043 config SPL_POWER_DOMAIN
1044 bool "Support power domain drivers"
1047 Enable support for power domain control in SPL. Many SoCs allow
1048 power to be applied to or removed from portions of the SoC (power
1049 domains). This may be used to save power. This API provides the
1050 means to control such power management hardware. This enables
1051 the drivers in drivers/power/domain as part of a SPL build.
1053 config SPL_RAM_SUPPORT
1054 bool "Support booting from RAM"
1055 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1057 Enable booting of an image in RAM. The image can be preloaded or
1058 it can be loaded by SPL directly into RAM (e.g. using USB).
1060 config SPL_RAM_DEVICE
1061 bool "Support booting from preloaded image in RAM"
1062 depends on SPL_RAM_SUPPORT
1063 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1065 Enable booting of an image already loaded in RAM. The image has to
1066 be already in memory when SPL takes over, e.g. loaded by the boot
1069 config SPL_REMOTEPROC
1070 bool "Support REMOTEPROCS"
1072 Enable support for REMOTEPROCs in SPL. This permits to load
1073 a remote processor firmware in SPL.
1076 bool "Support RTC drivers"
1078 Enable RTC (Real-time Clock) support in SPL. This includes support
1079 for reading and setting the time. Some RTC devices also have some
1080 non-volatile (battery-backed) memory which is accessible if
1081 needed. This enables the drivers in drivers/rtc as part of an SPL
1085 bool "Support loading from SATA"
1087 Enable support for SATA (Serial AT attachment) in SPL. This allows
1088 use of SATA devices such as hard drives and flash drivers for
1089 loading U-Boot. SATA is used in higher-end embedded systems and
1090 can provide higher performance than MMC , at somewhat higher
1091 expense and power consumption. This enables loading from SATA
1092 using a configured device.
1094 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1095 bool "SATA raw mode: by sector"
1097 default y if ARCH_MVEBU
1099 Use sector number for specifying U-Boot location on SATA disk in
1102 config SPL_SATA_RAW_U_BOOT_SECTOR
1103 hex "Sector on the SATA disk to load U-Boot from"
1104 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1105 default 0x1 if ARCH_MVEBU
1107 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1108 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1111 bool "Support serial"
1115 Enable support for serial in SPL. This allows use of a serial UART
1116 for displaying messages while SPL is running. It also brings in
1117 printf() and panic() functions. This should normally be enabled
1118 unless there are space reasons not to. Even then, consider
1119 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1122 bool "Support SPI drivers"
1124 Enable support for using SPI in SPL. This is used for connecting
1125 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1126 more details on that. The SPI driver provides the transport for
1127 data between the SPI flash and the CPU. This option can be used to
1128 enable SPI drivers that are needed for other purposes also, such
1131 config SPL_SPI_FLASH_SUPPORT
1132 bool "Support SPI flash drivers"
1135 Enable support for using SPI flash in SPL, and loading U-Boot from
1136 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1137 the SPI bus that is used to connect it to a system. It is a simple
1138 but fast bidirectional 4-wire bus (clock, chip select and two data
1139 lines). This enables the drivers in drivers/mtd/spi as part of an
1140 SPL build. This normally requires SPL_SPI.
1142 if SPL_SPI_FLASH_SUPPORT
1144 config SPL_SPI_FLASH_TINY
1145 bool "Enable low footprint SPL SPI Flash support"
1146 depends on !SPI_FLASH_BAR
1147 default y if SPI_FLASH
1149 Enable lightweight SPL SPI Flash support that supports just reading
1150 data/images from flash. No support to write/erase flash. Enable
1151 this if you have SPL size limitations and don't need full
1152 fledged SPI flash support.
1154 config SPL_SPI_FLASH_SFDP_SUPPORT
1155 bool "SFDP table parsing support for SPI NOR flashes"
1156 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1158 Enable support for parsing and auto discovery of parameters for
1159 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1160 tables as per JESD216 standard in SPL.
1162 config SPL_SPI_FLASH_MTD
1163 bool "Support for SPI flash MTD drivers in SPL"
1165 Enable support for SPI flash MTD drivers in SPL.
1168 bool "Support loading from SPI flash"
1170 Enable support for loading next stage, U-Boot or otherwise, from
1171 SPI NOR in U-Boot SPL.
1173 endif # SPL_SPI_FLASH_SUPPORT
1175 config SYS_SPI_U_BOOT_OFFS
1176 hex "address of u-boot payload in SPI flash"
1177 default 0x8000 if ARCH_SUNXI
1179 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1181 Address within SPI-Flash from where the u-boot payload is fetched
1185 bool "Driver support for thermal devices"
1187 Enable support for temperature-sensing devices. Some SoCs have on-chip
1188 temperature sensors to permit warnings, speed throttling or even
1189 automatic power-off when the temperature gets too high or low. Other
1190 devices may be discrete but connected on a suitable bus.
1193 bool "Support USB host drivers"
1194 select HAVE_BLOCK_DEVICE
1196 Enable access to USB (Universal Serial Bus) host devices so that
1197 SPL can load U-Boot from a connected USB peripheral, such as a USB
1198 flash stick. While USB takes a little longer to start up than most
1199 buses, it is very flexible since many different types of storage
1200 device can be attached. This option enables the drivers in
1201 drivers/usb/host as part of an SPL build.
1203 config SPL_USB_STORAGE
1204 bool "Support loading from USB"
1205 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1207 Enable support for USB devices in SPL. This allows use of USB
1208 devices such as hard drives and flash drivers for loading U-Boot.
1209 The actual drivers are enabled separately using the normal U-Boot
1210 config options. This enables loading from USB using a configured
1213 config SPL_USB_GADGET
1214 bool "Suppport USB Gadget drivers"
1216 Enable USB Gadget API which allows to enable USB device functions
1221 config SPL_USB_ETHER
1222 bool "Support USB Ethernet drivers"
1225 Enable access to the USB network subsystem and associated
1226 drivers in SPL. This permits SPL to load U-Boot over a
1227 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1228 than from an onboard peripheral. Environment support is required
1229 since the network stack uses a number of environment variables.
1230 See also SPL_NET and SPL_ETH.
1233 bool "Support DFU (Device Firmware Upgrade)"
1235 select SPL_DFU_NO_RESET
1236 depends on SPL_RAM_SUPPORT
1238 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1239 RAM memory device support. The ROM code will load and execute
1240 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1241 selected device partition from host-pc using dfu-utils.
1242 This feature is useful to flash the binaries to factory or bare-metal
1243 boards using USB interface.
1246 bool "DFU device selection"
1251 depends on SPL_DFU && SPL_RAM_SUPPORT
1253 select RAM/DDR memory device for loading binary images
1254 (u-boot/kernel) to the selected device partition using
1255 DFU and execute the u-boot/kernel from RAM.
1259 config SPL_USB_SDP_SUPPORT
1260 bool "Support SDP (Serial Download Protocol)"
1261 depends on SPL_SERIAL
1263 Enable Serial Download Protocol (SDP) device support in SPL. This
1264 allows to download images into memory and execute (jump to) them
1265 using the same protocol as implemented by the i.MX family's boot ROM.
1267 config SPL_SDP_USB_DEV
1268 int "SDP USB controller index"
1270 depends on SPL_USB_SDP_SUPPORT
1272 Some boards have USB controller other than 0. Define this option
1273 so it can be used in compiled environment.
1277 bool "Support watchdog drivers"
1278 imply SPL_WDT if !HW_WATCHDOG
1280 Enable support for watchdog drivers in SPL. A watchdog is
1281 typically a hardware peripheral which can reset the system when it
1282 detects no activity for a while (such as a software crash). This
1283 enables the drivers in drivers/watchdog as part of an SPL build.
1285 config SPL_YMODEM_SUPPORT
1286 bool "Support loading using Ymodem"
1287 depends on SPL_SERIAL
1289 While loading from serial is slow it can be a useful backup when
1290 there is no other option. The Ymodem protocol provides a reliable
1291 means of transmitting U-Boot over a serial line for using in SPL,
1292 with a checksum to ensure correctness.
1295 bool "Support ARM Trusted Firmware"
1296 depends on ARM64 && SPL_FIT
1298 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1299 is loaded by SPL (which is considered as BL2 in ATF terminology).
1300 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1302 config SPL_ATF_LOAD_IMAGE_V2
1303 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1306 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1308 If you want to load a bl31 image from the SPL and need the new
1311 config SPL_ATF_NO_PLATFORM_PARAM
1312 bool "Pass no platform parameter"
1315 While we expect to call a pointer to a valid FDT (or NULL)
1316 as the platform parameter to an ATF, some ATF versions are
1317 not U-Boot aware and have an insufficiently robust parameter
1318 validation to gracefully reject a FDT being passed.
1320 If this option is enabled, the spl_atf os-type handler will
1321 always pass NULL for the platform parameter.
1323 If your ATF is affected, say Y.
1325 config SPL_AM33XX_ENABLE_RTC32K_OSC
1326 bool "Enable the RTC32K OSC on AM33xx based platforms"
1329 Enable access to the AM33xx RTC and select the external 32kHz clock
1332 config SPL_OPTEE_IMAGE
1333 bool "Support OP-TEE Trusted OS image in SPL"
1336 OP-TEE is an open source Trusted OS which is loaded by SPL.
1337 More detail at: https://github.com/OP-TEE/optee_os
1340 bool "Support RISC-V OpenSBI"
1341 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1343 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1344 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1345 firmware. It is loaded and started by U-Boot SPL.
1347 More details are available at https://github.com/riscv/opensbi and
1348 https://github.com/riscv/riscv-sbi-doc
1350 config SPL_OPENSBI_LOAD_ADDR
1351 hex "OpenSBI load address"
1352 depends on SPL_OPENSBI
1354 Load address of the OpenSBI binary.
1358 depends on SUPPORT_TPL
1361 If you want to build TPL as well as the normal image and SPL, say Y.
1365 config TPL_SIZE_LIMIT
1366 hex "Maximum size of TPL image"
1370 Specifies the maximum length of the U-Boot TPL image.
1371 If this value is zero, it is ignored.
1373 config TPL_BINMAN_SYMBOLS
1374 bool "Declare binman symbols in TPL"
1375 depends on SPL_FRAMEWORK && BINMAN
1378 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1379 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1380 and spl_get_image_size().
1382 For this to work, you must have a U-Boot image in the binman image, so
1383 binman can update TPL with the location of it.
1385 config TPL_FRAMEWORK
1386 bool "Support TPL based upon the common SPL framework"
1387 default y if SPL_FRAMEWORK
1389 Enable the SPL framework under common/spl/ for TPL builds.
1390 This framework supports MMC, NAND and YMODEM and other methods
1391 loading of U-Boot's SPL stage. If unsure, say Y.
1394 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1395 depends on HANDOFF && TPL_BLOBLIST
1398 This option enables TPL to write handoff information. This can be
1399 used to pass information like the size of SDRAM from TPL to U-Boot
1400 proper. The information is also available to SPL if it is useful
1403 config TPL_BOARD_INIT
1404 bool "Call board-specific initialization in TPL"
1406 If this option is enabled, U-Boot will call the function
1407 spl_board_init() from board_init_r(). This function should be
1408 provided by the board.
1410 config TPL_BOOTCOUNT_LIMIT
1411 bool "Support bootcount in TPL"
1412 depends on TPL_ENV_SUPPORT
1414 If this option is enabled, the TPL will support bootcount.
1415 For example, it may be useful to choose the device to boot.
1418 string "Linker script for the TPL stage"
1420 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1421 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1423 The TPL stage will usually require a different linker-script
1424 (as it runs from a different memory region) than the regular
1425 U-Boot stage. Set this to the path of the linker-script to
1428 May be left empty to trigger the Makefile infrastructure to
1429 fall back to the linker-script used for the SPL stage.
1431 config TPL_NEEDS_SEPARATE_STACK
1432 bool "TPL needs a separate initial stack-pointer"
1435 Enable, if the TPL stage should not inherit its initial
1436 stack-pointer from the settings for the SPL stage.
1439 bool "Support power drivers"
1441 Enable support for power control in TPL. This includes support
1442 for PMICs (Power-management Integrated Circuits) and some of the
1443 features provided by PMICs. In particular, voltage regulators can
1444 be used to enable/disable power and vary its voltage. That can be
1445 useful in TPL to turn on boot peripherals and adjust CPU voltage
1446 so that the clock speed can be increased. This enables the drivers
1447 in drivers/power, drivers/power/pmic and drivers/power/regulator
1448 as part of an TPL build.
1450 config TPL_TEXT_BASE
1451 hex "Base address for the .text section of the TPL stage"
1454 The base address for the .text section of the TPL stage.
1457 int "Maximum size (in bytes) for the TPL stage"
1461 The maximum size (in bytes) of the TPL stage.
1464 hex "Address of the initial stack-pointer for the TPL stage"
1465 depends on TPL_NEEDS_SEPARATE_STACK
1467 The address of the initial stack-pointer for the TPL stage.
1468 Usually this will be the (aligned) top-of-stack.
1470 config TPL_READ_ONLY
1472 depends on TPL_OF_PLATDATA
1473 select TPL_OF_PLATDATA_NO_BIND
1474 select TPL_OF_PLATDATA_RT
1476 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1477 section of memory. This means that of-platdata must make a copy (in
1478 writeable memory) of anything it wants to modify, such as
1479 device-private data.
1481 config TPL_BOOTROM_SUPPORT
1482 bool "Support returning to the BOOTROM (from TPL)"
1484 Some platforms (e.g. the Rockchip RK3368) provide support in their
1485 ROM for loading the next boot-stage after performing basic setup
1488 Enable this option, to return to the BOOTROM through the
1489 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1490 boot device list, if not implemented for a given board)
1493 bool "Support CRC32 in TPL"
1494 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1496 Enable this to support CRC32 in uImages or FIT images within SPL.
1497 This is a 32-bit checksum value that can be used to verify images.
1498 For FIT images, this is the least secure type of checksum, suitable
1499 for detected accidental image corruption. For secure applications you
1500 should consider SHA1 or SHA256.
1502 config TPL_DRIVERS_MISC
1503 bool "Support misc drivers in TPL"
1505 Enable miscellaneous drivers in TPL. These drivers perform various
1506 tasks that don't fall nicely into other categories, Enable this
1507 option to build the drivers in drivers/misc as part of an TPL
1508 build, for those that support building in TPL (not all drivers do).
1510 config TPL_ENV_SUPPORT
1511 bool "Support an environment"
1513 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1516 bool "Support GPIO in TPL"
1518 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1519 GPIOs allow U-Boot to read the state of an input line (high or
1520 low) and set the state of an output line. This can be used to
1521 drive LEDs, control power to various system parts and read user
1522 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1523 for example. Enable this option to build the drivers in
1524 drivers/gpio as part of an TPL build.
1529 Enable support for the I2C bus in TPL. See SPL_I2C for
1532 config TPL_LIBCOMMON_SUPPORT
1533 bool "Support common libraries"
1535 Enable support for common U-Boot libraries within TPL. See
1536 SPL_LIBCOMMON_SUPPORT for details.
1538 config TPL_LIBGENERIC_SUPPORT
1539 bool "Support generic libraries"
1541 Enable support for generic U-Boot libraries within TPL. See
1542 SPL_LIBGENERIC_SUPPORT for details.
1544 config TPL_MPC8XXX_INIT_DDR
1545 bool "Support MPC8XXX DDR init"
1547 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1548 SPL_MPC8XXX_INIT_DDR for details.
1554 Enable support for MMC within TPL. See SPL_MMC for details.
1556 config TPL_NAND_SUPPORT
1557 bool "Support NAND flash"
1559 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1562 bool "Support PCI drivers"
1564 Enable support for PCI in TPL. For platforms that need PCI to boot,
1565 or must perform some init using PCI in SPL, this provides the
1566 necessary driver support. This enables the drivers in drivers/pci
1567 as part of a TPL build.
1570 bool "Support PCH drivers"
1572 Enable support for PCH (Platform Controller Hub) devices in TPL.
1573 These are used to set up GPIOs and the SPI peripheral early in
1574 boot. This enables the drivers in drivers/pch as part of a TPL
1577 config TPL_RAM_SUPPORT
1578 bool "Support booting from RAM"
1580 Enable booting of an image in RAM. The image can be preloaded or
1581 it can be loaded by TPL directly into RAM (e.g. using USB).
1583 config TPL_RAM_DEVICE
1584 bool "Support booting from preloaded image in RAM"
1585 depends on TPL_RAM_SUPPORT
1587 Enable booting of an image already loaded in RAM. The image has to
1588 be already in memory when TPL takes over, e.g. loaded by the boot
1592 bool "Support RTC drivers"
1594 Enable RTC (Real-time Clock) support in TPL. This includes support
1595 for reading and setting the time. Some RTC devices also have some
1596 non-volatile (battery-backed) memory which is accessible if
1597 needed. This enables the drivers in drivers/rtc as part of an TPL
1601 bool "Support serial"
1605 Enable support for serial in TPL. See SPL_SERIAL for
1608 config TPL_SPI_FLASH_SUPPORT
1609 bool "Support SPI flash drivers"
1611 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1614 config TPL_SPI_FLASH_TINY
1615 bool "Enable low footprint TPL SPI Flash support"
1616 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1617 default y if SPI_FLASH
1619 Enable lightweight TPL SPI Flash support that supports just reading
1620 data/images from flash. No support to write/erase flash. Enable
1621 this if you have TPL size limitations and don't need full-fledged
1625 bool "Support loading from SPI flash"
1626 depends on TPL_SPI_FLASH_SUPPORT
1628 Enable support for loading next stage, U-Boot or otherwise, from
1629 SPI NOR in U-Boot TPL.
1632 bool "Support SPI drivers"
1634 Enable support for using SPI in TPL. See SPL_SPI for
1638 bool "Support SPI DM drivers in TPL"
1640 Enable support for SPI DM drivers in TPL.
1642 config TPL_DM_SPI_FLASH
1643 bool "Support SPI DM FLASH drivers in TPL"
1645 Enable support for SPI DM flash drivers in TPL.
1647 config TPL_YMODEM_SUPPORT
1648 bool "Support loading using Ymodem"
1649 depends on TPL_SERIAL
1651 While loading from serial is slow it can be a useful backup when
1652 there is no other option. The Ymodem protocol provides a reliable
1653 means of transmitting U-Boot over a serial line for using in TPL,
1654 with a checksum to ensure correctness.
1660 depends on SUPPORT_SPL
1663 If you want to build VPL as well as the normal image, TPL and SPL,
1668 config VPL_BANNER_PRINT
1669 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1673 If this option is enabled, VPL will print the banner with version
1674 info. Disabling this option could be useful to reduce VPL boot time
1675 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1677 config VPL_BOARD_INIT
1678 bool "Call board-specific initialization in VPL"
1680 If this option is enabled, U-Boot will call the function
1681 spl_board_init() from board_init_r(). This function should be
1682 provided by the board.
1686 bool "Support cache drivers in VPL"
1688 Enable support for cache drivers in VPL.
1691 bool "Support CRC32 in VPL"
1692 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1694 Enable this to support CRC32 in uImages or FIT images within VPL.
1695 This is a 32-bit checksum value that can be used to verify images.
1696 For FIT images, this is the least secure type of checksum, suitable
1697 for detected accidental image corruption. For secure applications you
1698 should consider SHA1 or SHA256.
1701 bool "Support SPI DM drivers in VPL"
1703 Enable support for SPI DM drivers in VPL.
1705 config VPL_DM_SPI_FLASH
1706 bool "Support SPI DM FLASH drivers in VPL"
1708 Enable support for SPI DM flash drivers in VPL.
1710 config VPL_FRAMEWORK
1711 bool "Support VPL based upon the common SPL framework"
1714 Enable the SPL framework under common/spl/ for VPL builds.
1715 This framework supports MMC, NAND and YMODEM and other methods
1716 loading of U-Boot's next stage. If unsure, say Y.
1719 bool "Pass hand-off information from VPL to SPL"
1720 depends on HANDOFF && VPL_BLOBLIST
1723 This option enables VPL to write handoff information. This can be
1724 used to pass information like the size of SDRAM from VPL to SPL. Also
1725 VPL can receive information from TPL in the same place if that is
1728 config VPL_LIBCOMMON_SUPPORT
1729 bool "Support common libraries"
1730 default y if SPL_LIBCOMMON_SUPPORT
1732 Enable support for common U-Boot libraries within VPL. See
1733 SPL_LIBCOMMON_SUPPORT for details.
1735 config VPL_LIBGENERIC_SUPPORT
1736 bool "Support generic libraries"
1737 default y if SPL_LIBGENERIC_SUPPORT
1739 Enable support for generic U-Boot libraries within VPL. These
1740 libraries include generic code to deal with device tree, hashing,
1741 printf(), compression and the like. This option is enabled on many
1742 boards. Enable this option to build the code in lib/ as part of a
1745 config VPL_DRIVERS_MISC
1746 bool "Support misc drivers"
1747 default y if TPL_DRIVERS_MISC
1749 Enable miscellaneous drivers in VPL. These drivers perform various
1750 tasks that don't fall nicely into other categories, Enable this
1751 option to build the drivers in drivers/misc as part of a VPL
1752 build, for those that support building in VPL (not all drivers do).
1754 config VPL_ENV_SUPPORT
1755 bool "Support an environment"
1757 Enable environment support in VPL. The U-Boot environment provides
1758 a number of settings (essentially name/value pairs) which can
1759 control many aspects of U-Boot's operation. Enabling this option will
1760 make env_get() and env_set() available in VSPL.
1763 bool "Support GPIO in VPL"
1764 default y if SPL_GPIO
1766 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1767 GPIOs allow U-Boot to read the state of an input line (high or
1768 low) and set the state of an output line. This can be used to
1769 drive LEDs, control power to various system parts and read user
1770 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1771 for example. Enable this option to build the drivers in
1772 drivers/gpio as part of a VPL build.
1775 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1776 depends on HANDOFF && VPL_BLOBLIST
1779 This option enables VPL to write handoff information. This can be
1780 used to pass information like the size of SDRAM from VPL to U-Boot
1781 proper. The information is also available to VPL if it is useful
1785 bool "Support hashing drivers in VPL"
1790 Enable hashing drivers in VPL. These drivers can be used to
1791 accelerate secure boot processing in secure applications. Enable
1792 this option to build system-specific drivers for hash acceleration
1793 as part of a VPL build.
1795 config VPL_I2C_SUPPORT
1796 bool "Support I2C in VPL"
1797 default y if SPL_I2C_SUPPORT
1799 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1802 config VPL_PCH_SUPPORT
1803 bool "Support PCH drivers"
1804 default y if TPL_PCH_SUPPORT
1806 Enable support for PCH (Platform Controller Hub) devices in VPL.
1807 These are used to set up GPIOs and the SPI peripheral early in
1808 boot. This enables the drivers in drivers/pch as part of a VPL
1812 bool "Support PCI drivers"
1813 default y if SPL_PCI
1815 Enable support for PCI in VPL. For platforms that need PCI to boot,
1816 or must perform some init using PCI in VPL, this provides the
1817 necessary driver support. This enables the drivers in drivers/pci
1818 as part of a VPL build.
1821 bool "Support RTC drivers"
1823 Enable RTC (Real-time Clock) support in VPL. This includes support
1824 for reading and setting the time. Some RTC devices also have some
1825 non-volatile (battery-backed) memory which is accessible if
1826 needed. This enables the drivers in drivers/rtc as part of a VPL
1830 bool "Support serial"
1831 default y if TPL_SERIAL
1835 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1838 config VPL_SIZE_LIMIT
1839 hex "Maximum size of VPL image"
1843 Specifies the maximum length of the U-Boot VPL image.
1844 If this value is zero, it is ignored.
1847 bool "Support SPI drivers"
1849 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
1852 config VPL_SPI_FLASH_SUPPORT
1853 bool "Support SPI flash drivers"
1855 Enable support for using SPI flash in VPL, and loading U-Boot from
1856 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1857 the SPI bus that is used to connect it to a system. It is a simple
1858 but fast bidirectional 4-wire bus (clock, chip select and two data
1859 lines). This enables the drivers in drivers/mtd/spi as part of a
1860 VPL build. This normally requires VPL_SPI_SUPPORT.
1862 config VPL_TEXT_BASE
1866 The address in memory that VPL will be running from.
1870 config SPL_AT91_MCK_BYPASS
1871 bool "Use external clock signal as a source of main clock for AT91 platforms"
1872 depends on ARCH_AT91
1874 Use external 8 to 24 Mhz clock signal as source of main clock instead
1875 of an external crystal oscillator.
1876 This option disables the internal driving on the XOUT pin.
1877 The external source has to provide a stable clock on the XIN pin.
1878 If this option is disabled, the SoC expects a crystal oscillator
1879 that needs driving on both XIN and XOUT lines.