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
144 bool "Pass hand-off information from SPL to U-Boot proper"
145 depends on SPL && BLOBLIST
147 It is useful to be able to pass information from SPL to U-Boot
148 proper to preserve state that is known in SPL and is needed in U-Boot.
149 Enable this to locate the handoff information in U-Boot proper, early
150 in boot. It is available in gd->handoff. The state state is set up
151 in SPL (or TPL if that is being used).
156 bool "Pass hand-off information from SPL to U-Boot proper"
157 depends on HANDOFF && SPL_BLOBLIST
160 This option enables SPL to write handoff information. This can be
161 used to pass information like the size of SDRAM from SPL to U-Boot
162 proper. Also SPL can receive information from TPL in the same place
166 string "Linker script for the SPL stage"
167 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
169 The SPL stage will usually require a different linker-script
170 (as it runs from a different memory region) than the regular
171 U-Boot stage. Set this to the path of the linker-script to
176 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
177 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
178 default 0x20060 if SUN50I_GEN_H6
179 default 0x00060 if ARCH_SUNXI
180 default 0xfffc0000 if ARCH_ZYNQMP
183 The address in memory that SPL will be running from.
185 config SPL_BOARD_INIT
186 bool "Call board-specific initialization in SPL"
188 If this option is enabled, U-Boot will call the function
189 spl_board_init() from board_init_r(). This function should be
190 provided by the board.
192 config VPL_BOARD_INIT
193 bool "Call board-specific initialization in VPL"
195 If this option is enabled, U-Boot will call the function
196 spl_board_init() from board_init_r(). This function should be
197 provided by the board.
199 config SPL_BOOTROM_SUPPORT
200 bool "Support returning to the BOOTROM"
202 Some platforms (e.g. the Rockchip RK3368) provide support in their
203 ROM for loading the next boot-stage after performing basic setup
206 Enable this option, to return to the BOOTROM through the
207 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
208 boot device list, if not implemented for a given board)
210 config SPL_BOOTCOUNT_LIMIT
211 bool "Support bootcount in SPL"
212 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
214 On some boards, which use 'falcon' mode, it is necessary to check
215 and increment the number of boot attempts. Such boards do not
216 use proper U-Boot for normal boot flow and hence needs those
217 adjustments to be done in the SPL.
219 config SPL_RAW_IMAGE_SUPPORT
220 bool "Support SPL loading and booting of RAW images"
221 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
223 depends on !TI_SECURE_DEVICE
225 SPL will support loading and booting a RAW image when this option
226 is y. If this is not set, SPL will move on to other available
227 boot media to find a suitable image.
229 config SPL_LEGACY_IMAGE_FORMAT
230 bool "Support SPL loading and booting of Legacy images"
231 default y if !SPL_LOAD_FIT
232 depends on !TI_SECURE_DEVICE
234 SPL will support loading and booting Legacy images when this option
235 is y. If this is not set, SPL will move on to other available
236 boot media to find a suitable image.
238 config SPL_LEGACY_IMAGE_CRC_CHECK
239 bool "Check CRC of Legacy images"
240 depends on SPL_LEGACY_IMAGE_FORMAT
243 Enable this to check the CRC of Legacy images. While this increases
244 reliability, it affects both code size and boot duration.
245 If disabled, Legacy images are booted if the image magic and size
246 are correct, without further integrity checks.
248 config SPL_SYS_MALLOC_SIMPLE
250 prompt "Only use malloc_simple functions in the SPL"
252 Say Y here to only use the *_simple malloc functions from
253 malloc_simple.c, rather then using the versions from dlmalloc.c;
254 this will make the SPL binary smaller at the cost of more heap
255 usage as the *_simple malloc functions do not re-use free-ed mem.
257 config TPL_SYS_MALLOC_SIMPLE
259 prompt "Only use malloc_simple functions in the TPL"
262 Say Y here to only use the *_simple malloc functions from
263 malloc_simple.c, rather then using the versions from dlmalloc.c;
264 this will make the TPL binary smaller at the cost of more heap
265 usage as the *_simple malloc functions do not re-use free-ed mem.
268 bool "Enable SDRAM location for SPL stack"
270 SPL starts off execution in SRAM and thus typically has only a small
271 stack available. Since SPL sets up DRAM while in its board_init_f()
272 function, it is possible for the stack to move there before
273 board_init_r() is reached. This option enables a special SDRAM
274 location for the SPL stack. U-Boot SPL switches to this after
275 board_init_f() completes, and before board_init_r() starts.
277 config SPL_STACK_R_ADDR
278 depends on SPL_STACK_R
279 hex "SDRAM location for SPL stack"
280 default 0x82000000 if ARCH_OMAP2PLUS
282 Specify the address in SDRAM for the SPL stack. This will be set up
283 before board_init_r() is called.
285 config SPL_STACK_R_MALLOC_SIMPLE_LEN
286 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
287 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
290 Specify the amount of the stack to use as memory pool for
291 malloc_simple after switching the stack to DRAM. This may be set
292 to give board_init_r() a larger heap then the initial heap in
293 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
295 config SPL_SEPARATE_BSS
296 bool "BSS section is in a different memory region from text"
298 Some platforms need a large BSS region in SPL and can provide this
299 because RAM is already set up. In this case BSS can be moved to RAM.
300 This option should then be enabled so that the correct device tree
301 location is used. Normally we put the device tree at the end of BSS
302 but with this option enabled, it goes at _image_binary_end.
306 depends on SPL_OF_PLATDATA
307 # Bind cannot be supported because the udevice structs are in read-only
308 # memory so we cannot update the linked lists.
309 select SPL_OF_PLATDATA_NO_BIND
310 select SPL_OF_PLATDATA_RT
312 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
313 section of memory. This means that of-platdata must make a copy (in
314 writeable memory) of anything it wants to modify, such as
317 config TPL_SEPARATE_BSS
318 bool "BSS section is in a different memory region from text"
319 default y if SPL_SEPARATE_BSS
321 Some platforms need a large BSS region in TPL and can provide this
322 because RAM is already set up. In this case BSS can be moved to RAM.
323 This option should then be enabled so that the correct device tree
324 location is used. Normally we put the device tree at the end of BSS
325 but with this option enabled, it goes at _image_binary_end.
327 config SPL_BANNER_PRINT
328 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
331 If this option is enabled, SPL will print the banner with version
332 info. Disabling this option could be useful to reduce SPL boot time
333 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
335 config TPL_BANNER_PRINT
336 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
340 If this option is enabled, TPL will print the banner with version
341 info. Disabling this option could be useful to reduce TPL boot time
342 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
345 depends on ARM && !ARM64
346 bool "Allows initializing BSS early before entering board_init_f"
348 On some platform we have sufficient memory available early on to
349 allow setting up and using a basic BSS prior to entering
350 board_init_f. Activating this option will also de-activate the
351 clearing of BSS during the SPL relocation process, thus allowing
352 to carry state from board_init_f to board_init_r by way of BSS.
354 config SPL_DISPLAY_PRINT
355 bool "Display a board-specific message in SPL"
357 If this option is enabled, U-Boot will call the function
358 spl_display_print() immediately after displaying the SPL console
359 banner ("U-Boot SPL ..."). This function should be provided by
362 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
363 bool "MMC raw mode: by sector"
364 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
365 ARCH_MX6 || ARCH_MX7 || \
366 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
367 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
368 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
369 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
371 Use sector number for specifying U-Boot location on MMC/SD in
374 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
375 hex "Address on the MMC to load U-Boot from"
376 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
377 default 0x40 if ARCH_SUNXI
378 default 0x75 if ARCH_DAVINCI
379 default 0x8a if ARCH_MX6 || ARCH_MX7
380 default 0x100 if ARCH_UNIPHIER
381 default 0x0 if ARCH_MVEBU
382 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
383 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
384 OMAP54XX || AM33XX || AM43XX || ARCH_K3
385 default 0x4000 if ARCH_ROCKCHIP
386 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
388 Address on the MMC to load U-Boot from, when the MMC is being used
389 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
391 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
392 hex "U-Boot main hardware partition image offset"
393 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
394 default 0x10 if ARCH_SUNXI
397 On some platforms SPL location depends on hardware partition. The ROM
398 code skips the MBR sector when loading SPL from main hardware data
399 partition. This adds offset to the main U-Boot image. Set this symbol
400 to the number of skipped sectors.
402 If unsure, leave the default.
404 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
405 bool "MMC Raw mode: by partition"
407 Use a partition for loading U-Boot when using MMC/SD in raw mode.
409 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
410 hex "Partition to use to load U-Boot from"
411 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
414 Partition on the MMC to load U-Boot from when the MMC is being
417 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
418 bool "MMC raw mode: by partition type"
419 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
421 Use partition type for specifying U-Boot partition on MMC/SD in
422 raw mode. U-Boot will be loaded from the first partition of this
425 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
426 hex "Partition Type on the MMC to load U-Boot from"
427 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
429 Partition Type on the MMC to load U-Boot from, when the MMC is being
432 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
433 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
434 depends on SUPPORT_EMMC_BOOT
436 eMMC boot partition is normally configured by the bits of the EXT_CSD
437 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
438 cases it might be required in SPL to load the image from different
439 partition than the partition selected by EXT_CSC_PART_CONFIG register.
440 Enable this option if you intend to use an eMMC boot partition other
441 then selected via EXT_CSC_PART_CONFIG register and specify the custom
442 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
445 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
446 int "Number of the eMMC boot partition to use"
447 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
450 eMMC boot partition number to use when the eMMC in raw mode and
451 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
452 by user defined partition number.
456 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
457 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
459 Enable this to support CRC32 in uImages or FIT images within SPL.
460 This is a 32-bit checksum value that can be used to verify images.
461 For FIT images, this is the least secure type of checksum, suitable
462 for detected accidental image corruption. For secure applications you
463 should consider SHA1 or SHA256.
469 Enable this to support MD5 in FIT images within SPL. An MD5
470 checksum is a 128-bit hash value used to check that the image
471 contents have not been corrupted. Note that MD5 is not considered
472 secure as it is possible (with a brute-force attack) to adjust the
473 image while still retaining the same MD5 hash value. For secure
474 applications where images may be changed maliciously, you should
475 consider SHA256 or SHA384.
477 config SPL_FIT_IMAGE_TINY
478 bool "Remove functionality from SPL FIT loading to reduce size"
480 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
481 default y if ARCH_IMX8M
483 Enable this to reduce the size of the FIT image loading code
484 in SPL, if space for the SPL binary is very tight.
486 This skips the recording of each loaded payload
487 (i.e. loadable) into the FDT (modifying the loaded FDT to
488 ensure this information is available to the next image
492 bool "Support CACHE drivers"
494 Enable CACHE drivers in SPL. These drivers can keep data so that
495 future requests for that data can be served faster. Enable this option
496 to build the drivers in drivers/cache as part of an SPL build.
499 bool "Support CPU drivers"
501 Enable this to support CPU drivers in SPL. These drivers can set
502 up CPUs and provide information about them such as the model and
503 name. This can be useful in SPL since setting up the CPUs earlier
504 may improve boot performance. Enable this option to build the
505 drivers in drivers/cpu as part of an SPL build.
508 bool "Support crypto drivers"
510 Enable crypto drivers in SPL. These drivers can be used to
511 accelerate secure boot processing in secure applications. Enable
512 this option to build the drivers in drivers/crypto as part of an
516 bool "Support DMA drivers"
518 Enable DMA (direct-memory-access) drivers in SPL. These drivers
519 can be used to handle memory-to-peripheral data transfer without
520 the CPU moving the data. Enable this option to build the drivers
521 in drivers/dma as part of an SPL build.
523 config SPL_DRIVERS_MISC
524 bool "Support misc drivers"
526 Enable miscellaneous drivers in SPL. These drivers perform various
527 tasks that don't fall nicely into other categories, Enable this
528 option to build the drivers in drivers/misc as part of an SPL
529 build, for those that support building in SPL (not all drivers do).
531 config SPL_ENV_SUPPORT
532 bool "Support an environment"
534 Enable environment support in SPL. The U-Boot environment provides
535 a number of settings (essentially name/value pairs) which can
536 control many aspects of U-Boot's operation. Normally this is not
537 needed in SPL as it has a much simpler task with less
538 configuration. But some boards use this to support 'Falcon' boot
539 on EXT2 and FAT, where SPL boots directly into Linux without
540 starting U-Boot first. Enabling this option will make env_get()
541 and env_set() available in SPL.
544 bool "Support save environment"
545 depends on SPL_ENV_SUPPORT
546 select SPL_MMC_WRITE if ENV_IS_IN_MMC
548 Enable save environment support in SPL after setenv. By default
549 the saveenv option is not provided in SPL, but some boards need
550 this support in 'Falcon' boot, where SPL need to boot from
551 different images based on environment variable set by OS. For
552 example OS may set "reboot_image" environment variable to
553 "recovery" inorder to boot recovery image by SPL. The SPL read
554 "reboot_image" and act accordingly and change the reboot_image
555 to default mode using setenv and save the environment.
558 bool "Support Ethernet"
559 depends on SPL_ENV_SUPPORT
562 Enable access to the network subsystem and associated Ethernet
563 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
564 link rather than from an on-board peripheral. Environment support
565 is required since the network stack uses a number of environment
566 variables. See also SPL_NET.
569 bool "Support EXT filesystems"
571 Enable support for EXT2/3/4 filesystems with SPL. This permits
572 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
573 filesystem from within SPL. Support for the underlying block
574 device (e.g. MMC or USB) must be enabled separately.
576 config SPL_FS_SQUASHFS
577 bool "Support SquashFS filesystems"
580 Enable support for SquashFS filesystems with SPL. This permits
581 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
582 filesystem from within SPL. Support for the underlying block
583 device (e.g. MMC or USB) must be enabled separately.
586 bool "Support FAT filesystems"
589 Enable support for FAT and VFAT filesystems with SPL. This
590 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
591 filesystem from within SPL. Support for the underlying block
592 device (e.g. MMC or USB) must be enabled separately.
595 bool "Support write for FAT filesystems"
597 Enable write support for FAT and VFAT filesystems with SPL.
598 Support for the underlying block device (e.g. MMC or USB) must be
604 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
605 provide software-configurable hardware which is typically used to
606 implement peripherals (such as UARTs, LCD displays, MMC) or
607 accelerate custom processing functions, such as image processing
608 or machine learning. Sometimes it is useful to program the FPGA
609 as early as possible during boot, and this option can enable that
613 bool "Support GPIO in SPL"
615 Enable support for GPIOs (General-purpose Input/Output) in SPL.
616 GPIOs allow U-Boot to read the state of an input line (high or
617 low) and set the state of an output line. This can be used to
618 drive LEDs, control power to various system parts and read user
619 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
620 for example. Enable this option to build the drivers in
621 drivers/gpio as part of an SPL build.
626 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
627 I2C works with a clock and data line which can be driven by a
628 one or more masters or slaves. It is a fairly complex bus but is
629 widely used as it only needs two lines for communication. Speeds of
630 400kbps are typical but up to 3.4Mbps is supported by some
631 hardware. I2C can be useful in SPL to configure power management
632 ICs (PMICs) before raising the CPU clock speed, for example.
633 Enable this option to build the drivers in drivers/i2c as part of
636 config SPL_LIBCOMMON_SUPPORT
637 bool "Support common libraries"
639 Enable support for common U-Boot libraries within SPL. These
640 libraries include common code to deal with U-Boot images,
641 environment and USB, for example. This option is enabled on many
642 boards. Enable this option to build the code in common/ as part of
645 config SPL_LIBDISK_SUPPORT
646 bool "Support disk partitions"
649 Enable support for disk partitions within SPL. 'Disk' is something
650 of a misnomer as it includes non-spinning media such as flash (as
651 used in MMC and USB sticks). Partitions provide a way for a disk
652 to be split up into separate regions, with a partition table placed
653 at the start or end which describes the location and size of each
654 'partition'. These partitions are typically uses as individual block
655 devices, typically with an EXT2 or FAT filesystem in each. This
656 option enables whatever partition support has been enabled in
657 U-Boot to also be used in SPL. It brings in the code in disk/.
659 config SPL_LIBGENERIC_SUPPORT
660 bool "Support generic libraries"
662 Enable support for generic U-Boot libraries within SPL. These
663 libraries include generic code to deal with device tree, hashing,
664 printf(), compression and the like. This option is enabled on many
665 boards. Enable this option to build the code in lib/ as part of an
668 config SPL_DM_MAILBOX
669 bool "Support Mailbox"
671 Enable support for Mailbox within SPL. This enable the inter
672 processor communication protocols tobe used within SPL. Enable
673 this option to build the drivers in drivers/mailbox as part of
679 select HAVE_BLOCK_DEVICE
681 Enable support for MMC (Multimedia Card) within SPL. This enables
682 the MMC protocol implementation and allows any enabled drivers to
683 be used within SPL. MMC can be used with or without disk partition
684 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
685 this option to build the drivers in drivers/mmc as part of an SPL
688 config SYS_MMCSD_FS_BOOT_PARTITION
689 int "MMC Boot Partition"
692 Partition on the MMC to load U-Boot from when the MMC is being
694 Use -1 as a special value to use the first bootable partition.
697 bool "Tiny MMC framework in SPL"
700 Enable MMC framework tinification support. This option is useful if
701 if your SPL is extremely size constrained. Heed the warning, enable
702 this option if and only if you know exactly what you are doing, if
703 you are reading this help text, you most likely have no idea :-)
705 The MMC framework is reduced to bare minimum to be useful. No malloc
706 support is needed for the MMC framework operation with this option
707 enabled. The framework supports exactly one MMC device and exactly
708 one MMC driver. The MMC driver can be adjusted to avoid any malloc
709 operations too, which can remove the need for malloc support in SPL
710 and thus further reduce footprint.
713 bool "MMC/SD/SDIO card support for write operations in SPL"
716 Enable write access to MMC and SD Cards in SPL
719 config SPL_MPC8XXX_INIT_DDR
720 bool "Support MPC8XXX DDR init"
722 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
723 random-access memory) on the MPC8XXX family within SPL. This
724 allows DRAM to be set up before loading U-Boot into that DRAM,
727 config SPL_MTD_SUPPORT
728 bool "Support MTD drivers"
730 Enable support for MTD (Memory Technology Device) within SPL. MTD
731 provides a block interface over raw NAND and can also be used with
732 SPI flash. This allows SPL to load U-Boot from supported MTD
733 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
734 to enable specific MTD drivers.
737 bool "Support new Mentor Graphics USB"
739 Enable support for Mentor Graphics USB in SPL. This is a new
740 driver used by some boards. Enable this option to build
741 the drivers in drivers/usb/musb-new as part of an SPL build. The
742 old drivers are in drivers/usb/musb.
744 config SPL_NAND_SUPPORT
745 bool "Support NAND flash"
747 Enable support for NAND (Negative AND) flash in SPL. NAND flash
748 can be used to allow SPL to load U-Boot from supported devices.
749 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
752 config SPL_NAND_DRIVERS
753 bool "Use standard NAND driver"
755 SPL uses normal NAND drivers, not minimal drivers.
758 bool "Include standard software ECC in the SPL"
760 config SPL_NAND_SIMPLE
761 bool "Support simple NAND drivers in SPL"
763 Support for NAND boot using simple NAND drivers that
764 expose the cmd_ctrl() interface.
767 depends on SPL_NAND_DRIVERS
768 bool "Use Base NAND Driver"
770 Include nand_base.c in the SPL.
772 config SPL_NAND_IDENT
773 depends on SPL_NAND_BASE
774 bool "Use chip ID to identify NAND flash"
776 SPL uses the chip ID list to identify the NAND flash.
781 Enable support for loading payloads from UBI. See
782 README.ubispl for more info.
786 bool "Support SPI DM drivers in SPL"
788 Enable support for SPI DM drivers in SPL.
790 config SPL_DM_SPI_FLASH
791 bool "Support SPI DM FLASH drivers in SPL"
793 Enable support for SPI DM flash drivers in SPL.
797 config SPL_UBI_LOAD_BY_VOLNAME
798 bool "Support loading volumes by name"
800 This enables support for loading UBI volumes by name. When this
801 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
802 configure the volume name from which to load U-Boot.
804 config SPL_UBI_MAX_VOL_LEBS
805 int "Maximum number of LEBs per volume"
808 The maximum number of logical eraseblocks which a static volume
809 to load can contain. Used for sizing the scan data structure.
811 config SPL_UBI_MAX_PEB_SIZE
812 int "Maximum PEB size"
815 The maximum physical erase block size.
817 config SPL_UBI_MAX_PEBS
818 int "Maximum number of PEBs"
821 The maximum physical erase block size. If not overridden by
822 board code, this value will be used as the actual number of PEBs.
824 config SPL_UBI_PEB_OFFSET
825 int "Offset to first UBI PEB"
828 The offset in number of PEBs from the start of flash to the first
829 PEB part of the UBI image.
831 config SPL_UBI_VID_OFFSET
832 int "Offset to VID header"
835 config SPL_UBI_LEB_START
836 int "Offset to LEB in PEB"
839 The offset in bytes to the LEB within a PEB.
841 config SPL_UBI_INFO_ADDR
842 hex "Address to place UBI scan info"
845 Address for ubispl to place the scan info. Read README.ubispl to
846 determine the required size
848 config SPL_UBI_VOL_IDS
849 int "Maximum volume id"
852 The maximum volume id which can be loaded. Used for sizing the
855 config SPL_UBI_LOAD_MONITOR_ID
856 int "id of U-Boot volume"
859 The UBI volume id from which to load U-Boot
861 config SPL_UBI_LOAD_MONITOR_VOLNAME
862 string "volume name of U-Boot volume"
863 depends on SPL_UBI_LOAD_BY_VOLNAME
865 The UBI volume name from which to load U-Boot
867 config SPL_UBI_LOAD_KERNEL_ID
868 int "id of kernel volume"
869 depends on SPL_OS_BOOT && SPL_UBI
871 The UBI volume id from which to load the kernel
873 config SPL_UBI_LOAD_ARGS_ID
874 int "id of kernel args volume"
875 depends on SPL_OS_BOOT && SPL_UBI
877 The UBI volume id from which to load the device tree
879 config UBI_SPL_SILENCE_MSG
880 bool "silence UBI SPL messages"
882 Disable messages from UBI SPL. This leaves warnings
888 bool "Support networking"
890 Enable support for network devices (such as Ethernet) in SPL.
891 This permits SPL to load U-Boot over a network link rather than
892 from an on-board peripheral. Environment support is required since
893 the network stack uses a number of environment variables. See also
897 config SPL_NET_VCI_STRING
898 string "BOOTP Vendor Class Identifier string sent by SPL"
900 As defined by RFC 2132 the vendor class identifier field can be
901 sent by the client to identify the vendor type and configuration
902 of a client. This is often used in practice to allow for the DHCP
903 server to specify different files to load depending on if the ROM,
904 SPL or U-Boot itself makes the request
907 config SPL_NO_CPU_SUPPORT
908 bool "Drop CPU code in SPL"
910 This is specific to the ARM926EJ-S CPU. It disables the standard
911 start.S start-up code, presumably so that a replacement can be
912 used on that CPU. You should not enable it unless you know what
915 config SPL_NOR_SUPPORT
916 bool "Support NOR flash"
918 Enable support for loading U-Boot from memory-mapped NOR (Negative
919 OR) flash in SPL. NOR flash is slow to write but fast to read, and
920 a memory-mapped device makes it very easy to access. Loading from
921 NOR is typically achieved with just a memcpy().
923 config SPL_XIP_SUPPORT
927 Enable support for execute in place of U-Boot or kernel image. There
928 is no need to copy image from flash to ram if flash supports execute
929 in place. Its very useful in systems having enough flash but not
930 enough ram to load the image.
932 config SPL_ONENAND_SUPPORT
933 bool "Support OneNAND flash"
935 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
936 a type of NAND flash and therefore can be used to allow SPL to
937 load U-Boot from supported devices. This enables the drivers in
938 drivers/mtd/onenand as part of an SPL build.
941 bool "Activate Falcon Mode"
942 depends on !TI_SECURE_DEVICE
944 Enable booting directly to an OS from SPL.
945 for more info read doc/README.falcon
949 hex "addr, where OS is found"
950 depends on SPL_NOR_SUPPORT
952 Specify the address, where the OS image is found, which
957 config SPL_FALCON_BOOT_MMCSD
958 bool "Enable Falcon boot from MMC or SD media"
959 depends on SPL_OS_BOOT && SPL_MMC
961 Select this if the Falcon mode OS image mode is on MMC or SD media.
963 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
964 hex "Falcon mode: Sector to load kernel uImage from MMC"
965 depends on SPL_FALCON_BOOT_MMCSD
967 When Falcon mode is used with an MMC or SD media, SPL needs to know
968 where to look for the kernel uImage. The image is expected to begin
969 at the raw MMC specified in this config.
970 Note that the Falcon mode image can also be a FIT, if FIT support is
975 default "tpl/u-boot-with-tpl.bin" if TPL
978 Payload for SPL boot. For backward compatibility, default to
979 u-boot.bin, i.e. RAW image without any header. In case of
980 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
984 bool "Support PCI drivers"
986 Enable support for PCI in SPL. For platforms that need PCI to boot,
987 or must perform some init using PCI in SPL, this provides the
988 necessary driver support. This enables the drivers in drivers/pci
989 as part of an SPL build.
992 bool "Support PCH drivers"
994 Enable support for PCH (Platform Controller Hub) devices in SPL.
995 These are used to set up GPIOs and the SPI peripheral early in
996 boot. This enables the drivers in drivers/pch as part of an SPL
999 config SPL_POST_MEM_SUPPORT
1000 bool "Support POST drivers"
1002 Enable support for POST (Power-on Self Test) in SPL. POST is a
1003 procedure that checks that the hardware (CPU or board) appears to
1004 be functionally correctly. It is a sanity check that can be
1005 performed before booting. This enables the drivers in post/drivers
1006 as part of an SPL build.
1009 bool "Support reset drivers"
1012 Enable support for reset control in SPL.
1013 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1014 by using the generic reset API provided by driver model.
1015 This enables the drivers in drivers/reset as part of an SPL build.
1018 bool "Support power drivers"
1020 Enable support for power control in SPL. This includes support
1021 for PMICs (Power-management Integrated Circuits) and some of the
1022 features provided by PMICs. In particular, voltage regulators can
1023 be used to enable/disable power and vary its voltage. That can be
1024 useful in SPL to turn on boot peripherals and adjust CPU voltage
1025 so that the clock speed can be increased. This enables the drivers
1026 in drivers/power, drivers/power/pmic and drivers/power/regulator
1027 as part of an SPL build.
1029 config SPL_POWER_DOMAIN
1030 bool "Support power domain drivers"
1033 Enable support for power domain control in SPL. Many SoCs allow
1034 power to be applied to or removed from portions of the SoC (power
1035 domains). This may be used to save power. This API provides the
1036 means to control such power management hardware. This enables
1037 the drivers in drivers/power/domain as part of a SPL build.
1039 config SPL_RAM_SUPPORT
1040 bool "Support booting from RAM"
1041 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1043 Enable booting of an image in RAM. The image can be preloaded or
1044 it can be loaded by SPL directly into RAM (e.g. using USB).
1046 config SPL_RAM_DEVICE
1047 bool "Support booting from preloaded image in RAM"
1048 depends on SPL_RAM_SUPPORT
1049 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1051 Enable booting of an image already loaded in RAM. The image has to
1052 be already in memory when SPL takes over, e.g. loaded by the boot
1055 config SPL_REMOTEPROC
1056 bool "Support REMOTEPROCS"
1058 Enable support for REMOTEPROCs in SPL. This permits to load
1059 a remote processor firmware in SPL.
1062 bool "Support RTC drivers"
1064 Enable RTC (Real-time Clock) support in SPL. This includes support
1065 for reading and setting the time. Some RTC devices also have some
1066 non-volatile (battery-backed) memory which is accessible if
1067 needed. This enables the drivers in drivers/rtc as part of an SPL
1071 bool "Support loading from SATA"
1073 Enable support for SATA (Serial AT attachment) in SPL. This allows
1074 use of SATA devices such as hard drives and flash drivers for
1075 loading U-Boot. SATA is used in higher-end embedded systems and
1076 can provide higher performance than MMC , at somewhat higher
1077 expense and power consumption. This enables loading from SATA
1078 using a configured device.
1080 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1081 bool "SATA raw mode: by sector"
1083 default y if ARCH_MVEBU
1085 Use sector number for specifying U-Boot location on SATA disk in
1088 config SPL_SATA_RAW_U_BOOT_SECTOR
1089 hex "Sector on the SATA disk to load U-Boot from"
1090 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1091 default 0x1 if ARCH_MVEBU
1093 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1094 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1097 bool "Support serial"
1101 Enable support for serial in SPL. This allows use of a serial UART
1102 for displaying messages while SPL is running. It also brings in
1103 printf() and panic() functions. This should normally be enabled
1104 unless there are space reasons not to. Even then, consider
1105 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1108 bool "Support SPI drivers"
1110 Enable support for using SPI in SPL. This is used for connecting
1111 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1112 more details on that. The SPI driver provides the transport for
1113 data between the SPI flash and the CPU. This option can be used to
1114 enable SPI drivers that are needed for other purposes also, such
1117 config SPL_SPI_FLASH_SUPPORT
1118 bool "Support SPI flash drivers"
1121 Enable support for using SPI flash in SPL, and loading U-Boot from
1122 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1123 the SPI bus that is used to connect it to a system. It is a simple
1124 but fast bidirectional 4-wire bus (clock, chip select and two data
1125 lines). This enables the drivers in drivers/mtd/spi as part of an
1126 SPL build. This normally requires SPL_SPI.
1128 if SPL_SPI_FLASH_SUPPORT
1130 config SPL_SPI_FLASH_TINY
1131 bool "Enable low footprint SPL SPI Flash support"
1132 depends on !SPI_FLASH_BAR
1133 default y if SPI_FLASH
1135 Enable lightweight SPL SPI Flash support that supports just reading
1136 data/images from flash. No support to write/erase flash. Enable
1137 this if you have SPL size limitations and don't need full
1138 fledged SPI flash support.
1140 config SPL_SPI_FLASH_SFDP_SUPPORT
1141 bool "SFDP table parsing support for SPI NOR flashes"
1142 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1144 Enable support for parsing and auto discovery of parameters for
1145 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1146 tables as per JESD216 standard in SPL.
1148 config SPL_SPI_FLASH_MTD
1149 bool "Support for SPI flash MTD drivers in SPL"
1151 Enable support for SPI flash MTD drivers in SPL.
1154 bool "Support loading from SPI flash"
1156 Enable support for loading next stage, U-Boot or otherwise, from
1157 SPI NOR in U-Boot SPL.
1159 endif # SPL_SPI_FLASH_SUPPORT
1161 config SYS_SPI_U_BOOT_OFFS
1162 hex "address of u-boot payload in SPI flash"
1163 default 0x8000 if ARCH_SUNXI
1165 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1167 Address within SPI-Flash from where the u-boot payload is fetched
1171 bool "Driver support for thermal devices"
1173 Enable support for temperature-sensing devices. Some SoCs have on-chip
1174 temperature sensors to permit warnings, speed throttling or even
1175 automatic power-off when the temperature gets too high or low. Other
1176 devices may be discrete but connected on a suitable bus.
1179 bool "Support USB host drivers"
1180 select HAVE_BLOCK_DEVICE
1182 Enable access to USB (Universal Serial Bus) host devices so that
1183 SPL can load U-Boot from a connected USB peripheral, such as a USB
1184 flash stick. While USB takes a little longer to start up than most
1185 buses, it is very flexible since many different types of storage
1186 device can be attached. This option enables the drivers in
1187 drivers/usb/host as part of an SPL build.
1189 config SPL_USB_STORAGE
1190 bool "Support loading from USB"
1191 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1193 Enable support for USB devices in SPL. This allows use of USB
1194 devices such as hard drives and flash drivers for loading U-Boot.
1195 The actual drivers are enabled separately using the normal U-Boot
1196 config options. This enables loading from USB using a configured
1199 config SPL_USB_GADGET
1200 bool "Suppport USB Gadget drivers"
1202 Enable USB Gadget API which allows to enable USB device functions
1207 config SPL_USB_ETHER
1208 bool "Support USB Ethernet drivers"
1211 Enable access to the USB network subsystem and associated
1212 drivers in SPL. This permits SPL to load U-Boot over a
1213 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1214 than from an onboard peripheral. Environment support is required
1215 since the network stack uses a number of environment variables.
1216 See also SPL_NET and SPL_ETH.
1219 bool "Support DFU (Device Firmware Upgrade)"
1221 select SPL_DFU_NO_RESET
1222 depends on SPL_RAM_SUPPORT
1224 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1225 RAM memory device support. The ROM code will load and execute
1226 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1227 selected device partition from host-pc using dfu-utils.
1228 This feature is useful to flash the binaries to factory or bare-metal
1229 boards using USB interface.
1232 bool "DFU device selection"
1237 depends on SPL_DFU && SPL_RAM_SUPPORT
1239 select RAM/DDR memory device for loading binary images
1240 (u-boot/kernel) to the selected device partition using
1241 DFU and execute the u-boot/kernel from RAM.
1245 config SPL_USB_SDP_SUPPORT
1246 bool "Support SDP (Serial Download Protocol)"
1247 depends on SPL_SERIAL
1249 Enable Serial Download Protocol (SDP) device support in SPL. This
1250 allows to download images into memory and execute (jump to) them
1251 using the same protocol as implemented by the i.MX family's boot ROM.
1253 config SPL_SDP_USB_DEV
1254 int "SDP USB controller index"
1256 depends on SPL_USB_SDP_SUPPORT
1258 Some boards have USB controller other than 0. Define this option
1259 so it can be used in compiled environment.
1263 bool "Support watchdog drivers"
1264 imply SPL_WDT if !HW_WATCHDOG
1266 Enable support for watchdog drivers in SPL. A watchdog is
1267 typically a hardware peripheral which can reset the system when it
1268 detects no activity for a while (such as a software crash). This
1269 enables the drivers in drivers/watchdog as part of an SPL build.
1271 config SPL_YMODEM_SUPPORT
1272 bool "Support loading using Ymodem"
1273 depends on SPL_SERIAL
1275 While loading from serial is slow it can be a useful backup when
1276 there is no other option. The Ymodem protocol provides a reliable
1277 means of transmitting U-Boot over a serial line for using in SPL,
1278 with a checksum to ensure correctness.
1281 bool "Support ARM Trusted Firmware"
1282 depends on ARM64 && SPL_FIT
1284 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1285 is loaded by SPL (which is considered as BL2 in ATF terminology).
1286 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1288 config SPL_ATF_LOAD_IMAGE_V2
1289 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1292 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1294 If you want to load a bl31 image from the SPL and need the new
1297 config SPL_ATF_NO_PLATFORM_PARAM
1298 bool "Pass no platform parameter"
1301 While we expect to call a pointer to a valid FDT (or NULL)
1302 as the platform parameter to an ATF, some ATF versions are
1303 not U-Boot aware and have an insufficiently robust parameter
1304 validation to gracefully reject a FDT being passed.
1306 If this option is enabled, the spl_atf os-type handler will
1307 always pass NULL for the platform parameter.
1309 If your ATF is affected, say Y.
1311 config SPL_AM33XX_ENABLE_RTC32K_OSC
1312 bool "Enable the RTC32K OSC on AM33xx based platforms"
1315 Enable access to the AM33xx RTC and select the external 32kHz clock
1318 config SPL_OPTEE_IMAGE
1319 bool "Support OP-TEE Trusted OS image in SPL"
1322 OP-TEE is an open source Trusted OS which is loaded by SPL.
1323 More detail at: https://github.com/OP-TEE/optee_os
1326 bool "Support RISC-V OpenSBI"
1327 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1329 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1330 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1331 firmware. It is loaded and started by U-Boot SPL.
1333 More details are available at https://github.com/riscv/opensbi and
1334 https://github.com/riscv/riscv-sbi-doc
1336 config SPL_OPENSBI_LOAD_ADDR
1337 hex "OpenSBI load address"
1338 depends on SPL_OPENSBI
1340 Load address of the OpenSBI binary.
1344 depends on SUPPORT_TPL
1347 If you want to build TPL as well as the normal image and SPL, say Y.
1351 config TPL_SIZE_LIMIT
1352 hex "Maximum size of TPL image"
1356 Specifies the maximum length of the U-Boot TPL image.
1357 If this value is zero, it is ignored.
1359 config TPL_BINMAN_SYMBOLS
1360 bool "Declare binman symbols in TPL"
1361 depends on SPL_FRAMEWORK && BINMAN
1364 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1365 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1366 and spl_get_image_size().
1368 For this to work, you must have a U-Boot image in the binman image, so
1369 binman can update TPL with the location of it.
1371 config TPL_FRAMEWORK
1372 bool "Support TPL based upon the common SPL framework"
1373 default y if SPL_FRAMEWORK
1375 Enable the SPL framework under common/spl/ for TPL builds.
1376 This framework supports MMC, NAND and YMODEM and other methods
1377 loading of U-Boot's SPL stage. If unsure, say Y.
1380 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1381 depends on HANDOFF && TPL_BLOBLIST
1384 This option enables TPL to write handoff information. This can be
1385 used to pass information like the size of SDRAM from TPL to U-Boot
1386 proper. The information is also available to SPL if it is useful
1389 config TPL_BOARD_INIT
1390 bool "Call board-specific initialization in TPL"
1392 If this option is enabled, U-Boot will call the function
1393 spl_board_init() from board_init_r(). This function should be
1394 provided by the board.
1396 config TPL_BOOTCOUNT_LIMIT
1397 bool "Support bootcount in TPL"
1398 depends on TPL_ENV_SUPPORT
1400 If this option is enabled, the TPL will support bootcount.
1401 For example, it may be useful to choose the device to boot.
1404 string "Linker script for the TPL stage"
1406 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1407 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1409 The TPL stage will usually require a different linker-script
1410 (as it runs from a different memory region) than the regular
1411 U-Boot stage. Set this to the path of the linker-script to
1414 May be left empty to trigger the Makefile infrastructure to
1415 fall back to the linker-script used for the SPL stage.
1417 config TPL_NEEDS_SEPARATE_STACK
1418 bool "TPL needs a separate initial stack-pointer"
1421 Enable, if the TPL stage should not inherit its initial
1422 stack-pointer from the settings for the SPL stage.
1425 bool "Support power drivers"
1427 Enable support for power control in TPL. This includes support
1428 for PMICs (Power-management Integrated Circuits) and some of the
1429 features provided by PMICs. In particular, voltage regulators can
1430 be used to enable/disable power and vary its voltage. That can be
1431 useful in TPL to turn on boot peripherals and adjust CPU voltage
1432 so that the clock speed can be increased. This enables the drivers
1433 in drivers/power, drivers/power/pmic and drivers/power/regulator
1434 as part of an TPL build.
1436 config TPL_TEXT_BASE
1437 hex "Base address for the .text section of the TPL stage"
1440 The base address for the .text section of the TPL stage.
1443 int "Maximum size (in bytes) for the TPL stage"
1447 The maximum size (in bytes) of the TPL stage.
1450 hex "Address of the initial stack-pointer for the TPL stage"
1451 depends on TPL_NEEDS_SEPARATE_STACK
1453 The address of the initial stack-pointer for the TPL stage.
1454 Usually this will be the (aligned) top-of-stack.
1456 config TPL_READ_ONLY
1458 depends on TPL_OF_PLATDATA
1459 select TPL_OF_PLATDATA_NO_BIND
1460 select TPL_OF_PLATDATA_RT
1462 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1463 section of memory. This means that of-platdata must make a copy (in
1464 writeable memory) of anything it wants to modify, such as
1465 device-private data.
1467 config TPL_BOOTROM_SUPPORT
1468 bool "Support returning to the BOOTROM (from TPL)"
1470 Some platforms (e.g. the Rockchip RK3368) provide support in their
1471 ROM for loading the next boot-stage after performing basic setup
1474 Enable this option, to return to the BOOTROM through the
1475 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1476 boot device list, if not implemented for a given board)
1479 bool "Support CRC32 in TPL"
1480 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1482 Enable this to support CRC32 in uImages or FIT images within SPL.
1483 This is a 32-bit checksum value that can be used to verify images.
1484 For FIT images, this is the least secure type of checksum, suitable
1485 for detected accidental image corruption. For secure applications you
1486 should consider SHA1 or SHA256.
1488 config TPL_DRIVERS_MISC
1489 bool "Support misc drivers in TPL"
1491 Enable miscellaneous drivers in TPL. These drivers perform various
1492 tasks that don't fall nicely into other categories, Enable this
1493 option to build the drivers in drivers/misc as part of an TPL
1494 build, for those that support building in TPL (not all drivers do).
1496 config TPL_ENV_SUPPORT
1497 bool "Support an environment"
1499 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1502 bool "Support GPIO in TPL"
1504 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1505 GPIOs allow U-Boot to read the state of an input line (high or
1506 low) and set the state of an output line. This can be used to
1507 drive LEDs, control power to various system parts and read user
1508 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1509 for example. Enable this option to build the drivers in
1510 drivers/gpio as part of an TPL build.
1515 Enable support for the I2C bus in TPL. See SPL_I2C for
1518 config TPL_LIBCOMMON_SUPPORT
1519 bool "Support common libraries"
1521 Enable support for common U-Boot libraries within TPL. See
1522 SPL_LIBCOMMON_SUPPORT for details.
1524 config TPL_LIBGENERIC_SUPPORT
1525 bool "Support generic libraries"
1527 Enable support for generic U-Boot libraries within TPL. See
1528 SPL_LIBGENERIC_SUPPORT for details.
1530 config TPL_MPC8XXX_INIT_DDR
1531 bool "Support MPC8XXX DDR init"
1533 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1534 SPL_MPC8XXX_INIT_DDR for details.
1540 Enable support for MMC within TPL. See SPL_MMC for details.
1542 config TPL_NAND_SUPPORT
1543 bool "Support NAND flash"
1545 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1548 bool "Support PCI drivers"
1550 Enable support for PCI in TPL. For platforms that need PCI to boot,
1551 or must perform some init using PCI in SPL, this provides the
1552 necessary driver support. This enables the drivers in drivers/pci
1553 as part of a TPL build.
1556 bool "Support PCH drivers"
1558 Enable support for PCH (Platform Controller Hub) devices in TPL.
1559 These are used to set up GPIOs and the SPI peripheral early in
1560 boot. This enables the drivers in drivers/pch as part of a TPL
1563 config TPL_RAM_SUPPORT
1564 bool "Support booting from RAM"
1566 Enable booting of an image in RAM. The image can be preloaded or
1567 it can be loaded by TPL directly into RAM (e.g. using USB).
1569 config TPL_RAM_DEVICE
1570 bool "Support booting from preloaded image in RAM"
1571 depends on TPL_RAM_SUPPORT
1573 Enable booting of an image already loaded in RAM. The image has to
1574 be already in memory when TPL takes over, e.g. loaded by the boot
1578 bool "Support RTC drivers"
1580 Enable RTC (Real-time Clock) support in TPL. This includes support
1581 for reading and setting the time. Some RTC devices also have some
1582 non-volatile (battery-backed) memory which is accessible if
1583 needed. This enables the drivers in drivers/rtc as part of an TPL
1587 bool "Support serial"
1591 Enable support for serial in TPL. See SPL_SERIAL for
1594 config TPL_SPI_FLASH_SUPPORT
1595 bool "Support SPI flash drivers"
1597 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1600 config TPL_SPI_FLASH_TINY
1601 bool "Enable low footprint TPL SPI Flash support"
1602 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1603 default y if SPI_FLASH
1605 Enable lightweight TPL SPI Flash support that supports just reading
1606 data/images from flash. No support to write/erase flash. Enable
1607 this if you have TPL size limitations and don't need full-fledged
1611 bool "Support loading from SPI flash"
1612 depends on TPL_SPI_FLASH_SUPPORT
1614 Enable support for loading next stage, U-Boot or otherwise, from
1615 SPI NOR in U-Boot TPL.
1618 bool "Support SPI drivers"
1620 Enable support for using SPI in TPL. See SPL_SPI for
1624 bool "Support SPI DM drivers in TPL"
1626 Enable support for SPI DM drivers in TPL.
1628 config TPL_DM_SPI_FLASH
1629 bool "Support SPI DM FLASH drivers in TPL"
1631 Enable support for SPI DM flash drivers in TPL.
1633 config TPL_YMODEM_SUPPORT
1634 bool "Support loading using Ymodem"
1635 depends on TPL_SERIAL
1637 While loading from serial is slow it can be a useful backup when
1638 there is no other option. The Ymodem protocol provides a reliable
1639 means of transmitting U-Boot over a serial line for using in TPL,
1640 with a checksum to ensure correctness.
1646 depends on SUPPORT_SPL
1649 If you want to build VPL as well as the normal image, TPL and SPL,
1654 config VPL_BANNER_PRINT
1655 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1659 If this option is enabled, VPL will print the banner with version
1660 info. Disabling this option could be useful to reduce VPL boot time
1661 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1663 config VPL_BOARD_INIT
1664 bool "Call board-specific initialization in VPL"
1666 If this option is enabled, U-Boot will call the function
1667 spl_board_init() from board_init_r(). This function should be
1668 provided by the board.
1672 bool "Support cache drivers in VPL"
1674 Enable support for cache drivers in VPL.
1677 bool "Support CRC32 in VPL"
1678 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1680 Enable this to support CRC32 in uImages or FIT images within VPL.
1681 This is a 32-bit checksum value that can be used to verify images.
1682 For FIT images, this is the least secure type of checksum, suitable
1683 for detected accidental image corruption. For secure applications you
1684 should consider SHA1 or SHA256.
1687 bool "Support SPI DM drivers in VPL"
1689 Enable support for SPI DM drivers in VPL.
1691 config VPL_DM_SPI_FLASH
1692 bool "Support SPI DM FLASH drivers in VPL"
1694 Enable support for SPI DM flash drivers in VPL.
1696 config VPL_FRAMEWORK
1697 bool "Support VPL based upon the common SPL framework"
1700 Enable the SPL framework under common/spl/ for VPL builds.
1701 This framework supports MMC, NAND and YMODEM and other methods
1702 loading of U-Boot's next stage. If unsure, say Y.
1705 bool "Pass hand-off information from VPL to SPL"
1706 depends on HANDOFF && VPL_BLOBLIST
1709 This option enables VPL to write handoff information. This can be
1710 used to pass information like the size of SDRAM from VPL to SPL. Also
1711 VPL can receive information from TPL in the same place if that is
1714 config VPL_LIBCOMMON_SUPPORT
1715 bool "Support common libraries"
1716 default y if SPL_LIBCOMMON_SUPPORT
1718 Enable support for common U-Boot libraries within VPL. See
1719 SPL_LIBCOMMON_SUPPORT for details.
1721 config VPL_LIBGENERIC_SUPPORT
1722 bool "Support generic libraries"
1723 default y if SPL_LIBGENERIC_SUPPORT
1725 Enable support for generic U-Boot libraries within VPL. These
1726 libraries include generic code to deal with device tree, hashing,
1727 printf(), compression and the like. This option is enabled on many
1728 boards. Enable this option to build the code in lib/ as part of a
1731 config VPL_DRIVERS_MISC
1732 bool "Support misc drivers"
1733 default y if TPL_DRIVERS_MISC
1735 Enable miscellaneous drivers in VPL. These drivers perform various
1736 tasks that don't fall nicely into other categories, Enable this
1737 option to build the drivers in drivers/misc as part of a VPL
1738 build, for those that support building in VPL (not all drivers do).
1740 config VPL_ENV_SUPPORT
1741 bool "Support an environment"
1743 Enable environment support in VPL. The U-Boot environment provides
1744 a number of settings (essentially name/value pairs) which can
1745 control many aspects of U-Boot's operation. Enabling this option will
1746 make env_get() and env_set() available in VSPL.
1749 bool "Support GPIO in VPL"
1750 default y if SPL_GPIO
1752 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1753 GPIOs allow U-Boot to read the state of an input line (high or
1754 low) and set the state of an output line. This can be used to
1755 drive LEDs, control power to various system parts and read user
1756 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1757 for example. Enable this option to build the drivers in
1758 drivers/gpio as part of a VPL build.
1761 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1762 depends on HANDOFF && VPL_BLOBLIST
1765 This option enables VPL to write handoff information. This can be
1766 used to pass information like the size of SDRAM from VPL to U-Boot
1767 proper. The information is also available to VPL if it is useful
1771 bool "Support hashing drivers in VPL"
1776 Enable hashing drivers in VPL. These drivers can be used to
1777 accelerate secure boot processing in secure applications. Enable
1778 this option to build system-specific drivers for hash acceleration
1779 as part of a VPL build.
1781 config VPL_I2C_SUPPORT
1782 bool "Support I2C in VPL"
1783 default y if SPL_I2C_SUPPORT
1785 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1788 config VPL_PCH_SUPPORT
1789 bool "Support PCH drivers"
1790 default y if TPL_PCH_SUPPORT
1792 Enable support for PCH (Platform Controller Hub) devices in VPL.
1793 These are used to set up GPIOs and the SPI peripheral early in
1794 boot. This enables the drivers in drivers/pch as part of a VPL
1798 bool "Support PCI drivers"
1799 default y if SPL_PCI
1801 Enable support for PCI in VPL. For platforms that need PCI to boot,
1802 or must perform some init using PCI in VPL, this provides the
1803 necessary driver support. This enables the drivers in drivers/pci
1804 as part of a VPL build.
1807 bool "Support RTC drivers"
1809 Enable RTC (Real-time Clock) support in VPL. This includes support
1810 for reading and setting the time. Some RTC devices also have some
1811 non-volatile (battery-backed) memory which is accessible if
1812 needed. This enables the drivers in drivers/rtc as part of a VPL
1816 bool "Support serial"
1817 default y if TPL_SERIAL
1821 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1824 config VPL_SIZE_LIMIT
1825 hex "Maximum size of VPL image"
1829 Specifies the maximum length of the U-Boot VPL image.
1830 If this value is zero, it is ignored.
1833 bool "Support SPI drivers"
1835 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
1838 config VPL_SPI_FLASH_SUPPORT
1839 bool "Support SPI flash drivers"
1841 Enable support for using SPI flash in VPL, and loading U-Boot from
1842 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1843 the SPI bus that is used to connect it to a system. It is a simple
1844 but fast bidirectional 4-wire bus (clock, chip select and two data
1845 lines). This enables the drivers in drivers/mtd/spi as part of a
1846 VPL build. This normally requires VPL_SPI_SUPPORT.
1848 config VPL_TEXT_BASE
1852 The address in memory that VPL will be running from.
1856 config SPL_AT91_MCK_BYPASS
1857 bool "Use external clock signal as a source of main clock for AT91 platforms"
1858 depends on ARCH_AT91
1860 Use external 8 to 24 Mhz clock signal as source of main clock instead
1861 of an external crystal oscillator.
1862 This option disables the internal driving on the XOUT pin.
1863 The external source has to provide a stable clock on the XIN pin.
1864 If this option is disabled, the SoC expects a crystal oscillator
1865 that needs driving on both XIN and XOUT lines.