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
117 bool "Allocate memory for bd_info"
118 default y if X86 || SANDBOX
120 Some boards don't allocate space for this in their board_init_f()
121 code. In this case U-Boot can allocate space for gd->bd in the
122 standard SPL flow (board_init_r()). Enable this option to support
128 bool "Pass hand-off information from SPL to U-Boot proper"
129 depends on SPL && BLOBLIST
131 It is useful to be able to pass information from SPL to U-Boot
132 proper to preserve state that is known in SPL and is needed in U-Boot.
133 Enable this to locate the handoff information in U-Boot proper, early
134 in boot. It is available in gd->handoff. The state state is set up
135 in SPL (or TPL if that is being used).
140 bool "Pass hand-off information from SPL to U-Boot proper"
141 depends on HANDOFF && SPL_BLOBLIST
144 This option enables SPL to write handoff information. This can be
145 used to pass information like the size of SDRAM from SPL to U-Boot
146 proper. Also SPL can receive information from TPL in the same place
150 string "Linker script for the SPL stage"
151 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
153 The SPL stage will usually require a different linker-script
154 (as it runs from a different memory region) than the regular
155 U-Boot stage. Set this to the path of the linker-script to
160 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
161 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
162 default 0x20060 if SUN50I_GEN_H6
163 default 0x00060 if ARCH_SUNXI
164 default 0xfffc0000 if ARCH_ZYNQMP
167 The address in memory that SPL will be running from.
169 config SPL_BOARD_INIT
170 bool "Call board-specific initialization in SPL"
172 If this option is enabled, U-Boot will call the function
173 spl_board_init() from board_init_r(). This function should be
174 provided by the board.
176 config SPL_BOOTROM_SUPPORT
177 bool "Support returning to the BOOTROM"
179 Some platforms (e.g. the Rockchip RK3368) provide support in their
180 ROM for loading the next boot-stage after performing basic setup
183 Enable this option, to return to the BOOTROM through the
184 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
185 boot device list, if not implemented for a given board)
187 config SPL_BOOTCOUNT_LIMIT
188 bool "Support bootcount in SPL"
189 depends on SPL_ENV_SUPPORT
191 On some boards, which use 'falcon' mode, it is necessary to check
192 and increment the number of boot attempts. Such boards do not
193 use proper U-Boot for normal boot flow and hence needs those
194 adjustments to be done in the SPL.
196 config SPL_RAW_IMAGE_SUPPORT
197 bool "Support SPL loading and booting of RAW images"
198 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
199 default y if !TI_SECURE_DEVICE
201 SPL will support loading and booting a RAW image when this option
202 is y. If this is not set, SPL will move on to other available
203 boot media to find a suitable image.
205 config SPL_LEGACY_IMAGE_SUPPORT
206 bool "Support SPL loading and booting of Legacy images"
207 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
209 SPL will support loading and booting Legacy images when this option
210 is y. If this is not set, SPL will move on to other available
211 boot media to find a suitable image.
213 config SPL_LEGACY_IMAGE_CRC_CHECK
214 bool "Check CRC of Legacy images"
215 depends on SPL_LEGACY_IMAGE_SUPPORT
216 select SPL_CRC32_SUPPORT
218 Enable this to check the CRC of Legacy images. While this increases
219 reliability, it affects both code size and boot duration.
220 If disabled, Legacy images are booted if the image magic and size
221 are correct, without further integrity checks.
223 config SPL_SYS_MALLOC_SIMPLE
225 prompt "Only use malloc_simple functions in the SPL"
227 Say Y here to only use the *_simple malloc functions from
228 malloc_simple.c, rather then using the versions from dlmalloc.c;
229 this will make the SPL binary smaller at the cost of more heap
230 usage as the *_simple malloc functions do not re-use free-ed mem.
232 config TPL_SYS_MALLOC_SIMPLE
234 prompt "Only use malloc_simple functions in the TPL"
237 Say Y here to only use the *_simple malloc functions from
238 malloc_simple.c, rather then using the versions from dlmalloc.c;
239 this will make the TPL binary smaller at the cost of more heap
240 usage as the *_simple malloc functions do not re-use free-ed mem.
243 bool "Enable SDRAM location for SPL stack"
245 SPL starts off execution in SRAM and thus typically has only a small
246 stack available. Since SPL sets up DRAM while in its board_init_f()
247 function, it is possible for the stack to move there before
248 board_init_r() is reached. This option enables a special SDRAM
249 location for the SPL stack. U-Boot SPL switches to this after
250 board_init_f() completes, and before board_init_r() starts.
252 config SPL_STACK_R_ADDR
253 depends on SPL_STACK_R
254 hex "SDRAM location for SPL stack"
255 default 0x82000000 if ARCH_OMAP2PLUS
257 Specify the address in SDRAM for the SPL stack. This will be set up
258 before board_init_r() is called.
260 config SPL_STACK_R_MALLOC_SIMPLE_LEN
261 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
262 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
265 Specify the amount of the stack to use as memory pool for
266 malloc_simple after switching the stack to DRAM. This may be set
267 to give board_init_r() a larger heap then the initial heap in
268 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
270 config SPL_SEPARATE_BSS
271 bool "BSS section is in a different memory region from text"
273 Some platforms need a large BSS region in SPL and can provide this
274 because RAM is already set up. In this case BSS can be moved to RAM.
275 This option should then be enabled so that the correct device tree
276 location is used. Normally we put the device tree at the end of BSS
277 but with this option enabled, it goes at _image_binary_end.
279 config SPL_BANNER_PRINT
280 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
283 If this option is enabled, SPL will print the banner with version
284 info. Disabling this option could be useful to reduce SPL boot time
285 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
287 config TPL_BANNER_PRINT
288 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
292 If this option is enabled, TPL will print the banner with version
293 info. Disabling this option could be useful to reduce TPL boot time
294 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
297 depends on ARM && !ARM64
298 bool "Allows initializing BSS early before entering board_init_f"
300 On some platform we have sufficient memory available early on to
301 allow setting up and using a basic BSS prior to entering
302 board_init_f. Activating this option will also de-activate the
303 clearing of BSS during the SPL relocation process, thus allowing
304 to carry state from board_init_f to board_init_r by way of BSS.
306 config SPL_DISPLAY_PRINT
307 bool "Display a board-specific message in SPL"
309 If this option is enabled, U-Boot will call the function
310 spl_display_print() immediately after displaying the SPL console
311 banner ("U-Boot SPL ..."). This function should be provided by
314 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
315 bool "MMC raw mode: by sector"
316 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
317 ARCH_MX6 || ARCH_MX7 || \
318 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
319 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
320 OMAP44XX || OMAP54XX || AM33XX || AM43XX || TARGET_SIFIVE_FU540
322 Use sector number for specifying U-Boot location on MMC/SD in
325 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
326 hex "Address on the MMC to load U-Boot from"
327 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
328 default 0x50 if ARCH_SUNXI
329 default 0x75 if ARCH_DAVINCI
330 default 0x8a if ARCH_MX6 || ARCH_MX7
331 default 0x100 if ARCH_UNIPHIER
332 default 0x140 if ARCH_MVEBU
333 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
334 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
335 OMAP54XX || AM33XX || AM43XX || ARCH_K3
336 default 0x4000 if ARCH_ROCKCHIP
337 default 0x822 if TARGET_SIFIVE_FU540
339 Address on the MMC to load U-Boot from, when the MMC is being used
340 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
342 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
343 hex "U-Boot main hardware partition image offset"
344 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
347 On some platforms SPL location depends on hardware partition. The ROM
348 code skips the MBR sector when loading SPL from main hardware data
349 partition. This adds offset to the main U-Boot image. Set this symbol
350 to the number of skipped sectors.
352 If unsure, leave the default.
354 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
355 bool "MMC Raw mode: by partition"
357 Use a partition for loading U-Boot when using MMC/SD in raw mode.
359 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
360 hex "Partition to use to load U-Boot from"
361 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
364 Partition on the MMC to load U-Boot from when the MMC is being
367 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
368 bool "MMC raw mode: by partition type"
369 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
371 Use partition type for specifying U-Boot partition on MMC/SD in
372 raw mode. U-Boot will be loaded from the first partition of this
375 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
376 hex "Partition Type on the MMC to load U-Boot from"
377 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
379 Partition Type on the MMC to load U-Boot from, when the MMC is being
382 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
383 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
384 depends on SUPPORT_EMMC_BOOT
386 eMMC boot partition is normally configured by the bits of the EXT_CSD
387 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
388 cases it might be required in SPL to load the image from different
389 partition than the partition selected by EXT_CSC_PART_CONFIG register.
390 Enable this option if you intend to use an eMMC boot partition other
391 then selected via EXT_CSC_PART_CONFIG register and specify the custom
392 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
395 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
396 int "Number of the eMMC boot partition to use"
397 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
400 eMMC boot partition number to use when the eMMC in raw mode and
401 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
402 by user defined partition number.
404 config SPL_CRC32_SUPPORT
406 default y if SPL_LEGACY_IMAGE_SUPPORT
408 Enable this to support CRC32 in uImages or FIT images within SPL.
409 This is a 32-bit checksum value that can be used to verify images.
410 For FIT images, this is the least secure type of checksum, suitable
411 for detected accidental image corruption. For secure applications you
412 should consider SHA1 or SHA256.
414 config SPL_MD5_SUPPORT
418 Enable this to support MD5 in FIT images within SPL. An MD5
419 checksum is a 128-bit hash value used to check that the image
420 contents have not been corrupted. Note that MD5 is not considered
421 secure as it is possible (with a brute-force attack) to adjust the
422 image while still retaining the same MD5 hash value. For secure
423 applications where images may be changed maliciously, you should
424 consider SHA256 or SHA384.
426 config SPL_SHA1_SUPPORT
431 Enable this to support SHA1 in FIT images within SPL. A SHA1
432 checksum is a 160-bit (20-byte) hash value used to check that the
433 image contents have not been corrupted or maliciously altered.
434 While SHA1 is fairly secure it is coming to the end of its life
435 due to the expanding computing power available to brute-force
436 attacks. For more security, consider SHA256 or SHA384.
438 config SPL_SHA256_SUPPORT
439 bool "Support SHA256"
443 Enable this to support SHA256 in FIT images within SPL. A SHA256
444 checksum is a 256-bit (32-byte) hash value used to check that the
445 image contents have not been corrupted.
447 config SPL_SHA384_SUPPORT
448 bool "Support SHA384"
453 Enable this to support SHA384 in FIT images within SPL. A SHA384
454 checksum is a 384-bit (48-byte) hash value used to check that the
455 image contents have not been corrupted. Use this for the highest
458 config SPL_SHA512_SUPPORT
459 bool "Support SHA512"
464 Enable this to support SHA512 in FIT images within SPL. A SHA512
465 checksum is a 512-bit (64-byte) hash value used to check that the
466 image contents have not been corrupted.
468 config SPL_FIT_IMAGE_TINY
469 bool "Remove functionality from SPL FIT loading to reduce size"
471 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
472 default y if ARCH_IMX8M
474 Enable this to reduce the size of the FIT image loading code
475 in SPL, if space for the SPL binary is very tight.
477 This skips the recording of each loaded payload
478 (i.e. loadable) into the FDT (modifying the loaded FDT to
479 ensure this information is available to the next image
482 config SPL_CACHE_SUPPORT
483 bool "Support CACHE drivers"
485 Enable CACHE drivers in SPL. These drivers can keep data so that
486 future requests for that data can be served faster. Enable this option
487 to build the drivers in drivers/cache as part of an SPL build.
489 config SPL_CPU_SUPPORT
490 bool "Support CPU drivers"
492 Enable this to support CPU drivers in SPL. These drivers can set
493 up CPUs and provide information about them such as the model and
494 name. This can be useful in SPL since setting up the CPUs earlier
495 may improve boot performance. Enable this option to build the
496 drivers in drivers/cpu as part of an SPL build.
498 config SPL_CRYPTO_SUPPORT
499 bool "Support crypto drivers"
501 Enable crypto drivers in SPL. These drivers can be used to
502 accelerate secure boot processing in secure applications. Enable
503 this option to build the drivers in drivers/crypto as part of an
506 config SPL_HASH_SUPPORT
507 bool "Support hashing drivers"
511 Enable hashing drivers in SPL. These drivers can be used to
512 accelerate secure boot processing in secure applications. Enable
513 this option to build system-specific drivers for hash acceleration
514 as part of an SPL build.
516 config TPL_HASH_SUPPORT
517 bool "Support hashing drivers in TPL"
522 Enable hashing drivers in SPL. These drivers can be used to
523 accelerate secure boot processing in secure applications. Enable
524 this option to build system-specific drivers for hash acceleration
525 as part of an SPL build.
528 bool "Support DMA drivers"
530 Enable DMA (direct-memory-access) drivers in SPL. These drivers
531 can be used to handle memory-to-peripheral data transfer without
532 the CPU moving the data. Enable this option to build the drivers
533 in drivers/dma as part of an SPL build.
535 config SPL_DRIVERS_MISC_SUPPORT
536 bool "Support misc drivers"
538 Enable miscellaneous drivers in SPL. These drivers perform various
539 tasks that don't fall nicely into other categories, Enable this
540 option to build the drivers in drivers/misc as part of an SPL
541 build, for those that support building in SPL (not all drivers do).
543 config SPL_ENV_SUPPORT
544 bool "Support an environment"
546 Enable environment support in SPL. The U-Boot environment provides
547 a number of settings (essentially name/value pairs) which can
548 control many aspects of U-Boot's operation. Normally this is not
549 needed in SPL as it has a much simpler task with less
550 configuration. But some boards use this to support 'Falcon' boot
551 on EXT2 and FAT, where SPL boots directly into Linux without
552 starting U-Boot first. Enabling this option will make env_get()
553 and env_set() available in SPL.
556 bool "Support save environment"
557 depends on SPL_ENV_SUPPORT
558 select SPL_MMC_WRITE if ENV_IS_IN_MMC
560 Enable save environment support in SPL after setenv. By default
561 the saveenv option is not provided in SPL, but some boards need
562 this support in 'Falcon' boot, where SPL need to boot from
563 different images based on environment variable set by OS. For
564 example OS may set "reboot_image" environment variable to
565 "recovery" inorder to boot recovery image by SPL. The SPL read
566 "reboot_image" and act accordingly and change the reboot_image
567 to default mode using setenv and save the environment.
569 config SPL_ETH_SUPPORT
570 bool "Support Ethernet"
571 depends on SPL_ENV_SUPPORT
573 Enable access to the network subsystem and associated Ethernet
574 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
575 link rather than from an on-board peripheral. Environment support
576 is required since the network stack uses a number of environment
577 variables. See also SPL_NET_SUPPORT.
580 bool "Support EXT filesystems"
582 Enable support for EXT2/3/4 filesystems with SPL. This permits
583 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
584 filesystem from within SPL. Support for the underlying block
585 device (e.g. MMC or USB) must be enabled separately.
587 config SPL_FS_SQUASHFS
588 bool "Support SquashFS filesystems"
591 Enable support for SquashFS filesystems with SPL. This permits
592 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
593 filesystem from within SPL. Support for the underlying block
594 device (e.g. MMC or USB) must be enabled separately.
597 bool "Support FAT filesystems"
600 Enable support for FAT and VFAT filesystems with SPL. This
601 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
602 filesystem from within SPL. Support for the underlying block
603 device (e.g. MMC or USB) must be enabled separately.
606 bool "Support write for FAT filesystems"
608 Enable write support for FAT and VFAT filesystems with SPL.
609 Support for the underlying block device (e.g. MMC or USB) must be
615 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
616 provide software-configurable hardware which is typically used to
617 implement peripherals (such as UARTs, LCD displays, MMC) or
618 accelerate custom processing functions, such as image processing
619 or machine learning. Sometimes it is useful to program the FPGA
620 as early as possible during boot, and this option can enable that
623 config SPL_GPIO_SUPPORT
624 bool "Support GPIO in SPL"
626 Enable support for GPIOs (General-purpose Input/Output) in SPL.
627 GPIOs allow U-Boot to read the state of an input line (high or
628 low) and set the state of an output line. This can be used to
629 drive LEDs, control power to various system parts and read user
630 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
631 for example. Enable this option to build the drivers in
632 drivers/gpio as part of an SPL build.
634 config SPL_I2C_SUPPORT
637 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
638 I2C works with a clock and data line which can be driven by a
639 one or more masters or slaves. It is a fairly complex bus but is
640 widely used as it only needs two lines for communication. Speeds of
641 400kbps are typical but up to 3.4Mbps is supported by some
642 hardware. I2C can be useful in SPL to configure power management
643 ICs (PMICs) before raising the CPU clock speed, for example.
644 Enable this option to build the drivers in drivers/i2c as part of
647 config SPL_LIBCOMMON_SUPPORT
648 bool "Support common libraries"
650 Enable support for common U-Boot libraries within SPL. These
651 libraries include common code to deal with U-Boot images,
652 environment and USB, for example. This option is enabled on many
653 boards. Enable this option to build the code in common/ as part of
656 config SPL_LIBDISK_SUPPORT
657 bool "Support disk partitions"
660 Enable support for disk partitions within SPL. 'Disk' is something
661 of a misnomer as it includes non-spinning media such as flash (as
662 used in MMC and USB sticks). Partitions provide a way for a disk
663 to be split up into separate regions, with a partition table placed
664 at the start or end which describes the location and size of each
665 'partition'. These partitions are typically uses as individual block
666 devices, typically with an EXT2 or FAT filesystem in each. This
667 option enables whatever partition support has been enabled in
668 U-Boot to also be used in SPL. It brings in the code in disk/.
670 config SPL_LIBGENERIC_SUPPORT
671 bool "Support generic libraries"
673 Enable support for generic U-Boot libraries within SPL. These
674 libraries include generic code to deal with device tree, hashing,
675 printf(), compression and the like. This option is enabled on many
676 boards. Enable this option to build the code in lib/ as part of an
679 config SPL_DM_MAILBOX
680 bool "Support Mailbox"
682 Enable support for Mailbox within SPL. This enable the inter
683 processor communication protocols tobe used within SPL. Enable
684 this option to build the drivers in drivers/mailbox as part of
687 config SPL_MMC_SUPPORT
690 select HAVE_BLOCK_DEVICE
692 Enable support for MMC (Multimedia Card) within SPL. This enables
693 the MMC protocol implementation and allows any enabled drivers to
694 be used within SPL. MMC can be used with or without disk partition
695 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
696 this option to build the drivers in drivers/mmc as part of an SPL
699 config SYS_MMCSD_FS_BOOT_PARTITION
700 int "MMC Boot Partition"
703 Partition on the MMC to load U-Boot from when the MMC is being
707 bool "Tiny MMC framework in SPL"
708 depends on SPL_MMC_SUPPORT
711 Enable MMC framework tinification support. This option is useful if
712 if your SPL is extremely size constrained. Heed the warning, enable
713 this option if and only if you know exactly what you are doing, if
714 you are reading this help text, you most likely have no idea :-)
716 The MMC framework is reduced to bare minimum to be useful. No malloc
717 support is needed for the MMC framework operation with this option
718 enabled. The framework supports exactly one MMC device and exactly
719 one MMC driver. The MMC driver can be adjusted to avoid any malloc
720 operations too, which can remove the need for malloc support in SPL
721 and thus further reduce footprint.
724 bool "MMC/SD/SDIO card support for write operations in SPL"
725 depends on SPL_MMC_SUPPORT
728 Enable write access to MMC and SD Cards in SPL
731 config SPL_MPC8XXX_INIT_DDR_SUPPORT
732 bool "Support MPC8XXX DDR init"
734 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
735 random-access memory) on the MPC8XXX family within SPL. This
736 allows DRAM to be set up before loading U-Boot into that DRAM,
739 config SPL_MTD_SUPPORT
740 bool "Support MTD drivers"
742 Enable support for MTD (Memory Technology Device) within SPL. MTD
743 provides a block interface over raw NAND and can also be used with
744 SPI flash. This allows SPL to load U-Boot from supported MTD
745 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
746 to enable specific MTD drivers.
748 config SPL_MUSB_NEW_SUPPORT
749 bool "Support new Mentor Graphics USB"
751 Enable support for Mentor Graphics USB in SPL. This is a new
752 driver used by some boards. Enable this option to build
753 the drivers in drivers/usb/musb-new as part of an SPL build. The
754 old drivers are in drivers/usb/musb.
756 config SPL_NAND_SUPPORT
757 bool "Support NAND flash"
759 Enable support for NAND (Negative AND) flash in SPL. NAND flash
760 can be used to allow SPL to load U-Boot from supported devices.
761 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
764 config SPL_NAND_DRIVERS
765 bool "Use standard NAND driver"
767 SPL uses normal NAND drivers, not minimal drivers.
770 bool "Include standard software ECC in the SPL"
772 config SPL_NAND_SIMPLE
773 bool "Support simple NAND drivers in SPL"
775 Support for NAND boot using simple NAND drivers that
776 expose the cmd_ctrl() interface.
779 depends on SPL_NAND_DRIVERS
780 bool "Use Base NAND Driver"
782 Include nand_base.c in the SPL.
784 config SPL_NAND_IDENT
785 depends on SPL_NAND_BASE
786 bool "Use chip ID to identify NAND flash"
788 SPL uses the chip ID list to identify the NAND flash.
793 Enable support for loading payloads from UBI. See
794 README.ubispl for more info.
799 bool "Support cache drivers in SPL"
801 Enable support for cache drivers in SPL.
804 bool "Support SPI DM drivers in SPL"
806 Enable support for SPI DM drivers in SPL.
808 config SPL_DM_SPI_FLASH
809 bool "Support SPI DM FLASH drivers in SPL"
811 Enable support for SPI DM flash drivers in SPL.
815 config SPL_UBI_LOAD_BY_VOLNAME
816 bool "Support loading volumes by name"
818 This enables support for loading UBI volumes by name. When this
819 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
820 configure the volume name from which to load U-Boot.
822 config SPL_UBI_MAX_VOL_LEBS
823 int "Maximum number of LEBs per volume"
826 The maximum number of logical eraseblocks which a static volume
827 to load can contain. Used for sizing the scan data structure.
829 config SPL_UBI_MAX_PEB_SIZE
830 int "Maximum PEB size"
833 The maximum physical erase block size.
835 config SPL_UBI_MAX_PEBS
836 int "Maximum number of PEBs"
839 The maximum physical erase block size. If not overridden by
840 board code, this value will be used as the actual number of PEBs.
842 config SPL_UBI_PEB_OFFSET
843 int "Offset to first UBI PEB"
846 The offset in number of PEBs from the start of flash to the first
847 PEB part of the UBI image.
849 config SPL_UBI_VID_OFFSET
850 int "Offset to VID header"
853 config SPL_UBI_LEB_START
854 int "Offset to LEB in PEB"
857 The offset in bytes to the LEB within a PEB.
859 config SPL_UBI_INFO_ADDR
860 hex "Address to place UBI scan info"
863 Address for ubispl to place the scan info. Read README.ubispl to
864 determine the required size
866 config SPL_UBI_VOL_IDS
867 int "Maximum volume id"
870 The maximum volume id which can be loaded. Used for sizing the
873 config SPL_UBI_LOAD_MONITOR_ID
874 int "id of U-Boot volume"
877 The UBI volume id from which to load U-Boot
879 config SPL_UBI_LOAD_MONITOR_VOLNAME
880 string "volume name of U-Boot volume"
881 depends on SPL_UBI_LOAD_BY_VOLNAME
883 The UBI volume name from which to load U-Boot
885 config SPL_UBI_LOAD_KERNEL_ID
886 int "id of kernel volume"
887 depends on SPL_OS_BOOT && SPL_UBI
889 The UBI volume id from which to load the kernel
891 config SPL_UBI_LOAD_ARGS_ID
892 int "id of kernel args volume"
893 depends on SPL_OS_BOOT && SPL_UBI
895 The UBI volume id from which to load the device tree
897 config UBI_SPL_SILENCE_MSG
898 bool "silence UBI SPL messages"
901 Disable messages from UBI SPL. This leaves warnings
906 config SPL_NET_SUPPORT
907 bool "Support networking"
909 Enable support for network devices (such as Ethernet) in SPL.
910 This permits SPL to load U-Boot over a network link rather than
911 from an on-board peripheral. Environment support is required since
912 the network stack uses a number of environment variables. See also
916 config SPL_NET_VCI_STRING
917 string "BOOTP Vendor Class Identifier string sent by SPL"
919 As defined by RFC 2132 the vendor class identifier field can be
920 sent by the client to identify the vendor type and configuration
921 of a client. This is often used in practice to allow for the DHCP
922 server to specify different files to load depending on if the ROM,
923 SPL or U-Boot itself makes the request
924 endif # if SPL_NET_SUPPORT
926 config SPL_NO_CPU_SUPPORT
927 bool "Drop CPU code in SPL"
929 This is specific to the ARM926EJ-S CPU. It disables the standard
930 start.S start-up code, presumably so that a replacement can be
931 used on that CPU. You should not enable it unless you know what
934 config SPL_NOR_SUPPORT
935 bool "Support NOR flash"
937 Enable support for loading U-Boot from memory-mapped NOR (Negative
938 OR) flash in SPL. NOR flash is slow to write but fast to read, and
939 a memory-mapped device makes it very easy to access. Loading from
940 NOR is typically achieved with just a memcpy().
942 config SPL_XIP_SUPPORT
946 Enable support for execute in place of U-Boot or kernel image. There
947 is no need to copy image from flash to ram if flash supports execute
948 in place. Its very useful in systems having enough flash but not
949 enough ram to load the image.
951 config SPL_ONENAND_SUPPORT
952 bool "Support OneNAND flash"
954 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
955 a type of NAND flash and therefore can be used to allow SPL to
956 load U-Boot from supported devices. This enables the drivers in
957 drivers/mtd/onenand as part of an SPL build.
960 bool "Activate Falcon Mode"
961 depends on !TI_SECURE_DEVICE
964 Enable booting directly to an OS from SPL.
965 for more info read doc/README.falcon
969 hex "addr, where OS is found"
970 depends on SPL_NOR_SUPPORT
972 Specify the address, where the OS image is found, which
979 default "tpl/u-boot-with-tpl.bin" if TPL
982 Payload for SPL boot. For backward compatibility, default to
983 u-boot.bin, i.e. RAW image without any header. In case of
984 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
988 bool "Support PCI drivers"
990 Enable support for PCI in SPL. For platforms that need PCI to boot,
991 or must perform some init using PCI in SPL, this provides the
992 necessary driver support. This enables the drivers in drivers/pci
993 as part of an SPL build.
995 config SPL_PCH_SUPPORT
996 bool "Support PCH drivers"
998 Enable support for PCH (Platform Controller Hub) devices in SPL.
999 These are used to set up GPIOs and the SPI peripheral early in
1000 boot. This enables the drivers in drivers/pch as part of an SPL
1003 config SPL_POST_MEM_SUPPORT
1004 bool "Support POST drivers"
1006 Enable support for POST (Power-on Self Test) in SPL. POST is a
1007 procedure that checks that the hardware (CPU or board) appears to
1008 be functionally correctly. It is a sanity check that can be
1009 performed before booting. This enables the drivers in post/drivers
1010 as part of an SPL build.
1013 bool "Support reset drivers"
1016 Enable support for reset control in SPL.
1017 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1018 by using the generic reset API provided by driver model.
1019 This enables the drivers in drivers/reset as part of an SPL build.
1021 config SPL_POWER_SUPPORT
1022 bool "Support power drivers"
1024 Enable support for power control in SPL. This includes support
1025 for PMICs (Power-management Integrated Circuits) and some of the
1026 features provided by PMICs. In particular, voltage regulators can
1027 be used to enable/disable power and vary its voltage. That can be
1028 useful in SPL to turn on boot peripherals and adjust CPU voltage
1029 so that the clock speed can be increased. This enables the drivers
1030 in drivers/power, drivers/power/pmic and drivers/power/regulator
1031 as part of an SPL build.
1033 config SPL_POWER_DOMAIN
1034 bool "Support power domain drivers"
1036 Enable support for power domain control in SPL. Many SoCs allow
1037 power to be applied to or removed from portions of the SoC (power
1038 domains). This may be used to save power. This API provides the
1039 means to control such power management hardware. This enables
1040 the drivers in drivers/power/domain as part of a SPL build.
1042 config SPL_RAM_SUPPORT
1043 bool "Support booting from RAM"
1044 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1046 Enable booting of an image in RAM. The image can be preloaded or
1047 it can be loaded by SPL directly into RAM (e.g. using USB).
1049 config SPL_RAM_DEVICE
1050 bool "Support booting from preloaded image in RAM"
1051 depends on SPL_RAM_SUPPORT
1052 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1054 Enable booting of an image already loaded in RAM. The image has to
1055 be already in memory when SPL takes over, e.g. loaded by the boot
1058 config SPL_REMOTEPROC
1059 bool "Support REMOTEPROCS"
1061 Enable support for REMOTEPROCs in SPL. This permits to load
1062 a remote processor firmware in SPL.
1064 config SPL_RTC_SUPPORT
1065 bool "Support RTC drivers"
1067 Enable RTC (Real-time Clock) support in SPL. This includes support
1068 for reading and setting the time. Some RTC devices also have some
1069 non-volatile (battery-backed) memory which is accessible if
1070 needed. This enables the drivers in drivers/rtc as part of an SPL
1073 config SPL_SATA_SUPPORT
1074 bool "Support loading from SATA"
1076 Enable support for SATA (Serial AT attachment) in SPL. This allows
1077 use of SATA devices such as hard drives and flash drivers for
1078 loading U-Boot. SATA is used in higher-end embedded systems and
1079 can provide higher performance than MMC , at somewhat higher
1080 expense and power consumption. This enables loading from SATA
1081 using a configured device.
1083 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1084 bool "SATA raw mode: by sector"
1085 depends on SPL_SATA_SUPPORT
1087 Use sector number for specifying U-Boot location on SATA disk in
1090 config SPL_SATA_RAW_U_BOOT_SECTOR
1091 hex "Sector on the SATA disk to load U-Boot from"
1092 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1094 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1095 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1097 config SPL_SERIAL_SUPPORT
1098 bool "Support serial"
1102 Enable support for serial in SPL. This allows use of a serial UART
1103 for displaying messages while SPL is running. It also brings in
1104 printf() and panic() functions. This should normally be enabled
1105 unless there are space reasons not to. Even then, consider
1106 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1108 config SPL_SPI_SUPPORT
1109 bool "Support SPI drivers"
1111 Enable support for using SPI in SPL. This is used for connecting
1112 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1113 more details on that. The SPI driver provides the transport for
1114 data between the SPI flash and the CPU. This option can be used to
1115 enable SPI drivers that are needed for other purposes also, such
1118 config SPL_SPI_FLASH_SUPPORT
1119 bool "Support SPI flash drivers"
1120 depends on SPL_SPI_SUPPORT
1122 Enable support for using SPI flash in SPL, and loading U-Boot from
1123 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1124 the SPI bus that is used to connect it to a system. It is a simple
1125 but fast bidirectional 4-wire bus (clock, chip select and two data
1126 lines). This enables the drivers in drivers/mtd/spi as part of an
1127 SPL build. This normally requires SPL_SPI_SUPPORT.
1129 if SPL_SPI_FLASH_SUPPORT
1131 config SPL_SPI_FLASH_TINY
1132 bool "Enable low footprint SPL SPI Flash support"
1133 depends on !SPI_FLASH_BAR
1134 default y if SPI_FLASH
1136 Enable lightweight SPL SPI Flash support that supports just reading
1137 data/images from flash. No support to write/erase flash. Enable
1138 this if you have SPL size limitations and don't need full
1139 fledged SPI flash support.
1141 config SPL_SPI_FLASH_SFDP_SUPPORT
1142 bool "SFDP table parsing support for SPI NOR flashes"
1143 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1145 Enable support for parsing and auto discovery of parameters for
1146 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1147 tables as per JESD216 standard in SPL.
1149 config SPL_SPI_FLASH_MTD
1150 bool "Support for SPI flash MTD drivers in SPL"
1152 Enable support for SPI flash MTD drivers in SPL.
1155 bool "Support loading from SPI flash"
1157 Enable support for loading next stage, U-Boot or otherwise, from
1158 SPI NOR in U-Boot SPL.
1160 endif # SPL_SPI_FLASH_SUPPORT
1162 config SYS_SPI_U_BOOT_OFFS
1163 hex "address of u-boot payload in SPI flash"
1164 default 0x8000 if ARCH_SUNXI
1166 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1168 Address within SPI-Flash from where the u-boot payload is fetched
1172 bool "Driver support for thermal devices"
1174 Enable support for temperature-sensing devices. Some SoCs have on-chip
1175 temperature sensors to permit warnings, speed throttling or even
1176 automatic power-off when the temperature gets too high or low. Other
1177 devices may be discrete but connected on a suitable bus.
1179 config SPL_USB_HOST_SUPPORT
1180 bool "Support USB host drivers"
1181 select HAVE_BLOCK_DEVICE
1183 Enable access to USB (Universal Serial Bus) host devices so that
1184 SPL can load U-Boot from a connected USB peripheral, such as a USB
1185 flash stick. While USB takes a little longer to start up than most
1186 buses, it is very flexible since many different types of storage
1187 device can be attached. This option enables the drivers in
1188 drivers/usb/host as part of an SPL build.
1190 config SPL_USB_STORAGE
1191 bool "Support loading from USB"
1192 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1194 Enable support for USB devices in SPL. This allows use of USB
1195 devices such as hard drives and flash drivers for loading U-Boot.
1196 The actual drivers are enabled separately using the normal U-Boot
1197 config options. This enables loading from USB using a configured
1200 config SPL_USB_GADGET
1201 bool "Suppport USB Gadget drivers"
1203 Enable USB Gadget API which allows to enable USB device functions
1208 config SPL_USB_ETHER
1209 bool "Support USB Ethernet drivers"
1211 Enable access to the USB network subsystem and associated
1212 drivers in SPL. This permits SPL to load U-Boot over a
1213 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1214 than from an onboard peripheral. Environment support is required
1215 since the network stack uses a number of environment variables.
1216 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1219 bool "Support DFU (Device Firmware Upgrade)"
1220 select SPL_HASH_SUPPORT
1221 select SPL_DFU_NO_RESET
1222 depends on SPL_RAM_SUPPORT
1224 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1225 RAM memory device support. The ROM code will load and execute
1226 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1227 selected device partition from host-pc using dfu-utils.
1228 This feature is useful to flash the binaries to factory or bare-metal
1229 boards using USB interface.
1232 bool "DFU device selection"
1237 depends on SPL_DFU && SPL_RAM_SUPPORT
1239 select RAM/DDR memory device for loading binary images
1240 (u-boot/kernel) to the selected device partition using
1241 DFU and execute the u-boot/kernel from RAM.
1245 config SPL_USB_SDP_SUPPORT
1246 bool "Support SDP (Serial Download Protocol)"
1247 depends on SPL_SERIAL_SUPPORT
1249 Enable Serial Download Protocol (SDP) device support in SPL. This
1250 allows to download images into memory and execute (jump to) them
1251 using the same protocol as implemented by the i.MX family's boot ROM.
1253 config SPL_SDP_USB_DEV
1254 int "SDP USB controller index"
1256 depends on SPL_USB_SDP_SUPPORT
1258 Some boards have USB controller other than 0. Define this option
1259 so it can be used in compiled environment.
1262 config SPL_WATCHDOG_SUPPORT
1263 bool "Support watchdog drivers"
1264 imply SPL_WDT if !HW_WATCHDOG
1266 Enable support for watchdog drivers in SPL. A watchdog is
1267 typically a hardware peripheral which can reset the system when it
1268 detects no activity for a while (such as a software crash). This
1269 enables the drivers in drivers/watchdog as part of an SPL build.
1271 config SPL_YMODEM_SUPPORT
1272 bool "Support loading using Ymodem"
1273 depends on SPL_SERIAL_SUPPORT
1275 While loading from serial is slow it can be a useful backup when
1276 there is no other option. The Ymodem protocol provides a reliable
1277 means of transmitting U-Boot over a serial line for using in SPL,
1278 with a checksum to ensure correctness.
1281 bool "Support ARM Trusted Firmware"
1282 depends on ARM64 && SPL_FIT
1284 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1285 is loaded by SPL (which is considered as BL2 in ATF terminology).
1286 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1288 config SPL_ATF_LOAD_IMAGE_V2
1289 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1292 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1294 If you want to load a bl31 image from the SPL and need the new
1297 config SPL_ATF_NO_PLATFORM_PARAM
1298 bool "Pass no platform parameter"
1301 While we expect to call a pointer to a valid FDT (or NULL)
1302 as the platform parameter to an ATF, some ATF versions are
1303 not U-Boot aware and have an insufficiently robust parameter
1304 validation to gracefully reject a FDT being passed.
1306 If this option is enabled, the spl_atf os-type handler will
1307 always pass NULL for the platform parameter.
1309 If your ATF is affected, say Y.
1311 config SPL_AM33XX_ENABLE_RTC32K_OSC
1312 bool "Enable the RTC32K OSC on AM33xx based platforms"
1315 Enable access to the AM33xx RTC and select the external 32kHz clock
1319 bool "Support OP-TEE Trusted OS"
1322 OP-TEE is an open source Trusted OS which is loaded by SPL.
1323 More detail at: https://github.com/OP-TEE/optee_os
1326 bool "Support RISC-V OpenSBI"
1327 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1329 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1330 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1331 firmware. It is loaded and started by U-Boot SPL.
1333 More details are available at https://github.com/riscv/opensbi and
1334 https://github.com/riscv/riscv-sbi-doc
1336 config SPL_OPENSBI_LOAD_ADDR
1337 hex "OpenSBI load address"
1338 depends on SPL_OPENSBI
1340 Load address of the OpenSBI binary.
1344 depends on SUPPORT_TPL
1347 If you want to build TPL as well as the normal image and SPL, say Y.
1351 config TPL_SIZE_LIMIT
1352 hex "Maximum size of TPL image"
1356 Specifies the maximum length of the U-Boot TPL image.
1357 If this value is zero, it is ignored.
1359 config TPL_FRAMEWORK
1360 bool "Support TPL based upon the common SPL framework"
1361 default y if SPL_FRAMEWORK
1363 Enable the SPL framework under common/spl/ for TPL builds.
1364 This framework supports MMC, NAND and YMODEM and other methods
1365 loading of U-Boot's SPL stage. If unsure, say Y.
1368 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1369 depends on HANDOFF && TPL_BLOBLIST
1372 This option enables TPL to write handoff information. This can be
1373 used to pass information like the size of SDRAM from TPL to U-Boot
1374 proper. The information is also available to SPL if it is useful
1377 config TPL_BOARD_INIT
1378 bool "Call board-specific initialization in TPL"
1380 If this option is enabled, U-Boot will call the function
1381 spl_board_init() from board_init_r(). This function should be
1382 provided by the board.
1385 string "Linker script for the TPL stage"
1387 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1388 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1390 The TPL stage will usually require a different linker-script
1391 (as it runs from a different memory region) than the regular
1392 U-Boot stage. Set this to the path of the linker-script to
1395 May be left empty to trigger the Makefile infrastructure to
1396 fall back to the linker-script used for the SPL stage.
1398 config TPL_NEEDS_SEPARATE_TEXT_BASE
1399 bool "TPL needs a separate text-base"
1403 Enable, if the TPL stage should not inherit its text-base
1404 from the SPL stage. When enabled, a base address for the
1405 .text sections of the TPL stage has to be set below.
1407 config TPL_NEEDS_SEPARATE_STACK
1408 bool "TPL needs a separate initial stack-pointer"
1412 Enable, if the TPL stage should not inherit its initial
1413 stack-pointer from the settings for the SPL stage.
1415 config TPL_TEXT_BASE
1416 hex "Base address for the .text section of the TPL stage"
1417 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1419 The base address for the .text section of the TPL stage.
1422 int "Maximum size (in bytes) for the TPL stage"
1426 The maximum size (in bytes) of the TPL stage.
1429 hex "Address of the initial stack-pointer for the TPL stage"
1430 depends on TPL_NEEDS_SEPARATE_STACK
1432 The address of the initial stack-pointer for the TPL stage.
1433 Usually this will be the (aligned) top-of-stack.
1435 config TPL_BOOTROM_SUPPORT
1436 bool "Support returning to the BOOTROM (from TPL)"
1438 Some platforms (e.g. the Rockchip RK3368) provide support in their
1439 ROM for loading the next boot-stage after performing basic setup
1442 Enable this option, to return to the BOOTROM through the
1443 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1444 boot device list, if not implemented for a given board)
1446 config TPL_DRIVERS_MISC_SUPPORT
1447 bool "Support misc drivers in TPL"
1449 Enable miscellaneous drivers in TPL. These drivers perform various
1450 tasks that don't fall nicely into other categories, Enable this
1451 option to build the drivers in drivers/misc as part of an TPL
1452 build, for those that support building in TPL (not all drivers do).
1454 config TPL_ENV_SUPPORT
1455 bool "Support an environment"
1457 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1459 config TPL_GPIO_SUPPORT
1460 bool "Support GPIO in TPL"
1462 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1463 GPIOs allow U-Boot to read the state of an input line (high or
1464 low) and set the state of an output line. This can be used to
1465 drive LEDs, control power to various system parts and read user
1466 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1467 for example. Enable this option to build the drivers in
1468 drivers/gpio as part of an TPL build.
1470 config TPL_I2C_SUPPORT
1473 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1476 config TPL_LIBCOMMON_SUPPORT
1477 bool "Support common libraries"
1479 Enable support for common U-Boot libraries within TPL. See
1480 SPL_LIBCOMMON_SUPPORT for details.
1482 config TPL_LIBGENERIC_SUPPORT
1483 bool "Support generic libraries"
1485 Enable support for generic U-Boot libraries within TPL. See
1486 SPL_LIBGENERIC_SUPPORT for details.
1488 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1489 bool "Support MPC8XXX DDR init"
1491 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1492 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1494 config TPL_MMC_SUPPORT
1498 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1500 config TPL_NAND_SUPPORT
1501 bool "Support NAND flash"
1503 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1506 bool "Support PCI drivers"
1508 Enable support for PCI in TPL. For platforms that need PCI to boot,
1509 or must perform some init using PCI in SPL, this provides the
1510 necessary driver support. This enables the drivers in drivers/pci
1511 as part of a TPL build.
1513 config TPL_PCH_SUPPORT
1514 bool "Support PCH drivers"
1516 Enable support for PCH (Platform Controller Hub) devices in TPL.
1517 These are used to set up GPIOs and the SPI peripheral early in
1518 boot. This enables the drivers in drivers/pch as part of a TPL
1521 config TPL_RAM_SUPPORT
1522 bool "Support booting from RAM"
1524 Enable booting of an image in RAM. The image can be preloaded or
1525 it can be loaded by TPL directly into RAM (e.g. using USB).
1527 config TPL_RAM_DEVICE
1528 bool "Support booting from preloaded image in RAM"
1529 depends on TPL_RAM_SUPPORT
1531 Enable booting of an image already loaded in RAM. The image has to
1532 be already in memory when TPL takes over, e.g. loaded by the boot
1535 config TPL_RTC_SUPPORT
1536 bool "Support RTC drivers"
1538 Enable RTC (Real-time Clock) support in TPL. This includes support
1539 for reading and setting the time. Some RTC devices also have some
1540 non-volatile (battery-backed) memory which is accessible if
1541 needed. This enables the drivers in drivers/rtc as part of an TPL
1544 config TPL_SERIAL_SUPPORT
1545 bool "Support serial"
1549 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1552 config TPL_SPI_FLASH_SUPPORT
1553 bool "Support SPI flash drivers"
1555 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1558 config TPL_SPI_FLASH_TINY
1559 bool "Enable low footprint TPL SPI Flash support"
1560 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1561 default y if SPI_FLASH
1563 Enable lightweight TPL SPI Flash support that supports just reading
1564 data/images from flash. No support to write/erase flash. Enable
1565 this if you have TPL size limitations and don't need full-fledged
1569 bool "Support loading from SPI flash"
1570 depends on TPL_SPI_FLASH_SUPPORT
1572 Enable support for loading next stage, U-Boot or otherwise, from
1573 SPI NOR in U-Boot TPL.
1575 config TPL_SPI_SUPPORT
1576 bool "Support SPI drivers"
1578 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1582 bool "Support SPI DM drivers in TPL"
1584 Enable support for SPI DM drivers in TPL.
1586 config TPL_DM_SPI_FLASH
1587 bool "Support SPI DM FLASH drivers in TPL"
1589 Enable support for SPI DM flash drivers in TPL.
1591 config TPL_YMODEM_SUPPORT
1592 bool "Support loading using Ymodem"
1593 depends on TPL_SERIAL_SUPPORT
1595 While loading from serial is slow it can be a useful backup when
1596 there is no other option. The Ymodem protocol provides a reliable
1597 means of transmitting U-Boot over a serial line for using in TPL,
1598 with a checksum to ensure correctness.
1602 config SPL_AT91_MCK_BYPASS
1603 bool "Use external clock signal as a source of main clock for AT91 platforms"
1604 depends on ARCH_AT91
1607 Use external 8 to 24 Mhz clock signal as source of main clock instead
1608 of an external crystal oscillator.
1609 This option disables the internal driving on the XOUT pin.
1610 The external source has to provide a stable clock on the XIN pin.
1611 If this option is disabled, the SoC expects a crystal oscillator
1612 that needs driving on both XIN and XOUT lines.