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))
222 default y if !TI_SECURE_DEVICE
224 SPL will support loading and booting a RAW image when this option
225 is y. If this is not set, SPL will move on to other available
226 boot media to find a suitable image.
228 config SPL_LEGACY_IMAGE_SUPPORT
229 bool "Support SPL loading and booting of Legacy images"
230 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
232 SPL will support loading and booting Legacy images when this option
233 is y. If this is not set, SPL will move on to other available
234 boot media to find a suitable image.
236 config SPL_LEGACY_IMAGE_CRC_CHECK
237 bool "Check CRC of Legacy images"
238 depends on SPL_LEGACY_IMAGE_SUPPORT
241 Enable this to check the CRC of Legacy images. While this increases
242 reliability, it affects both code size and boot duration.
243 If disabled, Legacy images are booted if the image magic and size
244 are correct, without further integrity checks.
246 config SPL_SYS_MALLOC_SIMPLE
248 prompt "Only use malloc_simple functions in the SPL"
250 Say Y here to only use the *_simple malloc functions from
251 malloc_simple.c, rather then using the versions from dlmalloc.c;
252 this will make the SPL binary smaller at the cost of more heap
253 usage as the *_simple malloc functions do not re-use free-ed mem.
255 config TPL_SYS_MALLOC_SIMPLE
257 prompt "Only use malloc_simple functions in the TPL"
260 Say Y here to only use the *_simple malloc functions from
261 malloc_simple.c, rather then using the versions from dlmalloc.c;
262 this will make the TPL binary smaller at the cost of more heap
263 usage as the *_simple malloc functions do not re-use free-ed mem.
266 bool "Enable SDRAM location for SPL stack"
268 SPL starts off execution in SRAM and thus typically has only a small
269 stack available. Since SPL sets up DRAM while in its board_init_f()
270 function, it is possible for the stack to move there before
271 board_init_r() is reached. This option enables a special SDRAM
272 location for the SPL stack. U-Boot SPL switches to this after
273 board_init_f() completes, and before board_init_r() starts.
275 config SPL_STACK_R_ADDR
276 depends on SPL_STACK_R
277 hex "SDRAM location for SPL stack"
278 default 0x82000000 if ARCH_OMAP2PLUS
280 Specify the address in SDRAM for the SPL stack. This will be set up
281 before board_init_r() is called.
283 config SPL_STACK_R_MALLOC_SIMPLE_LEN
284 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
285 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
288 Specify the amount of the stack to use as memory pool for
289 malloc_simple after switching the stack to DRAM. This may be set
290 to give board_init_r() a larger heap then the initial heap in
291 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
293 config SPL_SEPARATE_BSS
294 bool "BSS section is in a different memory region from text"
296 Some platforms need a large BSS region in SPL and can provide this
297 because RAM is already set up. In this case BSS can be moved to RAM.
298 This option should then be enabled so that the correct device tree
299 location is used. Normally we put the device tree at the end of BSS
300 but with this option enabled, it goes at _image_binary_end.
304 depends on SPL_OF_PLATDATA
305 # Bind cannot be supported because the udevice structs are in read-only
306 # memory so we cannot update the linked lists.
307 select SPL_OF_PLATDATA_NO_BIND
308 select SPL_OF_PLATDATA_RT
310 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
311 section of memory. This means that of-platdata must make a copy (in
312 writeable memory) of anything it wants to modify, such as
315 config TPL_SEPARATE_BSS
316 bool "BSS section is in a different memory region from text"
317 default y if SPL_SEPARATE_BSS
319 Some platforms need a large BSS region in TPL and can provide this
320 because RAM is already set up. In this case BSS can be moved to RAM.
321 This option should then be enabled so that the correct device tree
322 location is used. Normally we put the device tree at the end of BSS
323 but with this option enabled, it goes at _image_binary_end.
325 config SPL_BANNER_PRINT
326 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
329 If this option is enabled, SPL will print the banner with version
330 info. Disabling this option could be useful to reduce SPL boot time
331 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
333 config TPL_BANNER_PRINT
334 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
338 If this option is enabled, TPL will print the banner with version
339 info. Disabling this option could be useful to reduce TPL boot time
340 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
343 depends on ARM && !ARM64
344 bool "Allows initializing BSS early before entering board_init_f"
346 On some platform we have sufficient memory available early on to
347 allow setting up and using a basic BSS prior to entering
348 board_init_f. Activating this option will also de-activate the
349 clearing of BSS during the SPL relocation process, thus allowing
350 to carry state from board_init_f to board_init_r by way of BSS.
352 config SPL_DISPLAY_PRINT
353 bool "Display a board-specific message in SPL"
355 If this option is enabled, U-Boot will call the function
356 spl_display_print() immediately after displaying the SPL console
357 banner ("U-Boot SPL ..."). This function should be provided by
360 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
361 bool "MMC raw mode: by sector"
362 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
363 ARCH_MX6 || ARCH_MX7 || \
364 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
365 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
366 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
367 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
369 Use sector number for specifying U-Boot location on MMC/SD in
372 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
373 hex "Address on the MMC to load U-Boot from"
374 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
375 default 0x40 if ARCH_SUNXI
376 default 0x75 if ARCH_DAVINCI
377 default 0x8a if ARCH_MX6 || ARCH_MX7
378 default 0x100 if ARCH_UNIPHIER
379 default 0x0 if ARCH_MVEBU
380 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
381 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
382 OMAP54XX || AM33XX || AM43XX || ARCH_K3
383 default 0x4000 if ARCH_ROCKCHIP
384 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
386 Address on the MMC to load U-Boot from, when the MMC is being used
387 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
389 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
390 hex "U-Boot main hardware partition image offset"
391 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
392 default 0x10 if ARCH_SUNXI
395 On some platforms SPL location depends on hardware partition. The ROM
396 code skips the MBR sector when loading SPL from main hardware data
397 partition. This adds offset to the main U-Boot image. Set this symbol
398 to the number of skipped sectors.
400 If unsure, leave the default.
402 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
403 bool "MMC Raw mode: by partition"
405 Use a partition for loading U-Boot when using MMC/SD in raw mode.
407 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
408 hex "Partition to use to load U-Boot from"
409 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
412 Partition on the MMC to load U-Boot from when the MMC is being
415 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
416 bool "MMC raw mode: by partition type"
417 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
419 Use partition type for specifying U-Boot partition on MMC/SD in
420 raw mode. U-Boot will be loaded from the first partition of this
423 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
424 hex "Partition Type on the MMC to load U-Boot from"
425 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
427 Partition Type on the MMC to load U-Boot from, when the MMC is being
430 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
431 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
432 depends on SUPPORT_EMMC_BOOT
434 eMMC boot partition is normally configured by the bits of the EXT_CSD
435 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
436 cases it might be required in SPL to load the image from different
437 partition than the partition selected by EXT_CSC_PART_CONFIG register.
438 Enable this option if you intend to use an eMMC boot partition other
439 then selected via EXT_CSC_PART_CONFIG register and specify the custom
440 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
443 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
444 int "Number of the eMMC boot partition to use"
445 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
448 eMMC boot partition number to use when the eMMC in raw mode and
449 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
450 by user defined partition number.
454 default y if SPL_LEGACY_IMAGE_SUPPORT || SPL_EFI_PARTITION
455 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
457 Enable this to support CRC32 in uImages or FIT images within SPL.
458 This is a 32-bit checksum value that can be used to verify images.
459 For FIT images, this is the least secure type of checksum, suitable
460 for detected accidental image corruption. For secure applications you
461 should consider SHA1 or SHA256.
467 Enable this to support MD5 in FIT images within SPL. An MD5
468 checksum is a 128-bit hash value used to check that the image
469 contents have not been corrupted. Note that MD5 is not considered
470 secure as it is possible (with a brute-force attack) to adjust the
471 image while still retaining the same MD5 hash value. For secure
472 applications where images may be changed maliciously, you should
473 consider SHA256 or SHA384.
475 config SPL_FIT_IMAGE_TINY
476 bool "Remove functionality from SPL FIT loading to reduce size"
478 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
479 default y if ARCH_IMX8M
481 Enable this to reduce the size of the FIT image loading code
482 in SPL, if space for the SPL binary is very tight.
484 This skips the recording of each loaded payload
485 (i.e. loadable) into the FDT (modifying the loaded FDT to
486 ensure this information is available to the next image
490 bool "Support CACHE drivers"
492 Enable CACHE drivers in SPL. These drivers can keep data so that
493 future requests for that data can be served faster. Enable this option
494 to build the drivers in drivers/cache as part of an SPL build.
497 bool "Support CPU drivers"
499 Enable this to support CPU drivers in SPL. These drivers can set
500 up CPUs and provide information about them such as the model and
501 name. This can be useful in SPL since setting up the CPUs earlier
502 may improve boot performance. Enable this option to build the
503 drivers in drivers/cpu as part of an SPL build.
506 bool "Support crypto drivers"
508 Enable crypto drivers in SPL. These drivers can be used to
509 accelerate secure boot processing in secure applications. Enable
510 this option to build the drivers in drivers/crypto as part of an
514 bool "Support DMA drivers"
516 Enable DMA (direct-memory-access) drivers in SPL. These drivers
517 can be used to handle memory-to-peripheral data transfer without
518 the CPU moving the data. Enable this option to build the drivers
519 in drivers/dma as part of an SPL build.
521 config SPL_DRIVERS_MISC
522 bool "Support misc drivers"
524 Enable miscellaneous drivers in SPL. These drivers perform various
525 tasks that don't fall nicely into other categories, Enable this
526 option to build the drivers in drivers/misc as part of an SPL
527 build, for those that support building in SPL (not all drivers do).
529 config SPL_ENV_SUPPORT
530 bool "Support an environment"
532 Enable environment support in SPL. The U-Boot environment provides
533 a number of settings (essentially name/value pairs) which can
534 control many aspects of U-Boot's operation. Normally this is not
535 needed in SPL as it has a much simpler task with less
536 configuration. But some boards use this to support 'Falcon' boot
537 on EXT2 and FAT, where SPL boots directly into Linux without
538 starting U-Boot first. Enabling this option will make env_get()
539 and env_set() available in SPL.
542 bool "Support save environment"
543 depends on SPL_ENV_SUPPORT
544 select SPL_MMC_WRITE if ENV_IS_IN_MMC
546 Enable save environment support in SPL after setenv. By default
547 the saveenv option is not provided in SPL, but some boards need
548 this support in 'Falcon' boot, where SPL need to boot from
549 different images based on environment variable set by OS. For
550 example OS may set "reboot_image" environment variable to
551 "recovery" inorder to boot recovery image by SPL. The SPL read
552 "reboot_image" and act accordingly and change the reboot_image
553 to default mode using setenv and save the environment.
556 bool "Support Ethernet"
557 depends on SPL_ENV_SUPPORT
560 Enable access to the network subsystem and associated Ethernet
561 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
562 link rather than from an on-board peripheral. Environment support
563 is required since the network stack uses a number of environment
564 variables. See also SPL_NET.
567 bool "Support EXT filesystems"
569 Enable support for EXT2/3/4 filesystems with SPL. This permits
570 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
571 filesystem from within SPL. Support for the underlying block
572 device (e.g. MMC or USB) must be enabled separately.
574 config SPL_FS_SQUASHFS
575 bool "Support SquashFS filesystems"
578 Enable support for SquashFS filesystems with SPL. This permits
579 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
580 filesystem from within SPL. Support for the underlying block
581 device (e.g. MMC or USB) must be enabled separately.
584 bool "Support FAT filesystems"
587 Enable support for FAT and VFAT filesystems with SPL. This
588 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
589 filesystem from within SPL. Support for the underlying block
590 device (e.g. MMC or USB) must be enabled separately.
593 bool "Support write for FAT filesystems"
595 Enable write support for FAT and VFAT filesystems with SPL.
596 Support for the underlying block device (e.g. MMC or USB) must be
602 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
603 provide software-configurable hardware which is typically used to
604 implement peripherals (such as UARTs, LCD displays, MMC) or
605 accelerate custom processing functions, such as image processing
606 or machine learning. Sometimes it is useful to program the FPGA
607 as early as possible during boot, and this option can enable that
611 bool "Support GPIO in SPL"
613 Enable support for GPIOs (General-purpose Input/Output) in SPL.
614 GPIOs allow U-Boot to read the state of an input line (high or
615 low) and set the state of an output line. This can be used to
616 drive LEDs, control power to various system parts and read user
617 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
618 for example. Enable this option to build the drivers in
619 drivers/gpio as part of an SPL build.
624 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
625 I2C works with a clock and data line which can be driven by a
626 one or more masters or slaves. It is a fairly complex bus but is
627 widely used as it only needs two lines for communication. Speeds of
628 400kbps are typical but up to 3.4Mbps is supported by some
629 hardware. I2C can be useful in SPL to configure power management
630 ICs (PMICs) before raising the CPU clock speed, for example.
631 Enable this option to build the drivers in drivers/i2c as part of
634 config SPL_LIBCOMMON_SUPPORT
635 bool "Support common libraries"
637 Enable support for common U-Boot libraries within SPL. These
638 libraries include common code to deal with U-Boot images,
639 environment and USB, for example. This option is enabled on many
640 boards. Enable this option to build the code in common/ as part of
643 config SPL_LIBDISK_SUPPORT
644 bool "Support disk partitions"
647 Enable support for disk partitions within SPL. 'Disk' is something
648 of a misnomer as it includes non-spinning media such as flash (as
649 used in MMC and USB sticks). Partitions provide a way for a disk
650 to be split up into separate regions, with a partition table placed
651 at the start or end which describes the location and size of each
652 'partition'. These partitions are typically uses as individual block
653 devices, typically with an EXT2 or FAT filesystem in each. This
654 option enables whatever partition support has been enabled in
655 U-Boot to also be used in SPL. It brings in the code in disk/.
657 config SPL_LIBGENERIC_SUPPORT
658 bool "Support generic libraries"
660 Enable support for generic U-Boot libraries within SPL. These
661 libraries include generic code to deal with device tree, hashing,
662 printf(), compression and the like. This option is enabled on many
663 boards. Enable this option to build the code in lib/ as part of an
666 config SPL_DM_MAILBOX
667 bool "Support Mailbox"
669 Enable support for Mailbox within SPL. This enable the inter
670 processor communication protocols tobe used within SPL. Enable
671 this option to build the drivers in drivers/mailbox as part of
677 select HAVE_BLOCK_DEVICE
679 Enable support for MMC (Multimedia Card) within SPL. This enables
680 the MMC protocol implementation and allows any enabled drivers to
681 be used within SPL. MMC can be used with or without disk partition
682 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
683 this option to build the drivers in drivers/mmc as part of an SPL
686 config SYS_MMCSD_FS_BOOT_PARTITION
687 int "MMC Boot Partition"
690 Partition on the MMC to load U-Boot from when the MMC is being
692 Use -1 as a special value to use the first bootable partition.
695 bool "Tiny MMC framework in SPL"
698 Enable MMC framework tinification support. This option is useful if
699 if your SPL is extremely size constrained. Heed the warning, enable
700 this option if and only if you know exactly what you are doing, if
701 you are reading this help text, you most likely have no idea :-)
703 The MMC framework is reduced to bare minimum to be useful. No malloc
704 support is needed for the MMC framework operation with this option
705 enabled. The framework supports exactly one MMC device and exactly
706 one MMC driver. The MMC driver can be adjusted to avoid any malloc
707 operations too, which can remove the need for malloc support in SPL
708 and thus further reduce footprint.
711 bool "MMC/SD/SDIO card support for write operations in SPL"
714 Enable write access to MMC and SD Cards in SPL
717 config SPL_MPC8XXX_INIT_DDR
718 bool "Support MPC8XXX DDR init"
720 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
721 random-access memory) on the MPC8XXX family within SPL. This
722 allows DRAM to be set up before loading U-Boot into that DRAM,
725 config SPL_MTD_SUPPORT
726 bool "Support MTD drivers"
728 Enable support for MTD (Memory Technology Device) within SPL. MTD
729 provides a block interface over raw NAND and can also be used with
730 SPI flash. This allows SPL to load U-Boot from supported MTD
731 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
732 to enable specific MTD drivers.
735 bool "Support new Mentor Graphics USB"
737 Enable support for Mentor Graphics USB in SPL. This is a new
738 driver used by some boards. Enable this option to build
739 the drivers in drivers/usb/musb-new as part of an SPL build. The
740 old drivers are in drivers/usb/musb.
742 config SPL_NAND_SUPPORT
743 bool "Support NAND flash"
745 Enable support for NAND (Negative AND) flash in SPL. NAND flash
746 can be used to allow SPL to load U-Boot from supported devices.
747 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
750 config SPL_NAND_DRIVERS
751 bool "Use standard NAND driver"
753 SPL uses normal NAND drivers, not minimal drivers.
756 bool "Include standard software ECC in the SPL"
758 config SPL_NAND_SIMPLE
759 bool "Support simple NAND drivers in SPL"
761 Support for NAND boot using simple NAND drivers that
762 expose the cmd_ctrl() interface.
765 depends on SPL_NAND_DRIVERS
766 bool "Use Base NAND Driver"
768 Include nand_base.c in the SPL.
770 config SPL_NAND_IDENT
771 depends on SPL_NAND_BASE
772 bool "Use chip ID to identify NAND flash"
774 SPL uses the chip ID list to identify the NAND flash.
779 Enable support for loading payloads from UBI. See
780 README.ubispl for more info.
784 bool "Support SPI DM drivers in SPL"
786 Enable support for SPI DM drivers in SPL.
788 config SPL_DM_SPI_FLASH
789 bool "Support SPI DM FLASH drivers in SPL"
791 Enable support for SPI DM flash drivers in SPL.
795 config SPL_UBI_LOAD_BY_VOLNAME
796 bool "Support loading volumes by name"
798 This enables support for loading UBI volumes by name. When this
799 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
800 configure the volume name from which to load U-Boot.
802 config SPL_UBI_MAX_VOL_LEBS
803 int "Maximum number of LEBs per volume"
806 The maximum number of logical eraseblocks which a static volume
807 to load can contain. Used for sizing the scan data structure.
809 config SPL_UBI_MAX_PEB_SIZE
810 int "Maximum PEB size"
813 The maximum physical erase block size.
815 config SPL_UBI_MAX_PEBS
816 int "Maximum number of PEBs"
819 The maximum physical erase block size. If not overridden by
820 board code, this value will be used as the actual number of PEBs.
822 config SPL_UBI_PEB_OFFSET
823 int "Offset to first UBI PEB"
826 The offset in number of PEBs from the start of flash to the first
827 PEB part of the UBI image.
829 config SPL_UBI_VID_OFFSET
830 int "Offset to VID header"
833 config SPL_UBI_LEB_START
834 int "Offset to LEB in PEB"
837 The offset in bytes to the LEB within a PEB.
839 config SPL_UBI_INFO_ADDR
840 hex "Address to place UBI scan info"
843 Address for ubispl to place the scan info. Read README.ubispl to
844 determine the required size
846 config SPL_UBI_VOL_IDS
847 int "Maximum volume id"
850 The maximum volume id which can be loaded. Used for sizing the
853 config SPL_UBI_LOAD_MONITOR_ID
854 int "id of U-Boot volume"
857 The UBI volume id from which to load U-Boot
859 config SPL_UBI_LOAD_MONITOR_VOLNAME
860 string "volume name of U-Boot volume"
861 depends on SPL_UBI_LOAD_BY_VOLNAME
863 The UBI volume name from which to load U-Boot
865 config SPL_UBI_LOAD_KERNEL_ID
866 int "id of kernel volume"
867 depends on SPL_OS_BOOT && SPL_UBI
869 The UBI volume id from which to load the kernel
871 config SPL_UBI_LOAD_ARGS_ID
872 int "id of kernel args volume"
873 depends on SPL_OS_BOOT && SPL_UBI
875 The UBI volume id from which to load the device tree
877 config UBI_SPL_SILENCE_MSG
878 bool "silence UBI SPL messages"
880 Disable messages from UBI SPL. This leaves warnings
886 bool "Support networking"
888 Enable support for network devices (such as Ethernet) in SPL.
889 This permits SPL to load U-Boot over a network link rather than
890 from an on-board peripheral. Environment support is required since
891 the network stack uses a number of environment variables. See also
895 config SPL_NET_VCI_STRING
896 string "BOOTP Vendor Class Identifier string sent by SPL"
898 As defined by RFC 2132 the vendor class identifier field can be
899 sent by the client to identify the vendor type and configuration
900 of a client. This is often used in practice to allow for the DHCP
901 server to specify different files to load depending on if the ROM,
902 SPL or U-Boot itself makes the request
905 config SPL_NO_CPU_SUPPORT
906 bool "Drop CPU code in SPL"
908 This is specific to the ARM926EJ-S CPU. It disables the standard
909 start.S start-up code, presumably so that a replacement can be
910 used on that CPU. You should not enable it unless you know what
913 config SPL_NOR_SUPPORT
914 bool "Support NOR flash"
916 Enable support for loading U-Boot from memory-mapped NOR (Negative
917 OR) flash in SPL. NOR flash is slow to write but fast to read, and
918 a memory-mapped device makes it very easy to access. Loading from
919 NOR is typically achieved with just a memcpy().
921 config SPL_XIP_SUPPORT
925 Enable support for execute in place of U-Boot or kernel image. There
926 is no need to copy image from flash to ram if flash supports execute
927 in place. Its very useful in systems having enough flash but not
928 enough ram to load the image.
930 config SPL_ONENAND_SUPPORT
931 bool "Support OneNAND flash"
933 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
934 a type of NAND flash and therefore can be used to allow SPL to
935 load U-Boot from supported devices. This enables the drivers in
936 drivers/mtd/onenand as part of an SPL build.
939 bool "Activate Falcon Mode"
940 depends on !TI_SECURE_DEVICE
942 Enable booting directly to an OS from SPL.
943 for more info read doc/README.falcon
947 hex "addr, where OS is found"
948 depends on SPL_NOR_SUPPORT
950 Specify the address, where the OS image is found, which
955 config SPL_FALCON_BOOT_MMCSD
956 bool "Enable Falcon boot from MMC or SD media"
957 depends on SPL_OS_BOOT && SPL_MMC
959 Select this if the Falcon mode OS image mode is on MMC or SD media.
961 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
962 hex "Falcon mode: Sector to load kernel uImage from MMC"
963 depends on SPL_FALCON_BOOT_MMCSD
965 When Falcon mode is used with an MMC or SD media, SPL needs to know
966 where to look for the kernel uImage. The image is expected to begin
967 at the raw MMC specified in this config.
968 Note that the Falcon mode image can also be a FIT, if FIT support is
973 default "tpl/u-boot-with-tpl.bin" if TPL
976 Payload for SPL boot. For backward compatibility, default to
977 u-boot.bin, i.e. RAW image without any header. In case of
978 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
982 bool "Support PCI drivers"
984 Enable support for PCI in SPL. For platforms that need PCI to boot,
985 or must perform some init using PCI in SPL, this provides the
986 necessary driver support. This enables the drivers in drivers/pci
987 as part of an SPL build.
990 bool "Support PCH drivers"
992 Enable support for PCH (Platform Controller Hub) devices in SPL.
993 These are used to set up GPIOs and the SPI peripheral early in
994 boot. This enables the drivers in drivers/pch as part of an SPL
997 config SPL_POST_MEM_SUPPORT
998 bool "Support POST drivers"
1000 Enable support for POST (Power-on Self Test) in SPL. POST is a
1001 procedure that checks that the hardware (CPU or board) appears to
1002 be functionally correctly. It is a sanity check that can be
1003 performed before booting. This enables the drivers in post/drivers
1004 as part of an SPL build.
1007 bool "Support reset drivers"
1010 Enable support for reset control in SPL.
1011 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1012 by using the generic reset API provided by driver model.
1013 This enables the drivers in drivers/reset as part of an SPL build.
1016 bool "Support power drivers"
1018 Enable support for power control in SPL. This includes support
1019 for PMICs (Power-management Integrated Circuits) and some of the
1020 features provided by PMICs. In particular, voltage regulators can
1021 be used to enable/disable power and vary its voltage. That can be
1022 useful in SPL to turn on boot peripherals and adjust CPU voltage
1023 so that the clock speed can be increased. This enables the drivers
1024 in drivers/power, drivers/power/pmic and drivers/power/regulator
1025 as part of an SPL build.
1027 config SPL_POWER_DOMAIN
1028 bool "Support power domain drivers"
1031 Enable support for power domain control in SPL. Many SoCs allow
1032 power to be applied to or removed from portions of the SoC (power
1033 domains). This may be used to save power. This API provides the
1034 means to control such power management hardware. This enables
1035 the drivers in drivers/power/domain as part of a SPL build.
1037 config SPL_RAM_SUPPORT
1038 bool "Support booting from RAM"
1039 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1041 Enable booting of an image in RAM. The image can be preloaded or
1042 it can be loaded by SPL directly into RAM (e.g. using USB).
1044 config SPL_RAM_DEVICE
1045 bool "Support booting from preloaded image in RAM"
1046 depends on SPL_RAM_SUPPORT
1047 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1049 Enable booting of an image already loaded in RAM. The image has to
1050 be already in memory when SPL takes over, e.g. loaded by the boot
1053 config SPL_REMOTEPROC
1054 bool "Support REMOTEPROCS"
1056 Enable support for REMOTEPROCs in SPL. This permits to load
1057 a remote processor firmware in SPL.
1060 bool "Support RTC drivers"
1062 Enable RTC (Real-time Clock) support in SPL. This includes support
1063 for reading and setting the time. Some RTC devices also have some
1064 non-volatile (battery-backed) memory which is accessible if
1065 needed. This enables the drivers in drivers/rtc as part of an SPL
1069 bool "Support loading from SATA"
1071 Enable support for SATA (Serial AT attachment) in SPL. This allows
1072 use of SATA devices such as hard drives and flash drivers for
1073 loading U-Boot. SATA is used in higher-end embedded systems and
1074 can provide higher performance than MMC , at somewhat higher
1075 expense and power consumption. This enables loading from SATA
1076 using a configured device.
1078 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1079 bool "SATA raw mode: by sector"
1081 default y if ARCH_MVEBU
1083 Use sector number for specifying U-Boot location on SATA disk in
1086 config SPL_SATA_RAW_U_BOOT_SECTOR
1087 hex "Sector on the SATA disk to load U-Boot from"
1088 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1089 default 0x1 if ARCH_MVEBU
1091 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1092 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1095 bool "Support serial"
1099 Enable support for serial in SPL. This allows use of a serial UART
1100 for displaying messages while SPL is running. It also brings in
1101 printf() and panic() functions. This should normally be enabled
1102 unless there are space reasons not to. Even then, consider
1103 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1106 bool "Support SPI drivers"
1108 Enable support for using SPI in SPL. This is used for connecting
1109 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1110 more details on that. The SPI driver provides the transport for
1111 data between the SPI flash and the CPU. This option can be used to
1112 enable SPI drivers that are needed for other purposes also, such
1115 config SPL_SPI_FLASH_SUPPORT
1116 bool "Support SPI flash drivers"
1119 Enable support for using SPI flash in SPL, and loading U-Boot from
1120 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1121 the SPI bus that is used to connect it to a system. It is a simple
1122 but fast bidirectional 4-wire bus (clock, chip select and two data
1123 lines). This enables the drivers in drivers/mtd/spi as part of an
1124 SPL build. This normally requires SPL_SPI.
1126 if SPL_SPI_FLASH_SUPPORT
1128 config SPL_SPI_FLASH_TINY
1129 bool "Enable low footprint SPL SPI Flash support"
1130 depends on !SPI_FLASH_BAR
1131 default y if SPI_FLASH
1133 Enable lightweight SPL SPI Flash support that supports just reading
1134 data/images from flash. No support to write/erase flash. Enable
1135 this if you have SPL size limitations and don't need full
1136 fledged SPI flash support.
1138 config SPL_SPI_FLASH_SFDP_SUPPORT
1139 bool "SFDP table parsing support for SPI NOR flashes"
1140 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1142 Enable support for parsing and auto discovery of parameters for
1143 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1144 tables as per JESD216 standard in SPL.
1146 config SPL_SPI_FLASH_MTD
1147 bool "Support for SPI flash MTD drivers in SPL"
1149 Enable support for SPI flash MTD drivers in SPL.
1152 bool "Support loading from SPI flash"
1154 Enable support for loading next stage, U-Boot or otherwise, from
1155 SPI NOR in U-Boot SPL.
1157 endif # SPL_SPI_FLASH_SUPPORT
1159 config SYS_SPI_U_BOOT_OFFS
1160 hex "address of u-boot payload in SPI flash"
1161 default 0x8000 if ARCH_SUNXI
1163 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1165 Address within SPI-Flash from where the u-boot payload is fetched
1169 bool "Driver support for thermal devices"
1171 Enable support for temperature-sensing devices. Some SoCs have on-chip
1172 temperature sensors to permit warnings, speed throttling or even
1173 automatic power-off when the temperature gets too high or low. Other
1174 devices may be discrete but connected on a suitable bus.
1177 bool "Support USB host drivers"
1178 select HAVE_BLOCK_DEVICE
1180 Enable access to USB (Universal Serial Bus) host devices so that
1181 SPL can load U-Boot from a connected USB peripheral, such as a USB
1182 flash stick. While USB takes a little longer to start up than most
1183 buses, it is very flexible since many different types of storage
1184 device can be attached. This option enables the drivers in
1185 drivers/usb/host as part of an SPL build.
1187 config SPL_USB_STORAGE
1188 bool "Support loading from USB"
1189 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1191 Enable support for USB devices in SPL. This allows use of USB
1192 devices such as hard drives and flash drivers for loading U-Boot.
1193 The actual drivers are enabled separately using the normal U-Boot
1194 config options. This enables loading from USB using a configured
1197 config SPL_USB_GADGET
1198 bool "Suppport USB Gadget drivers"
1200 Enable USB Gadget API which allows to enable USB device functions
1205 config SPL_USB_ETHER
1206 bool "Support USB Ethernet drivers"
1209 Enable access to the USB network subsystem and associated
1210 drivers in SPL. This permits SPL to load U-Boot over a
1211 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1212 than from an onboard peripheral. Environment support is required
1213 since the network stack uses a number of environment variables.
1214 See also SPL_NET and SPL_ETH.
1217 bool "Support DFU (Device Firmware Upgrade)"
1219 select SPL_DFU_NO_RESET
1220 depends on SPL_RAM_SUPPORT
1222 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1223 RAM memory device support. The ROM code will load and execute
1224 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1225 selected device partition from host-pc using dfu-utils.
1226 This feature is useful to flash the binaries to factory or bare-metal
1227 boards using USB interface.
1230 bool "DFU device selection"
1235 depends on SPL_DFU && SPL_RAM_SUPPORT
1237 select RAM/DDR memory device for loading binary images
1238 (u-boot/kernel) to the selected device partition using
1239 DFU and execute the u-boot/kernel from RAM.
1243 config SPL_USB_SDP_SUPPORT
1244 bool "Support SDP (Serial Download Protocol)"
1245 depends on SPL_SERIAL
1247 Enable Serial Download Protocol (SDP) device support in SPL. This
1248 allows to download images into memory and execute (jump to) them
1249 using the same protocol as implemented by the i.MX family's boot ROM.
1251 config SPL_SDP_USB_DEV
1252 int "SDP USB controller index"
1254 depends on SPL_USB_SDP_SUPPORT
1256 Some boards have USB controller other than 0. Define this option
1257 so it can be used in compiled environment.
1261 bool "Support watchdog drivers"
1262 imply SPL_WDT if !HW_WATCHDOG
1264 Enable support for watchdog drivers in SPL. A watchdog is
1265 typically a hardware peripheral which can reset the system when it
1266 detects no activity for a while (such as a software crash). This
1267 enables the drivers in drivers/watchdog as part of an SPL build.
1269 config SPL_YMODEM_SUPPORT
1270 bool "Support loading using Ymodem"
1271 depends on SPL_SERIAL
1273 While loading from serial is slow it can be a useful backup when
1274 there is no other option. The Ymodem protocol provides a reliable
1275 means of transmitting U-Boot over a serial line for using in SPL,
1276 with a checksum to ensure correctness.
1279 bool "Support ARM Trusted Firmware"
1280 depends on ARM64 && SPL_FIT
1282 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1283 is loaded by SPL (which is considered as BL2 in ATF terminology).
1284 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1286 config SPL_ATF_LOAD_IMAGE_V2
1287 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1290 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1292 If you want to load a bl31 image from the SPL and need the new
1295 config SPL_ATF_NO_PLATFORM_PARAM
1296 bool "Pass no platform parameter"
1299 While we expect to call a pointer to a valid FDT (or NULL)
1300 as the platform parameter to an ATF, some ATF versions are
1301 not U-Boot aware and have an insufficiently robust parameter
1302 validation to gracefully reject a FDT being passed.
1304 If this option is enabled, the spl_atf os-type handler will
1305 always pass NULL for the platform parameter.
1307 If your ATF is affected, say Y.
1309 config SPL_AM33XX_ENABLE_RTC32K_OSC
1310 bool "Enable the RTC32K OSC on AM33xx based platforms"
1313 Enable access to the AM33xx RTC and select the external 32kHz clock
1316 config SPL_OPTEE_IMAGE
1317 bool "Support OP-TEE Trusted OS image in SPL"
1320 OP-TEE is an open source Trusted OS which is loaded by SPL.
1321 More detail at: https://github.com/OP-TEE/optee_os
1324 bool "Support RISC-V OpenSBI"
1325 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1327 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1328 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1329 firmware. It is loaded and started by U-Boot SPL.
1331 More details are available at https://github.com/riscv/opensbi and
1332 https://github.com/riscv/riscv-sbi-doc
1334 config SPL_OPENSBI_LOAD_ADDR
1335 hex "OpenSBI load address"
1336 depends on SPL_OPENSBI
1338 Load address of the OpenSBI binary.
1342 depends on SUPPORT_TPL
1345 If you want to build TPL as well as the normal image and SPL, say Y.
1349 config TPL_SIZE_LIMIT
1350 hex "Maximum size of TPL image"
1354 Specifies the maximum length of the U-Boot TPL image.
1355 If this value is zero, it is ignored.
1357 config TPL_BINMAN_SYMBOLS
1358 bool "Declare binman symbols in TPL"
1359 depends on SPL_FRAMEWORK && BINMAN
1362 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1363 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1364 and spl_get_image_size().
1366 For this to work, you must have a U-Boot image in the binman image, so
1367 binman can update TPL with the location of it.
1369 config TPL_FRAMEWORK
1370 bool "Support TPL based upon the common SPL framework"
1371 default y if SPL_FRAMEWORK
1373 Enable the SPL framework under common/spl/ for TPL builds.
1374 This framework supports MMC, NAND and YMODEM and other methods
1375 loading of U-Boot's SPL stage. If unsure, say Y.
1378 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1379 depends on HANDOFF && TPL_BLOBLIST
1382 This option enables TPL to write handoff information. This can be
1383 used to pass information like the size of SDRAM from TPL to U-Boot
1384 proper. The information is also available to SPL if it is useful
1387 config TPL_BOARD_INIT
1388 bool "Call board-specific initialization in TPL"
1390 If this option is enabled, U-Boot will call the function
1391 spl_board_init() from board_init_r(). This function should be
1392 provided by the board.
1394 config TPL_BOOTCOUNT_LIMIT
1395 bool "Support bootcount in TPL"
1396 depends on TPL_ENV_SUPPORT
1398 If this option is enabled, the TPL will support bootcount.
1399 For example, it may be useful to choose the device to boot.
1402 string "Linker script for the TPL stage"
1404 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1405 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1407 The TPL stage will usually require a different linker-script
1408 (as it runs from a different memory region) than the regular
1409 U-Boot stage. Set this to the path of the linker-script to
1412 May be left empty to trigger the Makefile infrastructure to
1413 fall back to the linker-script used for the SPL stage.
1415 config TPL_NEEDS_SEPARATE_STACK
1416 bool "TPL needs a separate initial stack-pointer"
1419 Enable, if the TPL stage should not inherit its initial
1420 stack-pointer from the settings for the SPL stage.
1423 bool "Support power drivers"
1425 Enable support for power control in TPL. This includes support
1426 for PMICs (Power-management Integrated Circuits) and some of the
1427 features provided by PMICs. In particular, voltage regulators can
1428 be used to enable/disable power and vary its voltage. That can be
1429 useful in TPL to turn on boot peripherals and adjust CPU voltage
1430 so that the clock speed can be increased. This enables the drivers
1431 in drivers/power, drivers/power/pmic and drivers/power/regulator
1432 as part of an TPL build.
1434 config TPL_TEXT_BASE
1435 hex "Base address for the .text section of the TPL stage"
1438 The base address for the .text section of the TPL stage.
1441 int "Maximum size (in bytes) for the TPL stage"
1445 The maximum size (in bytes) of the TPL stage.
1448 hex "Address of the initial stack-pointer for the TPL stage"
1449 depends on TPL_NEEDS_SEPARATE_STACK
1451 The address of the initial stack-pointer for the TPL stage.
1452 Usually this will be the (aligned) top-of-stack.
1454 config TPL_READ_ONLY
1456 depends on TPL_OF_PLATDATA
1457 select TPL_OF_PLATDATA_NO_BIND
1458 select TPL_OF_PLATDATA_RT
1460 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1461 section of memory. This means that of-platdata must make a copy (in
1462 writeable memory) of anything it wants to modify, such as
1463 device-private data.
1465 config TPL_BOOTROM_SUPPORT
1466 bool "Support returning to the BOOTROM (from TPL)"
1468 Some platforms (e.g. the Rockchip RK3368) provide support in their
1469 ROM for loading the next boot-stage after performing basic setup
1472 Enable this option, to return to the BOOTROM through the
1473 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1474 boot device list, if not implemented for a given board)
1477 bool "Support CRC32 in TPL"
1478 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1480 Enable this to support CRC32 in uImages or FIT images within SPL.
1481 This is a 32-bit checksum value that can be used to verify images.
1482 For FIT images, this is the least secure type of checksum, suitable
1483 for detected accidental image corruption. For secure applications you
1484 should consider SHA1 or SHA256.
1486 config TPL_DRIVERS_MISC
1487 bool "Support misc drivers in TPL"
1489 Enable miscellaneous drivers in TPL. These drivers perform various
1490 tasks that don't fall nicely into other categories, Enable this
1491 option to build the drivers in drivers/misc as part of an TPL
1492 build, for those that support building in TPL (not all drivers do).
1494 config TPL_ENV_SUPPORT
1495 bool "Support an environment"
1497 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1500 bool "Support GPIO in TPL"
1502 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1503 GPIOs allow U-Boot to read the state of an input line (high or
1504 low) and set the state of an output line. This can be used to
1505 drive LEDs, control power to various system parts and read user
1506 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1507 for example. Enable this option to build the drivers in
1508 drivers/gpio as part of an TPL build.
1513 Enable support for the I2C bus in TPL. See SPL_I2C for
1516 config TPL_LIBCOMMON_SUPPORT
1517 bool "Support common libraries"
1519 Enable support for common U-Boot libraries within TPL. See
1520 SPL_LIBCOMMON_SUPPORT for details.
1522 config TPL_LIBGENERIC_SUPPORT
1523 bool "Support generic libraries"
1525 Enable support for generic U-Boot libraries within TPL. See
1526 SPL_LIBGENERIC_SUPPORT for details.
1528 config TPL_MPC8XXX_INIT_DDR
1529 bool "Support MPC8XXX DDR init"
1531 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1532 SPL_MPC8XXX_INIT_DDR for details.
1538 Enable support for MMC within TPL. See SPL_MMC for details.
1540 config TPL_NAND_SUPPORT
1541 bool "Support NAND flash"
1543 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1546 bool "Support PCI drivers"
1548 Enable support for PCI in TPL. For platforms that need PCI to boot,
1549 or must perform some init using PCI in SPL, this provides the
1550 necessary driver support. This enables the drivers in drivers/pci
1551 as part of a TPL build.
1554 bool "Support PCH drivers"
1556 Enable support for PCH (Platform Controller Hub) devices in TPL.
1557 These are used to set up GPIOs and the SPI peripheral early in
1558 boot. This enables the drivers in drivers/pch as part of a TPL
1561 config TPL_RAM_SUPPORT
1562 bool "Support booting from RAM"
1564 Enable booting of an image in RAM. The image can be preloaded or
1565 it can be loaded by TPL directly into RAM (e.g. using USB).
1567 config TPL_RAM_DEVICE
1568 bool "Support booting from preloaded image in RAM"
1569 depends on TPL_RAM_SUPPORT
1571 Enable booting of an image already loaded in RAM. The image has to
1572 be already in memory when TPL takes over, e.g. loaded by the boot
1576 bool "Support RTC drivers"
1578 Enable RTC (Real-time Clock) support in TPL. This includes support
1579 for reading and setting the time. Some RTC devices also have some
1580 non-volatile (battery-backed) memory which is accessible if
1581 needed. This enables the drivers in drivers/rtc as part of an TPL
1585 bool "Support serial"
1589 Enable support for serial in TPL. See SPL_SERIAL for
1592 config TPL_SPI_FLASH_SUPPORT
1593 bool "Support SPI flash drivers"
1595 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1598 config TPL_SPI_FLASH_TINY
1599 bool "Enable low footprint TPL SPI Flash support"
1600 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1601 default y if SPI_FLASH
1603 Enable lightweight TPL SPI Flash support that supports just reading
1604 data/images from flash. No support to write/erase flash. Enable
1605 this if you have TPL size limitations and don't need full-fledged
1609 bool "Support loading from SPI flash"
1610 depends on TPL_SPI_FLASH_SUPPORT
1612 Enable support for loading next stage, U-Boot or otherwise, from
1613 SPI NOR in U-Boot TPL.
1616 bool "Support SPI drivers"
1618 Enable support for using SPI in TPL. See SPL_SPI for
1622 bool "Support SPI DM drivers in TPL"
1624 Enable support for SPI DM drivers in TPL.
1626 config TPL_DM_SPI_FLASH
1627 bool "Support SPI DM FLASH drivers in TPL"
1629 Enable support for SPI DM flash drivers in TPL.
1631 config TPL_YMODEM_SUPPORT
1632 bool "Support loading using Ymodem"
1633 depends on TPL_SERIAL
1635 While loading from serial is slow it can be a useful backup when
1636 there is no other option. The Ymodem protocol provides a reliable
1637 means of transmitting U-Boot over a serial line for using in TPL,
1638 with a checksum to ensure correctness.
1644 depends on SUPPORT_SPL
1647 If you want to build VPL as well as the normal image, TPL and SPL,
1652 config VPL_BANNER_PRINT
1653 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1657 If this option is enabled, VPL will print the banner with version
1658 info. Disabling this option could be useful to reduce VPL boot time
1659 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1661 config VPL_BOARD_INIT
1662 bool "Call board-specific initialization in VPL"
1664 If this option is enabled, U-Boot will call the function
1665 spl_board_init() from board_init_r(). This function should be
1666 provided by the board.
1670 bool "Support cache drivers in VPL"
1672 Enable support for cache drivers in VPL.
1675 bool "Support CRC32 in VPL"
1676 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1678 Enable this to support CRC32 in uImages or FIT images within VPL.
1679 This is a 32-bit checksum value that can be used to verify images.
1680 For FIT images, this is the least secure type of checksum, suitable
1681 for detected accidental image corruption. For secure applications you
1682 should consider SHA1 or SHA256.
1685 bool "Support SPI DM drivers in VPL"
1687 Enable support for SPI DM drivers in VPL.
1689 config VPL_DM_SPI_FLASH
1690 bool "Support SPI DM FLASH drivers in VPL"
1692 Enable support for SPI DM flash drivers in VPL.
1694 config VPL_FRAMEWORK
1695 bool "Support VPL based upon the common SPL framework"
1698 Enable the SPL framework under common/spl/ for VPL builds.
1699 This framework supports MMC, NAND and YMODEM and other methods
1700 loading of U-Boot's next stage. If unsure, say Y.
1703 bool "Pass hand-off information from VPL to SPL"
1704 depends on HANDOFF && VPL_BLOBLIST
1707 This option enables VPL to write handoff information. This can be
1708 used to pass information like the size of SDRAM from VPL to SPL. Also
1709 VPL can receive information from TPL in the same place if that is
1712 config VPL_LIBCOMMON_SUPPORT
1713 bool "Support common libraries"
1714 default y if SPL_LIBCOMMON_SUPPORT
1716 Enable support for common U-Boot libraries within VPL. See
1717 SPL_LIBCOMMON_SUPPORT for details.
1719 config VPL_LIBGENERIC_SUPPORT
1720 bool "Support generic libraries"
1721 default y if SPL_LIBGENERIC_SUPPORT
1723 Enable support for generic U-Boot libraries within VPL. These
1724 libraries include generic code to deal with device tree, hashing,
1725 printf(), compression and the like. This option is enabled on many
1726 boards. Enable this option to build the code in lib/ as part of a
1729 config VPL_DRIVERS_MISC
1730 bool "Support misc drivers"
1731 default y if TPL_DRIVERS_MISC
1733 Enable miscellaneous drivers in VPL. These drivers perform various
1734 tasks that don't fall nicely into other categories, Enable this
1735 option to build the drivers in drivers/misc as part of a VPL
1736 build, for those that support building in VPL (not all drivers do).
1738 config VPL_ENV_SUPPORT
1739 bool "Support an environment"
1741 Enable environment support in VPL. The U-Boot environment provides
1742 a number of settings (essentially name/value pairs) which can
1743 control many aspects of U-Boot's operation. Enabling this option will
1744 make env_get() and env_set() available in VSPL.
1747 bool "Support GPIO in VPL"
1748 default y if SPL_GPIO
1750 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1751 GPIOs allow U-Boot to read the state of an input line (high or
1752 low) and set the state of an output line. This can be used to
1753 drive LEDs, control power to various system parts and read user
1754 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1755 for example. Enable this option to build the drivers in
1756 drivers/gpio as part of a VPL build.
1759 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1760 depends on HANDOFF && VPL_BLOBLIST
1763 This option enables VPL to write handoff information. This can be
1764 used to pass information like the size of SDRAM from VPL to U-Boot
1765 proper. The information is also available to VPL if it is useful
1769 bool "Support hashing drivers in VPL"
1774 Enable hashing drivers in VPL. These drivers can be used to
1775 accelerate secure boot processing in secure applications. Enable
1776 this option to build system-specific drivers for hash acceleration
1777 as part of a VPL build.
1779 config VPL_I2C_SUPPORT
1780 bool "Support I2C in VPL"
1781 default y if SPL_I2C_SUPPORT
1783 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1786 config VPL_PCH_SUPPORT
1787 bool "Support PCH drivers"
1788 default y if TPL_PCH_SUPPORT
1790 Enable support for PCH (Platform Controller Hub) devices in VPL.
1791 These are used to set up GPIOs and the SPI peripheral early in
1792 boot. This enables the drivers in drivers/pch as part of a VPL
1796 bool "Support PCI drivers"
1797 default y if SPL_PCI
1799 Enable support for PCI in VPL. For platforms that need PCI to boot,
1800 or must perform some init using PCI in VPL, this provides the
1801 necessary driver support. This enables the drivers in drivers/pci
1802 as part of a VPL build.
1805 bool "Support RTC drivers"
1807 Enable RTC (Real-time Clock) support in VPL. This includes support
1808 for reading and setting the time. Some RTC devices also have some
1809 non-volatile (battery-backed) memory which is accessible if
1810 needed. This enables the drivers in drivers/rtc as part of a VPL
1814 bool "Support serial"
1815 default y if TPL_SERIAL
1819 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1822 config VPL_SIZE_LIMIT
1823 hex "Maximum size of VPL image"
1827 Specifies the maximum length of the U-Boot VPL image.
1828 If this value is zero, it is ignored.
1831 bool "Support SPI drivers"
1833 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
1836 config VPL_SPI_FLASH_SUPPORT
1837 bool "Support SPI flash drivers"
1839 Enable support for using SPI flash in VPL, and loading U-Boot from
1840 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1841 the SPI bus that is used to connect it to a system. It is a simple
1842 but fast bidirectional 4-wire bus (clock, chip select and two data
1843 lines). This enables the drivers in drivers/mtd/spi as part of a
1844 VPL build. This normally requires VPL_SPI_SUPPORT.
1846 config VPL_TEXT_BASE
1850 The address in memory that VPL will be running from.
1854 config SPL_AT91_MCK_BYPASS
1855 bool "Use external clock signal as a source of main clock for AT91 platforms"
1856 depends on ARCH_AT91
1858 Use external 8 to 24 Mhz clock signal as source of main clock instead
1859 of an external crystal oscillator.
1860 This option disables the internal driving on the XOUT pin.
1861 The external source has to provide a stable clock on the XIN pin.
1862 If this option is disabled, the SoC expects a crystal oscillator
1863 that needs driving on both XIN and XOUT lines.