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 int "Maximum size of SPL image"
31 default 69632 if ARCH_MX6
34 Specifies the maximum length of the U-Boot SPL image.
35 If this value is zero, it is ignored.
37 config SPL_SIZE_LIMIT_SUBTRACT_GD
38 bool "SPL image size check: provide space for global data"
39 depends on SPL_SIZE_LIMIT > 0
41 If enabled, aligned size of global data is reserved in
42 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
43 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
44 pre-reloc global data is put into this SRAM, too.
46 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
47 bool "SPL image size check: provide space for malloc() pool before relocation"
48 depends on SPL_SIZE_LIMIT > 0
50 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
51 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
52 describes the size of SRAM available for SPL when pre-reloc malloc
53 pool is put into this SRAM, too.
55 config SPL_SIZE_LIMIT_PROVIDE_STACK
56 hex "SPL image size check: provide stack space before relocation"
57 depends on SPL_SIZE_LIMIT > 0
60 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
61 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
62 of SRAM available for SPL when the stack required before reolcation
66 bool "Pass hand-off information from SPL to U-Boot proper"
69 It is useful to be able to pass information from SPL to U-Boot
70 proper to preserve state that is known in SPL and is needed in U-Boot.
71 Enable this to locate the handoff information in U-Boot proper, early
72 in boot. It is available in gd->handoff. The state state is set up
73 in SPL (or TPL if that is being used).
78 bool "Pass hand-off information from SPL to U-Boot proper"
82 This option enables SPL to write handoff information. This can be
83 used to pass information like the size of SDRAM from SPL to U-Boot
84 proper. Also SPL can receive information from TPL in the same place
88 string "Linker script for the SPL stage"
89 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
91 The SPL stage will usually require a different linker-script
92 (as it runs from a different memory region) than the regular
93 U-Boot stage. Set this to the path of the linker-script to
98 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
101 The address in memory that SPL will be running from.
103 config SPL_BOARD_INIT
104 bool "Call board-specific initialization in SPL"
106 If this option is enabled, U-Boot will call the function
107 spl_board_init() from board_init_r(). This function should be
108 provided by the board.
110 config SPL_BOOTROM_SUPPORT
111 bool "Support returning to the BOOTROM"
113 Some platforms (e.g. the Rockchip RK3368) provide support in their
114 ROM for loading the next boot-stage after performing basic setup
117 Enable this option, to return to the BOOTROM through the
118 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
119 boot device list, if not implemented for a given board)
121 config SPL_BOOTCOUNT_LIMIT
122 bool "Support bootcount in SPL"
123 depends on SPL_ENV_SUPPORT
125 On some boards, which use 'falcon' mode, it is necessary to check
126 and increment the number of boot attempts. Such boards do not
127 use proper U-Boot for normal boot flow and hence needs those
128 adjustments to be done in the SPL.
130 config SPL_RAW_IMAGE_SUPPORT
131 bool "Support SPL loading and booting of RAW images"
132 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
133 default y if !TI_SECURE_DEVICE
135 SPL will support loading and booting a RAW image when this option
136 is y. If this is not set, SPL will move on to other available
137 boot media to find a suitable image.
139 config SPL_LEGACY_IMAGE_SUPPORT
140 bool "Support SPL loading and booting of Legacy images"
141 default y if !TI_SECURE_DEVICE
143 SPL will support loading and booting Legacy images when this option
144 is y. If this is not set, SPL will move on to other available
145 boot media to find a suitable image.
147 config SPL_LEGACY_IMAGE_CRC_CHECK
148 bool "Check CRC of Legacy images"
149 depends on SPL_LEGACY_IMAGE_SUPPORT
150 select SPL_CRC32_SUPPORT
152 Enable this to check the CRC of Legacy images. While this increases
153 reliability, it affects both code size and boot duration.
154 If disabled, Legacy images are booted if the image magic and size
155 are correct, without further integrity checks.
157 config SPL_SYS_MALLOC_SIMPLE
159 prompt "Only use malloc_simple functions in the SPL"
161 Say Y here to only use the *_simple malloc functions from
162 malloc_simple.c, rather then using the versions from dlmalloc.c;
163 this will make the SPL binary smaller at the cost of more heap
164 usage as the *_simple malloc functions do not re-use free-ed mem.
166 config TPL_SYS_MALLOC_SIMPLE
168 prompt "Only use malloc_simple functions in the TPL"
170 Say Y here to only use the *_simple malloc functions from
171 malloc_simple.c, rather then using the versions from dlmalloc.c;
172 this will make the TPL binary smaller at the cost of more heap
173 usage as the *_simple malloc functions do not re-use free-ed mem.
176 bool "Enable SDRAM location for SPL stack"
178 SPL starts off execution in SRAM and thus typically has only a small
179 stack available. Since SPL sets up DRAM while in its board_init_f()
180 function, it is possible for the stack to move there before
181 board_init_r() is reached. This option enables a special SDRAM
182 location for the SPL stack. U-Boot SPL switches to this after
183 board_init_f() completes, and before board_init_r() starts.
185 config SPL_STACK_R_ADDR
186 depends on SPL_STACK_R
187 hex "SDRAM location for SPL stack"
188 default 0x82000000 if ARCH_OMAP2PLUS
190 Specify the address in SDRAM for the SPL stack. This will be set up
191 before board_init_r() is called.
193 config SPL_STACK_R_MALLOC_SIMPLE_LEN
194 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
195 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
198 Specify the amount of the stack to use as memory pool for
199 malloc_simple after switching the stack to DRAM. This may be set
200 to give board_init_r() a larger heap then the initial heap in
201 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
203 config SPL_SEPARATE_BSS
204 bool "BSS section is in a different memory region from text"
206 Some platforms need a large BSS region in SPL and can provide this
207 because RAM is already set up. In this case BSS can be moved to RAM.
208 This option should then be enabled so that the correct device tree
209 location is used. Normally we put the device tree at the end of BSS
210 but with this option enabled, it goes at _image_binary_end.
212 config SPL_BANNER_PRINT
213 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
216 If this option is enabled, SPL will print the banner with version
217 info. Disabling this option could be useful to reduce TPL boot time
218 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
220 config TPL_BANNER_PRINT
221 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
224 If this option is enabled, SPL will not print the banner with version
225 info. Disabling this option could be useful to reduce SPL boot time
226 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
228 config SPL_DISPLAY_PRINT
229 bool "Display a board-specific message in SPL"
231 If this option is enabled, U-Boot will call the function
232 spl_display_print() immediately after displaying the SPL console
233 banner ("U-Boot SPL ..."). This function should be provided by
236 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
237 bool "MMC raw mode: by sector"
238 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
239 ARCH_MX6 || ARCH_MX7 || \
240 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
241 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
242 OMAP44XX || OMAP54XX || AM33XX || AM43XX
244 Use sector number for specifying U-Boot location on MMC/SD in
247 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
248 hex "Address on the MMC to load U-Boot from"
249 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
250 default 0x50 if ARCH_SUNXI
251 default 0x75 if ARCH_DAVINCI
252 default 0x8a if ARCH_MX6 || ARCH_MX7
253 default 0x100 if ARCH_UNIPHIER
254 default 0x140 if ARCH_MVEBU
255 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
256 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
257 OMAP54XX || AM33XX || AM43XX || ARCH_K3
258 default 0x4000 if ARCH_ROCKCHIP
260 Address on the MMC to load U-Boot from, when the MMC is being used
261 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
263 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
264 bool "MMC Raw mode: by partition"
266 Use a partition for loading U-Boot when using MMC/SD in raw mode.
268 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
269 hex "Partition to use to load U-Boot from"
270 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
273 Partition on the MMC to load U-Boot from when the MMC is being
276 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
277 bool "MMC raw mode: by partition type"
278 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
280 Use partition type for specifying U-Boot partition on MMC/SD in
281 raw mode. U-Boot will be loaded from the first partition of this
284 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
285 hex "Partition Type on the MMC to load U-Boot from"
286 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
288 Partition Type on the MMC to load U-Boot from, when the MMC is being
291 config SPL_CRC32_SUPPORT
293 default y if SPL_LEGACY_IMAGE_SUPPORT
295 Enable this to support CRC32 in uImages or FIT images within SPL.
296 This is a 32-bit checksum value that can be used to verify images.
297 For FIT images, this is the least secure type of checksum, suitable
298 for detected accidental image corruption. For secure applications you
299 should consider SHA1 or SHA256.
301 config SPL_MD5_SUPPORT
305 Enable this to support MD5 in FIT images within SPL. An MD5
306 checksum is a 128-bit hash value used to check that the image
307 contents have not been corrupted. Note that MD5 is not considered
308 secure as it is possible (with a brute-force attack) to adjust the
309 image while still retaining the same MD5 hash value. For secure
310 applications where images may be changed maliciously, you should
311 consider SHA1 or SHA256.
313 config SPL_SHA1_SUPPORT
318 Enable this to support SHA1 in FIT images within SPL. A SHA1
319 checksum is a 160-bit (20-byte) hash value used to check that the
320 image contents have not been corrupted or maliciously altered.
321 While SHA1 is fairly secure it is coming to the end of its life
322 due to the expanding computing power available to brute-force
323 attacks. For more security, consider SHA256.
325 config SPL_SHA256_SUPPORT
326 bool "Support SHA256"
330 Enable this to support SHA256 in FIT images within SPL. A SHA256
331 checksum is a 256-bit (32-byte) hash value used to check that the
332 image contents have not been corrupted. SHA256 is recommended for
333 use in secure applications since (as at 2016) there is no known
334 feasible attack that could produce a 'collision' with differing
335 input data. Use this for the highest security. Note that only the
336 SHA256 variant is supported: SHA512 and others are not currently
339 config SPL_FIT_IMAGE_TINY
340 bool "Remove functionality from SPL FIT loading to reduce size"
342 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
343 default y if ARCH_IMX8M
345 Enable this to reduce the size of the FIT image loading code
346 in SPL, if space for the SPL binary is very tight.
348 This removes the detection of image types (which forces the
349 first image to be treated as having a U-Boot style calling
350 convention) and skips the recording of each loaded payload
351 (i.e. loadable) into the FDT (modifying the loaded FDT to
352 ensure this information is available to the next image
355 config SPL_CPU_SUPPORT
356 bool "Support CPU drivers"
358 Enable this to support CPU drivers in SPL. These drivers can set
359 up CPUs and provide information about them such as the model and
360 name. This can be useful in SPL since setting up the CPUs earlier
361 may improve boot performance. Enable this option to build the
362 drivers in drivers/cpu as part of an SPL build.
364 config SPL_CRYPTO_SUPPORT
365 bool "Support crypto drivers"
367 Enable crypto drivers in SPL. These drivers can be used to
368 accelerate secure boot processing in secure applications. Enable
369 this option to build the drivers in drivers/crypto as part of an
372 config SPL_HASH_SUPPORT
373 bool "Support hashing drivers"
377 Enable hashing drivers in SPL. These drivers can be used to
378 accelerate secure boot processing in secure applications. Enable
379 this option to build system-specific drivers for hash acceleration
380 as part of an SPL build.
382 config TPL_HASH_SUPPORT
383 bool "Support hashing drivers in TPL"
387 Enable hashing drivers in SPL. These drivers can be used to
388 accelerate secure boot processing in secure applications. Enable
389 this option to build system-specific drivers for hash acceleration
390 as part of an SPL build.
392 config SPL_DMA_SUPPORT
393 bool "Support DMA drivers"
395 Enable DMA (direct-memory-access) drivers in SPL. These drivers
396 can be used to handle memory-to-peripheral data transfer without
397 the CPU moving the data. Enable this option to build the drivers
398 in drivers/dma as part of an SPL build.
400 config SPL_DRIVERS_MISC_SUPPORT
401 bool "Support misc drivers"
403 Enable miscellaneous drivers in SPL. These drivers perform various
404 tasks that don't fall nicely into other categories, Enable this
405 option to build the drivers in drivers/misc as part of an SPL
406 build, for those that support building in SPL (not all drivers do).
408 config SPL_ENV_SUPPORT
409 bool "Support an environment"
411 Enable environment support in SPL. The U-Boot environment provides
412 a number of settings (essentially name/value pairs) which can
413 control many aspects of U-Boot's operation. Normally this is not
414 needed in SPL as it has a much simpler task with less
415 configuration. But some boards use this to support 'Falcon' boot
416 on EXT2 and FAT, where SPL boots directly into Linux without
417 starting U-Boot first. Enabling this option will make env_get()
418 and env_set() available in SPL.
421 bool "Support save environment"
422 depends on SPL_ENV_SUPPORT
423 select SPL_MMC_WRITE if ENV_IS_IN_MMC
425 Enable save environment support in SPL after setenv. By default
426 the saveenv option is not provided in SPL, but some boards need
427 this support in 'Falcon' boot, where SPL need to boot from
428 different images based on environment variable set by OS. For
429 example OS may set "reboot_image" environment variable to
430 "recovery" inorder to boot recovery image by SPL. The SPL read
431 "reboot_image" and act accordingly and change the reboot_image
432 to default mode using setenv and save the environment.
434 config SPL_ETH_SUPPORT
435 bool "Support Ethernet"
436 depends on SPL_ENV_SUPPORT
438 Enable access to the network subsystem and associated Ethernet
439 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
440 link rather than from an on-board peripheral. Environment support
441 is required since the network stack uses a number of environment
442 variables. See also SPL_NET_SUPPORT.
445 bool "Support EXT filesystems"
447 Enable support for EXT2/3/4 filesystems with SPL. This permits
448 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
449 filesystem from within SPL. Support for the underlying block
450 device (e.g. MMC or USB) must be enabled separately.
453 bool "Support FAT filesystems"
456 Enable support for FAT and VFAT filesystems with SPL. This
457 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
458 filesystem from within SPL. Support for the underlying block
459 device (e.g. MMC or USB) must be enabled separately.
462 bool "Support write for FAT filesystems"
464 Enable write support for FAT and VFAT filesystems with SPL.
465 Support for the underlying block device (e.g. MMC or USB) must be
468 config SPL_FPGA_SUPPORT
471 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
472 provide software-configurable hardware which is typically used to
473 implement peripherals (such as UARTs, LCD displays, MMC) or
474 accelerate custom processing functions, such as image processing
475 or machine learning. Sometimes it is useful to program the FPGA
476 as early as possible during boot, and this option can enable that
479 config SPL_GPIO_SUPPORT
480 bool "Support GPIO in SPL"
482 Enable support for GPIOs (General-purpose Input/Output) in SPL.
483 GPIOs allow U-Boot to read the state of an input line (high or
484 low) and set the state of an output line. This can be used to
485 drive LEDs, control power to various system parts and read user
486 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
487 for example. Enable this option to build the drivers in
488 drivers/gpio as part of an SPL build.
490 config SPL_I2C_SUPPORT
493 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
494 I2C works with a clock and data line which can be driven by a
495 one or more masters or slaves. It is a fairly complex bus but is
496 widely used as it only needs two lines for communication. Speeds of
497 400kbps are typical but up to 3.4Mbps is supported by some
498 hardware. I2C can be useful in SPL to configure power management
499 ICs (PMICs) before raising the CPU clock speed, for example.
500 Enable this option to build the drivers in drivers/i2c as part of
503 config SPL_LIBCOMMON_SUPPORT
504 bool "Support common libraries"
506 Enable support for common U-Boot libraries within SPL. These
507 libraries include common code to deal with U-Boot images,
508 environment and USB, for example. This option is enabled on many
509 boards. Enable this option to build the code in common/ as part of
512 config SPL_LIBDISK_SUPPORT
513 bool "Support disk partitions"
516 Enable support for disk partitions within SPL. 'Disk' is something
517 of a misnomer as it includes non-spinning media such as flash (as
518 used in MMC and USB sticks). Partitions provide a way for a disk
519 to be split up into separate regions, with a partition table placed
520 at the start or end which describes the location and size of each
521 'partition'. These partitions are typically uses as individual block
522 devices, typically with an EXT2 or FAT filesystem in each. This
523 option enables whatever partition support has been enabled in
524 U-Boot to also be used in SPL. It brings in the code in disk/.
526 config SPL_LIBGENERIC_SUPPORT
527 bool "Support generic libraries"
529 Enable support for generic U-Boot libraries within SPL. These
530 libraries include generic code to deal with device tree, hashing,
531 printf(), compression and the like. This option is enabled on many
532 boards. Enable this option to build the code in lib/ as part of an
535 config SPL_DM_MAILBOX
536 bool "Support Mailbox"
538 Enable support for Mailbox within SPL. This enable the inter
539 processor communication protocols tobe used within SPL. Enable
540 this option to build the drivers in drivers/mailbox as part of
543 config SPL_MMC_SUPPORT
546 select HAVE_BLOCK_DEVICE
548 Enable support for MMC (Multimedia Card) within SPL. This enables
549 the MMC protocol implementation and allows any enabled drivers to
550 be used within SPL. MMC can be used with or without disk partition
551 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
552 this option to build the drivers in drivers/mmc as part of an SPL
556 bool "MMC/SD/SDIO card support for write operations in SPL"
557 depends on SPL_MMC_SUPPORT
560 Enable write access to MMC and SD Cards in SPL
563 config SPL_MPC8XXX_INIT_DDR_SUPPORT
564 bool "Support MPC8XXX DDR init"
566 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
567 random-access memory) on the MPC8XXX family within SPL. This
568 allows DRAM to be set up before loading U-Boot into that DRAM,
571 config SPL_MTD_SUPPORT
572 bool "Support MTD drivers"
574 Enable support for MTD (Memory Technology Device) within SPL. MTD
575 provides a block interface over raw NAND and can also be used with
576 SPI flash. This allows SPL to load U-Boot from supported MTD
577 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
578 to enable specific MTD drivers.
580 config SPL_MUSB_NEW_SUPPORT
581 bool "Support new Mentor Graphics USB"
583 Enable support for Mentor Graphics USB in SPL. This is a new
584 driver used by some boards. Enable this option to build
585 the drivers in drivers/usb/musb-new as part of an SPL build. The
586 old drivers are in drivers/usb/musb.
588 config SPL_NAND_SUPPORT
589 bool "Support NAND flash"
591 Enable support for NAND (Negative AND) flash in SPL. NAND flash
592 can be used to allow SPL to load U-Boot from supported devices.
593 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
596 config SPL_NET_SUPPORT
597 bool "Support networking"
599 Enable support for network devices (such as Ethernet) in SPL.
600 This permits SPL to load U-Boot over a network link rather than
601 from an on-board peripheral. Environment support is required since
602 the network stack uses a number of environment variables. See also
606 config SPL_NET_VCI_STRING
607 string "BOOTP Vendor Class Identifier string sent by SPL"
609 As defined by RFC 2132 the vendor class identifier field can be
610 sent by the client to identify the vendor type and configuration
611 of a client. This is often used in practice to allow for the DHCP
612 server to specify different files to load depending on if the ROM,
613 SPL or U-Boot itself makes the request
614 endif # if SPL_NET_SUPPORT
616 config SPL_NO_CPU_SUPPORT
617 bool "Drop CPU code in SPL"
619 This is specific to the ARM926EJ-S CPU. It disables the standard
620 start.S start-up code, presumably so that a replacement can be
621 used on that CPU. You should not enable it unless you know what
624 config SPL_NOR_SUPPORT
625 bool "Support NOR flash"
627 Enable support for loading U-Boot from memory-mapped NOR (Negative
628 OR) flash in SPL. NOR flash is slow to write but fast to read, and
629 a memory-mapped device makes it very easy to access. Loading from
630 NOR is typically achieved with just a memcpy().
632 config SPL_XIP_SUPPORT
636 Enable support for execute in place of U-Boot or kernel image. There
637 is no need to copy image from flash to ram if flash supports execute
638 in place. Its very useful in systems having enough flash but not
639 enough ram to load the image.
641 config SPL_ONENAND_SUPPORT
642 bool "Support OneNAND flash"
644 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
645 a type of NAND flash and therefore can be used to allow SPL to
646 load U-Boot from supported devices. This enables the drivers in
647 drivers/mtd/onenand as part of an SPL build.
650 bool "Activate Falcon Mode"
651 depends on !TI_SECURE_DEVICE
654 Enable booting directly to an OS from SPL.
655 for more info read doc/README.falcon
659 hex "addr, where OS is found"
660 depends on SPL_NOR_SUPPORT
662 Specify the address, where the OS image is found, which
669 default "tpl/u-boot-with-tpl.bin" if TPL
672 Payload for SPL boot. For backward compatibility, default to
673 u-boot.bin, i.e. RAW image without any header. In case of
674 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
678 bool "Support PCI drivers"
680 Enable support for PCI in SPL. For platforms that need PCI to boot,
681 or must perform some init using PCI in SPL, this provides the
682 necessary driver support. This enables the drivers in drivers/pci
683 as part of an SPL build.
685 config SPL_PCH_SUPPORT
686 bool "Support PCH drivers"
688 Enable support for PCH (Platform Controller Hub) devices in SPL.
689 These are used to set up GPIOs and the SPI peripheral early in
690 boot. This enables the drivers in drivers/pch as part of an SPL
693 config SPL_POST_MEM_SUPPORT
694 bool "Support POST drivers"
696 Enable support for POST (Power-on Self Test) in SPL. POST is a
697 procedure that checks that the hardware (CPU or board) appears to
698 be functionally correctly. It is a sanity check that can be
699 performed before booting. This enables the drivers in post/drivers
700 as part of an SPL build.
703 bool "Support reset drivers"
706 Enable support for reset control in SPL.
707 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
708 by using the generic reset API provided by driver model.
709 This enables the drivers in drivers/reset as part of an SPL build.
711 config SPL_POWER_SUPPORT
712 bool "Support power drivers"
714 Enable support for power control in SPL. This includes support
715 for PMICs (Power-management Integrated Circuits) and some of the
716 features provided by PMICs. In particular, voltage regulators can
717 be used to enable/disable power and vary its voltage. That can be
718 useful in SPL to turn on boot peripherals and adjust CPU voltage
719 so that the clock speed can be increased. This enables the drivers
720 in drivers/power, drivers/power/pmic and drivers/power/regulator
721 as part of an SPL build.
723 config SPL_POWER_DOMAIN
724 bool "Support power domain drivers"
726 Enable support for power domain control in SPL. Many SoCs allow
727 power to be applied to or removed from portions of the SoC (power
728 domains). This may be used to save power. This API provides the
729 means to control such power management hardware. This enables
730 the drivers in drivers/power/domain as part of a SPL build.
732 config SPL_RAM_SUPPORT
733 bool "Support booting from RAM"
734 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
736 Enable booting of an image in RAM. The image can be preloaded or
737 it can be loaded by SPL directly into RAM (e.g. using USB).
739 config SPL_RAM_DEVICE
740 bool "Support booting from preloaded image in RAM"
741 depends on SPL_RAM_SUPPORT
742 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
744 Enable booting of an image already loaded in RAM. The image has to
745 be already in memory when SPL takes over, e.g. loaded by the boot
748 config SPL_REMOTEPROC
749 bool "Support REMOTEPROCS"
751 Enable support for REMOTEPROCs in SPL. This permits to load
752 a remote processor firmware in SPL.
754 config SPL_RTC_SUPPORT
755 bool "Support RTC drivers"
757 Enable RTC (Real-time Clock) support in SPL. This includes support
758 for reading and setting the time. Some RTC devices also have some
759 non-volatile (battery-backed) memory which is accessible if
760 needed. This enables the drivers in drivers/rtc as part of an SPL
763 config SPL_SATA_SUPPORT
764 bool "Support loading from SATA"
766 Enable support for SATA (Serial AT attachment) in SPL. This allows
767 use of SATA devices such as hard drives and flash drivers for
768 loading U-Boot. SATA is used in higher-end embedded systems and
769 can provide higher performance than MMC , at somewhat higher
770 expense and power consumption. This enables loading from SATA
771 using a configured device.
773 config SPL_SERIAL_SUPPORT
774 bool "Support serial"
778 Enable support for serial in SPL. This allows use of a serial UART
779 for displaying messages while SPL is running. It also brings in
780 printf() and panic() functions. This should normally be enabled
781 unless there are space reasons not to. Even then, consider
782 enabling USE_TINY_PRINTF which is a small printf() version.
784 config SPL_SPI_FLASH_SUPPORT
785 bool "Support SPI flash drivers"
787 Enable support for using SPI flash in SPL, and loading U-Boot from
788 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
789 the SPI bus that is used to connect it to a system. It is a simple
790 but fast bidirectional 4-wire bus (clock, chip select and two data
791 lines). This enables the drivers in drivers/mtd/spi as part of an
792 SPL build. This normally requires SPL_SPI_SUPPORT.
794 if SPL_SPI_FLASH_SUPPORT
796 config SPL_SPI_FLASH_TINY
797 bool "Enable low footprint SPL SPI Flash support"
798 depends on !SPI_FLASH_BAR
799 default y if SPI_FLASH
801 Enable lightweight SPL SPI Flash support that supports just reading
802 data/images from flash. No support to write/erase flash. Enable
803 this if you have SPL size limitations and don't need full
804 fledged SPI flash support.
806 config SPL_SPI_FLASH_SFDP_SUPPORT
807 bool "SFDP table parsing support for SPI NOR flashes"
808 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
810 Enable support for parsing and auto discovery of parameters for
811 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
812 tables as per JESD216 standard in SPL.
815 bool "Support loading from SPI flash"
817 Enable support for loading next stage, U-Boot or otherwise, from
818 SPI NOR in U-Boot SPL.
820 endif # SPL_SPI_FLASH_SUPPORT
822 config SPL_SPI_SUPPORT
823 bool "Support SPI drivers"
825 Enable support for using SPI in SPL. This is used for connecting
826 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
827 more details on that. The SPI driver provides the transport for
828 data between the SPI flash and the CPU. This option can be used to
829 enable SPI drivers that are needed for other purposes also, such
833 bool "Driver support for thermal devices"
835 Enable support for temperature-sensing devices. Some SoCs have on-chip
836 temperature sensors to permit warnings, speed throttling or even
837 automatic power-off when the temperature gets too high or low. Other
838 devices may be discrete but connected on a suitable bus.
840 config SPL_USB_HOST_SUPPORT
841 bool "Support USB host drivers"
842 select HAVE_BLOCK_DEVICE
844 Enable access to USB (Universal Serial Bus) host devices so that
845 SPL can load U-Boot from a connected USB peripheral, such as a USB
846 flash stick. While USB takes a little longer to start up than most
847 buses, it is very flexible since many different types of storage
848 device can be attached. This option enables the drivers in
849 drivers/usb/host as part of an SPL build.
851 config SPL_USB_STORAGE
852 bool "Support loading from USB"
853 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
855 Enable support for USB devices in SPL. This allows use of USB
856 devices such as hard drives and flash drivers for loading U-Boot.
857 The actual drivers are enabled separately using the normal U-Boot
858 config options. This enables loading from USB using a configured
861 config SPL_USB_GADGET
862 bool "Suppport USB Gadget drivers"
864 Enable USB Gadget API which allows to enable USB device functions
870 bool "Support USB Ethernet drivers"
872 Enable access to the USB network subsystem and associated
873 drivers in SPL. This permits SPL to load U-Boot over a
874 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
875 than from an onboard peripheral. Environment support is required
876 since the network stack uses a number of environment variables.
877 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
880 bool "Support DFU (Device Firmware Upgrade)"
881 select SPL_HASH_SUPPORT
882 select SPL_DFU_NO_RESET
883 depends on SPL_RAM_SUPPORT
885 This feature enables the DFU (Device Firmware Upgrade) in SPL with
886 RAM memory device support. The ROM code will load and execute
887 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
888 selected device partition from host-pc using dfu-utils.
889 This feature is useful to flash the binaries to factory or bare-metal
890 boards using USB interface.
893 bool "DFU device selection"
898 depends on SPL_DFU && SPL_RAM_SUPPORT
900 select RAM/DDR memory device for loading binary images
901 (u-boot/kernel) to the selected device partition using
902 DFU and execute the u-boot/kernel from RAM.
906 config SPL_USB_SDP_SUPPORT
907 bool "Support SDP (Serial Download Protocol)"
909 Enable Serial Download Protocol (SDP) device support in SPL. This
910 allows to download images into memory and execute (jump to) them
911 using the same protocol as implemented by the i.MX family's boot ROM.
914 config SPL_WATCHDOG_SUPPORT
915 bool "Support watchdog drivers"
917 Enable support for watchdog drivers in SPL. A watchdog is
918 typically a hardware peripheral which can reset the system when it
919 detects no activity for a while (such as a software crash). This
920 enables the drivers in drivers/watchdog as part of an SPL build.
922 config SPL_YMODEM_SUPPORT
923 bool "Support loading using Ymodem"
924 depends on SPL_SERIAL_SUPPORT
926 While loading from serial is slow it can be a useful backup when
927 there is no other option. The Ymodem protocol provides a reliable
928 means of transmitting U-Boot over a serial line for using in SPL,
929 with a checksum to ensure correctness.
932 bool "Support ARM Trusted Firmware"
935 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
936 is loaded by SPL (which is considered as BL2 in ATF terminology).
937 More detail at: https://github.com/ARM-software/arm-trusted-firmware
939 config SPL_ATF_NO_PLATFORM_PARAM
940 bool "Pass no platform parameter"
943 While we expect to call a pointer to a valid FDT (or NULL)
944 as the platform parameter to an ATF, some ATF versions are
945 not U-Boot aware and have an insufficiently robust parameter
946 validation to gracefully reject a FDT being passed.
948 If this option is enabled, the spl_atf os-type handler will
949 always pass NULL for the platform parameter.
951 If your ATF is affected, say Y.
953 config SPL_AM33XX_ENABLE_RTC32K_OSC
954 bool "Enable the RTC32K OSC on AM33xx based platforms"
957 Enable access to the AM33xx RTC and select the external 32kHz clock
961 bool "Support OP-TEE Trusted OS"
964 OP-TEE is an open source Trusted OS which is loaded by SPL.
965 More detail at: https://github.com/OP-TEE/optee_os
969 depends on SUPPORT_TPL
972 If you want to build TPL as well as the normal image and SPL, say Y.
977 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
981 This option enables TPL to write handoff information. This can be
982 used to pass information like the size of SDRAM from TPL to U-Boot
983 proper. The information is also available to SPL if it is useful
986 config TPL_BOARD_INIT
987 bool "Call board-specific initialization in TPL"
989 If this option is enabled, U-Boot will call the function
990 spl_board_init() from board_init_r(). This function should be
991 provided by the board.
994 string "Linker script for the TPL stage"
996 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
997 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
999 The TPL stage will usually require a different linker-script
1000 (as it runs from a different memory region) than the regular
1001 U-Boot stage. Set this to the path of the linker-script to
1004 May be left empty to trigger the Makefile infrastructure to
1005 fall back to the linker-script used for the SPL stage.
1007 config TPL_NEEDS_SEPARATE_TEXT_BASE
1008 bool "TPL needs a separate text-base"
1012 Enable, if the TPL stage should not inherit its text-base
1013 from the SPL stage. When enabled, a base address for the
1014 .text sections of the TPL stage has to be set below.
1016 config TPL_NEEDS_SEPARATE_STACK
1017 bool "TPL needs a separate initial stack-pointer"
1021 Enable, if the TPL stage should not inherit its initial
1022 stack-pointer from the settings for the SPL stage.
1024 config TPL_TEXT_BASE
1025 hex "Base address for the .text section of the TPL stage"
1026 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1028 The base address for the .text section of the TPL stage.
1031 int "Maximum size (in bytes) for the TPL stage"
1035 The maximum size (in bytes) of the TPL stage.
1038 hex "Address of the initial stack-pointer for the TPL stage"
1039 depends on TPL_NEEDS_SEPARATE_STACK
1041 The address of the initial stack-pointer for the TPL stage.
1042 Usually this will be the (aligned) top-of-stack.
1044 config TPL_BOOTROM_SUPPORT
1045 bool "Support returning to the BOOTROM (from TPL)"
1047 Some platforms (e.g. the Rockchip RK3368) provide support in their
1048 ROM for loading the next boot-stage after performing basic setup
1051 Enable this option, to return to the BOOTROM through the
1052 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1053 boot device list, if not implemented for a given board)
1055 config TPL_DRIVERS_MISC_SUPPORT
1056 bool "Support misc drivers in TPL"
1058 Enable miscellaneous drivers in TPL. These drivers perform various
1059 tasks that don't fall nicely into other categories, Enable this
1060 option to build the drivers in drivers/misc as part of an TPL
1061 build, for those that support building in TPL (not all drivers do).
1063 config TPL_ENV_SUPPORT
1064 bool "Support an environment"
1066 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1068 config TPL_GPIO_SUPPORT
1069 bool "Support GPIO in TPL"
1071 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1072 GPIOs allow U-Boot to read the state of an input line (high or
1073 low) and set the state of an output line. This can be used to
1074 drive LEDs, control power to various system parts and read user
1075 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1076 for example. Enable this option to build the drivers in
1077 drivers/gpio as part of an TPL build.
1079 config TPL_I2C_SUPPORT
1082 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1085 config TPL_LIBCOMMON_SUPPORT
1086 bool "Support common libraries"
1088 Enable support for common U-Boot libraries within TPL. See
1089 SPL_LIBCOMMON_SUPPORT for details.
1091 config TPL_LIBGENERIC_SUPPORT
1092 bool "Support generic libraries"
1094 Enable support for generic U-Boot libraries within TPL. See
1095 SPL_LIBGENERIC_SUPPORT for details.
1097 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1098 bool "Support MPC8XXX DDR init"
1100 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1101 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1103 config TPL_MMC_SUPPORT
1107 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1109 config TPL_NAND_SUPPORT
1110 bool "Support NAND flash"
1112 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1115 bool "Support PCI drivers"
1117 Enable support for PCI in TPL. For platforms that need PCI to boot,
1118 or must perform some init using PCI in SPL, this provides the
1119 necessary driver support. This enables the drivers in drivers/pci
1120 as part of a TPL build.
1122 config TPL_PCH_SUPPORT
1123 bool "Support PCH drivers"
1125 Enable support for PCH (Platform Controller Hub) devices in TPL.
1126 These are used to set up GPIOs and the SPI peripheral early in
1127 boot. This enables the drivers in drivers/pch as part of a TPL
1130 config TPL_RAM_SUPPORT
1131 bool "Support booting from RAM"
1133 Enable booting of an image in RAM. The image can be preloaded or
1134 it can be loaded by TPL directly into RAM (e.g. using USB).
1136 config TPL_RAM_DEVICE
1137 bool "Support booting from preloaded image in RAM"
1138 depends on TPL_RAM_SUPPORT
1140 Enable booting of an image already loaded in RAM. The image has to
1141 be already in memory when TPL takes over, e.g. loaded by the boot
1144 config TPL_RTC_SUPPORT
1145 bool "Support RTC drivers"
1147 Enable RTC (Real-time Clock) support in TPL. This includes support
1148 for reading and setting the time. Some RTC devices also have some
1149 non-volatile (battery-backed) memory which is accessible if
1150 needed. This enables the drivers in drivers/rtc as part of an TPL
1153 config TPL_SERIAL_SUPPORT
1154 bool "Support serial"
1158 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1161 config TPL_SPI_FLASH_SUPPORT
1162 bool "Support SPI flash drivers"
1164 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1168 bool "Support loading from SPI flash"
1169 depends on TPL_SPI_FLASH_SUPPORT
1171 Enable support for loading next stage, U-Boot or otherwise, from
1172 SPI NOR in U-Boot TPL.
1174 config TPL_SPI_SUPPORT
1175 bool "Support SPI drivers"
1177 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1180 config TPL_YMODEM_SUPPORT
1181 bool "Support loading using Ymodem"
1182 depends on TPL_SERIAL_SUPPORT
1184 While loading from serial is slow it can be a useful backup when
1185 there is no other option. The Ymodem protocol provides a reliable
1186 means of transmitting U-Boot over a serial line for using in TPL,
1187 with a checksum to ensure correctness.