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
290 Enable this to reduce the size of the FIT image loading code
291 in SPL, if space for the SPL binary is very tight.
293 This removes the detection of image types (which forces the
294 first image to be treated as having a U-Boot style calling
295 convention) and skips the recording of each loaded payload
296 (i.e. loadable) into the FDT (modifying the loaded FDT to
297 ensure this information is available to the next image
300 config SPL_CPU_SUPPORT
301 bool "Support CPU drivers"
303 Enable this to support CPU drivers in SPL. These drivers can set
304 up CPUs and provide information about them such as the model and
305 name. This can be useful in SPL since setting up the CPUs earlier
306 may improve boot performance. Enable this option to build the
307 drivers in drivers/cpu as part of an SPL build.
309 config SPL_CRYPTO_SUPPORT
310 bool "Support crypto drivers"
312 Enable crypto drivers in SPL. These drivers can be used to
313 accelerate secure boot processing in secure applications. Enable
314 this option to build the drivers in drivers/crypto as part of an
317 config SPL_HASH_SUPPORT
318 bool "Support hashing drivers"
322 Enable hashing drivers in SPL. These drivers can be used to
323 accelerate secure boot processing in secure applications. Enable
324 this option to build system-specific drivers for hash acceleration
325 as part of an SPL build.
327 config TPL_HASH_SUPPORT
328 bool "Support hashing drivers in TPL"
332 Enable hashing drivers in SPL. These drivers can be used to
333 accelerate secure boot processing in secure applications. Enable
334 this option to build system-specific drivers for hash acceleration
335 as part of an SPL build.
337 config SPL_DMA_SUPPORT
338 bool "Support DMA drivers"
340 Enable DMA (direct-memory-access) drivers in SPL. These drivers
341 can be used to handle memory-to-peripheral data transfer without
342 the CPU moving the data. Enable this option to build the drivers
343 in drivers/dma as part of an SPL build.
345 config SPL_DRIVERS_MISC_SUPPORT
346 bool "Support misc drivers"
348 Enable miscellaneous drivers in SPL. These drivers perform various
349 tasks that don't fall nicely into other categories, Enable this
350 option to build the drivers in drivers/misc as part of an SPL
351 build, for those that support building in SPL (not all drivers do).
353 config SPL_ENV_SUPPORT
354 bool "Support an environment"
356 Enable environment support in SPL. The U-Boot environment provides
357 a number of settings (essentially name/value pairs) which can
358 control many aspects of U-Boot's operation. Normally this is not
359 needed in SPL as it has a much simpler task with less
360 configuration. But some boards use this to support 'Falcon' boot
361 on EXT2 and FAT, where SPL boots directly into Linux without
362 starting U-Boot first. Enabling this option will make env_get()
363 and env_set() available in SPL.
366 bool "Support save environment"
367 depends on SPL_ENV_SUPPORT
368 select SPL_MMC_WRITE if ENV_IS_IN_MMC
370 Enable save environment support in SPL after setenv. By default
371 the saveenv option is not provided in SPL, but some boards need
372 this support in 'Falcon' boot, where SPL need to boot from
373 different images based on environment variable set by OS. For
374 example OS may set "reboot_image" environment variable to
375 "recovery" inorder to boot recovery image by SPL. The SPL read
376 "reboot_image" and act accordingly and change the reboot_image
377 to default mode using setenv and save the environment.
379 config SPL_ETH_SUPPORT
380 bool "Support Ethernet"
381 depends on SPL_ENV_SUPPORT
383 Enable access to the network subsystem and associated Ethernet
384 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
385 link rather than from an on-board peripheral. Environment support
386 is required since the network stack uses a number of environment
387 variables. See also SPL_NET_SUPPORT.
389 config SPL_EXT_SUPPORT
390 bool "Support EXT filesystems"
392 Enable support for EXT2/3/4 filesystems with SPL. This permits
393 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
394 filesystem from within SPL. Support for the underlying block
395 device (e.g. MMC or USB) must be enabled separately.
397 config SPL_FAT_SUPPORT
398 bool "Support FAT filesystems"
401 Enable support for FAT and VFAT filesystems with SPL. This
402 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
403 filesystem from within SPL. Support for the underlying block
404 device (e.g. MMC or USB) must be enabled separately.
406 config SPL_FPGA_SUPPORT
409 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
410 provide software-configurable hardware which is typically used to
411 implement peripherals (such as UARTs, LCD displays, MMC) or
412 accelerate custom processing functions, such as image processing
413 or machine learning. Sometimes it is useful to program the FPGA
414 as early as possible during boot, and this option can enable that
417 config SPL_GPIO_SUPPORT
418 bool "Support GPIO in SPL"
420 Enable support for GPIOs (General-purpose Input/Output) in SPL.
421 GPIOs allow U-Boot to read the state of an input line (high or
422 low) and set the state of an output line. This can be used to
423 drive LEDs, control power to various system parts and read user
424 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
425 for example. Enable this option to build the drivers in
426 drivers/gpio as part of an SPL build.
428 config SPL_I2C_SUPPORT
431 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
432 I2C works with a clock and data line which can be driven by a
433 one or more masters or slaves. It is a fairly complex bus but is
434 widely used as it only needs two lines for communication. Speeds of
435 400kbps are typical but up to 3.4Mbps is supported by some
436 hardware. I2C can be useful in SPL to configure power management
437 ICs (PMICs) before raising the CPU clock speed, for example.
438 Enable this option to build the drivers in drivers/i2c as part of
441 config SPL_LIBCOMMON_SUPPORT
442 bool "Support common libraries"
444 Enable support for common U-Boot libraries within SPL. These
445 libraries include common code to deal with U-Boot images,
446 environment and USB, for example. This option is enabled on many
447 boards. Enable this option to build the code in common/ as part of
450 config SPL_LIBDISK_SUPPORT
451 bool "Support disk partitions"
453 Enable support for disk partitions within SPL. 'Disk' is something
454 of a misnomer as it includes non-spinning media such as flash (as
455 used in MMC and USB sticks). Partitions provide a way for a disk
456 to be split up into separate regions, with a partition table placed
457 at the start or end which describes the location and size of each
458 'partition'. These partitions are typically uses as individual block
459 devices, typically with an EXT2 or FAT filesystem in each. This
460 option enables whatever partition support has been enabled in
461 U-Boot to also be used in SPL. It brings in the code in disk/.
463 config SPL_LIBGENERIC_SUPPORT
464 bool "Support generic libraries"
466 Enable support for generic U-Boot libraries within SPL. These
467 libraries include generic code to deal with device tree, hashing,
468 printf(), compression and the like. This option is enabled on many
469 boards. Enable this option to build the code in lib/ as part of an
472 config SPL_DM_MAILBOX
473 bool "Support Mailbox"
475 Enable support for Mailbox within SPL. This enable the inter
476 processor communication protocols tobe used within SPL. Enable
477 this option to build the drivers in drivers/mailbox as part of
480 config SPL_MMC_SUPPORT
484 Enable support for MMC (Multimedia Card) within SPL. This enables
485 the MMC protocol implementation and allows any enabled drivers to
486 be used within SPL. MMC can be used with or without disk partition
487 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
488 this option to build the drivers in drivers/mmc as part of an SPL
492 bool "MMC/SD/SDIO card support for write operations in SPL"
493 depends on SPL_MMC_SUPPORT
496 Enable write access to MMC and SD Cards in SPL
499 config SPL_MPC8XXX_INIT_DDR_SUPPORT
500 bool "Support MPC8XXX DDR init"
502 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
503 random-access memory) on the MPC8XXX family within SPL. This
504 allows DRAM to be set up before loading U-Boot into that DRAM,
507 config SPL_MTD_SUPPORT
508 bool "Support MTD drivers"
510 Enable support for MTD (Memory Technology Device) within SPL. MTD
511 provides a block interface over raw NAND and can also be used with
512 SPI flash. This allows SPL to load U-Boot from supported MTD
513 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
514 to enable specific MTD drivers.
516 config SPL_MUSB_NEW_SUPPORT
517 bool "Support new Mentor Graphics USB"
519 Enable support for Mentor Graphics USB in SPL. This is a new
520 driver used by some boards. Enable this option to build
521 the drivers in drivers/usb/musb-new as part of an SPL build. The
522 old drivers are in drivers/usb/musb.
524 config SPL_NAND_SUPPORT
525 bool "Support NAND flash"
527 Enable support for NAND (Negative AND) flash in SPL. NAND flash
528 can be used to allow SPL to load U-Boot from supported devices.
529 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
532 config SPL_NET_SUPPORT
533 bool "Support networking"
535 Enable support for network devices (such as Ethernet) in SPL.
536 This permits SPL to load U-Boot over a network link rather than
537 from an on-board peripheral. Environment support is required since
538 the network stack uses a number of environment variables. See also
542 config SPL_NET_VCI_STRING
543 string "BOOTP Vendor Class Identifier string sent by SPL"
545 As defined by RFC 2132 the vendor class identifier field can be
546 sent by the client to identify the vendor type and configuration
547 of a client. This is often used in practice to allow for the DHCP
548 server to specify different files to load depending on if the ROM,
549 SPL or U-Boot itself makes the request
550 endif # if SPL_NET_SUPPORT
552 config SPL_NO_CPU_SUPPORT
553 bool "Drop CPU code in SPL"
555 This is specific to the ARM926EJ-S CPU. It disables the standard
556 start.S start-up code, presumably so that a replacement can be
557 used on that CPU. You should not enable it unless you know what
560 config SPL_NOR_SUPPORT
561 bool "Support NOR flash"
563 Enable support for loading U-Boot from memory-mapped NOR (Negative
564 OR) flash in SPL. NOR flash is slow to write but fast to read, and
565 a memory-mapped device makes it very easy to access. Loading from
566 NOR is typically achieved with just a memcpy().
568 config SPL_XIP_SUPPORT
572 Enable support for execute in place of U-Boot or kernel image. There
573 is no need to copy image from flash to ram if flash supports execute
574 in place. Its very useful in systems having enough flash but not
575 enough ram to load the image.
577 config SPL_ONENAND_SUPPORT
578 bool "Support OneNAND flash"
580 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
581 a type of NAND flash and therefore can be used to allow SPL to
582 load U-Boot from supported devices. This enables the drivers in
583 drivers/mtd/onenand as part of an SPL build.
586 bool "Activate Falcon Mode"
587 depends on !TI_SECURE_DEVICE
590 Enable booting directly to an OS from SPL.
591 for more info read doc/README.falcon
595 hex "addr, where OS is found"
596 depends on SPL_NOR_SUPPORT
598 Specify the address, where the OS image is found, which
605 default "tpl/u-boot-with-tpl.bin" if TPL
608 Payload for SPL boot. For backward compability, default to
609 u-boot.bin, i.e. RAW image without any header. In case of
610 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
613 config SPL_PCI_SUPPORT
614 bool "Support PCI drivers"
616 Enable support for PCI in SPL. For platforms that need PCI to boot,
617 or must perform some init using PCI in SPL, this provides the
618 necessary driver support. This enables the drivers in drivers/pci
619 as part of an SPL build.
621 config SPL_PCH_SUPPORT
622 bool "Support PCH drivers"
624 Enable support for PCH (Platform Controller Hub) devices in SPL.
625 These are used to set up GPIOs and the SPI peripheral early in
626 boot. This enables the drivers in drivers/pch as part of an SPL
629 config SPL_POST_MEM_SUPPORT
630 bool "Support POST drivers"
632 Enable support for POST (Power-on Self Test) in SPL. POST is a
633 procedure that checks that the hardware (CPU or board) appears to
634 be functionally correctly. It is a sanity check that can be
635 performed before booting. This enables the drivers in post/drivers
636 as part of an SPL build.
639 bool "Support reset drivers"
642 Enable support for reset control in SPL.
643 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
644 by using the generic reset API provided by driver model.
645 This enables the drivers in drivers/reset as part of an SPL build.
647 config SPL_POWER_SUPPORT
648 bool "Support power drivers"
650 Enable support for power control in SPL. This includes support
651 for PMICs (Power-management Integrated Circuits) and some of the
652 features provided by PMICs. In particular, voltage regulators can
653 be used to enable/disable power and vary its voltage. That can be
654 useful in SPL to turn on boot peripherals and adjust CPU voltage
655 so that the clock speed can be increased. This enables the drivers
656 in drivers/power, drivers/power/pmic and drivers/power/regulator
657 as part of an SPL build.
659 config SPL_POWER_DOMAIN
660 bool "Support power domain drivers"
662 Enable support for power domain control in SPL. Many SoCs allow
663 power to be applied to or removed from portions of the SoC (power
664 domains). This may be used to save power. This API provides the
665 means to control such power management hardware. This enables
666 the drivers in drivers/power/domain as part of a SPL build.
668 config SPL_RAM_SUPPORT
669 bool "Support booting from RAM"
670 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
672 Enable booting of an image in RAM. The image can be preloaded or
673 it can be loaded by SPL directly into RAM (e.g. using USB).
675 config SPL_RAM_DEVICE
676 bool "Support booting from preloaded image in RAM"
677 depends on SPL_RAM_SUPPORT
678 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
680 Enable booting of an image already loaded in RAM. The image has to
681 be already in memory when SPL takes over, e.g. loaded by the boot
684 config SPL_REMOTEPROC
685 bool "Support REMOTEPROCS"
687 Enable support for REMOTEPROCs in SPL. This permits to load
688 a remote processor firmware in SPL.
690 config SPL_RTC_SUPPORT
691 bool "Support RTC drivers"
693 Enable RTC (Real-time Clock) support in SPL. This includes support
694 for reading and setting the time. Some RTC devices also have some
695 non-volatile (battery-backed) memory which is accessible if
696 needed. This enables the drivers in drivers/rtc as part of an SPL
699 config SPL_SATA_SUPPORT
700 bool "Support loading from SATA"
702 Enable support for SATA (Serial AT attachment) in SPL. This allows
703 use of SATA devices such as hard drives and flash drivers for
704 loading U-Boot. SATA is used in higher-end embedded systems and
705 can provide higher performance than MMC , at somewhat higher
706 expense and power consumption. This enables loading from SATA
707 using a configured device.
709 config SPL_SERIAL_SUPPORT
710 bool "Support serial"
714 Enable support for serial in SPL. This allows use of a serial UART
715 for displaying messages while SPL is running. It also brings in
716 printf() and panic() functions. This should normally be enabled
717 unless there are space reasons not to. Even then, consider
718 enabling USE_TINY_PRINTF which is a small printf() version.
720 config SPL_SPI_FLASH_SUPPORT
721 bool "Support SPI flash drivers"
723 Enable support for using SPI flash in SPL, and loading U-Boot from
724 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
725 the SPI bus that is used to connect it to a system. It is a simple
726 but fast bidirectional 4-wire bus (clock, chip select and two data
727 lines). This enables the drivers in drivers/mtd/spi as part of an
728 SPL build. This normally requires SPL_SPI_SUPPORT.
731 bool "Support loading from SPI flash"
732 depends on SPL_SPI_FLASH_SUPPORT
734 Enable support for loading next stage, U-Boot or otherwise, from
735 SPI NOR in U-Boot SPL.
737 config SPL_SPI_SUPPORT
738 bool "Support SPI drivers"
740 Enable support for using SPI in SPL. This is used for connecting
741 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
742 more details on that. The SPI driver provides the transport for
743 data between the SPI flash and the CPU. This option can be used to
744 enable SPI drivers that are needed for other purposes also, such
748 bool "Driver support for thermal devices"
750 Enable support for temperature-sensing devices. Some SoCs have on-chip
751 temperature sensors to permit warnings, speed throttling or even
752 automatic power-off when the temperature gets too high or low. Other
753 devices may be discrete but connected on a suitable bus.
755 config SPL_USB_HOST_SUPPORT
756 bool "Support USB host drivers"
758 Enable access to USB (Universal Serial Bus) host devices so that
759 SPL can load U-Boot from a connected USB peripheral, such as a USB
760 flash stick. While USB takes a little longer to start up than most
761 buses, it is very flexible since many different types of storage
762 device can be attached. This option enables the drivers in
763 drivers/usb/host as part of an SPL build.
765 config SPL_USB_SUPPORT
766 bool "Support loading from USB"
767 depends on SPL_USB_HOST_SUPPORT
769 Enable support for USB devices in SPL. This allows use of USB
770 devices such as hard drives and flash drivers for loading U-Boot.
771 The actual drivers are enabled separately using the normal U-Boot
772 config options. This enables loading from USB using a configured
775 config SPL_USB_GADGET_SUPPORT
776 bool "Suppport USB Gadget drivers"
778 Enable USB Gadget API which allows to enable USB device functions
781 if SPL_USB_GADGET_SUPPORT
784 bool "Support USB Ethernet drivers"
786 Enable access to the USB network subsystem and associated
787 drivers in SPL. This permits SPL to load U-Boot over a
788 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
789 than from an onboard peripheral. Environment support is required
790 since the network stack uses a number of environment variables.
791 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
793 config SPL_DFU_SUPPORT
794 bool "Support DFU (Device Firmware Upgrade)"
795 select SPL_HASH_SUPPORT
796 select SPL_DFU_NO_RESET
797 depends on SPL_RAM_SUPPORT
799 This feature enables the DFU (Device Firmware Upgrade) in SPL with
800 RAM memory device support. The ROM code will load and execute
801 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
802 selected device partition from host-pc using dfu-utils.
803 This feature is useful to flash the binaries to factory or bare-metal
804 boards using USB interface.
807 bool "DFU device selection"
808 depends on SPL_DFU_SUPPORT
812 depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
814 select RAM/DDR memory device for loading binary images
815 (u-boot/kernel) to the selected device partition using
816 DFU and execute the u-boot/kernel from RAM.
820 config SPL_USB_SDP_SUPPORT
821 bool "Support SDP (Serial Download Protocol)"
823 Enable Serial Download Protocol (SDP) device support in SPL. This
824 allows to download images into memory and execute (jump to) them
825 using the same protocol as implemented by the i.MX family's boot ROM.
828 config SPL_WATCHDOG_SUPPORT
829 bool "Support watchdog drivers"
831 Enable support for watchdog drivers in SPL. A watchdog is
832 typically a hardware peripheral which can reset the system when it
833 detects no activity for a while (such as a software crash). This
834 enables the drivers in drivers/watchdog as part of an SPL build.
836 config SPL_YMODEM_SUPPORT
837 bool "Support loading using Ymodem"
838 depends on SPL_SERIAL_SUPPORT
840 While loading from serial is slow it can be a useful backup when
841 there is no other option. The Ymodem protocol provides a reliable
842 means of transmitting U-Boot over a serial line for using in SPL,
843 with a checksum to ensure correctness.
846 bool "Support ARM Trusted Firmware"
849 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
850 is loaded by SPL (which is considered as BL2 in ATF terminology).
851 More detail at: https://github.com/ARM-software/arm-trusted-firmware
853 config SPL_ATF_NO_PLATFORM_PARAM
854 bool "Pass no platform parameter"
857 While we expect to call a pointer to a valid FDT (or NULL)
858 as the platform parameter to an ATF, some ATF versions are
859 not U-Boot aware and have an insufficiently robust parameter
860 validation to gracefully reject a FDT being passed.
862 If this option is enabled, the spl_atf os-type handler will
863 always pass NULL for the platform parameter.
865 If your ATF is affected, say Y.
867 config SPL_AM33XX_ENABLE_RTC32K_OSC
868 bool "Enable the RTC32K OSC on AM33xx based platforms"
871 Enable access to the AM33xx RTC and select the external 32kHz clock
875 bool "Support OP-TEE Trusted OS"
878 OP-TEE is an open source Trusted OS which is loaded by SPL.
879 More detail at: https://github.com/OP-TEE/optee_os
883 depends on SUPPORT_TPL
886 If you want to build TPL as well as the normal image and SPL, say Y.
891 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
895 This option enables TPL to write handoff information. This can be
896 used to pass information like the size of SDRAM from TPL to U-Boot
897 proper. The information is also available to SPL if it is useful
900 config TPL_BOARD_INIT
901 bool "Call board-specific initialization in TPL"
903 If this option is enabled, U-Boot will call the function
904 spl_board_init() from board_init_r(). This function should be
905 provided by the board.
908 string "Linker script for the TPL stage"
911 The TPL stage will usually require a different linker-script
912 (as it runs from a different memory region) than the regular
913 U-Boot stage. Set this to the path of the linker-script to
916 May be left empty to trigger the Makefile infrastructure to
917 fall back to the linker-script used for the SPL stage.
919 config TPL_NEEDS_SEPARATE_TEXT_BASE
920 bool "TPL needs a separate text-base"
924 Enable, if the TPL stage should not inherit its text-base
925 from the SPL stage. When enabled, a base address for the
926 .text sections of the TPL stage has to be set below.
928 config TPL_NEEDS_SEPARATE_STACK
929 bool "TPL needs a separate initial stack-pointer"
933 Enable, if the TPL stage should not inherit its initial
934 stack-pointer from the settings for the SPL stage.
937 hex "Base address for the .text section of the TPL stage"
938 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
940 The base address for the .text section of the TPL stage.
943 int "Maximum size (in bytes) for the TPL stage"
947 The maximum size (in bytes) of the TPL stage.
950 hex "Address of the initial stack-pointer for the TPL stage"
951 depends on TPL_NEEDS_SEPARATE_STACK
953 The address of the initial stack-pointer for the TPL stage.
954 Usually this will be the (aligned) top-of-stack.
956 config TPL_BOOTROM_SUPPORT
957 bool "Support returning to the BOOTROM (from TPL)"
959 Some platforms (e.g. the Rockchip RK3368) provide support in their
960 ROM for loading the next boot-stage after performing basic setup
963 Enable this option, to return to the BOOTROM through the
964 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
965 boot device list, if not implemented for a given board)
967 config TPL_DRIVERS_MISC_SUPPORT
968 bool "Support misc drivers in TPL"
970 Enable miscellaneous drivers in TPL. These drivers perform various
971 tasks that don't fall nicely into other categories, Enable this
972 option to build the drivers in drivers/misc as part of an TPL
973 build, for those that support building in TPL (not all drivers do).
975 config TPL_ENV_SUPPORT
976 bool "Support an environment"
978 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
980 config TPL_GPIO_SUPPORT
981 bool "Support GPIO in TPL"
983 Enable support for GPIOs (General-purpose Input/Output) in TPL.
984 GPIOs allow U-Boot to read the state of an input line (high or
985 low) and set the state of an output line. This can be used to
986 drive LEDs, control power to various system parts and read user
987 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
988 for example. Enable this option to build the drivers in
989 drivers/gpio as part of an TPL build.
991 config TPL_I2C_SUPPORT
994 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
997 config TPL_LIBCOMMON_SUPPORT
998 bool "Support common libraries"
1000 Enable support for common U-Boot libraries within TPL. See
1001 SPL_LIBCOMMON_SUPPORT for details.
1003 config TPL_LIBGENERIC_SUPPORT
1004 bool "Support generic libraries"
1006 Enable support for generic U-Boot libraries within TPL. See
1007 SPL_LIBGENERIC_SUPPORT for details.
1009 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1010 bool "Support MPC8XXX DDR init"
1012 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1013 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1015 config TPL_MMC_SUPPORT
1019 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1021 config TPL_NAND_SUPPORT
1022 bool "Support NAND flash"
1024 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1026 config TPL_PCI_SUPPORT
1027 bool "Support PCI drivers"
1029 Enable support for PCI in TPL. For platforms that need PCI to boot,
1030 or must perform some init using PCI in SPL, this provides the
1031 necessary driver support. This enables the drivers in drivers/pci
1032 as part of a TPL build.
1034 config TPL_PCH_SUPPORT
1035 bool "Support PCH drivers"
1037 Enable support for PCH (Platform Controller Hub) devices in TPL.
1038 These are used to set up GPIOs and the SPI peripheral early in
1039 boot. This enables the drivers in drivers/pch as part of a TPL
1042 config TPL_RAM_SUPPORT
1043 bool "Support booting from RAM"
1045 Enable booting of an image in RAM. The image can be preloaded or
1046 it can be loaded by TPL directly into RAM (e.g. using USB).
1048 config TPL_RAM_DEVICE
1049 bool "Support booting from preloaded image in RAM"
1050 depends on TPL_RAM_SUPPORT
1052 Enable booting of an image already loaded in RAM. The image has to
1053 be already in memory when TPL takes over, e.g. loaded by the boot
1056 config TPL_RTC_SUPPORT
1057 bool "Support RTC drivers"
1059 Enable RTC (Real-time Clock) support in TPL. This includes support
1060 for reading and setting the time. Some RTC devices also have some
1061 non-volatile (battery-backed) memory which is accessible if
1062 needed. This enables the drivers in drivers/rtc as part of an TPL
1065 config TPL_SERIAL_SUPPORT
1066 bool "Support serial"
1070 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1073 config TPL_SPI_FLASH_SUPPORT
1074 bool "Support SPI flash drivers"
1076 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1080 bool "Support loading from SPI flash"
1081 depends on TPL_SPI_FLASH_SUPPORT
1083 Enable support for loading next stage, U-Boot or otherwise, from
1084 SPI NOR in U-Boot TPL.
1086 config TPL_SPI_SUPPORT
1087 bool "Support SPI drivers"
1089 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1092 config TPL_YMODEM_SUPPORT
1093 bool "Support loading using Ymodem"
1094 depends on TPL_SERIAL_SUPPORT
1096 While loading from serial is slow it can be a useful backup when
1097 there is no other option. The Ymodem protocol provides a reliable
1098 means of transmitting U-Boot over a serial line for using in TPL,
1099 with a checksum to ensure correctness.