9 config SPL_DFU_NO_RESET
14 depends on SUPPORT_SPL
17 If you want to build SPL as well as the normal image, say Y.
20 bool "Support SPL based upon the common SPL framework"
24 Enable the SPL framework under common/spl/. This framework
25 supports MMC, NAND and YMODEM and other methods loading of U-Boot
26 and the Linux Kernel. If unsure, say Y.
28 config SPL_FRAMEWORK_BOARD_INIT_F
29 bool "Define a generic function board_init_f"
30 depends on SPL_FRAMEWORK
32 Define a generic function board_init_f that:
33 - initialize the spl (spl_early_init)
34 - initialize the serial (preloader_console_init)
35 Unless you want to provide your own board_init_f, you should say Y.
38 hex "Maximum size of SPL image"
40 default 0x11000 if ARCH_MX6 && !MX6_OCRAM_256KB
41 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
44 Specifies the maximum length of the U-Boot SPL image.
45 If this value is zero, it is ignored.
47 config SPL_SIZE_LIMIT_SUBTRACT_GD
48 bool "SPL image size check: provide space for global data"
49 depends on SPL_SIZE_LIMIT > 0
51 If enabled, aligned size of global data is reserved in
52 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
53 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
54 pre-reloc global data is put into this SRAM, too.
56 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
57 bool "SPL image size check: provide space for malloc() pool before relocation"
58 depends on SPL_SIZE_LIMIT > 0
60 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
61 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
62 describes the size of SRAM available for SPL when pre-reloc malloc
63 pool is put into this SRAM, too.
65 config SPL_SIZE_LIMIT_PROVIDE_STACK
66 hex "SPL image size check: provide stack space before relocation"
67 depends on SPL_SIZE_LIMIT > 0
70 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
71 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
72 of SRAM available for SPL when the stack required before reolcation
75 config SPL_SYS_STACK_F_CHECK_BYTE
79 Constant used to check the stack
81 config SPL_SYS_REPORT_STACK_F_USAGE
82 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
83 bool "Check and report stack usage in SPL before relocation"
85 If this option is enabled, the initial SPL stack is filled with 0xaa
86 very early, up to the size configured with
87 SPL_SIZE_LIMIT_PROVIDE_STACK.
88 Later when SPL is done using this initial stack and switches to a
89 stack in DRAM, the actually used size of this initial stack is
90 reported by examining the memory and searching for the lowest
91 occurrence of non 0xaa bytes.
92 This default implementation works for stacks growing down only.
94 menu "PowerPC and LayerScape SPL Boot options"
97 bool "Load SPL from NAND flash"
98 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
101 bool "Load SPL from SD Card / eMMC"
102 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
105 bool "Load SPL from SPI flash"
106 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
109 bool "Create SPL in Freescale PBI format"
110 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
113 Create boot binary having SPL binary in PBI format concatenated with
119 bool "Pass hand-off information from SPL to U-Boot proper"
122 It is useful to be able to pass information from SPL to U-Boot
123 proper to preserve state that is known in SPL and is needed in U-Boot.
124 Enable this to locate the handoff information in U-Boot proper, early
125 in boot. It is available in gd->handoff. The state state is set up
126 in SPL (or TPL if that is being used).
131 bool "Pass hand-off information from SPL to U-Boot proper"
132 depends on HANDOFF && SPL_BLOBLIST
135 This option enables SPL to write handoff information. This can be
136 used to pass information like the size of SDRAM from SPL to U-Boot
137 proper. Also SPL can receive information from TPL in the same place
141 string "Linker script for the SPL stage"
142 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
144 The SPL stage will usually require a different linker-script
145 (as it runs from a different memory region) than the regular
146 U-Boot stage. Set this to the path of the linker-script to
151 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
152 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
153 default 0x20060 if MACH_SUN50I_H6
154 default 0x00060 if ARCH_SUNXI
155 default 0xfffc0000 if ARCH_ZYNQMP
158 The address in memory that SPL will be running from.
160 config SPL_BOARD_INIT
161 bool "Call board-specific initialization in SPL"
163 If this option is enabled, U-Boot will call the function
164 spl_board_init() from board_init_r(). This function should be
165 provided by the board.
167 config SPL_BOOTROM_SUPPORT
168 bool "Support returning to the BOOTROM"
170 Some platforms (e.g. the Rockchip RK3368) provide support in their
171 ROM for loading the next boot-stage after performing basic setup
174 Enable this option, to return to the BOOTROM through the
175 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
176 boot device list, if not implemented for a given board)
178 config SPL_BOOTCOUNT_LIMIT
179 bool "Support bootcount in SPL"
180 depends on SPL_ENV_SUPPORT
182 On some boards, which use 'falcon' mode, it is necessary to check
183 and increment the number of boot attempts. Such boards do not
184 use proper U-Boot for normal boot flow and hence needs those
185 adjustments to be done in the SPL.
187 config SPL_RAW_IMAGE_SUPPORT
188 bool "Support SPL loading and booting of RAW images"
189 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
190 default y if !TI_SECURE_DEVICE
192 SPL will support loading and booting a RAW image when this option
193 is y. If this is not set, SPL will move on to other available
194 boot media to find a suitable image.
196 config SPL_LEGACY_IMAGE_SUPPORT
197 bool "Support SPL loading and booting of Legacy images"
198 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
200 SPL will support loading and booting Legacy images when this option
201 is y. If this is not set, SPL will move on to other available
202 boot media to find a suitable image.
204 config SPL_LEGACY_IMAGE_CRC_CHECK
205 bool "Check CRC of Legacy images"
206 depends on SPL_LEGACY_IMAGE_SUPPORT
207 select SPL_CRC32_SUPPORT
209 Enable this to check the CRC of Legacy images. While this increases
210 reliability, it affects both code size and boot duration.
211 If disabled, Legacy images are booted if the image magic and size
212 are correct, without further integrity checks.
214 config SPL_SYS_MALLOC_SIMPLE
216 prompt "Only use malloc_simple functions in the SPL"
218 Say Y here to only use the *_simple malloc functions from
219 malloc_simple.c, rather then using the versions from dlmalloc.c;
220 this will make the SPL binary smaller at the cost of more heap
221 usage as the *_simple malloc functions do not re-use free-ed mem.
223 config TPL_SYS_MALLOC_SIMPLE
225 prompt "Only use malloc_simple functions in the TPL"
228 Say Y here to only use the *_simple malloc functions from
229 malloc_simple.c, rather then using the versions from dlmalloc.c;
230 this will make the TPL binary smaller at the cost of more heap
231 usage as the *_simple malloc functions do not re-use free-ed mem.
234 bool "Enable SDRAM location for SPL stack"
236 SPL starts off execution in SRAM and thus typically has only a small
237 stack available. Since SPL sets up DRAM while in its board_init_f()
238 function, it is possible for the stack to move there before
239 board_init_r() is reached. This option enables a special SDRAM
240 location for the SPL stack. U-Boot SPL switches to this after
241 board_init_f() completes, and before board_init_r() starts.
243 config SPL_STACK_R_ADDR
244 depends on SPL_STACK_R
245 hex "SDRAM location for SPL stack"
246 default 0x82000000 if ARCH_OMAP2PLUS
248 Specify the address in SDRAM for the SPL stack. This will be set up
249 before board_init_r() is called.
251 config SPL_STACK_R_MALLOC_SIMPLE_LEN
252 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
253 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
256 Specify the amount of the stack to use as memory pool for
257 malloc_simple after switching the stack to DRAM. This may be set
258 to give board_init_r() a larger heap then the initial heap in
259 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
261 config SPL_SEPARATE_BSS
262 bool "BSS section is in a different memory region from text"
264 Some platforms need a large BSS region in SPL and can provide this
265 because RAM is already set up. In this case BSS can be moved to RAM.
266 This option should then be enabled so that the correct device tree
267 location is used. Normally we put the device tree at the end of BSS
268 but with this option enabled, it goes at _image_binary_end.
270 config SPL_BANNER_PRINT
271 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
274 If this option is enabled, SPL will print the banner with version
275 info. Disabling this option could be useful to reduce SPL boot time
276 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
278 config TPL_BANNER_PRINT
279 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
283 If this option is enabled, TPL will print the banner with version
284 info. Disabling this option could be useful to reduce TPL boot time
285 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
288 depends on ARM && !ARM64
289 bool "Allows initializing BSS early before entering board_init_f"
291 On some platform we have sufficient memory available early on to
292 allow setting up and using a basic BSS prior to entering
293 board_init_f. Activating this option will also de-activate the
294 clearing of BSS during the SPL relocation process, thus allowing
295 to carry state from board_init_f to board_init_r by way of BSS.
297 config SPL_DISPLAY_PRINT
298 bool "Display a board-specific message in SPL"
300 If this option is enabled, U-Boot will call the function
301 spl_display_print() immediately after displaying the SPL console
302 banner ("U-Boot SPL ..."). This function should be provided by
305 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
306 bool "MMC raw mode: by sector"
307 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
308 ARCH_MX6 || ARCH_MX7 || \
309 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
310 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
311 OMAP44XX || OMAP54XX || AM33XX || AM43XX || TARGET_SIFIVE_FU540
313 Use sector number for specifying U-Boot location on MMC/SD in
316 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
317 hex "Address on the MMC to load U-Boot from"
318 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
319 default 0x50 if ARCH_SUNXI
320 default 0x75 if ARCH_DAVINCI
321 default 0x8a if ARCH_MX6 || ARCH_MX7
322 default 0x100 if ARCH_UNIPHIER
323 default 0x140 if ARCH_MVEBU
324 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
325 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
326 OMAP54XX || AM33XX || AM43XX || ARCH_K3
327 default 0x4000 if ARCH_ROCKCHIP
328 default 0x822 if TARGET_SIFIVE_FU540
330 Address on the MMC to load U-Boot from, when the MMC is being used
331 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
333 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
334 hex "U-Boot main hardware partition image offset"
335 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
338 On some platforms SPL location depends on hardware partition. The ROM
339 code skips the MBR sector when loading SPL from main hardware data
340 partition. This adds offset to the main U-Boot image. Set this symbol
341 to the number of skipped sectors.
343 If unsure, leave the default.
345 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
346 bool "MMC Raw mode: by partition"
348 Use a partition for loading U-Boot when using MMC/SD in raw mode.
350 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
351 hex "Partition to use to load U-Boot from"
352 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
355 Partition on the MMC to load U-Boot from when the MMC is being
358 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
359 bool "MMC raw mode: by partition type"
360 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
362 Use partition type for specifying U-Boot partition on MMC/SD in
363 raw mode. U-Boot will be loaded from the first partition of this
366 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
367 hex "Partition Type on the MMC to load U-Boot from"
368 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
370 Partition Type on the MMC to load U-Boot from, when the MMC is being
373 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
374 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
375 depends on SUPPORT_EMMC_BOOT
377 eMMC boot partition is normally configured by the bits of the EXT_CSD
378 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
379 cases it might be required in SPL to load the image from different
380 partition than the partition selected by EXT_CSC_PART_CONFIG register.
381 Enable this option if you intend to use an eMMC boot partition other
382 then selected via EXT_CSC_PART_CONFIG register and specify the custom
383 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
386 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
387 int "Number of the eMMC boot partition to use"
388 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
391 eMMC boot partition number to use when the eMMC in raw mode and
392 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
393 by user defined partition number.
395 config SPL_CRC32_SUPPORT
397 default y if SPL_LEGACY_IMAGE_SUPPORT
399 Enable this to support CRC32 in uImages or FIT images within SPL.
400 This is a 32-bit checksum value that can be used to verify images.
401 For FIT images, this is the least secure type of checksum, suitable
402 for detected accidental image corruption. For secure applications you
403 should consider SHA1 or SHA256.
405 config SPL_MD5_SUPPORT
409 Enable this to support MD5 in FIT images within SPL. An MD5
410 checksum is a 128-bit hash value used to check that the image
411 contents have not been corrupted. Note that MD5 is not considered
412 secure as it is possible (with a brute-force attack) to adjust the
413 image while still retaining the same MD5 hash value. For secure
414 applications where images may be changed maliciously, you should
415 consider SHA256 or SHA384.
417 config SPL_SHA1_SUPPORT
422 Enable this to support SHA1 in FIT images within SPL. A SHA1
423 checksum is a 160-bit (20-byte) hash value used to check that the
424 image contents have not been corrupted or maliciously altered.
425 While SHA1 is fairly secure it is coming to the end of its life
426 due to the expanding computing power available to brute-force
427 attacks. For more security, consider SHA256 or SHA384.
429 config SPL_SHA256_SUPPORT
430 bool "Support SHA256"
434 Enable this to support SHA256 in FIT images within SPL. A SHA256
435 checksum is a 256-bit (32-byte) hash value used to check that the
436 image contents have not been corrupted.
438 config SPL_SHA384_SUPPORT
439 bool "Support SHA384"
444 Enable this to support SHA384 in FIT images within SPL. A SHA384
445 checksum is a 384-bit (48-byte) hash value used to check that the
446 image contents have not been corrupted. Use this for the highest
449 config SPL_SHA512_SUPPORT
450 bool "Support SHA512"
455 Enable this to support SHA512 in FIT images within SPL. A SHA512
456 checksum is a 512-bit (64-byte) hash value used to check that the
457 image contents have not been corrupted.
459 config SPL_FIT_IMAGE_TINY
460 bool "Remove functionality from SPL FIT loading to reduce size"
462 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
463 default y if ARCH_IMX8M
465 Enable this to reduce the size of the FIT image loading code
466 in SPL, if space for the SPL binary is very tight.
468 This skips the recording of each loaded payload
469 (i.e. loadable) into the FDT (modifying the loaded FDT to
470 ensure this information is available to the next image
473 config SPL_CACHE_SUPPORT
474 bool "Support CACHE drivers"
476 Enable CACHE drivers in SPL. These drivers can keep data so that
477 future requests for that data can be served faster. Enable this option
478 to build the drivers in drivers/cache as part of an SPL build.
480 config SPL_CPU_SUPPORT
481 bool "Support CPU drivers"
483 Enable this to support CPU drivers in SPL. These drivers can set
484 up CPUs and provide information about them such as the model and
485 name. This can be useful in SPL since setting up the CPUs earlier
486 may improve boot performance. Enable this option to build the
487 drivers in drivers/cpu as part of an SPL build.
489 config SPL_CRYPTO_SUPPORT
490 bool "Support crypto drivers"
492 Enable crypto drivers in SPL. These drivers can be used to
493 accelerate secure boot processing in secure applications. Enable
494 this option to build the drivers in drivers/crypto as part of an
497 config SPL_HASH_SUPPORT
498 bool "Support hashing drivers"
502 Enable hashing drivers in SPL. These drivers can be used to
503 accelerate secure boot processing in secure applications. Enable
504 this option to build system-specific drivers for hash acceleration
505 as part of an SPL build.
507 config TPL_HASH_SUPPORT
508 bool "Support hashing drivers in TPL"
513 Enable hashing drivers in SPL. These drivers can be used to
514 accelerate secure boot processing in secure applications. Enable
515 this option to build system-specific drivers for hash acceleration
516 as part of an SPL build.
519 bool "Support DMA drivers"
521 Enable DMA (direct-memory-access) drivers in SPL. These drivers
522 can be used to handle memory-to-peripheral data transfer without
523 the CPU moving the data. Enable this option to build the drivers
524 in drivers/dma as part of an SPL build.
526 config SPL_DRIVERS_MISC_SUPPORT
527 bool "Support misc drivers"
529 Enable miscellaneous drivers in SPL. These drivers perform various
530 tasks that don't fall nicely into other categories, Enable this
531 option to build the drivers in drivers/misc as part of an SPL
532 build, for those that support building in SPL (not all drivers do).
534 config SPL_ENV_SUPPORT
535 bool "Support an environment"
537 Enable environment support in SPL. The U-Boot environment provides
538 a number of settings (essentially name/value pairs) which can
539 control many aspects of U-Boot's operation. Normally this is not
540 needed in SPL as it has a much simpler task with less
541 configuration. But some boards use this to support 'Falcon' boot
542 on EXT2 and FAT, where SPL boots directly into Linux without
543 starting U-Boot first. Enabling this option will make env_get()
544 and env_set() available in SPL.
547 bool "Support save environment"
548 depends on SPL_ENV_SUPPORT
549 select SPL_MMC_WRITE if ENV_IS_IN_MMC
551 Enable save environment support in SPL after setenv. By default
552 the saveenv option is not provided in SPL, but some boards need
553 this support in 'Falcon' boot, where SPL need to boot from
554 different images based on environment variable set by OS. For
555 example OS may set "reboot_image" environment variable to
556 "recovery" inorder to boot recovery image by SPL. The SPL read
557 "reboot_image" and act accordingly and change the reboot_image
558 to default mode using setenv and save the environment.
560 config SPL_ETH_SUPPORT
561 bool "Support Ethernet"
562 depends on SPL_ENV_SUPPORT
564 Enable access to the network subsystem and associated Ethernet
565 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
566 link rather than from an on-board peripheral. Environment support
567 is required since the network stack uses a number of environment
568 variables. See also SPL_NET_SUPPORT.
571 bool "Support EXT filesystems"
573 Enable support for EXT2/3/4 filesystems with SPL. This permits
574 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
575 filesystem from within SPL. Support for the underlying block
576 device (e.g. MMC or USB) must be enabled separately.
578 config SPL_FS_SQUASHFS
579 bool "Support SquashFS filesystems"
582 Enable support for SquashFS filesystems with SPL. This permits
583 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
584 filesystem from within SPL. Support for the underlying block
585 device (e.g. MMC or USB) must be enabled separately.
588 bool "Support FAT filesystems"
591 Enable support for FAT and VFAT filesystems with SPL. This
592 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
593 filesystem from within SPL. Support for the underlying block
594 device (e.g. MMC or USB) must be enabled separately.
597 bool "Support write for FAT filesystems"
599 Enable write support for FAT and VFAT filesystems with SPL.
600 Support for the underlying block device (e.g. MMC or USB) must be
606 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
607 provide software-configurable hardware which is typically used to
608 implement peripherals (such as UARTs, LCD displays, MMC) or
609 accelerate custom processing functions, such as image processing
610 or machine learning. Sometimes it is useful to program the FPGA
611 as early as possible during boot, and this option can enable that
614 config SPL_GPIO_SUPPORT
615 bool "Support GPIO in SPL"
617 Enable support for GPIOs (General-purpose Input/Output) in SPL.
618 GPIOs allow U-Boot to read the state of an input line (high or
619 low) and set the state of an output line. This can be used to
620 drive LEDs, control power to various system parts and read user
621 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
622 for example. Enable this option to build the drivers in
623 drivers/gpio as part of an SPL build.
625 config SPL_I2C_SUPPORT
628 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
629 I2C works with a clock and data line which can be driven by a
630 one or more masters or slaves. It is a fairly complex bus but is
631 widely used as it only needs two lines for communication. Speeds of
632 400kbps are typical but up to 3.4Mbps is supported by some
633 hardware. I2C can be useful in SPL to configure power management
634 ICs (PMICs) before raising the CPU clock speed, for example.
635 Enable this option to build the drivers in drivers/i2c as part of
638 config SPL_LIBCOMMON_SUPPORT
639 bool "Support common libraries"
641 Enable support for common U-Boot libraries within SPL. These
642 libraries include common code to deal with U-Boot images,
643 environment and USB, for example. This option is enabled on many
644 boards. Enable this option to build the code in common/ as part of
647 config SPL_LIBDISK_SUPPORT
648 bool "Support disk partitions"
651 Enable support for disk partitions within SPL. 'Disk' is something
652 of a misnomer as it includes non-spinning media such as flash (as
653 used in MMC and USB sticks). Partitions provide a way for a disk
654 to be split up into separate regions, with a partition table placed
655 at the start or end which describes the location and size of each
656 'partition'. These partitions are typically uses as individual block
657 devices, typically with an EXT2 or FAT filesystem in each. This
658 option enables whatever partition support has been enabled in
659 U-Boot to also be used in SPL. It brings in the code in disk/.
661 config SPL_LIBGENERIC_SUPPORT
662 bool "Support generic libraries"
664 Enable support for generic U-Boot libraries within SPL. These
665 libraries include generic code to deal with device tree, hashing,
666 printf(), compression and the like. This option is enabled on many
667 boards. Enable this option to build the code in lib/ as part of an
670 config SPL_DM_MAILBOX
671 bool "Support Mailbox"
673 Enable support for Mailbox within SPL. This enable the inter
674 processor communication protocols tobe used within SPL. Enable
675 this option to build the drivers in drivers/mailbox as part of
678 config SPL_MMC_SUPPORT
681 select HAVE_BLOCK_DEVICE
683 Enable support for MMC (Multimedia Card) within SPL. This enables
684 the MMC protocol implementation and allows any enabled drivers to
685 be used within SPL. MMC can be used with or without disk partition
686 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
687 this option to build the drivers in drivers/mmc as part of an SPL
690 config SYS_MMCSD_FS_BOOT_PARTITION
691 int "MMC Boot Partition"
694 Partition on the MMC to load U-Boot from when the MMC is being
698 bool "Tiny MMC framework in SPL"
699 depends on SPL_MMC_SUPPORT
702 Enable MMC framework tinification support. This option is useful if
703 if your SPL is extremely size constrained. Heed the warning, enable
704 this option if and only if you know exactly what you are doing, if
705 you are reading this help text, you most likely have no idea :-)
707 The MMC framework is reduced to bare minimum to be useful. No malloc
708 support is needed for the MMC framework operation with this option
709 enabled. The framework supports exactly one MMC device and exactly
710 one MMC driver. The MMC driver can be adjusted to avoid any malloc
711 operations too, which can remove the need for malloc support in SPL
712 and thus further reduce footprint.
715 bool "MMC/SD/SDIO card support for write operations in SPL"
716 depends on SPL_MMC_SUPPORT
719 Enable write access to MMC and SD Cards in SPL
722 config SPL_MPC8XXX_INIT_DDR_SUPPORT
723 bool "Support MPC8XXX DDR init"
725 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
726 random-access memory) on the MPC8XXX family within SPL. This
727 allows DRAM to be set up before loading U-Boot into that DRAM,
730 config SPL_MTD_SUPPORT
731 bool "Support MTD drivers"
733 Enable support for MTD (Memory Technology Device) within SPL. MTD
734 provides a block interface over raw NAND and can also be used with
735 SPI flash. This allows SPL to load U-Boot from supported MTD
736 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
737 to enable specific MTD drivers.
739 config SPL_MUSB_NEW_SUPPORT
740 bool "Support new Mentor Graphics USB"
742 Enable support for Mentor Graphics USB in SPL. This is a new
743 driver used by some boards. Enable this option to build
744 the drivers in drivers/usb/musb-new as part of an SPL build. The
745 old drivers are in drivers/usb/musb.
747 config SPL_NAND_SUPPORT
748 bool "Support NAND flash"
750 Enable support for NAND (Negative AND) flash in SPL. NAND flash
751 can be used to allow SPL to load U-Boot from supported devices.
752 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
755 config SPL_NAND_DRIVERS
756 bool "Use standard NAND driver"
758 SPL uses normal NAND drivers, not minimal drivers.
761 bool "Include standard software ECC in the SPL"
763 config SPL_NAND_SIMPLE
764 bool "Support simple NAND drivers in SPL"
766 Support for NAND boot using simple NAND drivers that
767 expose the cmd_ctrl() interface.
770 depends on SPL_NAND_DRIVERS
771 bool "Use Base NAND Driver"
773 Include nand_base.c in the SPL.
775 config SPL_NAND_IDENT
776 depends on SPL_NAND_BASE
777 bool "Use chip ID to identify NAND flash"
779 SPL uses the chip ID list to identify the NAND flash.
784 Enable support for loading payloads from UBI. See
785 README.ubispl for more info.
790 bool "Support cache drivers in SPL"
792 Enable support for cache drivers in SPL.
795 bool "Support SPI DM drivers in SPL"
797 Enable support for SPI DM drivers in SPL.
799 config SPL_DM_SPI_FLASH
800 bool "Support SPI DM FLASH drivers in SPL"
802 Enable support for SPI DM flash drivers in SPL.
806 config SPL_UBI_LOAD_BY_VOLNAME
807 bool "Support loading volumes by name"
809 This enables support for loading UBI volumes by name. When this
810 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
811 configure the volume name from which to load U-Boot.
813 config SPL_UBI_MAX_VOL_LEBS
814 int "Maximum number of LEBs per volume"
817 The maximum number of logical eraseblocks which a static volume
818 to load can contain. Used for sizing the scan data structure.
820 config SPL_UBI_MAX_PEB_SIZE
821 int "Maximum PEB size"
824 The maximum physical erase block size.
826 config SPL_UBI_MAX_PEBS
827 int "Maximum number of PEBs"
830 The maximum physical erase block size. If not overridden by
831 board code, this value will be used as the actual number of PEBs.
833 config SPL_UBI_PEB_OFFSET
834 int "Offset to first UBI PEB"
837 The offset in number of PEBs from the start of flash to the first
838 PEB part of the UBI image.
840 config SPL_UBI_VID_OFFSET
841 int "Offset to VID header"
844 config SPL_UBI_LEB_START
845 int "Offset to LEB in PEB"
848 The offset in bytes to the LEB within a PEB.
850 config SPL_UBI_INFO_ADDR
851 hex "Address to place UBI scan info"
854 Address for ubispl to place the scan info. Read README.ubispl to
855 determine the required size
857 config SPL_UBI_VOL_IDS
858 int "Maximum volume id"
861 The maximum volume id which can be loaded. Used for sizing the
864 config SPL_UBI_LOAD_MONITOR_ID
865 int "id of U-Boot volume"
868 The UBI volume id from which to load U-Boot
870 config SPL_UBI_LOAD_MONITOR_VOLNAME
871 string "volume name of U-Boot volume"
872 depends on SPL_UBI_LOAD_BY_VOLNAME
874 The UBI volume name from which to load U-Boot
876 config SPL_UBI_LOAD_KERNEL_ID
877 int "id of kernel volume"
878 depends on SPL_OS_BOOT && SPL_UBI
880 The UBI volume id from which to load the kernel
882 config SPL_UBI_LOAD_ARGS_ID
883 int "id of kernel args volume"
884 depends on SPL_OS_BOOT && SPL_UBI
886 The UBI volume id from which to load the device tree
888 config UBI_SPL_SILENCE_MSG
889 bool "silence UBI SPL messages"
892 Disable messages from UBI SPL. This leaves warnings
897 config SPL_NET_SUPPORT
898 bool "Support networking"
900 Enable support for network devices (such as Ethernet) in SPL.
901 This permits SPL to load U-Boot over a network link rather than
902 from an on-board peripheral. Environment support is required since
903 the network stack uses a number of environment variables. See also
907 config SPL_NET_VCI_STRING
908 string "BOOTP Vendor Class Identifier string sent by SPL"
910 As defined by RFC 2132 the vendor class identifier field can be
911 sent by the client to identify the vendor type and configuration
912 of a client. This is often used in practice to allow for the DHCP
913 server to specify different files to load depending on if the ROM,
914 SPL or U-Boot itself makes the request
915 endif # if SPL_NET_SUPPORT
917 config SPL_NO_CPU_SUPPORT
918 bool "Drop CPU code in SPL"
920 This is specific to the ARM926EJ-S CPU. It disables the standard
921 start.S start-up code, presumably so that a replacement can be
922 used on that CPU. You should not enable it unless you know what
925 config SPL_NOR_SUPPORT
926 bool "Support NOR flash"
928 Enable support for loading U-Boot from memory-mapped NOR (Negative
929 OR) flash in SPL. NOR flash is slow to write but fast to read, and
930 a memory-mapped device makes it very easy to access. Loading from
931 NOR is typically achieved with just a memcpy().
933 config SPL_XIP_SUPPORT
937 Enable support for execute in place of U-Boot or kernel image. There
938 is no need to copy image from flash to ram if flash supports execute
939 in place. Its very useful in systems having enough flash but not
940 enough ram to load the image.
942 config SPL_ONENAND_SUPPORT
943 bool "Support OneNAND flash"
945 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
946 a type of NAND flash and therefore can be used to allow SPL to
947 load U-Boot from supported devices. This enables the drivers in
948 drivers/mtd/onenand as part of an SPL build.
951 bool "Activate Falcon Mode"
952 depends on !TI_SECURE_DEVICE
955 Enable booting directly to an OS from SPL.
956 for more info read doc/README.falcon
960 hex "addr, where OS is found"
961 depends on SPL_NOR_SUPPORT
963 Specify the address, where the OS image is found, which
970 default "tpl/u-boot-with-tpl.bin" if TPL
973 Payload for SPL boot. For backward compatibility, default to
974 u-boot.bin, i.e. RAW image without any header. In case of
975 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
979 bool "Support PCI drivers"
981 Enable support for PCI in SPL. For platforms that need PCI to boot,
982 or must perform some init using PCI in SPL, this provides the
983 necessary driver support. This enables the drivers in drivers/pci
984 as part of an SPL build.
986 config SPL_PCH_SUPPORT
987 bool "Support PCH drivers"
989 Enable support for PCH (Platform Controller Hub) devices in SPL.
990 These are used to set up GPIOs and the SPI peripheral early in
991 boot. This enables the drivers in drivers/pch as part of an SPL
994 config SPL_POST_MEM_SUPPORT
995 bool "Support POST drivers"
997 Enable support for POST (Power-on Self Test) in SPL. POST is a
998 procedure that checks that the hardware (CPU or board) appears to
999 be functionally correctly. It is a sanity check that can be
1000 performed before booting. This enables the drivers in post/drivers
1001 as part of an SPL build.
1004 bool "Support reset drivers"
1007 Enable support for reset control in SPL.
1008 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1009 by using the generic reset API provided by driver model.
1010 This enables the drivers in drivers/reset as part of an SPL build.
1012 config SPL_POWER_SUPPORT
1013 bool "Support power drivers"
1015 Enable support for power control in SPL. This includes support
1016 for PMICs (Power-management Integrated Circuits) and some of the
1017 features provided by PMICs. In particular, voltage regulators can
1018 be used to enable/disable power and vary its voltage. That can be
1019 useful in SPL to turn on boot peripherals and adjust CPU voltage
1020 so that the clock speed can be increased. This enables the drivers
1021 in drivers/power, drivers/power/pmic and drivers/power/regulator
1022 as part of an SPL build.
1024 config SPL_POWER_DOMAIN
1025 bool "Support power domain drivers"
1027 Enable support for power domain control in SPL. Many SoCs allow
1028 power to be applied to or removed from portions of the SoC (power
1029 domains). This may be used to save power. This API provides the
1030 means to control such power management hardware. This enables
1031 the drivers in drivers/power/domain as part of a SPL build.
1033 config SPL_RAM_SUPPORT
1034 bool "Support booting from RAM"
1035 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1037 Enable booting of an image in RAM. The image can be preloaded or
1038 it can be loaded by SPL directly into RAM (e.g. using USB).
1040 config SPL_RAM_DEVICE
1041 bool "Support booting from preloaded image in RAM"
1042 depends on SPL_RAM_SUPPORT
1043 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1045 Enable booting of an image already loaded in RAM. The image has to
1046 be already in memory when SPL takes over, e.g. loaded by the boot
1049 config SPL_REMOTEPROC
1050 bool "Support REMOTEPROCS"
1052 Enable support for REMOTEPROCs in SPL. This permits to load
1053 a remote processor firmware in SPL.
1055 config SPL_RTC_SUPPORT
1056 bool "Support RTC drivers"
1058 Enable RTC (Real-time Clock) support in SPL. This includes support
1059 for reading and setting the time. Some RTC devices also have some
1060 non-volatile (battery-backed) memory which is accessible if
1061 needed. This enables the drivers in drivers/rtc as part of an SPL
1064 config SPL_SATA_SUPPORT
1065 bool "Support loading from SATA"
1067 Enable support for SATA (Serial AT attachment) in SPL. This allows
1068 use of SATA devices such as hard drives and flash drivers for
1069 loading U-Boot. SATA is used in higher-end embedded systems and
1070 can provide higher performance than MMC , at somewhat higher
1071 expense and power consumption. This enables loading from SATA
1072 using a configured device.
1074 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1075 bool "SATA raw mode: by sector"
1076 depends on SPL_SATA_SUPPORT
1078 Use sector number for specifying U-Boot location on SATA disk in
1081 config SPL_SATA_RAW_U_BOOT_SECTOR
1082 hex "Sector on the SATA disk to load U-Boot from"
1083 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1085 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1086 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1088 config SPL_SERIAL_SUPPORT
1089 bool "Support serial"
1093 Enable support for serial in SPL. This allows use of a serial UART
1094 for displaying messages while SPL is running. It also brings in
1095 printf() and panic() functions. This should normally be enabled
1096 unless there are space reasons not to. Even then, consider
1097 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1099 config SPL_SPI_SUPPORT
1100 bool "Support SPI drivers"
1102 Enable support for using SPI in SPL. This is used for connecting
1103 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1104 more details on that. The SPI driver provides the transport for
1105 data between the SPI flash and the CPU. This option can be used to
1106 enable SPI drivers that are needed for other purposes also, such
1109 config SPL_SPI_FLASH_SUPPORT
1110 bool "Support SPI flash drivers"
1111 depends on SPL_SPI_SUPPORT
1113 Enable support for using SPI flash in SPL, and loading U-Boot from
1114 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1115 the SPI bus that is used to connect it to a system. It is a simple
1116 but fast bidirectional 4-wire bus (clock, chip select and two data
1117 lines). This enables the drivers in drivers/mtd/spi as part of an
1118 SPL build. This normally requires SPL_SPI_SUPPORT.
1120 if SPL_SPI_FLASH_SUPPORT
1122 config SPL_SPI_FLASH_TINY
1123 bool "Enable low footprint SPL SPI Flash support"
1124 depends on !SPI_FLASH_BAR
1125 default y if SPI_FLASH
1127 Enable lightweight SPL SPI Flash support that supports just reading
1128 data/images from flash. No support to write/erase flash. Enable
1129 this if you have SPL size limitations and don't need full
1130 fledged SPI flash support.
1132 config SPL_SPI_FLASH_SFDP_SUPPORT
1133 bool "SFDP table parsing support for SPI NOR flashes"
1134 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1136 Enable support for parsing and auto discovery of parameters for
1137 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1138 tables as per JESD216 standard in SPL.
1140 config SPL_SPI_FLASH_MTD
1141 bool "Support for SPI flash MTD drivers in SPL"
1143 Enable support for SPI flash MTD drivers in SPL.
1146 bool "Support loading from SPI flash"
1148 Enable support for loading next stage, U-Boot or otherwise, from
1149 SPI NOR in U-Boot SPL.
1151 endif # SPL_SPI_FLASH_SUPPORT
1153 config SYS_SPI_U_BOOT_OFFS
1154 hex "address of u-boot payload in SPI flash"
1155 default 0x8000 if ARCH_SUNXI
1157 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1159 Address within SPI-Flash from where the u-boot payload is fetched
1163 bool "Driver support for thermal devices"
1165 Enable support for temperature-sensing devices. Some SoCs have on-chip
1166 temperature sensors to permit warnings, speed throttling or even
1167 automatic power-off when the temperature gets too high or low. Other
1168 devices may be discrete but connected on a suitable bus.
1170 config SPL_USB_HOST_SUPPORT
1171 bool "Support USB host drivers"
1172 select HAVE_BLOCK_DEVICE
1174 Enable access to USB (Universal Serial Bus) host devices so that
1175 SPL can load U-Boot from a connected USB peripheral, such as a USB
1176 flash stick. While USB takes a little longer to start up than most
1177 buses, it is very flexible since many different types of storage
1178 device can be attached. This option enables the drivers in
1179 drivers/usb/host as part of an SPL build.
1181 config SPL_USB_STORAGE
1182 bool "Support loading from USB"
1183 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1185 Enable support for USB devices in SPL. This allows use of USB
1186 devices such as hard drives and flash drivers for loading U-Boot.
1187 The actual drivers are enabled separately using the normal U-Boot
1188 config options. This enables loading from USB using a configured
1191 config SPL_USB_GADGET
1192 bool "Suppport USB Gadget drivers"
1194 Enable USB Gadget API which allows to enable USB device functions
1199 config SPL_USB_ETHER
1200 bool "Support USB Ethernet drivers"
1202 Enable access to the USB network subsystem and associated
1203 drivers in SPL. This permits SPL to load U-Boot over a
1204 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1205 than from an onboard peripheral. Environment support is required
1206 since the network stack uses a number of environment variables.
1207 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1210 bool "Support DFU (Device Firmware Upgrade)"
1211 select SPL_HASH_SUPPORT
1212 select SPL_DFU_NO_RESET
1213 depends on SPL_RAM_SUPPORT
1215 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1216 RAM memory device support. The ROM code will load and execute
1217 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1218 selected device partition from host-pc using dfu-utils.
1219 This feature is useful to flash the binaries to factory or bare-metal
1220 boards using USB interface.
1223 bool "DFU device selection"
1228 depends on SPL_DFU && SPL_RAM_SUPPORT
1230 select RAM/DDR memory device for loading binary images
1231 (u-boot/kernel) to the selected device partition using
1232 DFU and execute the u-boot/kernel from RAM.
1236 config SPL_USB_SDP_SUPPORT
1237 bool "Support SDP (Serial Download Protocol)"
1238 depends on SPL_SERIAL_SUPPORT
1240 Enable Serial Download Protocol (SDP) device support in SPL. This
1241 allows to download images into memory and execute (jump to) them
1242 using the same protocol as implemented by the i.MX family's boot ROM.
1244 config SPL_SDP_USB_DEV
1245 int "SDP USB controller index"
1247 depends on SPL_USB_SDP_SUPPORT
1249 Some boards have USB controller other than 0. Define this option
1250 so it can be used in compiled environment.
1253 config SPL_WATCHDOG_SUPPORT
1254 bool "Support watchdog drivers"
1255 imply SPL_WDT if !HW_WATCHDOG
1257 Enable support for watchdog drivers in SPL. A watchdog is
1258 typically a hardware peripheral which can reset the system when it
1259 detects no activity for a while (such as a software crash). This
1260 enables the drivers in drivers/watchdog as part of an SPL build.
1262 config SPL_YMODEM_SUPPORT
1263 bool "Support loading using Ymodem"
1264 depends on SPL_SERIAL_SUPPORT
1266 While loading from serial is slow it can be a useful backup when
1267 there is no other option. The Ymodem protocol provides a reliable
1268 means of transmitting U-Boot over a serial line for using in SPL,
1269 with a checksum to ensure correctness.
1272 bool "Support ARM Trusted Firmware"
1273 depends on ARM64 && SPL_FIT
1275 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1276 is loaded by SPL (which is considered as BL2 in ATF terminology).
1277 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1279 config SPL_ATF_NO_PLATFORM_PARAM
1280 bool "Pass no platform parameter"
1283 While we expect to call a pointer to a valid FDT (or NULL)
1284 as the platform parameter to an ATF, some ATF versions are
1285 not U-Boot aware and have an insufficiently robust parameter
1286 validation to gracefully reject a FDT being passed.
1288 If this option is enabled, the spl_atf os-type handler will
1289 always pass NULL for the platform parameter.
1291 If your ATF is affected, say Y.
1293 config SPL_AM33XX_ENABLE_RTC32K_OSC
1294 bool "Enable the RTC32K OSC on AM33xx based platforms"
1297 Enable access to the AM33xx RTC and select the external 32kHz clock
1301 bool "Support OP-TEE Trusted OS"
1304 OP-TEE is an open source Trusted OS which is loaded by SPL.
1305 More detail at: https://github.com/OP-TEE/optee_os
1308 bool "Support RISC-V OpenSBI"
1309 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1311 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1312 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1313 firmware. It is loaded and started by U-Boot SPL.
1315 More details are available at https://github.com/riscv/opensbi and
1316 https://github.com/riscv/riscv-sbi-doc
1318 config SPL_OPENSBI_LOAD_ADDR
1319 hex "OpenSBI load address"
1320 depends on SPL_OPENSBI
1322 Load address of the OpenSBI binary.
1326 depends on SUPPORT_TPL
1329 If you want to build TPL as well as the normal image and SPL, say Y.
1333 config TPL_SIZE_LIMIT
1334 hex "Maximum size of TPL image"
1338 Specifies the maximum length of the U-Boot TPL image.
1339 If this value is zero, it is ignored.
1341 config TPL_FRAMEWORK
1342 bool "Support TPL based upon the common SPL framework"
1343 default y if SPL_FRAMEWORK
1345 Enable the SPL framework under common/spl/ for TPL builds.
1346 This framework supports MMC, NAND and YMODEM and other methods
1347 loading of U-Boot's SPL stage. If unsure, say Y.
1350 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1351 depends on HANDOFF && TPL_BLOBLIST
1354 This option enables TPL to write handoff information. This can be
1355 used to pass information like the size of SDRAM from TPL to U-Boot
1356 proper. The information is also available to SPL if it is useful
1359 config TPL_BOARD_INIT
1360 bool "Call board-specific initialization in TPL"
1362 If this option is enabled, U-Boot will call the function
1363 spl_board_init() from board_init_r(). This function should be
1364 provided by the board.
1367 string "Linker script for the TPL stage"
1369 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1370 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1372 The TPL stage will usually require a different linker-script
1373 (as it runs from a different memory region) than the regular
1374 U-Boot stage. Set this to the path of the linker-script to
1377 May be left empty to trigger the Makefile infrastructure to
1378 fall back to the linker-script used for the SPL stage.
1380 config TPL_NEEDS_SEPARATE_TEXT_BASE
1381 bool "TPL needs a separate text-base"
1385 Enable, if the TPL stage should not inherit its text-base
1386 from the SPL stage. When enabled, a base address for the
1387 .text sections of the TPL stage has to be set below.
1389 config TPL_NEEDS_SEPARATE_STACK
1390 bool "TPL needs a separate initial stack-pointer"
1394 Enable, if the TPL stage should not inherit its initial
1395 stack-pointer from the settings for the SPL stage.
1397 config TPL_TEXT_BASE
1398 hex "Base address for the .text section of the TPL stage"
1399 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1401 The base address for the .text section of the TPL stage.
1404 int "Maximum size (in bytes) for the TPL stage"
1408 The maximum size (in bytes) of the TPL stage.
1411 hex "Address of the initial stack-pointer for the TPL stage"
1412 depends on TPL_NEEDS_SEPARATE_STACK
1414 The address of the initial stack-pointer for the TPL stage.
1415 Usually this will be the (aligned) top-of-stack.
1417 config TPL_BOOTROM_SUPPORT
1418 bool "Support returning to the BOOTROM (from TPL)"
1420 Some platforms (e.g. the Rockchip RK3368) provide support in their
1421 ROM for loading the next boot-stage after performing basic setup
1424 Enable this option, to return to the BOOTROM through the
1425 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1426 boot device list, if not implemented for a given board)
1428 config TPL_DRIVERS_MISC_SUPPORT
1429 bool "Support misc drivers in TPL"
1431 Enable miscellaneous drivers in TPL. These drivers perform various
1432 tasks that don't fall nicely into other categories, Enable this
1433 option to build the drivers in drivers/misc as part of an TPL
1434 build, for those that support building in TPL (not all drivers do).
1436 config TPL_ENV_SUPPORT
1437 bool "Support an environment"
1439 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1441 config TPL_GPIO_SUPPORT
1442 bool "Support GPIO in TPL"
1444 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1445 GPIOs allow U-Boot to read the state of an input line (high or
1446 low) and set the state of an output line. This can be used to
1447 drive LEDs, control power to various system parts and read user
1448 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1449 for example. Enable this option to build the drivers in
1450 drivers/gpio as part of an TPL build.
1452 config TPL_I2C_SUPPORT
1455 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1458 config TPL_LIBCOMMON_SUPPORT
1459 bool "Support common libraries"
1461 Enable support for common U-Boot libraries within TPL. See
1462 SPL_LIBCOMMON_SUPPORT for details.
1464 config TPL_LIBGENERIC_SUPPORT
1465 bool "Support generic libraries"
1467 Enable support for generic U-Boot libraries within TPL. See
1468 SPL_LIBGENERIC_SUPPORT for details.
1470 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1471 bool "Support MPC8XXX DDR init"
1473 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1474 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1476 config TPL_MMC_SUPPORT
1480 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1482 config TPL_NAND_SUPPORT
1483 bool "Support NAND flash"
1485 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1488 bool "Support PCI drivers"
1490 Enable support for PCI in TPL. For platforms that need PCI to boot,
1491 or must perform some init using PCI in SPL, this provides the
1492 necessary driver support. This enables the drivers in drivers/pci
1493 as part of a TPL build.
1495 config TPL_PCH_SUPPORT
1496 bool "Support PCH drivers"
1498 Enable support for PCH (Platform Controller Hub) devices in TPL.
1499 These are used to set up GPIOs and the SPI peripheral early in
1500 boot. This enables the drivers in drivers/pch as part of a TPL
1503 config TPL_RAM_SUPPORT
1504 bool "Support booting from RAM"
1506 Enable booting of an image in RAM. The image can be preloaded or
1507 it can be loaded by TPL directly into RAM (e.g. using USB).
1509 config TPL_RAM_DEVICE
1510 bool "Support booting from preloaded image in RAM"
1511 depends on TPL_RAM_SUPPORT
1513 Enable booting of an image already loaded in RAM. The image has to
1514 be already in memory when TPL takes over, e.g. loaded by the boot
1517 config TPL_RTC_SUPPORT
1518 bool "Support RTC drivers"
1520 Enable RTC (Real-time Clock) support in TPL. This includes support
1521 for reading and setting the time. Some RTC devices also have some
1522 non-volatile (battery-backed) memory which is accessible if
1523 needed. This enables the drivers in drivers/rtc as part of an TPL
1526 config TPL_SERIAL_SUPPORT
1527 bool "Support serial"
1531 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1534 config TPL_SPI_FLASH_SUPPORT
1535 bool "Support SPI flash drivers"
1537 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1540 config TPL_SPI_FLASH_TINY
1541 bool "Enable low footprint TPL SPI Flash support"
1542 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1543 default y if SPI_FLASH
1545 Enable lightweight TPL SPI Flash support that supports just reading
1546 data/images from flash. No support to write/erase flash. Enable
1547 this if you have TPL size limitations and don't need full-fledged
1551 bool "Support loading from SPI flash"
1552 depends on TPL_SPI_FLASH_SUPPORT
1554 Enable support for loading next stage, U-Boot or otherwise, from
1555 SPI NOR in U-Boot TPL.
1557 config TPL_SPI_SUPPORT
1558 bool "Support SPI drivers"
1560 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1564 bool "Support SPI DM drivers in TPL"
1566 Enable support for SPI DM drivers in TPL.
1568 config TPL_DM_SPI_FLASH
1569 bool "Support SPI DM FLASH drivers in TPL"
1571 Enable support for SPI DM flash drivers in TPL.
1573 config TPL_YMODEM_SUPPORT
1574 bool "Support loading using Ymodem"
1575 depends on TPL_SERIAL_SUPPORT
1577 While loading from serial is slow it can be a useful backup when
1578 there is no other option. The Ymodem protocol provides a reliable
1579 means of transmitting U-Boot over a serial line for using in TPL,
1580 with a checksum to ensure correctness.
1584 config SPL_AT91_MCK_BYPASS
1585 bool "Use external clock signal as a source of main clock for AT91 platforms"
1586 depends on ARCH_AT91
1589 Use external 8 to 24 Mhz clock signal as source of main clock instead
1590 of an external crystal oscillator.
1591 This option disables the internal driving on the XOUT pin.
1592 The external source has to provide a stable clock on the XIN pin.
1593 If this option is disabled, the SoC expects a crystal oscillator
1594 that needs driving on both XIN and XOUT lines.