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.
29 bool "Pass hand-off information from SPL to U-Boot proper"
32 It is useful to be able to pass information from SPL to U-Boot
33 proper to preserve state that is known in SPL and is needed in U-Boot.
34 Enable this to locate the handoff information in U-Boot proper, early
35 in boot. It is available in gd->handoff. The state state is set up
36 in SPL (or TPL if that is being used).
41 bool "Pass hand-off information from SPL to U-Boot proper"
45 This option enables SPL to write handoff information. This can be
46 used to pass information like the size of SDRAM from SPL to U-Boot
47 proper. Also SPL can receive information from TPL in the same place
51 string "Linker script for the SPL stage"
52 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
54 The SPL stage will usually require a different linker-script
55 (as it runs from a different memory region) than the regular
56 U-Boot stage. Set this to the path of the linker-script to
60 bool "Call board-specific initialization in SPL"
62 If this option is enabled, U-Boot will call the function
63 spl_board_init() from board_init_r(). This function should be
64 provided by the board.
66 config SPL_BOOTROM_SUPPORT
67 bool "Support returning to the BOOTROM"
69 Some platforms (e.g. the Rockchip RK3368) provide support in their
70 ROM for loading the next boot-stage after performing basic setup
73 Enable this option, to return to the BOOTROM through the
74 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
75 boot device list, if not implemented for a given board)
77 config SPL_BOOTCOUNT_LIMIT
78 bool "Support bootcount in SPL"
79 depends on SPL_ENV_SUPPORT
81 On some boards, which use 'falcon' mode, it is necessary to check
82 and increment the number of boot attempts. Such boards do not
83 use proper U-Boot for normal boot flow and hence needs those
84 adjustments to be done in the SPL.
86 config SPL_RAW_IMAGE_SUPPORT
87 bool "Support SPL loading and booting of RAW images"
88 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
89 default y if !TI_SECURE_DEVICE
91 SPL will support loading and booting a RAW image when this option
92 is y. If this is not set, SPL will move on to other available
93 boot media to find a suitable image.
95 config SPL_LEGACY_IMAGE_SUPPORT
96 bool "Support SPL loading and booting of Legacy images"
97 default y if !TI_SECURE_DEVICE
99 SPL will support loading and booting Legacy images when this option
100 is y. If this is not set, SPL will move on to other available
101 boot media to find a suitable image.
103 config SPL_SYS_MALLOC_SIMPLE
105 prompt "Only use malloc_simple functions in the SPL"
107 Say Y here to only use the *_simple malloc functions from
108 malloc_simple.c, rather then using the versions from dlmalloc.c;
109 this will make the SPL binary smaller at the cost of more heap
110 usage as the *_simple malloc functions do not re-use free-ed mem.
112 config TPL_SYS_MALLOC_SIMPLE
114 prompt "Only use malloc_simple functions in the TPL"
116 Say Y here to only use the *_simple malloc functions from
117 malloc_simple.c, rather then using the versions from dlmalloc.c;
118 this will make the TPL binary smaller at the cost of more heap
119 usage as the *_simple malloc functions do not re-use free-ed mem.
122 bool "Enable SDRAM location for SPL stack"
124 SPL starts off execution in SRAM and thus typically has only a small
125 stack available. Since SPL sets up DRAM while in its board_init_f()
126 function, it is possible for the stack to move there before
127 board_init_r() is reached. This option enables a special SDRAM
128 location for the SPL stack. U-Boot SPL switches to this after
129 board_init_f() completes, and before board_init_r() starts.
131 config SPL_STACK_R_ADDR
132 depends on SPL_STACK_R
133 hex "SDRAM location for SPL stack"
134 default 0x82000000 if ARCH_OMAP2PLUS
136 Specify the address in SDRAM for the SPL stack. This will be set up
137 before board_init_r() is called.
139 config SPL_STACK_R_MALLOC_SIMPLE_LEN
140 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
141 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
144 Specify the amount of the stack to use as memory pool for
145 malloc_simple after switching the stack to DRAM. This may be set
146 to give board_init_r() a larger heap then the initial heap in
147 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
149 config SPL_SEPARATE_BSS
150 bool "BSS section is in a different memory region from text"
152 Some platforms need a large BSS region in SPL and can provide this
153 because RAM is already set up. In this case BSS can be moved to RAM.
154 This option should then be enabled so that the correct device tree
155 location is used. Normally we put the device tree at the end of BSS
156 but with this option enabled, it goes at _image_binary_end.
158 config SPL_BANNER_PRINT
159 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
162 If this option is enabled, SPL will print the banner with version
163 info. Disabling this option could be useful to reduce TPL boot time
164 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
166 config TPL_BANNER_PRINT
167 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
170 If this option is enabled, SPL will not print the banner with version
171 info. Disabling this option could be useful to reduce SPL boot time
172 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
174 config SPL_DISPLAY_PRINT
175 bool "Display a board-specific message in SPL"
177 If this option is enabled, U-Boot will call the function
178 spl_display_print() immediately after displaying the SPL console
179 banner ("U-Boot SPL ..."). This function should be provided by
182 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
183 bool "MMC raw mode: by sector"
184 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
185 ARCH_MX6 || ARCH_MX7 || \
186 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
187 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
188 OMAP44XX || OMAP54XX || AM33XX || AM43XX
190 Use sector number for specifying U-Boot location on MMC/SD in
193 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
194 hex "Address on the MMC to load U-Boot from"
195 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
196 default 0x50 if ARCH_SUNXI
197 default 0x75 if ARCH_DAVINCI
198 default 0x8a if ARCH_MX6 || ARCH_MX7
199 default 0x100 if ARCH_UNIPHIER
200 default 0x140 if ARCH_MVEBU
201 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
202 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
203 OMAP54XX || AM33XX || AM43XX || ARCH_K3
204 default 0x4000 if ARCH_ROCKCHIP
206 Address on the MMC to load U-Boot from, when the MMC is being used
207 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
209 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
210 bool "MMC Raw mode: by partition"
212 Use a partition for loading U-Boot when using MMC/SD in raw mode.
214 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
215 hex "Partition to use to load U-Boot from"
216 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
219 Partition on the MMC to load U-Boot from when the MMC is being
222 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
223 bool "MMC raw mode: by partition type"
224 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
226 Use partition type for specifying U-Boot partition on MMC/SD in
227 raw mode. U-Boot will be loaded from the first partition of this
230 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
231 hex "Partition Type on the MMC to load U-Boot from"
232 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
234 Partition Type on the MMC to load U-Boot from, when the MMC is being
237 config SPL_CRC32_SUPPORT
241 Enable this to support CRC32 in FIT images within SPL. This is a
242 32-bit checksum value that can be used to verify images. This is
243 the least secure type of checksum, suitable for detected
244 accidental image corruption. For secure applications you should
245 consider SHA1 or SHA256.
247 config SPL_MD5_SUPPORT
251 Enable this to support MD5 in FIT images within SPL. An MD5
252 checksum is a 128-bit hash value used to check that the image
253 contents have not been corrupted. Note that MD5 is not considered
254 secure as it is possible (with a brute-force attack) to adjust the
255 image while still retaining the same MD5 hash value. For secure
256 applications where images may be changed maliciously, you should
257 consider SHA1 or SHA256.
259 config SPL_SHA1_SUPPORT
264 Enable this to support SHA1 in FIT images within SPL. A SHA1
265 checksum is a 160-bit (20-byte) hash value used to check that the
266 image contents have not been corrupted or maliciously altered.
267 While SHA1 is fairly secure it is coming to the end of its life
268 due to the expanding computing power avaiable to brute-force
269 attacks. For more security, consider SHA256.
271 config SPL_SHA256_SUPPORT
272 bool "Support SHA256"
276 Enable this to support SHA256 in FIT images within SPL. A SHA256
277 checksum is a 256-bit (32-byte) hash value used to check that the
278 image contents have not been corrupted. SHA256 is recommended for
279 use in secure applications since (as at 2016) there is no known
280 feasible attack that could produce a 'collision' with differing
281 input data. Use this for the highest security. Note that only the
282 SHA256 variant is supported: SHA512 and others are not currently
285 config SPL_FIT_IMAGE_TINY
286 bool "Remove functionality from SPL FIT loading to reduce size"
288 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
289 default y if ARCH_IMX8M
291 Enable this to reduce the size of the FIT image loading code
292 in SPL, if space for the SPL binary is very tight.
294 This removes the detection of image types (which forces the
295 first image to be treated as having a U-Boot style calling
296 convention) and skips the recording of each loaded payload
297 (i.e. loadable) into the FDT (modifying the loaded FDT to
298 ensure this information is available to the next image
301 config SPL_CPU_SUPPORT
302 bool "Support CPU drivers"
304 Enable this to support CPU drivers in SPL. These drivers can set
305 up CPUs and provide information about them such as the model and
306 name. This can be useful in SPL since setting up the CPUs earlier
307 may improve boot performance. Enable this option to build the
308 drivers in drivers/cpu as part of an SPL build.
310 config SPL_CRYPTO_SUPPORT
311 bool "Support crypto drivers"
313 Enable crypto drivers in SPL. These drivers can be used to
314 accelerate secure boot processing in secure applications. Enable
315 this option to build the drivers in drivers/crypto as part of an
318 config SPL_HASH_SUPPORT
319 bool "Support hashing drivers"
323 Enable hashing drivers in SPL. These drivers can be used to
324 accelerate secure boot processing in secure applications. Enable
325 this option to build system-specific drivers for hash acceleration
326 as part of an SPL build.
328 config TPL_HASH_SUPPORT
329 bool "Support hashing drivers in TPL"
333 Enable hashing drivers in SPL. These drivers can be used to
334 accelerate secure boot processing in secure applications. Enable
335 this option to build system-specific drivers for hash acceleration
336 as part of an SPL build.
338 config SPL_DMA_SUPPORT
339 bool "Support DMA drivers"
341 Enable DMA (direct-memory-access) drivers in SPL. These drivers
342 can be used to handle memory-to-peripheral data transfer without
343 the CPU moving the data. Enable this option to build the drivers
344 in drivers/dma as part of an SPL build.
346 config SPL_DRIVERS_MISC_SUPPORT
347 bool "Support misc drivers"
349 Enable miscellaneous drivers in SPL. These drivers perform various
350 tasks that don't fall nicely into other categories, Enable this
351 option to build the drivers in drivers/misc as part of an SPL
352 build, for those that support building in SPL (not all drivers do).
354 config SPL_ENV_SUPPORT
355 bool "Support an environment"
357 Enable environment support in SPL. The U-Boot environment provides
358 a number of settings (essentially name/value pairs) which can
359 control many aspects of U-Boot's operation. Normally this is not
360 needed in SPL as it has a much simpler task with less
361 configuration. But some boards use this to support 'Falcon' boot
362 on EXT2 and FAT, where SPL boots directly into Linux without
363 starting U-Boot first. Enabling this option will make env_get()
364 and env_set() available in SPL.
367 bool "Support save environment"
368 depends on SPL_ENV_SUPPORT
369 select SPL_MMC_WRITE if ENV_IS_IN_MMC
371 Enable save environment support in SPL after setenv. By default
372 the saveenv option is not provided in SPL, but some boards need
373 this support in 'Falcon' boot, where SPL need to boot from
374 different images based on environment variable set by OS. For
375 example OS may set "reboot_image" environment variable to
376 "recovery" inorder to boot recovery image by SPL. The SPL read
377 "reboot_image" and act accordingly and change the reboot_image
378 to default mode using setenv and save the environment.
380 config SPL_ETH_SUPPORT
381 bool "Support Ethernet"
382 depends on SPL_ENV_SUPPORT
384 Enable access to the network subsystem and associated Ethernet
385 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
386 link rather than from an on-board peripheral. Environment support
387 is required since the network stack uses a number of environment
388 variables. See also SPL_NET_SUPPORT.
391 bool "Support EXT filesystems"
393 Enable support for EXT2/3/4 filesystems with SPL. This permits
394 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
395 filesystem from within SPL. Support for the underlying block
396 device (e.g. MMC or USB) must be enabled separately.
399 bool "Support FAT filesystems"
402 Enable support for FAT and VFAT filesystems with SPL. This
403 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
404 filesystem from within SPL. Support for the underlying block
405 device (e.g. MMC or USB) must be enabled separately.
408 bool "Support write for FAT filesystems"
410 Enable write support for FAT and VFAT filesystems with SPL.
411 Support for the underlying block device (e.g. MMC or USB) must be
414 config SPL_FPGA_SUPPORT
417 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
418 provide software-configurable hardware which is typically used to
419 implement peripherals (such as UARTs, LCD displays, MMC) or
420 accelerate custom processing functions, such as image processing
421 or machine learning. Sometimes it is useful to program the FPGA
422 as early as possible during boot, and this option can enable that
425 config SPL_GPIO_SUPPORT
426 bool "Support GPIO in SPL"
428 Enable support for GPIOs (General-purpose Input/Output) in SPL.
429 GPIOs allow U-Boot to read the state of an input line (high or
430 low) and set the state of an output line. This can be used to
431 drive LEDs, control power to various system parts and read user
432 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
433 for example. Enable this option to build the drivers in
434 drivers/gpio as part of an SPL build.
436 config SPL_I2C_SUPPORT
439 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
440 I2C works with a clock and data line which can be driven by a
441 one or more masters or slaves. It is a fairly complex bus but is
442 widely used as it only needs two lines for communication. Speeds of
443 400kbps are typical but up to 3.4Mbps is supported by some
444 hardware. I2C can be useful in SPL to configure power management
445 ICs (PMICs) before raising the CPU clock speed, for example.
446 Enable this option to build the drivers in drivers/i2c as part of
449 config SPL_LIBCOMMON_SUPPORT
450 bool "Support common libraries"
452 Enable support for common U-Boot libraries within SPL. These
453 libraries include common code to deal with U-Boot images,
454 environment and USB, for example. This option is enabled on many
455 boards. Enable this option to build the code in common/ as part of
458 config SPL_LIBDISK_SUPPORT
459 bool "Support disk partitions"
462 Enable support for disk partitions within SPL. 'Disk' is something
463 of a misnomer as it includes non-spinning media such as flash (as
464 used in MMC and USB sticks). Partitions provide a way for a disk
465 to be split up into separate regions, with a partition table placed
466 at the start or end which describes the location and size of each
467 'partition'. These partitions are typically uses as individual block
468 devices, typically with an EXT2 or FAT filesystem in each. This
469 option enables whatever partition support has been enabled in
470 U-Boot to also be used in SPL. It brings in the code in disk/.
472 config SPL_LIBGENERIC_SUPPORT
473 bool "Support generic libraries"
475 Enable support for generic U-Boot libraries within SPL. These
476 libraries include generic code to deal with device tree, hashing,
477 printf(), compression and the like. This option is enabled on many
478 boards. Enable this option to build the code in lib/ as part of an
481 config SPL_DM_MAILBOX
482 bool "Support Mailbox"
484 Enable support for Mailbox within SPL. This enable the inter
485 processor communication protocols tobe used within SPL. Enable
486 this option to build the drivers in drivers/mailbox as part of
489 config SPL_MMC_SUPPORT
492 select HAVE_BLOCK_DEVICE
494 Enable support for MMC (Multimedia Card) within SPL. This enables
495 the MMC protocol implementation and allows any enabled drivers to
496 be used within SPL. MMC can be used with or without disk partition
497 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
498 this option to build the drivers in drivers/mmc as part of an SPL
502 bool "MMC/SD/SDIO card support for write operations in SPL"
503 depends on SPL_MMC_SUPPORT
506 Enable write access to MMC and SD Cards in SPL
509 config SPL_MPC8XXX_INIT_DDR_SUPPORT
510 bool "Support MPC8XXX DDR init"
512 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
513 random-access memory) on the MPC8XXX family within SPL. This
514 allows DRAM to be set up before loading U-Boot into that DRAM,
517 config SPL_MTD_SUPPORT
518 bool "Support MTD drivers"
520 Enable support for MTD (Memory Technology Device) within SPL. MTD
521 provides a block interface over raw NAND and can also be used with
522 SPI flash. This allows SPL to load U-Boot from supported MTD
523 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
524 to enable specific MTD drivers.
526 config SPL_MUSB_NEW_SUPPORT
527 bool "Support new Mentor Graphics USB"
529 Enable support for Mentor Graphics USB in SPL. This is a new
530 driver used by some boards. Enable this option to build
531 the drivers in drivers/usb/musb-new as part of an SPL build. The
532 old drivers are in drivers/usb/musb.
534 config SPL_NAND_SUPPORT
535 bool "Support NAND flash"
537 Enable support for NAND (Negative AND) flash in SPL. NAND flash
538 can be used to allow SPL to load U-Boot from supported devices.
539 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
542 config SPL_NET_SUPPORT
543 bool "Support networking"
545 Enable support for network devices (such as Ethernet) in SPL.
546 This permits SPL to load U-Boot over a network link rather than
547 from an on-board peripheral. Environment support is required since
548 the network stack uses a number of environment variables. See also
552 config SPL_NET_VCI_STRING
553 string "BOOTP Vendor Class Identifier string sent by SPL"
555 As defined by RFC 2132 the vendor class identifier field can be
556 sent by the client to identify the vendor type and configuration
557 of a client. This is often used in practice to allow for the DHCP
558 server to specify different files to load depending on if the ROM,
559 SPL or U-Boot itself makes the request
560 endif # if SPL_NET_SUPPORT
562 config SPL_NO_CPU_SUPPORT
563 bool "Drop CPU code in SPL"
565 This is specific to the ARM926EJ-S CPU. It disables the standard
566 start.S start-up code, presumably so that a replacement can be
567 used on that CPU. You should not enable it unless you know what
570 config SPL_NOR_SUPPORT
571 bool "Support NOR flash"
573 Enable support for loading U-Boot from memory-mapped NOR (Negative
574 OR) flash in SPL. NOR flash is slow to write but fast to read, and
575 a memory-mapped device makes it very easy to access. Loading from
576 NOR is typically achieved with just a memcpy().
578 config SPL_XIP_SUPPORT
582 Enable support for execute in place of U-Boot or kernel image. There
583 is no need to copy image from flash to ram if flash supports execute
584 in place. Its very useful in systems having enough flash but not
585 enough ram to load the image.
587 config SPL_ONENAND_SUPPORT
588 bool "Support OneNAND flash"
590 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
591 a type of NAND flash and therefore can be used to allow SPL to
592 load U-Boot from supported devices. This enables the drivers in
593 drivers/mtd/onenand as part of an SPL build.
596 bool "Activate Falcon Mode"
597 depends on !TI_SECURE_DEVICE
600 Enable booting directly to an OS from SPL.
601 for more info read doc/README.falcon
605 hex "addr, where OS is found"
606 depends on SPL_NOR_SUPPORT
608 Specify the address, where the OS image is found, which
615 default "tpl/u-boot-with-tpl.bin" if TPL
618 Payload for SPL boot. For backward compatibility, default to
619 u-boot.bin, i.e. RAW image without any header. In case of
620 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
624 bool "Support PCI drivers"
626 Enable support for PCI in SPL. For platforms that need PCI to boot,
627 or must perform some init using PCI in SPL, this provides the
628 necessary driver support. This enables the drivers in drivers/pci
629 as part of an SPL build.
631 config SPL_PCH_SUPPORT
632 bool "Support PCH drivers"
634 Enable support for PCH (Platform Controller Hub) devices in SPL.
635 These are used to set up GPIOs and the SPI peripheral early in
636 boot. This enables the drivers in drivers/pch as part of an SPL
639 config SPL_POST_MEM_SUPPORT
640 bool "Support POST drivers"
642 Enable support for POST (Power-on Self Test) in SPL. POST is a
643 procedure that checks that the hardware (CPU or board) appears to
644 be functionally correctly. It is a sanity check that can be
645 performed before booting. This enables the drivers in post/drivers
646 as part of an SPL build.
649 bool "Support reset drivers"
652 Enable support for reset control in SPL.
653 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
654 by using the generic reset API provided by driver model.
655 This enables the drivers in drivers/reset as part of an SPL build.
657 config SPL_POWER_SUPPORT
658 bool "Support power drivers"
660 Enable support for power control in SPL. This includes support
661 for PMICs (Power-management Integrated Circuits) and some of the
662 features provided by PMICs. In particular, voltage regulators can
663 be used to enable/disable power and vary its voltage. That can be
664 useful in SPL to turn on boot peripherals and adjust CPU voltage
665 so that the clock speed can be increased. This enables the drivers
666 in drivers/power, drivers/power/pmic and drivers/power/regulator
667 as part of an SPL build.
669 config SPL_POWER_DOMAIN
670 bool "Support power domain drivers"
672 Enable support for power domain control in SPL. Many SoCs allow
673 power to be applied to or removed from portions of the SoC (power
674 domains). This may be used to save power. This API provides the
675 means to control such power management hardware. This enables
676 the drivers in drivers/power/domain as part of a SPL build.
678 config SPL_RAM_SUPPORT
679 bool "Support booting from RAM"
680 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
682 Enable booting of an image in RAM. The image can be preloaded or
683 it can be loaded by SPL directly into RAM (e.g. using USB).
685 config SPL_RAM_DEVICE
686 bool "Support booting from preloaded image in RAM"
687 depends on SPL_RAM_SUPPORT
688 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
690 Enable booting of an image already loaded in RAM. The image has to
691 be already in memory when SPL takes over, e.g. loaded by the boot
694 config SPL_REMOTEPROC
695 bool "Support REMOTEPROCS"
697 Enable support for REMOTEPROCs in SPL. This permits to load
698 a remote processor firmware in SPL.
700 config SPL_RTC_SUPPORT
701 bool "Support RTC drivers"
703 Enable RTC (Real-time Clock) support in SPL. This includes support
704 for reading and setting the time. Some RTC devices also have some
705 non-volatile (battery-backed) memory which is accessible if
706 needed. This enables the drivers in drivers/rtc as part of an SPL
709 config SPL_SATA_SUPPORT
710 bool "Support loading from SATA"
712 Enable support for SATA (Serial AT attachment) in SPL. This allows
713 use of SATA devices such as hard drives and flash drivers for
714 loading U-Boot. SATA is used in higher-end embedded systems and
715 can provide higher performance than MMC , at somewhat higher
716 expense and power consumption. This enables loading from SATA
717 using a configured device.
719 config SPL_SERIAL_SUPPORT
720 bool "Support serial"
724 Enable support for serial in SPL. This allows use of a serial UART
725 for displaying messages while SPL is running. It also brings in
726 printf() and panic() functions. This should normally be enabled
727 unless there are space reasons not to. Even then, consider
728 enabling USE_TINY_PRINTF which is a small printf() version.
730 config SPL_SPI_FLASH_SUPPORT
731 bool "Support SPI flash drivers"
733 Enable support for using SPI flash in SPL, and loading U-Boot from
734 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
735 the SPI bus that is used to connect it to a system. It is a simple
736 but fast bidirectional 4-wire bus (clock, chip select and two data
737 lines). This enables the drivers in drivers/mtd/spi as part of an
738 SPL build. This normally requires SPL_SPI_SUPPORT.
741 bool "Support loading from SPI flash"
742 depends on SPL_SPI_FLASH_SUPPORT
744 Enable support for loading next stage, U-Boot or otherwise, from
745 SPI NOR in U-Boot SPL.
747 config SPL_SPI_SUPPORT
748 bool "Support SPI drivers"
750 Enable support for using SPI in SPL. This is used for connecting
751 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
752 more details on that. The SPI driver provides the transport for
753 data between the SPI flash and the CPU. This option can be used to
754 enable SPI drivers that are needed for other purposes also, such
758 bool "Driver support for thermal devices"
760 Enable support for temperature-sensing devices. Some SoCs have on-chip
761 temperature sensors to permit warnings, speed throttling or even
762 automatic power-off when the temperature gets too high or low. Other
763 devices may be discrete but connected on a suitable bus.
765 config SPL_USB_HOST_SUPPORT
766 bool "Support USB host drivers"
767 select HAVE_BLOCK_DEVICE
769 Enable access to USB (Universal Serial Bus) host devices so that
770 SPL can load U-Boot from a connected USB peripheral, such as a USB
771 flash stick. While USB takes a little longer to start up than most
772 buses, it is very flexible since many different types of storage
773 device can be attached. This option enables the drivers in
774 drivers/usb/host as part of an SPL build.
776 config SPL_USB_SUPPORT
777 bool "Support loading from USB"
778 depends on SPL_USB_HOST_SUPPORT
780 Enable support for USB devices in SPL. This allows use of USB
781 devices such as hard drives and flash drivers for loading U-Boot.
782 The actual drivers are enabled separately using the normal U-Boot
783 config options. This enables loading from USB using a configured
786 config SPL_USB_GADGET
787 bool "Suppport USB Gadget drivers"
789 Enable USB Gadget API which allows to enable USB device functions
795 bool "Support USB Ethernet drivers"
797 Enable access to the USB network subsystem and associated
798 drivers in SPL. This permits SPL to load U-Boot over a
799 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
800 than from an onboard peripheral. Environment support is required
801 since the network stack uses a number of environment variables.
802 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
805 bool "Support DFU (Device Firmware Upgrade)"
806 select SPL_HASH_SUPPORT
807 select SPL_DFU_NO_RESET
808 depends on SPL_RAM_SUPPORT
810 This feature enables the DFU (Device Firmware Upgrade) in SPL with
811 RAM memory device support. The ROM code will load and execute
812 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
813 selected device partition from host-pc using dfu-utils.
814 This feature is useful to flash the binaries to factory or bare-metal
815 boards using USB interface.
818 bool "DFU device selection"
823 depends on SPL_DFU && SPL_RAM_SUPPORT
825 select RAM/DDR memory device for loading binary images
826 (u-boot/kernel) to the selected device partition using
827 DFU and execute the u-boot/kernel from RAM.
831 config SPL_USB_SDP_SUPPORT
832 bool "Support SDP (Serial Download Protocol)"
834 Enable Serial Download Protocol (SDP) device support in SPL. This
835 allows to download images into memory and execute (jump to) them
836 using the same protocol as implemented by the i.MX family's boot ROM.
839 config SPL_WATCHDOG_SUPPORT
840 bool "Support watchdog drivers"
842 Enable support for watchdog drivers in SPL. A watchdog is
843 typically a hardware peripheral which can reset the system when it
844 detects no activity for a while (such as a software crash). This
845 enables the drivers in drivers/watchdog as part of an SPL build.
847 config SPL_YMODEM_SUPPORT
848 bool "Support loading using Ymodem"
849 depends on SPL_SERIAL_SUPPORT
851 While loading from serial is slow it can be a useful backup when
852 there is no other option. The Ymodem protocol provides a reliable
853 means of transmitting U-Boot over a serial line for using in SPL,
854 with a checksum to ensure correctness.
857 bool "Support ARM Trusted Firmware"
860 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
861 is loaded by SPL (which is considered as BL2 in ATF terminology).
862 More detail at: https://github.com/ARM-software/arm-trusted-firmware
864 config SPL_ATF_NO_PLATFORM_PARAM
865 bool "Pass no platform parameter"
868 While we expect to call a pointer to a valid FDT (or NULL)
869 as the platform parameter to an ATF, some ATF versions are
870 not U-Boot aware and have an insufficiently robust parameter
871 validation to gracefully reject a FDT being passed.
873 If this option is enabled, the spl_atf os-type handler will
874 always pass NULL for the platform parameter.
876 If your ATF is affected, say Y.
878 config SPL_AM33XX_ENABLE_RTC32K_OSC
879 bool "Enable the RTC32K OSC on AM33xx based platforms"
882 Enable access to the AM33xx RTC and select the external 32kHz clock
886 bool "Support OP-TEE Trusted OS"
889 OP-TEE is an open source Trusted OS which is loaded by SPL.
890 More detail at: https://github.com/OP-TEE/optee_os
894 depends on SUPPORT_TPL
897 If you want to build TPL as well as the normal image and SPL, say Y.
902 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
906 This option enables TPL to write handoff information. This can be
907 used to pass information like the size of SDRAM from TPL to U-Boot
908 proper. The information is also available to SPL if it is useful
911 config TPL_BOARD_INIT
912 bool "Call board-specific initialization in TPL"
914 If this option is enabled, U-Boot will call the function
915 spl_board_init() from board_init_r(). This function should be
916 provided by the board.
919 string "Linker script for the TPL stage"
921 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
922 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
924 The TPL stage will usually require a different linker-script
925 (as it runs from a different memory region) than the regular
926 U-Boot stage. Set this to the path of the linker-script to
929 May be left empty to trigger the Makefile infrastructure to
930 fall back to the linker-script used for the SPL stage.
932 config TPL_NEEDS_SEPARATE_TEXT_BASE
933 bool "TPL needs a separate text-base"
937 Enable, if the TPL stage should not inherit its text-base
938 from the SPL stage. When enabled, a base address for the
939 .text sections of the TPL stage has to be set below.
941 config TPL_NEEDS_SEPARATE_STACK
942 bool "TPL needs a separate initial stack-pointer"
946 Enable, if the TPL stage should not inherit its initial
947 stack-pointer from the settings for the SPL stage.
950 hex "Base address for the .text section of the TPL stage"
951 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
953 The base address for the .text section of the TPL stage.
956 int "Maximum size (in bytes) for the TPL stage"
960 The maximum size (in bytes) of the TPL stage.
963 hex "Address of the initial stack-pointer for the TPL stage"
964 depends on TPL_NEEDS_SEPARATE_STACK
966 The address of the initial stack-pointer for the TPL stage.
967 Usually this will be the (aligned) top-of-stack.
969 config TPL_BOOTROM_SUPPORT
970 bool "Support returning to the BOOTROM (from TPL)"
972 Some platforms (e.g. the Rockchip RK3368) provide support in their
973 ROM for loading the next boot-stage after performing basic setup
976 Enable this option, to return to the BOOTROM through the
977 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
978 boot device list, if not implemented for a given board)
980 config TPL_DRIVERS_MISC_SUPPORT
981 bool "Support misc drivers in TPL"
983 Enable miscellaneous drivers in TPL. These drivers perform various
984 tasks that don't fall nicely into other categories, Enable this
985 option to build the drivers in drivers/misc as part of an TPL
986 build, for those that support building in TPL (not all drivers do).
988 config TPL_ENV_SUPPORT
989 bool "Support an environment"
991 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
993 config TPL_GPIO_SUPPORT
994 bool "Support GPIO in TPL"
996 Enable support for GPIOs (General-purpose Input/Output) in TPL.
997 GPIOs allow U-Boot to read the state of an input line (high or
998 low) and set the state of an output line. This can be used to
999 drive LEDs, control power to various system parts and read user
1000 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1001 for example. Enable this option to build the drivers in
1002 drivers/gpio as part of an TPL build.
1004 config TPL_I2C_SUPPORT
1007 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1010 config TPL_LIBCOMMON_SUPPORT
1011 bool "Support common libraries"
1013 Enable support for common U-Boot libraries within TPL. See
1014 SPL_LIBCOMMON_SUPPORT for details.
1016 config TPL_LIBGENERIC_SUPPORT
1017 bool "Support generic libraries"
1019 Enable support for generic U-Boot libraries within TPL. See
1020 SPL_LIBGENERIC_SUPPORT for details.
1022 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1023 bool "Support MPC8XXX DDR init"
1025 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1026 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1028 config TPL_MMC_SUPPORT
1032 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1034 config TPL_NAND_SUPPORT
1035 bool "Support NAND flash"
1037 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1040 bool "Support PCI drivers"
1042 Enable support for PCI in TPL. For platforms that need PCI to boot,
1043 or must perform some init using PCI in SPL, this provides the
1044 necessary driver support. This enables the drivers in drivers/pci
1045 as part of a TPL build.
1047 config TPL_PCH_SUPPORT
1048 bool "Support PCH drivers"
1050 Enable support for PCH (Platform Controller Hub) devices in TPL.
1051 These are used to set up GPIOs and the SPI peripheral early in
1052 boot. This enables the drivers in drivers/pch as part of a TPL
1055 config TPL_RAM_SUPPORT
1056 bool "Support booting from RAM"
1058 Enable booting of an image in RAM. The image can be preloaded or
1059 it can be loaded by TPL directly into RAM (e.g. using USB).
1061 config TPL_RAM_DEVICE
1062 bool "Support booting from preloaded image in RAM"
1063 depends on TPL_RAM_SUPPORT
1065 Enable booting of an image already loaded in RAM. The image has to
1066 be already in memory when TPL takes over, e.g. loaded by the boot
1069 config TPL_RTC_SUPPORT
1070 bool "Support RTC drivers"
1072 Enable RTC (Real-time Clock) support in TPL. This includes support
1073 for reading and setting the time. Some RTC devices also have some
1074 non-volatile (battery-backed) memory which is accessible if
1075 needed. This enables the drivers in drivers/rtc as part of an TPL
1078 config TPL_SERIAL_SUPPORT
1079 bool "Support serial"
1083 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1086 config TPL_SPI_FLASH_SUPPORT
1087 bool "Support SPI flash drivers"
1089 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1093 bool "Support loading from SPI flash"
1094 depends on TPL_SPI_FLASH_SUPPORT
1096 Enable support for loading next stage, U-Boot or otherwise, from
1097 SPI NOR in U-Boot TPL.
1099 config TPL_SPI_SUPPORT
1100 bool "Support SPI drivers"
1102 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1105 config TPL_YMODEM_SUPPORT
1106 bool "Support loading using Ymodem"
1107 depends on TPL_SERIAL_SUPPORT
1109 While loading from serial is slow it can be a useful backup when
1110 there is no other option. The Ymodem protocol provides a reliable
1111 means of transmitting U-Boot over a serial line for using in TPL,
1112 with a checksum to ensure correctness.