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.
31 string "Linker script for the SPL stage"
32 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
34 The SPL stage will usually require a different linker-script
35 (as it runs from a different memory region) than the regular
36 U-Boot stage. Set this to the path of the linker-script to
40 bool "Call board-specific initialization in SPL"
42 If this option is enabled, U-Boot will call the function
43 spl_board_init() from board_init_r(). This function should be
44 provided by the board.
46 config SPL_BOOTROM_SUPPORT
47 bool "Support returning to the BOOTROM"
49 Some platforms (e.g. the Rockchip RK3368) provide support in their
50 ROM for loading the next boot-stage after performing basic setup
53 Enable this option, to return to the BOOTROM through the
54 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
55 boot device list, if not implemented for a given board)
57 config SPL_BOOTCOUNT_LIMIT
58 bool "Support bootcount in SPL"
59 depends on SPL_ENV_SUPPORT
61 On some boards, which use 'falcon' mode, it is necessary to check
62 and increment the number of boot attempts. Such boards do not
63 use proper U-Boot for normal boot flow and hence needs those
64 adjustments to be done in the SPL.
66 config SPL_RAW_IMAGE_SUPPORT
67 bool "Support SPL loading and booting of RAW images"
68 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
69 default y if !TI_SECURE_DEVICE
71 SPL will support loading and booting a RAW image when this option
72 is y. If this is not set, SPL will move on to other available
73 boot media to find a suitable image.
75 config SPL_LEGACY_IMAGE_SUPPORT
76 bool "Support SPL loading and booting of Legacy images"
77 default y if !TI_SECURE_DEVICE
79 SPL will support loading and booting Legacy images when this option
80 is y. If this is not set, SPL will move on to other available
81 boot media to find a suitable image.
83 config SPL_SYS_MALLOC_SIMPLE
85 prompt "Only use malloc_simple functions in the SPL"
87 Say Y here to only use the *_simple malloc functions from
88 malloc_simple.c, rather then using the versions from dlmalloc.c;
89 this will make the SPL binary smaller at the cost of more heap
90 usage as the *_simple malloc functions do not re-use free-ed mem.
92 config TPL_SYS_MALLOC_SIMPLE
94 prompt "Only use malloc_simple functions in the TPL"
96 Say Y here to only use the *_simple malloc functions from
97 malloc_simple.c, rather then using the versions from dlmalloc.c;
98 this will make the TPL binary smaller at the cost of more heap
99 usage as the *_simple malloc functions do not re-use free-ed mem.
102 bool "Enable SDRAM location for SPL stack"
104 SPL starts off execution in SRAM and thus typically has only a small
105 stack available. Since SPL sets up DRAM while in its board_init_f()
106 function, it is possible for the stack to move there before
107 board_init_r() is reached. This option enables a special SDRAM
108 location for the SPL stack. U-Boot SPL switches to this after
109 board_init_f() completes, and before board_init_r() starts.
111 config SPL_STACK_R_ADDR
112 depends on SPL_STACK_R
113 hex "SDRAM location for SPL stack"
114 default 0x82000000 if ARCH_OMAP2PLUS
116 Specify the address in SDRAM for the SPL stack. This will be set up
117 before board_init_r() is called.
119 config SPL_STACK_R_MALLOC_SIMPLE_LEN
120 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
121 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
124 Specify the amount of the stack to use as memory pool for
125 malloc_simple after switching the stack to DRAM. This may be set
126 to give board_init_r() a larger heap then the initial heap in
127 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
129 config SPL_SEPARATE_BSS
130 bool "BSS section is in a different memory region from text"
132 Some platforms need a large BSS region in SPL and can provide this
133 because RAM is already set up. In this case BSS can be moved to RAM.
134 This option should then be enabled so that the correct device tree
135 location is used. Normally we put the device tree at the end of BSS
136 but with this option enabled, it goes at _image_binary_end.
138 config SPL_DISABLE_BANNER_PRINT
139 bool "Disable output of the SPL banner 'U-Boot SPL ...'"
141 If this option is enabled, SPL will not print the banner with version
142 info. Selecting this option could be useful to reduce SPL boot time
143 (e.g. approx. 6 ms slower, when output on i.MX6 with 115200 baud).
145 config SPL_DISPLAY_PRINT
146 bool "Display a board-specific message in SPL"
148 If this option is enabled, U-Boot will call the function
149 spl_display_print() immediately after displaying the SPL console
150 banner ("U-Boot SPL ..."). This function should be provided by
153 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
154 bool "MMC raw mode: by sector"
155 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
156 ARCH_MX6 || ARCH_MX7 || \
157 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
158 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
159 OMAP44XX || OMAP54XX || AM33XX || AM43XX
161 Use sector number for specifying U-Boot location on MMC/SD in
164 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
165 hex "Address on the MMC to load U-Boot from"
166 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
167 default 0x50 if ARCH_SUNXI
168 default 0x75 if ARCH_DAVINCI
169 default 0x8a if ARCH_MX6 || ARCH_MX7
170 default 0x100 if ARCH_UNIPHIER
171 default 0x140 if ARCH_MVEBU
172 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
173 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
174 OMAP54XX || AM33XX || AM43XX || ARCH_K3
175 default 0x4000 if ARCH_ROCKCHIP
177 Address on the MMC to load U-Boot from, when the MMC is being used
178 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
180 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
181 bool "MMC Raw mode: by partition"
183 Use a partition for loading U-Boot when using MMC/SD in raw mode.
185 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
186 hex "Partition to use to load U-Boot from"
187 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
190 Partition on the MMC to load U-Boot from when the MMC is being
193 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
194 bool "MMC raw mode: by partition type"
195 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
197 Use partition type for specifying U-Boot partition on MMC/SD in
198 raw mode. U-Boot will be loaded from the first partition of this
201 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
202 hex "Partition Type on the MMC to load U-Boot from"
203 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
205 Partition Type on the MMC to load U-Boot from, when the MMC is being
208 config SPL_CRC32_SUPPORT
212 Enable this to support CRC32 in FIT images within SPL. This is a
213 32-bit checksum value that can be used to verify images. This is
214 the least secure type of checksum, suitable for detected
215 accidental image corruption. For secure applications you should
216 consider SHA1 or SHA256.
218 config SPL_MD5_SUPPORT
222 Enable this to support MD5 in FIT images within SPL. An MD5
223 checksum is a 128-bit hash value used to check that the image
224 contents have not been corrupted. Note that MD5 is not considered
225 secure as it is possible (with a brute-force attack) to adjust the
226 image while still retaining the same MD5 hash value. For secure
227 applications where images may be changed maliciously, you should
228 consider SHA1 or SHA256.
230 config SPL_SHA1_SUPPORT
235 Enable this to support SHA1 in FIT images within SPL. A SHA1
236 checksum is a 160-bit (20-byte) hash value used to check that the
237 image contents have not been corrupted or maliciously altered.
238 While SHA1 is fairly secure it is coming to the end of its life
239 due to the expanding computing power avaiable to brute-force
240 attacks. For more security, consider SHA256.
242 config SPL_SHA256_SUPPORT
243 bool "Support SHA256"
247 Enable this to support SHA256 in FIT images within SPL. A SHA256
248 checksum is a 256-bit (32-byte) hash value used to check that the
249 image contents have not been corrupted. SHA256 is recommended for
250 use in secure applications since (as at 2016) there is no known
251 feasible attack that could produce a 'collision' with differing
252 input data. Use this for the highest security. Note that only the
253 SHA256 variant is supported: SHA512 and others are not currently
256 config SPL_FIT_IMAGE_TINY
257 bool "Remove functionality from SPL FIT loading to reduce size"
259 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
261 Enable this to reduce the size of the FIT image loading code
262 in SPL, if space for the SPL binary is very tight.
264 This removes the detection of image types (which forces the
265 first image to be treated as having a U-Boot style calling
266 convention) and skips the recording of each loaded payload
267 (i.e. loadable) into the FDT (modifying the loaded FDT to
268 ensure this information is available to the next image
271 config SPL_CPU_SUPPORT
272 bool "Support CPU drivers"
274 Enable this to support CPU drivers in SPL. These drivers can set
275 up CPUs and provide information about them such as the model and
276 name. This can be useful in SPL since setting up the CPUs earlier
277 may improve boot performance. Enable this option to build the
278 drivers in drivers/cpu as part of an SPL build.
280 config SPL_CRYPTO_SUPPORT
281 bool "Support crypto drivers"
283 Enable crypto drivers in SPL. These drivers can be used to
284 accelerate secure boot processing in secure applications. Enable
285 this option to build the drivers in drivers/crypto as part of an
288 config SPL_HASH_SUPPORT
289 bool "Support hashing drivers"
293 Enable hashing drivers in SPL. These drivers can be used to
294 accelerate secure boot processing in secure applications. Enable
295 this option to build system-specific drivers for hash acceleration
296 as part of an SPL build.
298 config TPL_HASH_SUPPORT
299 bool "Support hashing drivers in TPL"
303 Enable hashing drivers in SPL. These drivers can be used to
304 accelerate secure boot processing in secure applications. Enable
305 this option to build system-specific drivers for hash acceleration
306 as part of an SPL build.
308 config SPL_DMA_SUPPORT
309 bool "Support DMA drivers"
311 Enable DMA (direct-memory-access) drivers in SPL. These drivers
312 can be used to handle memory-to-peripheral data transfer without
313 the CPU moving the data. Enable this option to build the drivers
314 in drivers/dma as part of an SPL build.
316 config SPL_DRIVERS_MISC_SUPPORT
317 bool "Support misc drivers"
319 Enable miscellaneous drivers in SPL. These drivers perform various
320 tasks that don't fall nicely into other categories, Enable this
321 option to build the drivers in drivers/misc as part of an SPL
322 build, for those that support building in SPL (not all drivers do).
324 config SPL_ENV_SUPPORT
325 bool "Support an environment"
327 Enable environment support in SPL. The U-Boot environment provides
328 a number of settings (essentially name/value pairs) which can
329 control many aspects of U-Boot's operation. Normally this is not
330 needed in SPL as it has a much simpler task with less
331 configuration. But some boards use this to support 'Falcon' boot
332 on EXT2 and FAT, where SPL boots directly into Linux without
333 starting U-Boot first. Enabling this option will make env_get()
334 and env_set() available in SPL.
337 bool "Support save environment"
338 depends on SPL_ENV_SUPPORT
339 select SPL_MMC_WRITE if ENV_IS_IN_MMC
341 Enable save environment support in SPL after setenv. By default
342 the saveenv option is not provided in SPL, but some boards need
343 this support in 'Falcon' boot, where SPL need to boot from
344 different images based on environment variable set by OS. For
345 example OS may set "reboot_image" environment variable to
346 "recovery" inorder to boot recovery image by SPL. The SPL read
347 "reboot_image" and act accordingly and change the reboot_image
348 to default mode using setenv and save the environment.
350 config SPL_ETH_SUPPORT
351 bool "Support Ethernet"
352 depends on SPL_ENV_SUPPORT
354 Enable access to the network subsystem and associated Ethernet
355 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
356 link rather than from an on-board peripheral. Environment support
357 is required since the network stack uses a number of environment
358 variables. See also SPL_NET_SUPPORT.
360 config SPL_EXT_SUPPORT
361 bool "Support EXT filesystems"
363 Enable support for EXT2/3/4 filesystems with SPL. This permits
364 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
365 filesystem from within SPL. Support for the underlying block
366 device (e.g. MMC or USB) must be enabled separately.
368 config SPL_FAT_SUPPORT
369 bool "Support FAT filesystems"
372 Enable support for FAT and VFAT filesystems with SPL. This
373 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
374 filesystem from within SPL. Support for the underlying block
375 device (e.g. MMC or USB) must be enabled separately.
377 config SPL_FPGA_SUPPORT
380 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
381 provide software-configurable hardware which is typically used to
382 implement peripherals (such as UARTs, LCD displays, MMC) or
383 accelerate custom processing functions, such as image processing
384 or machine learning. Sometimes it is useful to program the FPGA
385 as early as possible during boot, and this option can enable that
388 config SPL_GPIO_SUPPORT
389 bool "Support GPIO in SPL"
391 Enable support for GPIOs (General-purpose Input/Output) in SPL.
392 GPIOs allow U-Boot to read the state of an input line (high or
393 low) and set the state of an output line. This can be used to
394 drive LEDs, control power to various system parts and read user
395 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
396 for example. Enable this option to build the drivers in
397 drivers/gpio as part of an SPL build.
399 config SPL_I2C_SUPPORT
402 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
403 I2C works with a clock and data line which can be driven by a
404 one or more masters or slaves. It is a fairly complex bus but is
405 widely used as it only needs two lines for communication. Speeds of
406 400kbps are typical but up to 3.4Mbps is supported by some
407 hardware. I2C can be useful in SPL to configure power management
408 ICs (PMICs) before raising the CPU clock speed, for example.
409 Enable this option to build the drivers in drivers/i2c as part of
412 config SPL_LIBCOMMON_SUPPORT
413 bool "Support common libraries"
415 Enable support for common U-Boot libraries within SPL. These
416 libraries include common code to deal with U-Boot images,
417 environment and USB, for example. This option is enabled on many
418 boards. Enable this option to build the code in common/ as part of
421 config SPL_LIBDISK_SUPPORT
422 bool "Support disk partitions"
424 Enable support for disk partitions within SPL. 'Disk' is something
425 of a misnomer as it includes non-spinning media such as flash (as
426 used in MMC and USB sticks). Partitions provide a way for a disk
427 to be split up into separate regions, with a partition table placed
428 at the start or end which describes the location and size of each
429 'partition'. These partitions are typically uses as individual block
430 devices, typically with an EXT2 or FAT filesystem in each. This
431 option enables whatever partition support has been enabled in
432 U-Boot to also be used in SPL. It brings in the code in disk/.
434 config SPL_LIBGENERIC_SUPPORT
435 bool "Support generic libraries"
437 Enable support for generic U-Boot libraries within SPL. These
438 libraries include generic code to deal with device tree, hashing,
439 printf(), compression and the like. This option is enabled on many
440 boards. Enable this option to build the code in lib/ as part of an
443 config SPL_DM_MAILBOX
444 bool "Support Mailbox"
446 Enable support for Mailbox within SPL. This enable the inter
447 processor communication protocols tobe used within SPL. Enable
448 this option to build the drivers in drivers/mailbox as part of
451 config SPL_MMC_SUPPORT
455 Enable support for MMC (Multimedia Card) within SPL. This enables
456 the MMC protocol implementation and allows any enabled drivers to
457 be used within SPL. MMC can be used with or without disk partition
458 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
459 this option to build the drivers in drivers/mmc as part of an SPL
463 bool "MMC/SD/SDIO card support for write operations in SPL"
464 depends on SPL_MMC_SUPPORT
467 Enable write access to MMC and SD Cards in SPL
470 config SPL_MPC8XXX_INIT_DDR_SUPPORT
471 bool "Support MPC8XXX DDR init"
473 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
474 random-access memory) on the MPC8XXX family within SPL. This
475 allows DRAM to be set up before loading U-Boot into that DRAM,
478 config SPL_MTD_SUPPORT
479 bool "Support MTD drivers"
481 Enable support for MTD (Memory Technology Device) within SPL. MTD
482 provides a block interface over raw NAND and can also be used with
483 SPI flash. This allows SPL to load U-Boot from supported MTD
484 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
485 to enable specific MTD drivers.
487 config SPL_MUSB_NEW_SUPPORT
488 bool "Support new Mentor Graphics USB"
490 Enable support for Mentor Graphics USB in SPL. This is a new
491 driver used by some boards. Enable this option to build
492 the drivers in drivers/usb/musb-new as part of an SPL build. The
493 old drivers are in drivers/usb/musb.
495 config SPL_NAND_SUPPORT
496 bool "Support NAND flash"
498 Enable support for NAND (Negative AND) flash in SPL. NAND flash
499 can be used to allow SPL to load U-Boot from supported devices.
500 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
503 config SPL_NET_SUPPORT
504 bool "Support networking"
506 Enable support for network devices (such as Ethernet) in SPL.
507 This permits SPL to load U-Boot over a network link rather than
508 from an on-board peripheral. Environment support is required since
509 the network stack uses a number of environment variables. See also
513 config SPL_NET_VCI_STRING
514 string "BOOTP Vendor Class Identifier string sent by SPL"
516 As defined by RFC 2132 the vendor class identifier field can be
517 sent by the client to identify the vendor type and configuration
518 of a client. This is often used in practice to allow for the DHCP
519 server to specify different files to load depending on if the ROM,
520 SPL or U-Boot itself makes the request
521 endif # if SPL_NET_SUPPORT
523 config SPL_NO_CPU_SUPPORT
524 bool "Drop CPU code in SPL"
526 This is specific to the ARM926EJ-S CPU. It disables the standard
527 start.S start-up code, presumably so that a replacement can be
528 used on that CPU. You should not enable it unless you know what
531 config SPL_NOR_SUPPORT
532 bool "Support NOR flash"
534 Enable support for loading U-Boot from memory-mapped NOR (Negative
535 OR) flash in SPL. NOR flash is slow to write but fast to read, and
536 a memory-mapped device makes it very easy to access. Loading from
537 NOR is typically achieved with just a memcpy().
539 config SPL_XIP_SUPPORT
543 Enable support for execute in place of U-Boot or kernel image. There
544 is no need to copy image from flash to ram if flash supports execute
545 in place. Its very useful in systems having enough flash but not
546 enough ram to load the image.
548 config SPL_ONENAND_SUPPORT
549 bool "Support OneNAND flash"
551 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
552 a type of NAND flash and therefore can be used to allow SPL to
553 load U-Boot from supported devices. This enables the drivers in
554 drivers/mtd/onenand as part of an SPL build.
557 bool "Activate Falcon Mode"
558 depends on !TI_SECURE_DEVICE
561 Enable booting directly to an OS from SPL.
562 for more info read doc/README.falcon
566 hex "addr, where OS is found"
567 depends on SPL_NOR_SUPPORT
569 Specify the address, where the OS image is found, which
576 default "tpl/u-boot-with-tpl.bin" if TPL
579 Payload for SPL boot. For backward compability, default to
580 u-boot.bin, i.e. RAW image without any header. In case of
581 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
584 config SPL_PCI_SUPPORT
585 bool "Support PCI drivers"
587 Enable support for PCI in SPL. For platforms that need PCI to boot,
588 or must perform some init using PCI in SPL, this provides the
589 necessary driver support. This enables the drivers in drivers/pci
590 as part of an SPL build.
592 config SPL_PCH_SUPPORT
593 bool "Support PCH drivers"
595 Enable support for PCH (Platform Controller Hub) devices in SPL.
596 These are used to set up GPIOs and the SPI peripheral early in
597 boot. This enables the drivers in drivers/pch as part of an SPL
600 config SPL_POST_MEM_SUPPORT
601 bool "Support POST drivers"
603 Enable support for POST (Power-on Self Test) in SPL. POST is a
604 procedure that checks that the hardware (CPU or board) appears to
605 be functionally correctly. It is a sanity check that can be
606 performed before booting. This enables the drivers in post/drivers
607 as part of an SPL build.
610 bool "Support reset drivers"
613 Enable support for reset control in SPL.
614 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
615 by using the generic reset API provided by driver model.
616 This enables the drivers in drivers/reset as part of an SPL build.
618 config SPL_POWER_SUPPORT
619 bool "Support power drivers"
621 Enable support for power control in SPL. This includes support
622 for PMICs (Power-management Integrated Circuits) and some of the
623 features provided by PMICs. In particular, voltage regulators can
624 be used to enable/disable power and vary its voltage. That can be
625 useful in SPL to turn on boot peripherals and adjust CPU voltage
626 so that the clock speed can be increased. This enables the drivers
627 in drivers/power, drivers/power/pmic and drivers/power/regulator
628 as part of an SPL build.
630 config SPL_POWER_DOMAIN
631 bool "Support power domain drivers"
633 Enable support for power domain control in SPL. Many SoCs allow
634 power to be applied to or removed from portions of the SoC (power
635 domains). This may be used to save power. This API provides the
636 means to control such power management hardware. This enables
637 the drivers in drivers/power/domain as part of a SPL build.
639 config SPL_RAM_SUPPORT
640 bool "Support booting from RAM"
641 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
643 Enable booting of an image in RAM. The image can be preloaded or
644 it can be loaded by SPL directly into RAM (e.g. using USB).
646 config SPL_RAM_DEVICE
647 bool "Support booting from preloaded image in RAM"
648 depends on SPL_RAM_SUPPORT
649 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
651 Enable booting of an image already loaded in RAM. The image has to
652 be already in memory when SPL takes over, e.g. loaded by the boot
655 config SPL_REMOTEPROC
656 bool "Support REMOTEPROCS"
658 Enable support for REMOTEPROCs in SPL. This permits to load
659 a remote processor firmware in SPL.
661 config SPL_RTC_SUPPORT
662 bool "Support RTC drivers"
664 Enable RTC (Real-time Clock) support in SPL. This includes support
665 for reading and setting the time. Some RTC devices also have some
666 non-volatile (battery-backed) memory which is accessible if
667 needed. This enables the drivers in drivers/rtc as part of an SPL
670 config SPL_SATA_SUPPORT
671 bool "Support loading from SATA"
673 Enable support for SATA (Serial AT attachment) in SPL. This allows
674 use of SATA devices such as hard drives and flash drivers for
675 loading U-Boot. SATA is used in higher-end embedded systems and
676 can provide higher performance than MMC , at somewhat higher
677 expense and power consumption. This enables loading from SATA
678 using a configured device.
680 config SPL_SERIAL_SUPPORT
681 bool "Support serial"
685 Enable support for serial in SPL. This allows use of a serial UART
686 for displaying messages while SPL is running. It also brings in
687 printf() and panic() functions. This should normally be enabled
688 unless there are space reasons not to. Even then, consider
689 enabling USE_TINY_PRINTF which is a small printf() version.
691 config SPL_SPI_FLASH_SUPPORT
692 bool "Support SPI flash drivers"
694 Enable support for using SPI flash in SPL, and loading U-Boot from
695 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
696 the SPI bus that is used to connect it to a system. It is a simple
697 but fast bidirectional 4-wire bus (clock, chip select and two data
698 lines). This enables the drivers in drivers/mtd/spi as part of an
699 SPL build. This normally requires SPL_SPI_SUPPORT.
702 bool "Support loading from SPI flash"
703 depends on SPL_SPI_FLASH_SUPPORT
705 Enable support for loading next stage, U-Boot or otherwise, from
706 SPI NOR in U-Boot SPL.
708 config SPL_SPI_SUPPORT
709 bool "Support SPI drivers"
711 Enable support for using SPI in SPL. This is used for connecting
712 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
713 more details on that. The SPI driver provides the transport for
714 data between the SPI flash and the CPU. This option can be used to
715 enable SPI drivers that are needed for other purposes also, such
719 bool "Driver support for thermal devices"
721 Enable support for temperature-sensing devices. Some SoCs have on-chip
722 temperature sensors to permit warnings, speed throttling or even
723 automatic power-off when the temperature gets too high or low. Other
724 devices may be discrete but connected on a suitable bus.
726 config SPL_USB_HOST_SUPPORT
727 bool "Support USB host drivers"
729 Enable access to USB (Universal Serial Bus) host devices so that
730 SPL can load U-Boot from a connected USB peripheral, such as a USB
731 flash stick. While USB takes a little longer to start up than most
732 buses, it is very flexible since many different types of storage
733 device can be attached. This option enables the drivers in
734 drivers/usb/host as part of an SPL build.
736 config SPL_USB_SUPPORT
737 bool "Support loading from USB"
738 depends on SPL_USB_HOST_SUPPORT
740 Enable support for USB devices in SPL. This allows use of USB
741 devices such as hard drives and flash drivers for loading U-Boot.
742 The actual drivers are enabled separately using the normal U-Boot
743 config options. This enables loading from USB using a configured
746 config SPL_USB_GADGET_SUPPORT
747 bool "Suppport USB Gadget drivers"
749 Enable USB Gadget API which allows to enable USB device functions
752 if SPL_USB_GADGET_SUPPORT
755 bool "Support USB Ethernet drivers"
757 Enable access to the USB network subsystem and associated
758 drivers in SPL. This permits SPL to load U-Boot over a
759 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
760 than from an onboard peripheral. Environment support is required
761 since the network stack uses a number of environment variables.
762 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
764 config SPL_DFU_SUPPORT
765 bool "Support DFU (Device Firmware Upgrade)"
766 select SPL_HASH_SUPPORT
767 select SPL_DFU_NO_RESET
768 depends on SPL_RAM_SUPPORT
770 This feature enables the DFU (Device Firmware Upgrade) in SPL with
771 RAM memory device support. The ROM code will load and execute
772 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
773 selected device partition from host-pc using dfu-utils.
774 This feature is useful to flash the binaries to factory or bare-metal
775 boards using USB interface.
778 bool "DFU device selection"
779 depends on SPL_DFU_SUPPORT
783 depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
785 select RAM/DDR memory device for loading binary images
786 (u-boot/kernel) to the selected device partition using
787 DFU and execute the u-boot/kernel from RAM.
791 config SPL_USB_SDP_SUPPORT
792 bool "Support SDP (Serial Download Protocol)"
794 Enable Serial Download Protocol (SDP) device support in SPL. This
795 allows to download images into memory and execute (jump to) them
796 using the same protocol as implemented by the i.MX family's boot ROM.
799 config SPL_WATCHDOG_SUPPORT
800 bool "Support watchdog drivers"
802 Enable support for watchdog drivers in SPL. A watchdog is
803 typically a hardware peripheral which can reset the system when it
804 detects no activity for a while (such as a software crash). This
805 enables the drivers in drivers/watchdog as part of an SPL build.
807 config SPL_YMODEM_SUPPORT
808 bool "Support loading using Ymodem"
809 depends on SPL_SERIAL_SUPPORT
811 While loading from serial is slow it can be a useful backup when
812 there is no other option. The Ymodem protocol provides a reliable
813 means of transmitting U-Boot over a serial line for using in SPL,
814 with a checksum to ensure correctness.
817 bool "Support ARM Trusted Firmware"
820 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
821 is loaded by SPL (which is considered as BL2 in ATF terminology).
822 More detail at: https://github.com/ARM-software/arm-trusted-firmware
824 config SPL_ATF_NO_PLATFORM_PARAM
825 bool "Pass no platform parameter"
828 While we expect to call a pointer to a valid FDT (or NULL)
829 as the platform parameter to an ATF, some ATF versions are
830 not U-Boot aware and have an insufficiently robust parameter
831 validation to gracefully reject a FDT being passed.
833 If this option is enabled, the spl_atf os-type handler will
834 always pass NULL for the platform parameter.
836 If your ATF is affected, say Y.
838 config SPL_AM33XX_ENABLE_RTC32K_OSC
839 bool "Enable the RTC32K OSC on AM33xx based platforms"
842 Enable access to the AM33xx RTC and select the external 32kHz clock
846 bool "Support OP-TEE Trusted OS"
849 OP-TEE is an open source Trusted OS which is loaded by SPL.
850 More detail at: https://github.com/OP-TEE/optee_os
854 depends on SUPPORT_TPL
857 If you want to build TPL as well as the normal image and SPL, say Y.
861 config TPL_BOARD_INIT
862 bool "Call board-specific initialization in TPL"
864 If this option is enabled, U-Boot will call the function
865 spl_board_init() from board_init_r(). This function should be
866 provided by the board.
869 string "Linker script for the TPL stage"
872 The TPL stage will usually require a different linker-script
873 (as it runs from a different memory region) than the regular
874 U-Boot stage. Set this to the path of the linker-script to
877 May be left empty to trigger the Makefile infrastructure to
878 fall back to the linker-script used for the SPL stage.
880 config TPL_NEEDS_SEPARATE_TEXT_BASE
881 bool "TPL needs a separate text-base"
885 Enable, if the TPL stage should not inherit its text-base
886 from the SPL stage. When enabled, a base address for the
887 .text sections of the TPL stage has to be set below.
889 config TPL_NEEDS_SEPARATE_STACK
890 bool "TPL needs a separate initial stack-pointer"
894 Enable, if the TPL stage should not inherit its initial
895 stack-pointer from the settings for the SPL stage.
898 hex "Base address for the .text section of the TPL stage"
899 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
901 The base address for the .text section of the TPL stage.
904 int "Maximum size (in bytes) for the TPL stage"
908 The maximum size (in bytes) of the TPL stage.
911 hex "Address of the initial stack-pointer for the TPL stage"
912 depends on TPL_NEEDS_SEPARATE_STACK
914 The address of the initial stack-pointer for the TPL stage.
915 Usually this will be the (aligned) top-of-stack.
917 config TPL_BOOTROM_SUPPORT
918 bool "Support returning to the BOOTROM (from TPL)"
920 Some platforms (e.g. the Rockchip RK3368) provide support in their
921 ROM for loading the next boot-stage after performing basic setup
924 Enable this option, to return to the BOOTROM through the
925 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
926 boot device list, if not implemented for a given board)
928 config TPL_DRIVERS_MISC_SUPPORT
929 bool "Support misc drivers in TPL"
931 Enable miscellaneous drivers in TPL. These drivers perform various
932 tasks that don't fall nicely into other categories, Enable this
933 option to build the drivers in drivers/misc as part of an TPL
934 build, for those that support building in TPL (not all drivers do).
936 config TPL_ENV_SUPPORT
937 bool "Support an environment"
939 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
941 config TPL_GPIO_SUPPORT
942 bool "Support GPIO in TPL"
944 Enable support for GPIOs (General-purpose Input/Output) in TPL.
945 GPIOs allow U-Boot to read the state of an input line (high or
946 low) and set the state of an output line. This can be used to
947 drive LEDs, control power to various system parts and read user
948 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
949 for example. Enable this option to build the drivers in
950 drivers/gpio as part of an TPL build.
952 config TPL_I2C_SUPPORT
955 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
958 config TPL_LIBCOMMON_SUPPORT
959 bool "Support common libraries"
961 Enable support for common U-Boot libraries within TPL. See
962 SPL_LIBCOMMON_SUPPORT for details.
964 config TPL_LIBGENERIC_SUPPORT
965 bool "Support generic libraries"
967 Enable support for generic U-Boot libraries within TPL. See
968 SPL_LIBGENERIC_SUPPORT for details.
970 config TPL_MPC8XXX_INIT_DDR_SUPPORT
971 bool "Support MPC8XXX DDR init"
973 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
974 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
976 config TPL_MMC_SUPPORT
980 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
982 config TPL_NAND_SUPPORT
983 bool "Support NAND flash"
985 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
987 config TPL_PCI_SUPPORT
988 bool "Support PCI drivers"
990 Enable support for PCI in TPL. For platforms that need PCI to boot,
991 or must perform some init using PCI in SPL, this provides the
992 necessary driver support. This enables the drivers in drivers/pci
993 as part of a TPL build.
995 config TPL_PCH_SUPPORT
996 bool "Support PCH drivers"
998 Enable support for PCH (Platform Controller Hub) devices in TPL.
999 These are used to set up GPIOs and the SPI peripheral early in
1000 boot. This enables the drivers in drivers/pch as part of a TPL
1003 config TPL_RAM_SUPPORT
1004 bool "Support booting from RAM"
1006 Enable booting of an image in RAM. The image can be preloaded or
1007 it can be loaded by TPL directly into RAM (e.g. using USB).
1009 config TPL_RAM_DEVICE
1010 bool "Support booting from preloaded image in RAM"
1011 depends on TPL_RAM_SUPPORT
1013 Enable booting of an image already loaded in RAM. The image has to
1014 be already in memory when TPL takes over, e.g. loaded by the boot
1017 config TPL_RTC_SUPPORT
1018 bool "Support RTC drivers"
1020 Enable RTC (Real-time Clock) support in TPL. This includes support
1021 for reading and setting the time. Some RTC devices also have some
1022 non-volatile (battery-backed) memory which is accessible if
1023 needed. This enables the drivers in drivers/rtc as part of an TPL
1026 config TPL_SERIAL_SUPPORT
1027 bool "Support serial"
1031 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1034 config TPL_SPI_FLASH_SUPPORT
1035 bool "Support SPI flash drivers"
1037 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1041 bool "Support loading from SPI flash"
1042 depends on TPL_SPI_FLASH_SUPPORT
1044 Enable support for loading next stage, U-Boot or otherwise, from
1045 SPI NOR in U-Boot TPL.
1047 config TPL_SPI_SUPPORT
1048 bool "Support SPI drivers"
1050 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1053 config TPL_YMODEM_SUPPORT
1054 bool "Support loading using Ymodem"
1055 depends on TPL_SERIAL_SUPPORT
1057 While loading from serial is slow it can be a useful backup when
1058 there is no other option. The Ymodem protocol provides a reliable
1059 means of transmitting U-Boot over a serial line for using in TPL,
1060 with a checksum to ensure correctness.