12 config SPL_DFU_NO_RESET
17 depends on SUPPORT_SPL
20 If you want to build SPL as well as the normal image, say Y.
23 bool "Support SPL based upon the common SPL framework"
27 Enable the SPL framework under common/spl/. This framework
28 supports MMC, NAND and YMODEM and other methods loading of U-Boot
29 and the Linux Kernel. If unsure, say Y.
31 config SPL_FRAMEWORK_BOARD_INIT_F
32 bool "Define a generic function board_init_f"
33 depends on SPL_FRAMEWORK
35 Define a generic function board_init_f that:
36 - initialize the spl (spl_early_init)
37 - initialize the serial (preloader_console_init)
38 Unless you want to provide your own board_init_f, you should say Y.
41 hex "Maximum size of SPL image"
43 default 0x11000 if ARCH_MX6 && !MX6_OCRAM_256KB
44 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
47 Specifies the maximum length of the U-Boot SPL image.
48 If this value is zero, it is ignored.
50 config SPL_SIZE_LIMIT_SUBTRACT_GD
51 bool "SPL image size check: provide space for global data"
52 depends on SPL_SIZE_LIMIT > 0
54 If enabled, aligned size of global data is reserved in
55 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
56 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
57 pre-reloc global data is put into this SRAM, too.
59 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
60 bool "SPL image size check: provide space for malloc() pool before relocation"
61 depends on SPL_SIZE_LIMIT > 0
63 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
64 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
65 describes the size of SRAM available for SPL when pre-reloc malloc
66 pool is put into this SRAM, too.
68 config SPL_SIZE_LIMIT_PROVIDE_STACK
69 hex "SPL image size check: provide stack space before relocation"
70 depends on SPL_SIZE_LIMIT > 0
73 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
74 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
75 of SRAM available for SPL when the stack required before reolcation
78 config SPL_SYS_STACK_F_CHECK_BYTE
82 Constant used to check the stack
84 config SPL_SYS_REPORT_STACK_F_USAGE
85 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
86 bool "Check and report stack usage in SPL before relocation"
88 If this option is enabled, the initial SPL stack is filled with 0xaa
89 very early, up to the size configured with
90 SPL_SIZE_LIMIT_PROVIDE_STACK.
91 Later when SPL is done using this initial stack and switches to a
92 stack in DRAM, the actually used size of this initial stack is
93 reported by examining the memory and searching for the lowest
94 occurrence of non 0xaa bytes.
95 This default implementation works for stacks growing down only.
97 config SPL_SHOW_ERRORS
98 bool "Show more information when something goes wrong"
100 This enabled more verbose error messages and checking when something
101 goes wrong in SPL. For example, it shows the error code when U-Boot
102 cannot be located. This can help to diagnose the problem and figure
103 out a fix, particularly during development.
105 This adds a small amount to SPL code size, perhaps 100 bytes.
107 config SPL_BINMAN_SYMBOLS
108 bool "Declare binman symbols in SPL"
109 depends on SPL_FRAMEWORK && BINMAN
112 This enables use of symbols in SPL which refer to U-Boot, enabling SPL
113 to obtain the location of U-Boot simply by calling spl_get_image_pos()
114 and spl_get_image_size().
116 For this to work, you must have a U-Boot image in the binman image, so
117 binman can update SPL with the location of it.
119 menu "PowerPC and LayerScape SPL Boot options"
122 bool "Load SPL from NAND flash"
123 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
126 bool "Load SPL from SD Card / eMMC"
127 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
130 bool "Load SPL from SPI flash"
131 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
134 bool "Create SPL in Freescale PBI format"
135 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
138 Create boot binary having SPL binary in PBI format concatenated with
144 bool "Pass hand-off information from SPL to U-Boot proper"
145 depends on SPL && BLOBLIST
147 It is useful to be able to pass information from SPL to U-Boot
148 proper to preserve state that is known in SPL and is needed in U-Boot.
149 Enable this to locate the handoff information in U-Boot proper, early
150 in boot. It is available in gd->handoff. The state state is set up
151 in SPL (or TPL if that is being used).
156 bool "Pass hand-off information from SPL to U-Boot proper"
157 depends on HANDOFF && SPL_BLOBLIST
160 This option enables SPL to write handoff information. This can be
161 used to pass information like the size of SDRAM from SPL to U-Boot
162 proper. Also SPL can receive information from TPL in the same place
166 string "Linker script for the SPL stage"
167 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
169 The SPL stage will usually require a different linker-script
170 (as it runs from a different memory region) than the regular
171 U-Boot stage. Set this to the path of the linker-script to
176 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
177 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
178 default 0x20060 if SUN50I_GEN_H6
179 default 0x00060 if ARCH_SUNXI
180 default 0xfffc0000 if ARCH_ZYNQMP
183 The address in memory that SPL will be running from.
185 config SPL_BOARD_INIT
186 bool "Call board-specific initialization in SPL"
188 If this option is enabled, U-Boot will call the function
189 spl_board_init() from board_init_r(). This function should be
190 provided by the board.
192 config SPL_BOOTROM_SUPPORT
193 bool "Support returning to the BOOTROM"
195 Some platforms (e.g. the Rockchip RK3368) provide support in their
196 ROM for loading the next boot-stage after performing basic setup
199 Enable this option, to return to the BOOTROM through the
200 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
201 boot device list, if not implemented for a given board)
203 config SPL_BOOTCOUNT_LIMIT
204 bool "Support bootcount in SPL"
205 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
207 On some boards, which use 'falcon' mode, it is necessary to check
208 and increment the number of boot attempts. Such boards do not
209 use proper U-Boot for normal boot flow and hence needs those
210 adjustments to be done in the SPL.
212 config SPL_RAW_IMAGE_SUPPORT
213 bool "Support SPL loading and booting of RAW images"
214 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
215 default y if !TI_SECURE_DEVICE
217 SPL will support loading and booting a RAW image when this option
218 is y. If this is not set, SPL will move on to other available
219 boot media to find a suitable image.
221 config SPL_LEGACY_IMAGE_SUPPORT
222 bool "Support SPL loading and booting of Legacy images"
223 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
225 SPL will support loading and booting Legacy images when this option
226 is y. If this is not set, SPL will move on to other available
227 boot media to find a suitable image.
229 config SPL_LEGACY_IMAGE_CRC_CHECK
230 bool "Check CRC of Legacy images"
231 depends on SPL_LEGACY_IMAGE_SUPPORT
234 Enable this to check the CRC of Legacy images. While this increases
235 reliability, it affects both code size and boot duration.
236 If disabled, Legacy images are booted if the image magic and size
237 are correct, without further integrity checks.
239 config SPL_SYS_MALLOC_SIMPLE
241 prompt "Only use malloc_simple functions in the SPL"
243 Say Y here to only use the *_simple malloc functions from
244 malloc_simple.c, rather then using the versions from dlmalloc.c;
245 this will make the SPL binary smaller at the cost of more heap
246 usage as the *_simple malloc functions do not re-use free-ed mem.
248 config TPL_SYS_MALLOC_SIMPLE
250 prompt "Only use malloc_simple functions in the TPL"
253 Say Y here to only use the *_simple malloc functions from
254 malloc_simple.c, rather then using the versions from dlmalloc.c;
255 this will make the TPL binary smaller at the cost of more heap
256 usage as the *_simple malloc functions do not re-use free-ed mem.
259 bool "Enable SDRAM location for SPL stack"
261 SPL starts off execution in SRAM and thus typically has only a small
262 stack available. Since SPL sets up DRAM while in its board_init_f()
263 function, it is possible for the stack to move there before
264 board_init_r() is reached. This option enables a special SDRAM
265 location for the SPL stack. U-Boot SPL switches to this after
266 board_init_f() completes, and before board_init_r() starts.
268 config SPL_STACK_R_ADDR
269 depends on SPL_STACK_R
270 hex "SDRAM location for SPL stack"
271 default 0x82000000 if ARCH_OMAP2PLUS
273 Specify the address in SDRAM for the SPL stack. This will be set up
274 before board_init_r() is called.
276 config SPL_STACK_R_MALLOC_SIMPLE_LEN
277 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
278 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
281 Specify the amount of the stack to use as memory pool for
282 malloc_simple after switching the stack to DRAM. This may be set
283 to give board_init_r() a larger heap then the initial heap in
284 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
286 config SPL_SEPARATE_BSS
287 bool "BSS section is in a different memory region from text"
289 Some platforms need a large BSS region in SPL and can provide this
290 because RAM is already set up. In this case BSS can be moved to RAM.
291 This option should then be enabled so that the correct device tree
292 location is used. Normally we put the device tree at the end of BSS
293 but with this option enabled, it goes at _image_binary_end.
297 depends on SPL_OF_PLATDATA
298 # Bind cannot be supported because the udevice structs are in read-only
299 # memory so we cannot update the linked lists.
300 select SPL_OF_PLATDATA_NO_BIND
301 select SPL_OF_PLATDATA_RT
303 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
304 section of memory. This means that of-platdata must make a copy (in
305 writeable memory) of anything it wants to modify, such as
308 config TPL_SEPARATE_BSS
309 bool "BSS section is in a different memory region from text"
310 default y if SPL_SEPARATE_BSS
312 Some platforms need a large BSS region in TPL and can provide this
313 because RAM is already set up. In this case BSS can be moved to RAM.
314 This option should then be enabled so that the correct device tree
315 location is used. Normally we put the device tree at the end of BSS
316 but with this option enabled, it goes at _image_binary_end.
318 config SPL_BANNER_PRINT
319 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
322 If this option is enabled, SPL will print the banner with version
323 info. Disabling this option could be useful to reduce SPL boot time
324 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
326 config TPL_BANNER_PRINT
327 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
331 If this option is enabled, TPL will print the banner with version
332 info. Disabling this option could be useful to reduce TPL boot time
333 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
336 depends on ARM && !ARM64
337 bool "Allows initializing BSS early before entering board_init_f"
339 On some platform we have sufficient memory available early on to
340 allow setting up and using a basic BSS prior to entering
341 board_init_f. Activating this option will also de-activate the
342 clearing of BSS during the SPL relocation process, thus allowing
343 to carry state from board_init_f to board_init_r by way of BSS.
345 config SPL_DISPLAY_PRINT
346 bool "Display a board-specific message in SPL"
348 If this option is enabled, U-Boot will call the function
349 spl_display_print() immediately after displaying the SPL console
350 banner ("U-Boot SPL ..."). This function should be provided by
353 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
354 bool "MMC raw mode: by sector"
355 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
356 ARCH_MX6 || ARCH_MX7 || \
357 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
358 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
359 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
360 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
362 Use sector number for specifying U-Boot location on MMC/SD in
365 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
366 hex "Address on the MMC to load U-Boot from"
367 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
368 default 0x40 if ARCH_SUNXI
369 default 0x75 if ARCH_DAVINCI
370 default 0x8a if ARCH_MX6 || ARCH_MX7
371 default 0x100 if ARCH_UNIPHIER
372 default 0x0 if ARCH_MVEBU
373 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
374 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
375 OMAP54XX || AM33XX || AM43XX || ARCH_K3
376 default 0x4000 if ARCH_ROCKCHIP
377 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
379 Address on the MMC to load U-Boot from, when the MMC is being used
380 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
382 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
383 hex "U-Boot main hardware partition image offset"
384 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
385 default 0x10 if ARCH_SUNXI
388 On some platforms SPL location depends on hardware partition. The ROM
389 code skips the MBR sector when loading SPL from main hardware data
390 partition. This adds offset to the main U-Boot image. Set this symbol
391 to the number of skipped sectors.
393 If unsure, leave the default.
395 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
396 bool "MMC Raw mode: by partition"
398 Use a partition for loading U-Boot when using MMC/SD in raw mode.
400 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
401 hex "Partition to use to load U-Boot from"
402 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
405 Partition on the MMC to load U-Boot from when the MMC is being
408 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
409 bool "MMC raw mode: by partition type"
410 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
412 Use partition type for specifying U-Boot partition on MMC/SD in
413 raw mode. U-Boot will be loaded from the first partition of this
416 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
417 hex "Partition Type on the MMC to load U-Boot from"
418 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
420 Partition Type on the MMC to load U-Boot from, when the MMC is being
423 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
424 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
425 depends on SUPPORT_EMMC_BOOT
427 eMMC boot partition is normally configured by the bits of the EXT_CSD
428 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
429 cases it might be required in SPL to load the image from different
430 partition than the partition selected by EXT_CSC_PART_CONFIG register.
431 Enable this option if you intend to use an eMMC boot partition other
432 then selected via EXT_CSC_PART_CONFIG register and specify the custom
433 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
436 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
437 int "Number of the eMMC boot partition to use"
438 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
441 eMMC boot partition number to use when the eMMC in raw mode and
442 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
443 by user defined partition number.
447 default y if SPL_LEGACY_IMAGE_SUPPORT || SPL_EFI_PARTITION
448 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
450 Enable this to support CRC32 in uImages or FIT images within SPL.
451 This is a 32-bit checksum value that can be used to verify images.
452 For FIT images, this is the least secure type of checksum, suitable
453 for detected accidental image corruption. For secure applications you
454 should consider SHA1 or SHA256.
460 Enable this to support MD5 in FIT images within SPL. An MD5
461 checksum is a 128-bit hash value used to check that the image
462 contents have not been corrupted. Note that MD5 is not considered
463 secure as it is possible (with a brute-force attack) to adjust the
464 image while still retaining the same MD5 hash value. For secure
465 applications where images may be changed maliciously, you should
466 consider SHA256 or SHA384.
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
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.
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.
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
507 bool "Support DMA drivers"
509 Enable DMA (direct-memory-access) drivers in SPL. These drivers
510 can be used to handle memory-to-peripheral data transfer without
511 the CPU moving the data. Enable this option to build the drivers
512 in drivers/dma as part of an SPL build.
514 config SPL_DRIVERS_MISC
515 bool "Support misc drivers"
517 Enable miscellaneous drivers in SPL. These drivers perform various
518 tasks that don't fall nicely into other categories, Enable this
519 option to build the drivers in drivers/misc as part of an SPL
520 build, for those that support building in SPL (not all drivers do).
522 config SPL_ENV_SUPPORT
523 bool "Support an environment"
525 Enable environment support in SPL. The U-Boot environment provides
526 a number of settings (essentially name/value pairs) which can
527 control many aspects of U-Boot's operation. Normally this is not
528 needed in SPL as it has a much simpler task with less
529 configuration. But some boards use this to support 'Falcon' boot
530 on EXT2 and FAT, where SPL boots directly into Linux without
531 starting U-Boot first. Enabling this option will make env_get()
532 and env_set() available in SPL.
535 bool "Support save environment"
536 depends on SPL_ENV_SUPPORT
537 select SPL_MMC_WRITE if ENV_IS_IN_MMC
539 Enable save environment support in SPL after setenv. By default
540 the saveenv option is not provided in SPL, but some boards need
541 this support in 'Falcon' boot, where SPL need to boot from
542 different images based on environment variable set by OS. For
543 example OS may set "reboot_image" environment variable to
544 "recovery" inorder to boot recovery image by SPL. The SPL read
545 "reboot_image" and act accordingly and change the reboot_image
546 to default mode using setenv and save the environment.
549 bool "Support Ethernet"
550 depends on SPL_ENV_SUPPORT
553 Enable access to the network subsystem and associated Ethernet
554 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
555 link rather than from an on-board peripheral. Environment support
556 is required since the network stack uses a number of environment
557 variables. See also SPL_NET.
560 bool "Support EXT filesystems"
562 Enable support for EXT2/3/4 filesystems with SPL. This permits
563 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
564 filesystem from within SPL. Support for the underlying block
565 device (e.g. MMC or USB) must be enabled separately.
567 config SPL_FS_SQUASHFS
568 bool "Support SquashFS filesystems"
571 Enable support for SquashFS filesystems with SPL. This permits
572 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
573 filesystem from within SPL. Support for the underlying block
574 device (e.g. MMC or USB) must be enabled separately.
577 bool "Support FAT filesystems"
580 Enable support for FAT and VFAT filesystems with SPL. This
581 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
582 filesystem from within SPL. Support for the underlying block
583 device (e.g. MMC or USB) must be enabled separately.
586 bool "Support write for FAT filesystems"
588 Enable write support for FAT and VFAT filesystems with SPL.
589 Support for the underlying block device (e.g. MMC or USB) must be
595 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
596 provide software-configurable hardware which is typically used to
597 implement peripherals (such as UARTs, LCD displays, MMC) or
598 accelerate custom processing functions, such as image processing
599 or machine learning. Sometimes it is useful to program the FPGA
600 as early as possible during boot, and this option can enable that
604 bool "Support GPIO in SPL"
606 Enable support for GPIOs (General-purpose Input/Output) in SPL.
607 GPIOs allow U-Boot to read the state of an input line (high or
608 low) and set the state of an output line. This can be used to
609 drive LEDs, control power to various system parts and read user
610 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
611 for example. Enable this option to build the drivers in
612 drivers/gpio as part of an SPL build.
617 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
618 I2C works with a clock and data line which can be driven by a
619 one or more masters or slaves. It is a fairly complex bus but is
620 widely used as it only needs two lines for communication. Speeds of
621 400kbps are typical but up to 3.4Mbps is supported by some
622 hardware. I2C can be useful in SPL to configure power management
623 ICs (PMICs) before raising the CPU clock speed, for example.
624 Enable this option to build the drivers in drivers/i2c as part of
627 config SPL_LIBCOMMON_SUPPORT
628 bool "Support common libraries"
630 Enable support for common U-Boot libraries within SPL. These
631 libraries include common code to deal with U-Boot images,
632 environment and USB, for example. This option is enabled on many
633 boards. Enable this option to build the code in common/ as part of
636 config SPL_LIBDISK_SUPPORT
637 bool "Support disk partitions"
640 Enable support for disk partitions within SPL. 'Disk' is something
641 of a misnomer as it includes non-spinning media such as flash (as
642 used in MMC and USB sticks). Partitions provide a way for a disk
643 to be split up into separate regions, with a partition table placed
644 at the start or end which describes the location and size of each
645 'partition'. These partitions are typically uses as individual block
646 devices, typically with an EXT2 or FAT filesystem in each. This
647 option enables whatever partition support has been enabled in
648 U-Boot to also be used in SPL. It brings in the code in disk/.
650 config SPL_LIBGENERIC_SUPPORT
651 bool "Support generic libraries"
653 Enable support for generic U-Boot libraries within SPL. These
654 libraries include generic code to deal with device tree, hashing,
655 printf(), compression and the like. This option is enabled on many
656 boards. Enable this option to build the code in lib/ as part of an
659 config SPL_DM_MAILBOX
660 bool "Support Mailbox"
662 Enable support for Mailbox within SPL. This enable the inter
663 processor communication protocols tobe used within SPL. Enable
664 this option to build the drivers in drivers/mailbox as part of
670 select HAVE_BLOCK_DEVICE
672 Enable support for MMC (Multimedia Card) within SPL. This enables
673 the MMC protocol implementation and allows any enabled drivers to
674 be used within SPL. MMC can be used with or without disk partition
675 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
676 this option to build the drivers in drivers/mmc as part of an SPL
679 config SYS_MMCSD_FS_BOOT_PARTITION
680 int "MMC Boot Partition"
683 Partition on the MMC to load U-Boot from when the MMC is being
685 Use -1 as a special value to use the first bootable partition.
688 bool "Tiny MMC framework in SPL"
691 Enable MMC framework tinification support. This option is useful if
692 if your SPL is extremely size constrained. Heed the warning, enable
693 this option if and only if you know exactly what you are doing, if
694 you are reading this help text, you most likely have no idea :-)
696 The MMC framework is reduced to bare minimum to be useful. No malloc
697 support is needed for the MMC framework operation with this option
698 enabled. The framework supports exactly one MMC device and exactly
699 one MMC driver. The MMC driver can be adjusted to avoid any malloc
700 operations too, which can remove the need for malloc support in SPL
701 and thus further reduce footprint.
704 bool "MMC/SD/SDIO card support for write operations in SPL"
707 Enable write access to MMC and SD Cards in SPL
710 config SPL_MPC8XXX_INIT_DDR
711 bool "Support MPC8XXX DDR init"
713 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
714 random-access memory) on the MPC8XXX family within SPL. This
715 allows DRAM to be set up before loading U-Boot into that DRAM,
718 config SPL_MTD_SUPPORT
719 bool "Support MTD drivers"
721 Enable support for MTD (Memory Technology Device) within SPL. MTD
722 provides a block interface over raw NAND and can also be used with
723 SPI flash. This allows SPL to load U-Boot from supported MTD
724 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
725 to enable specific MTD drivers.
728 bool "Support new Mentor Graphics USB"
730 Enable support for Mentor Graphics USB in SPL. This is a new
731 driver used by some boards. Enable this option to build
732 the drivers in drivers/usb/musb-new as part of an SPL build. The
733 old drivers are in drivers/usb/musb.
735 config SPL_NAND_SUPPORT
736 bool "Support NAND flash"
738 Enable support for NAND (Negative AND) flash in SPL. NAND flash
739 can be used to allow SPL to load U-Boot from supported devices.
740 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
743 config SPL_NAND_DRIVERS
744 bool "Use standard NAND driver"
746 SPL uses normal NAND drivers, not minimal drivers.
749 bool "Include standard software ECC in the SPL"
751 config SPL_NAND_SIMPLE
752 bool "Support simple NAND drivers in SPL"
754 Support for NAND boot using simple NAND drivers that
755 expose the cmd_ctrl() interface.
758 depends on SPL_NAND_DRIVERS
759 bool "Use Base NAND Driver"
761 Include nand_base.c in the SPL.
763 config SPL_NAND_IDENT
764 depends on SPL_NAND_BASE
765 bool "Use chip ID to identify NAND flash"
767 SPL uses the chip ID list to identify the NAND flash.
772 Enable support for loading payloads from UBI. See
773 README.ubispl for more info.
777 bool "Support SPI DM drivers in SPL"
779 Enable support for SPI DM drivers in SPL.
781 config SPL_DM_SPI_FLASH
782 bool "Support SPI DM FLASH drivers in SPL"
784 Enable support for SPI DM flash drivers in SPL.
788 config SPL_UBI_LOAD_BY_VOLNAME
789 bool "Support loading volumes by name"
791 This enables support for loading UBI volumes by name. When this
792 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
793 configure the volume name from which to load U-Boot.
795 config SPL_UBI_MAX_VOL_LEBS
796 int "Maximum number of LEBs per volume"
799 The maximum number of logical eraseblocks which a static volume
800 to load can contain. Used for sizing the scan data structure.
802 config SPL_UBI_MAX_PEB_SIZE
803 int "Maximum PEB size"
806 The maximum physical erase block size.
808 config SPL_UBI_MAX_PEBS
809 int "Maximum number of PEBs"
812 The maximum physical erase block size. If not overridden by
813 board code, this value will be used as the actual number of PEBs.
815 config SPL_UBI_PEB_OFFSET
816 int "Offset to first UBI PEB"
819 The offset in number of PEBs from the start of flash to the first
820 PEB part of the UBI image.
822 config SPL_UBI_VID_OFFSET
823 int "Offset to VID header"
826 config SPL_UBI_LEB_START
827 int "Offset to LEB in PEB"
830 The offset in bytes to the LEB within a PEB.
832 config SPL_UBI_INFO_ADDR
833 hex "Address to place UBI scan info"
836 Address for ubispl to place the scan info. Read README.ubispl to
837 determine the required size
839 config SPL_UBI_VOL_IDS
840 int "Maximum volume id"
843 The maximum volume id which can be loaded. Used for sizing the
846 config SPL_UBI_LOAD_MONITOR_ID
847 int "id of U-Boot volume"
850 The UBI volume id from which to load U-Boot
852 config SPL_UBI_LOAD_MONITOR_VOLNAME
853 string "volume name of U-Boot volume"
854 depends on SPL_UBI_LOAD_BY_VOLNAME
856 The UBI volume name from which to load U-Boot
858 config SPL_UBI_LOAD_KERNEL_ID
859 int "id of kernel volume"
860 depends on SPL_OS_BOOT && SPL_UBI
862 The UBI volume id from which to load the kernel
864 config SPL_UBI_LOAD_ARGS_ID
865 int "id of kernel args volume"
866 depends on SPL_OS_BOOT && SPL_UBI
868 The UBI volume id from which to load the device tree
870 config UBI_SPL_SILENCE_MSG
871 bool "silence UBI SPL messages"
873 Disable messages from UBI SPL. This leaves warnings
879 bool "Support networking"
881 Enable support for network devices (such as Ethernet) in SPL.
882 This permits SPL to load U-Boot over a network link rather than
883 from an on-board peripheral. Environment support is required since
884 the network stack uses a number of environment variables. See also
888 config SPL_NET_VCI_STRING
889 string "BOOTP Vendor Class Identifier string sent by SPL"
891 As defined by RFC 2132 the vendor class identifier field can be
892 sent by the client to identify the vendor type and configuration
893 of a client. This is often used in practice to allow for the DHCP
894 server to specify different files to load depending on if the ROM,
895 SPL or U-Boot itself makes the request
898 config SPL_NO_CPU_SUPPORT
899 bool "Drop CPU code in SPL"
901 This is specific to the ARM926EJ-S CPU. It disables the standard
902 start.S start-up code, presumably so that a replacement can be
903 used on that CPU. You should not enable it unless you know what
906 config SPL_NOR_SUPPORT
907 bool "Support NOR flash"
909 Enable support for loading U-Boot from memory-mapped NOR (Negative
910 OR) flash in SPL. NOR flash is slow to write but fast to read, and
911 a memory-mapped device makes it very easy to access. Loading from
912 NOR is typically achieved with just a memcpy().
914 config SPL_XIP_SUPPORT
918 Enable support for execute in place of U-Boot or kernel image. There
919 is no need to copy image from flash to ram if flash supports execute
920 in place. Its very useful in systems having enough flash but not
921 enough ram to load the image.
923 config SPL_ONENAND_SUPPORT
924 bool "Support OneNAND flash"
926 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
927 a type of NAND flash and therefore can be used to allow SPL to
928 load U-Boot from supported devices. This enables the drivers in
929 drivers/mtd/onenand as part of an SPL build.
932 bool "Activate Falcon Mode"
933 depends on !TI_SECURE_DEVICE
935 Enable booting directly to an OS from SPL.
936 for more info read doc/README.falcon
940 hex "addr, where OS is found"
941 depends on SPL_NOR_SUPPORT
943 Specify the address, where the OS image is found, which
948 config SPL_FALCON_BOOT_MMCSD
949 bool "Enable Falcon boot from MMC or SD media"
950 depends on SPL_OS_BOOT && SPL_MMC
952 Select this if the Falcon mode OS image mode is on MMC or SD media.
954 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
955 hex "Falcon mode: Sector to load kernel uImage from MMC"
956 depends on SPL_FALCON_BOOT_MMCSD
958 When Falcon mode is used with an MMC or SD media, SPL needs to know
959 where to look for the kernel uImage. The image is expected to begin
960 at the raw MMC specified in this config.
961 Note that the Falcon mode image can also be a FIT, if FIT support is
966 default "tpl/u-boot-with-tpl.bin" if TPL
969 Payload for SPL boot. For backward compatibility, default to
970 u-boot.bin, i.e. RAW image without any header. In case of
971 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
975 bool "Support PCI drivers"
977 Enable support for PCI in SPL. For platforms that need PCI to boot,
978 or must perform some init using PCI in SPL, this provides the
979 necessary driver support. This enables the drivers in drivers/pci
980 as part of an SPL build.
983 bool "Support PCH drivers"
985 Enable support for PCH (Platform Controller Hub) devices in SPL.
986 These are used to set up GPIOs and the SPI peripheral early in
987 boot. This enables the drivers in drivers/pch as part of an SPL
990 config SPL_POST_MEM_SUPPORT
991 bool "Support POST drivers"
993 Enable support for POST (Power-on Self Test) in SPL. POST is a
994 procedure that checks that the hardware (CPU or board) appears to
995 be functionally correctly. It is a sanity check that can be
996 performed before booting. This enables the drivers in post/drivers
997 as part of an SPL build.
1000 bool "Support reset drivers"
1003 Enable support for reset control in SPL.
1004 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1005 by using the generic reset API provided by driver model.
1006 This enables the drivers in drivers/reset as part of an SPL build.
1009 bool "Support power drivers"
1011 Enable support for power control in SPL. This includes support
1012 for PMICs (Power-management Integrated Circuits) and some of the
1013 features provided by PMICs. In particular, voltage regulators can
1014 be used to enable/disable power and vary its voltage. That can be
1015 useful in SPL to turn on boot peripherals and adjust CPU voltage
1016 so that the clock speed can be increased. This enables the drivers
1017 in drivers/power, drivers/power/pmic and drivers/power/regulator
1018 as part of an SPL build.
1020 config SPL_POWER_DOMAIN
1021 bool "Support power domain drivers"
1024 Enable support for power domain control in SPL. Many SoCs allow
1025 power to be applied to or removed from portions of the SoC (power
1026 domains). This may be used to save power. This API provides the
1027 means to control such power management hardware. This enables
1028 the drivers in drivers/power/domain as part of a SPL build.
1030 config SPL_RAM_SUPPORT
1031 bool "Support booting from RAM"
1032 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1034 Enable booting of an image in RAM. The image can be preloaded or
1035 it can be loaded by SPL directly into RAM (e.g. using USB).
1037 config SPL_RAM_DEVICE
1038 bool "Support booting from preloaded image in RAM"
1039 depends on SPL_RAM_SUPPORT
1040 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1042 Enable booting of an image already loaded in RAM. The image has to
1043 be already in memory when SPL takes over, e.g. loaded by the boot
1046 config SPL_REMOTEPROC
1047 bool "Support REMOTEPROCS"
1049 Enable support for REMOTEPROCs in SPL. This permits to load
1050 a remote processor firmware in SPL.
1053 bool "Support RTC drivers"
1055 Enable RTC (Real-time Clock) support in SPL. This includes support
1056 for reading and setting the time. Some RTC devices also have some
1057 non-volatile (battery-backed) memory which is accessible if
1058 needed. This enables the drivers in drivers/rtc as part of an SPL
1062 bool "Support loading from SATA"
1064 Enable support for SATA (Serial AT attachment) in SPL. This allows
1065 use of SATA devices such as hard drives and flash drivers for
1066 loading U-Boot. SATA is used in higher-end embedded systems and
1067 can provide higher performance than MMC , at somewhat higher
1068 expense and power consumption. This enables loading from SATA
1069 using a configured device.
1071 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1072 bool "SATA raw mode: by sector"
1074 default y if ARCH_MVEBU
1076 Use sector number for specifying U-Boot location on SATA disk in
1079 config SPL_SATA_RAW_U_BOOT_SECTOR
1080 hex "Sector on the SATA disk to load U-Boot from"
1081 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1082 default 0x1 if ARCH_MVEBU
1084 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1085 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1088 bool "Support serial"
1092 Enable support for serial in SPL. This allows use of a serial UART
1093 for displaying messages while SPL is running. It also brings in
1094 printf() and panic() functions. This should normally be enabled
1095 unless there are space reasons not to. Even then, consider
1096 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1099 bool "Support SPI drivers"
1101 Enable support for using SPI in SPL. This is used for connecting
1102 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1103 more details on that. The SPI driver provides the transport for
1104 data between the SPI flash and the CPU. This option can be used to
1105 enable SPI drivers that are needed for other purposes also, such
1108 config SPL_SPI_FLASH_SUPPORT
1109 bool "Support SPI flash drivers"
1112 Enable support for using SPI flash in SPL, and loading U-Boot from
1113 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1114 the SPI bus that is used to connect it to a system. It is a simple
1115 but fast bidirectional 4-wire bus (clock, chip select and two data
1116 lines). This enables the drivers in drivers/mtd/spi as part of an
1117 SPL build. This normally requires SPL_SPI.
1119 if SPL_SPI_FLASH_SUPPORT
1121 config SPL_SPI_FLASH_TINY
1122 bool "Enable low footprint SPL SPI Flash support"
1123 depends on !SPI_FLASH_BAR
1124 default y if SPI_FLASH
1126 Enable lightweight SPL SPI Flash support that supports just reading
1127 data/images from flash. No support to write/erase flash. Enable
1128 this if you have SPL size limitations and don't need full
1129 fledged SPI flash support.
1131 config SPL_SPI_FLASH_SFDP_SUPPORT
1132 bool "SFDP table parsing support for SPI NOR flashes"
1133 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1135 Enable support for parsing and auto discovery of parameters for
1136 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1137 tables as per JESD216 standard in SPL.
1139 config SPL_SPI_FLASH_MTD
1140 bool "Support for SPI flash MTD drivers in SPL"
1142 Enable support for SPI flash MTD drivers in SPL.
1145 bool "Support loading from SPI flash"
1147 Enable support for loading next stage, U-Boot or otherwise, from
1148 SPI NOR in U-Boot SPL.
1150 endif # SPL_SPI_FLASH_SUPPORT
1152 config SYS_SPI_U_BOOT_OFFS
1153 hex "address of u-boot payload in SPI flash"
1154 default 0x8000 if ARCH_SUNXI
1156 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1158 Address within SPI-Flash from where the u-boot payload is fetched
1162 bool "Driver support for thermal devices"
1164 Enable support for temperature-sensing devices. Some SoCs have on-chip
1165 temperature sensors to permit warnings, speed throttling or even
1166 automatic power-off when the temperature gets too high or low. Other
1167 devices may be discrete but connected on a suitable bus.
1170 bool "Support USB host drivers"
1171 select HAVE_BLOCK_DEVICE
1173 Enable access to USB (Universal Serial Bus) host devices so that
1174 SPL can load U-Boot from a connected USB peripheral, such as a USB
1175 flash stick. While USB takes a little longer to start up than most
1176 buses, it is very flexible since many different types of storage
1177 device can be attached. This option enables the drivers in
1178 drivers/usb/host as part of an SPL build.
1180 config SPL_USB_STORAGE
1181 bool "Support loading from USB"
1182 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1184 Enable support for USB devices in SPL. This allows use of USB
1185 devices such as hard drives and flash drivers for loading U-Boot.
1186 The actual drivers are enabled separately using the normal U-Boot
1187 config options. This enables loading from USB using a configured
1190 config SPL_USB_GADGET
1191 bool "Suppport USB Gadget drivers"
1193 Enable USB Gadget API which allows to enable USB device functions
1198 config SPL_USB_ETHER
1199 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 and SPL_ETH.
1210 bool "Support DFU (Device Firmware Upgrade)"
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
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.
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
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_LOAD_IMAGE_V2
1280 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1283 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1285 If you want to load a bl31 image from the SPL and need the new
1288 config SPL_ATF_NO_PLATFORM_PARAM
1289 bool "Pass no platform parameter"
1292 While we expect to call a pointer to a valid FDT (or NULL)
1293 as the platform parameter to an ATF, some ATF versions are
1294 not U-Boot aware and have an insufficiently robust parameter
1295 validation to gracefully reject a FDT being passed.
1297 If this option is enabled, the spl_atf os-type handler will
1298 always pass NULL for the platform parameter.
1300 If your ATF is affected, say Y.
1302 config SPL_AM33XX_ENABLE_RTC32K_OSC
1303 bool "Enable the RTC32K OSC on AM33xx based platforms"
1306 Enable access to the AM33xx RTC and select the external 32kHz clock
1309 config SPL_OPTEE_IMAGE
1310 bool "Support OP-TEE Trusted OS image in SPL"
1313 OP-TEE is an open source Trusted OS which is loaded by SPL.
1314 More detail at: https://github.com/OP-TEE/optee_os
1317 bool "Support RISC-V OpenSBI"
1318 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1320 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1321 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1322 firmware. It is loaded and started by U-Boot SPL.
1324 More details are available at https://github.com/riscv/opensbi and
1325 https://github.com/riscv/riscv-sbi-doc
1327 config SPL_OPENSBI_LOAD_ADDR
1328 hex "OpenSBI load address"
1329 depends on SPL_OPENSBI
1331 Load address of the OpenSBI binary.
1335 depends on SUPPORT_TPL
1338 If you want to build TPL as well as the normal image and SPL, say Y.
1342 config TPL_SIZE_LIMIT
1343 hex "Maximum size of TPL image"
1347 Specifies the maximum length of the U-Boot TPL image.
1348 If this value is zero, it is ignored.
1350 config TPL_BINMAN_SYMBOLS
1351 bool "Declare binman symbols in TPL"
1352 depends on SPL_FRAMEWORK && BINMAN
1355 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1356 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1357 and spl_get_image_size().
1359 For this to work, you must have a U-Boot image in the binman image, so
1360 binman can update TPL with the location of it.
1362 config TPL_FRAMEWORK
1363 bool "Support TPL based upon the common SPL framework"
1364 default y if SPL_FRAMEWORK
1366 Enable the SPL framework under common/spl/ for TPL builds.
1367 This framework supports MMC, NAND and YMODEM and other methods
1368 loading of U-Boot's SPL stage. If unsure, say Y.
1371 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1372 depends on HANDOFF && TPL_BLOBLIST
1375 This option enables TPL to write handoff information. This can be
1376 used to pass information like the size of SDRAM from TPL to U-Boot
1377 proper. The information is also available to SPL if it is useful
1380 config TPL_BOARD_INIT
1381 bool "Call board-specific initialization in TPL"
1383 If this option is enabled, U-Boot will call the function
1384 spl_board_init() from board_init_r(). This function should be
1385 provided by the board.
1387 config TPL_BOOTCOUNT_LIMIT
1388 bool "Support bootcount in TPL"
1389 depends on TPL_ENV_SUPPORT
1391 If this option is enabled, the TPL will support bootcount.
1392 For example, it may be useful to choose the device to boot.
1395 string "Linker script for the TPL stage"
1397 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1398 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1400 The TPL stage will usually require a different linker-script
1401 (as it runs from a different memory region) than the regular
1402 U-Boot stage. Set this to the path of the linker-script to
1405 May be left empty to trigger the Makefile infrastructure to
1406 fall back to the linker-script used for the SPL stage.
1408 config TPL_NEEDS_SEPARATE_STACK
1409 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.
1416 bool "Support power drivers"
1418 Enable support for power control in TPL. This includes support
1419 for PMICs (Power-management Integrated Circuits) and some of the
1420 features provided by PMICs. In particular, voltage regulators can
1421 be used to enable/disable power and vary its voltage. That can be
1422 useful in TPL to turn on boot peripherals and adjust CPU voltage
1423 so that the clock speed can be increased. This enables the drivers
1424 in drivers/power, drivers/power/pmic and drivers/power/regulator
1425 as part of an TPL build.
1427 config TPL_TEXT_BASE
1428 hex "Base address for the .text section of the TPL stage"
1431 The base address for the .text section of the TPL stage.
1434 int "Maximum size (in bytes) for the TPL stage"
1438 The maximum size (in bytes) of the TPL stage.
1441 hex "Address of the initial stack-pointer for the TPL stage"
1442 depends on TPL_NEEDS_SEPARATE_STACK
1444 The address of the initial stack-pointer for the TPL stage.
1445 Usually this will be the (aligned) top-of-stack.
1447 config TPL_READ_ONLY
1449 depends on TPL_OF_PLATDATA
1450 select TPL_OF_PLATDATA_NO_BIND
1451 select TPL_OF_PLATDATA_RT
1453 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1454 section of memory. This means that of-platdata must make a copy (in
1455 writeable memory) of anything it wants to modify, such as
1456 device-private data.
1458 config TPL_BOOTROM_SUPPORT
1459 bool "Support returning to the BOOTROM (from TPL)"
1461 Some platforms (e.g. the Rockchip RK3368) provide support in their
1462 ROM for loading the next boot-stage after performing basic setup
1465 Enable this option, to return to the BOOTROM through the
1466 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1467 boot device list, if not implemented for a given board)
1470 bool "Support CRC32 in TPL"
1471 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1473 Enable this to support CRC32 in uImages or FIT images within SPL.
1474 This is a 32-bit checksum value that can be used to verify images.
1475 For FIT images, this is the least secure type of checksum, suitable
1476 for detected accidental image corruption. For secure applications you
1477 should consider SHA1 or SHA256.
1479 config TPL_DRIVERS_MISC
1480 bool "Support misc drivers in TPL"
1482 Enable miscellaneous drivers in TPL. These drivers perform various
1483 tasks that don't fall nicely into other categories, Enable this
1484 option to build the drivers in drivers/misc as part of an TPL
1485 build, for those that support building in TPL (not all drivers do).
1487 config TPL_ENV_SUPPORT
1488 bool "Support an environment"
1490 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1493 bool "Support GPIO in TPL"
1495 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1496 GPIOs allow U-Boot to read the state of an input line (high or
1497 low) and set the state of an output line. This can be used to
1498 drive LEDs, control power to various system parts and read user
1499 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1500 for example. Enable this option to build the drivers in
1501 drivers/gpio as part of an TPL build.
1506 Enable support for the I2C bus in TPL. See SPL_I2C for
1509 config TPL_LIBCOMMON_SUPPORT
1510 bool "Support common libraries"
1512 Enable support for common U-Boot libraries within TPL. See
1513 SPL_LIBCOMMON_SUPPORT for details.
1515 config TPL_LIBGENERIC_SUPPORT
1516 bool "Support generic libraries"
1518 Enable support for generic U-Boot libraries within TPL. See
1519 SPL_LIBGENERIC_SUPPORT for details.
1521 config TPL_MPC8XXX_INIT_DDR
1522 bool "Support MPC8XXX DDR init"
1524 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1525 SPL_MPC8XXX_INIT_DDR for details.
1531 Enable support for MMC within TPL. See SPL_MMC for details.
1533 config TPL_NAND_SUPPORT
1534 bool "Support NAND flash"
1536 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1539 bool "Support PCI drivers"
1541 Enable support for PCI in TPL. For platforms that need PCI to boot,
1542 or must perform some init using PCI in SPL, this provides the
1543 necessary driver support. This enables the drivers in drivers/pci
1544 as part of a TPL build.
1547 bool "Support PCH drivers"
1549 Enable support for PCH (Platform Controller Hub) devices in TPL.
1550 These are used to set up GPIOs and the SPI peripheral early in
1551 boot. This enables the drivers in drivers/pch as part of a TPL
1554 config TPL_RAM_SUPPORT
1555 bool "Support booting from RAM"
1557 Enable booting of an image in RAM. The image can be preloaded or
1558 it can be loaded by TPL directly into RAM (e.g. using USB).
1560 config TPL_RAM_DEVICE
1561 bool "Support booting from preloaded image in RAM"
1562 depends on TPL_RAM_SUPPORT
1564 Enable booting of an image already loaded in RAM. The image has to
1565 be already in memory when TPL takes over, e.g. loaded by the boot
1569 bool "Support RTC drivers"
1571 Enable RTC (Real-time Clock) support in TPL. This includes support
1572 for reading and setting the time. Some RTC devices also have some
1573 non-volatile (battery-backed) memory which is accessible if
1574 needed. This enables the drivers in drivers/rtc as part of an TPL
1578 bool "Support serial"
1582 Enable support for serial in TPL. See SPL_SERIAL for
1585 config TPL_SPI_FLASH_SUPPORT
1586 bool "Support SPI flash drivers"
1588 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1591 config TPL_SPI_FLASH_TINY
1592 bool "Enable low footprint TPL SPI Flash support"
1593 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1594 default y if SPI_FLASH
1596 Enable lightweight TPL SPI Flash support that supports just reading
1597 data/images from flash. No support to write/erase flash. Enable
1598 this if you have TPL size limitations and don't need full-fledged
1602 bool "Support loading from SPI flash"
1603 depends on TPL_SPI_FLASH_SUPPORT
1605 Enable support for loading next stage, U-Boot or otherwise, from
1606 SPI NOR in U-Boot TPL.
1609 bool "Support SPI drivers"
1611 Enable support for using SPI in TPL. See SPL_SPI for
1615 bool "Support SPI DM drivers in TPL"
1617 Enable support for SPI DM drivers in TPL.
1619 config TPL_DM_SPI_FLASH
1620 bool "Support SPI DM FLASH drivers in TPL"
1622 Enable support for SPI DM flash drivers in TPL.
1624 config TPL_YMODEM_SUPPORT
1625 bool "Support loading using Ymodem"
1626 depends on TPL_SERIAL
1628 While loading from serial is slow it can be a useful backup when
1629 there is no other option. The Ymodem protocol provides a reliable
1630 means of transmitting U-Boot over a serial line for using in TPL,
1631 with a checksum to ensure correctness.
1635 config SPL_AT91_MCK_BYPASS
1636 bool "Use external clock signal as a source of main clock for AT91 platforms"
1637 depends on ARCH_AT91
1639 Use external 8 to 24 Mhz clock signal as source of main clock instead
1640 of an external crystal oscillator.
1641 This option disables the internal driving on the XOUT pin.
1642 The external source has to provide a stable clock on the XIN pin.
1643 If this option is disabled, the SoC expects a crystal oscillator
1644 that needs driving on both XIN and XOUT lines.