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.
28 config SPL_FRAMEWORK_BOARD_INIT_F
29 bool "Define a generic function board_init_f"
30 depends on SPL_FRAMEWORK
32 Define a generic function board_init_f that:
33 - initialize the spl (spl_early_init)
34 - initialize the serial (preloader_console_init)
35 Unless you want to provide your own board_init_f, you should say Y.
38 hex "Maximum size of SPL image"
40 default 69632 if ARCH_MX6 && !MX6_OCRAM_256KB
41 default 200704 if ARCH_MX6 && MX6_OCRAM_256KB
44 Specifies the maximum length of the U-Boot SPL image.
45 If this value is zero, it is ignored.
47 config SPL_SIZE_LIMIT_SUBTRACT_GD
48 bool "SPL image size check: provide space for global data"
49 depends on SPL_SIZE_LIMIT > 0
51 If enabled, aligned size of global data is reserved in
52 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
53 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
54 pre-reloc global data is put into this SRAM, too.
56 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
57 bool "SPL image size check: provide space for malloc() pool before relocation"
58 depends on SPL_SIZE_LIMIT > 0
60 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
61 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
62 describes the size of SRAM available for SPL when pre-reloc malloc
63 pool is put into this SRAM, too.
65 config SPL_SIZE_LIMIT_PROVIDE_STACK
66 hex "SPL image size check: provide stack space before relocation"
67 depends on SPL_SIZE_LIMIT > 0
70 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
71 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
72 of SRAM available for SPL when the stack required before reolcation
75 config SPL_SYS_STACK_F_CHECK_BYTE
79 Constant used to check the stack
81 config SPL_SYS_REPORT_STACK_F_USAGE
82 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
83 bool "Check and report stack usage in SPL before relocation"
85 If this option is enabled, the initial SPL stack is filled with 0xaa
86 very early, up to the size configured with
87 SPL_SIZE_LIMIT_PROVIDE_STACK.
88 Later when SPL is done using this initial stack and switches to a
89 stack in DRAM, the actually used size of this initial stack is
90 reported by examining the memory and searching for the lowest
91 occurrence of non 0xaa bytes.
92 This default implementation works for stacks growing down only.
94 menu "PowerPC and LayerScape SPL Boot options"
97 bool "Load SPL from NAND flash"
98 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
101 bool "Load SPL from SD Card / eMMC"
102 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
105 bool "Load SPL from SPI flash"
106 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
109 bool "Create SPL in Freescale PBI format"
110 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
113 Create boot binary having SPL binary in PBI format concatenated with
119 bool "Pass hand-off information from SPL to U-Boot proper"
122 It is useful to be able to pass information from SPL to U-Boot
123 proper to preserve state that is known in SPL and is needed in U-Boot.
124 Enable this to locate the handoff information in U-Boot proper, early
125 in boot. It is available in gd->handoff. The state state is set up
126 in SPL (or TPL if that is being used).
131 bool "Pass hand-off information from SPL to U-Boot proper"
132 depends on HANDOFF && SPL_BLOBLIST
135 This option enables SPL to write handoff information. This can be
136 used to pass information like the size of SDRAM from SPL to U-Boot
137 proper. Also SPL can receive information from TPL in the same place
141 string "Linker script for the SPL stage"
142 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
144 The SPL stage will usually require a different linker-script
145 (as it runs from a different memory region) than the regular
146 U-Boot stage. Set this to the path of the linker-script to
151 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
152 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
153 default 0x20060 if MACH_SUN50I_H6
154 default 0x00060 if ARCH_SUNXI
155 default 0xfffc0000 if ARCH_ZYNQMP
158 The address in memory that SPL will be running from.
160 config SPL_BOARD_INIT
161 bool "Call board-specific initialization in SPL"
163 If this option is enabled, U-Boot will call the function
164 spl_board_init() from board_init_r(). This function should be
165 provided by the board.
167 config SPL_BOOTROM_SUPPORT
168 bool "Support returning to the BOOTROM"
170 Some platforms (e.g. the Rockchip RK3368) provide support in their
171 ROM for loading the next boot-stage after performing basic setup
174 Enable this option, to return to the BOOTROM through the
175 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
176 boot device list, if not implemented for a given board)
178 config SPL_BOOTCOUNT_LIMIT
179 bool "Support bootcount in SPL"
180 depends on SPL_ENV_SUPPORT
182 On some boards, which use 'falcon' mode, it is necessary to check
183 and increment the number of boot attempts. Such boards do not
184 use proper U-Boot for normal boot flow and hence needs those
185 adjustments to be done in the SPL.
187 config SPL_RAW_IMAGE_SUPPORT
188 bool "Support SPL loading and booting of RAW images"
189 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
190 default y if !TI_SECURE_DEVICE
192 SPL will support loading and booting a RAW image when this option
193 is y. If this is not set, SPL will move on to other available
194 boot media to find a suitable image.
196 config SPL_LEGACY_IMAGE_SUPPORT
197 bool "Support SPL loading and booting of Legacy images"
198 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
200 SPL will support loading and booting Legacy images when this option
201 is y. If this is not set, SPL will move on to other available
202 boot media to find a suitable image.
204 config SPL_LEGACY_IMAGE_CRC_CHECK
205 bool "Check CRC of Legacy images"
206 depends on SPL_LEGACY_IMAGE_SUPPORT
207 select SPL_CRC32_SUPPORT
209 Enable this to check the CRC of Legacy images. While this increases
210 reliability, it affects both code size and boot duration.
211 If disabled, Legacy images are booted if the image magic and size
212 are correct, without further integrity checks.
214 config SPL_SYS_MALLOC_SIMPLE
216 prompt "Only use malloc_simple functions in the SPL"
218 Say Y here to only use the *_simple malloc functions from
219 malloc_simple.c, rather then using the versions from dlmalloc.c;
220 this will make the SPL binary smaller at the cost of more heap
221 usage as the *_simple malloc functions do not re-use free-ed mem.
223 config TPL_SYS_MALLOC_SIMPLE
225 prompt "Only use malloc_simple functions in the TPL"
228 Say Y here to only use the *_simple malloc functions from
229 malloc_simple.c, rather then using the versions from dlmalloc.c;
230 this will make the TPL binary smaller at the cost of more heap
231 usage as the *_simple malloc functions do not re-use free-ed mem.
234 bool "Enable SDRAM location for SPL stack"
236 SPL starts off execution in SRAM and thus typically has only a small
237 stack available. Since SPL sets up DRAM while in its board_init_f()
238 function, it is possible for the stack to move there before
239 board_init_r() is reached. This option enables a special SDRAM
240 location for the SPL stack. U-Boot SPL switches to this after
241 board_init_f() completes, and before board_init_r() starts.
243 config SPL_STACK_R_ADDR
244 depends on SPL_STACK_R
245 hex "SDRAM location for SPL stack"
246 default 0x82000000 if ARCH_OMAP2PLUS
248 Specify the address in SDRAM for the SPL stack. This will be set up
249 before board_init_r() is called.
251 config SPL_STACK_R_MALLOC_SIMPLE_LEN
252 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
253 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
256 Specify the amount of the stack to use as memory pool for
257 malloc_simple after switching the stack to DRAM. This may be set
258 to give board_init_r() a larger heap then the initial heap in
259 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
261 config SPL_SEPARATE_BSS
262 bool "BSS section is in a different memory region from text"
264 Some platforms need a large BSS region in SPL and can provide this
265 because RAM is already set up. In this case BSS can be moved to RAM.
266 This option should then be enabled so that the correct device tree
267 location is used. Normally we put the device tree at the end of BSS
268 but with this option enabled, it goes at _image_binary_end.
270 config SPL_BANNER_PRINT
271 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
274 If this option is enabled, SPL will print the banner with version
275 info. Disabling this option could be useful to reduce SPL boot time
276 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
278 config TPL_BANNER_PRINT
279 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
283 If this option is enabled, TPL will print the banner with version
284 info. Disabling this option could be useful to reduce TPL boot time
285 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
288 depends on ARM && !ARM64
289 bool "Allows initializing BSS early before entering board_init_f"
291 On some platform we have sufficient memory available early on to
292 allow setting up and using a basic BSS prior to entering
293 board_init_f. Activating this option will also de-activate the
294 clearing of BSS during the SPL relocation process, thus allowing
295 to carry state from board_init_f to board_init_r by way of BSS.
297 config SPL_DISPLAY_PRINT
298 bool "Display a board-specific message in SPL"
300 If this option is enabled, U-Boot will call the function
301 spl_display_print() immediately after displaying the SPL console
302 banner ("U-Boot SPL ..."). This function should be provided by
305 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
306 bool "MMC raw mode: by sector"
307 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
308 ARCH_MX6 || ARCH_MX7 || \
309 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
310 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
311 OMAP44XX || OMAP54XX || AM33XX || AM43XX || TARGET_SIFIVE_FU540
313 Use sector number for specifying U-Boot location on MMC/SD in
316 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
317 hex "Address on the MMC to load U-Boot from"
318 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
319 default 0x50 if ARCH_SUNXI
320 default 0x75 if ARCH_DAVINCI
321 default 0x8a if ARCH_MX6 || ARCH_MX7
322 default 0x100 if ARCH_UNIPHIER
323 default 0x140 if ARCH_MVEBU
324 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
325 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
326 OMAP54XX || AM33XX || AM43XX || ARCH_K3
327 default 0x4000 if ARCH_ROCKCHIP
328 default 0x822 if TARGET_SIFIVE_FU540
330 Address on the MMC to load U-Boot from, when the MMC is being used
331 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
333 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
334 hex "U-Boot main hardware partition image offset"
335 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
338 On some platforms SPL location depends on hardware partition. The ROM
339 code skips the MBR sector when loading SPL from main hardware data
340 partition. This adds offset to the main U-Boot image. Set this symbol
341 to the number of skipped sectors.
343 If unsure, leave the default.
345 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
346 bool "MMC Raw mode: by partition"
348 Use a partition for loading U-Boot when using MMC/SD in raw mode.
350 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
351 hex "Partition to use to load U-Boot from"
352 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
355 Partition on the MMC to load U-Boot from when the MMC is being
358 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
359 bool "MMC raw mode: by partition type"
360 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
362 Use partition type for specifying U-Boot partition on MMC/SD in
363 raw mode. U-Boot will be loaded from the first partition of this
366 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
367 hex "Partition Type on the MMC to load U-Boot from"
368 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
370 Partition Type on the MMC to load U-Boot from, when the MMC is being
373 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
374 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
375 depends on SUPPORT_EMMC_BOOT
377 eMMC boot partition is normally configured by the bits of the EXT_CSD
378 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
379 cases it might be required in SPL to load the image from different
380 partition than the partition selected by EXT_CSC_PART_CONFIG register.
381 Enable this option if you intend to use an eMMC boot partition other
382 then selected via EXT_CSC_PART_CONFIG register and specify the custom
383 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
386 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
387 int "Number of the eMMC boot partition to use"
388 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
391 eMMC boot partition number to use when the eMMC in raw mode and
392 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
393 by user defined partition number.
395 config SPL_CRC32_SUPPORT
397 default y if SPL_LEGACY_IMAGE_SUPPORT
399 Enable this to support CRC32 in uImages or FIT images within SPL.
400 This is a 32-bit checksum value that can be used to verify images.
401 For FIT images, this is the least secure type of checksum, suitable
402 for detected accidental image corruption. For secure applications you
403 should consider SHA1 or SHA256.
405 config SPL_MD5_SUPPORT
409 Enable this to support MD5 in FIT images within SPL. An MD5
410 checksum is a 128-bit hash value used to check that the image
411 contents have not been corrupted. Note that MD5 is not considered
412 secure as it is possible (with a brute-force attack) to adjust the
413 image while still retaining the same MD5 hash value. For secure
414 applications where images may be changed maliciously, you should
415 consider SHA256 or SHA384.
417 config SPL_SHA1_SUPPORT
422 Enable this to support SHA1 in FIT images within SPL. A SHA1
423 checksum is a 160-bit (20-byte) hash value used to check that the
424 image contents have not been corrupted or maliciously altered.
425 While SHA1 is fairly secure it is coming to the end of its life
426 due to the expanding computing power available to brute-force
427 attacks. For more security, consider SHA256 or SHA384.
429 config SPL_SHA256_SUPPORT
430 bool "Support SHA256"
434 Enable this to support SHA256 in FIT images within SPL. A SHA256
435 checksum is a 256-bit (32-byte) hash value used to check that the
436 image contents have not been corrupted.
438 config SPL_SHA384_SUPPORT
439 bool "Support SHA384"
444 Enable this to support SHA384 in FIT images within SPL. A SHA384
445 checksum is a 384-bit (48-byte) hash value used to check that the
446 image contents have not been corrupted. Use this for the highest
449 config SPL_SHA512_SUPPORT
450 bool "Support SHA512"
455 Enable this to support SHA512 in FIT images within SPL. A SHA512
456 checksum is a 512-bit (64-byte) hash value used to check that the
457 image contents have not been corrupted.
459 config SPL_FIT_IMAGE_TINY
460 bool "Remove functionality from SPL FIT loading to reduce size"
462 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
463 default y if ARCH_IMX8M
465 Enable this to reduce the size of the FIT image loading code
466 in SPL, if space for the SPL binary is very tight.
468 This removes the detection of image types (which forces the
469 first image to be treated as having a U-Boot style calling
470 convention) and skips the recording of each loaded payload
471 (i.e. loadable) into the FDT (modifying the loaded FDT to
472 ensure this information is available to the next image
475 config SPL_CACHE_SUPPORT
476 bool "Support CACHE drivers"
478 Enable CACHE drivers in SPL. These drivers can keep data so that
479 future requests for that data can be served faster. Enable this option
480 to build the drivers in drivers/cache as part of an SPL build.
482 config SPL_CPU_SUPPORT
483 bool "Support CPU drivers"
485 Enable this to support CPU drivers in SPL. These drivers can set
486 up CPUs and provide information about them such as the model and
487 name. This can be useful in SPL since setting up the CPUs earlier
488 may improve boot performance. Enable this option to build the
489 drivers in drivers/cpu as part of an SPL build.
491 config SPL_CRYPTO_SUPPORT
492 bool "Support crypto drivers"
494 Enable crypto drivers in SPL. These drivers can be used to
495 accelerate secure boot processing in secure applications. Enable
496 this option to build the drivers in drivers/crypto as part of an
499 config SPL_HASH_SUPPORT
500 bool "Support hashing drivers"
504 Enable hashing drivers in SPL. These drivers can be used to
505 accelerate secure boot processing in secure applications. Enable
506 this option to build system-specific drivers for hash acceleration
507 as part of an SPL build.
509 config TPL_HASH_SUPPORT
510 bool "Support hashing drivers in TPL"
515 Enable hashing drivers in SPL. These drivers can be used to
516 accelerate secure boot processing in secure applications. Enable
517 this option to build system-specific drivers for hash acceleration
518 as part of an SPL build.
521 bool "Support DMA drivers"
523 Enable DMA (direct-memory-access) drivers in SPL. These drivers
524 can be used to handle memory-to-peripheral data transfer without
525 the CPU moving the data. Enable this option to build the drivers
526 in drivers/dma as part of an SPL build.
528 config SPL_DRIVERS_MISC_SUPPORT
529 bool "Support misc drivers"
531 Enable miscellaneous drivers in SPL. These drivers perform various
532 tasks that don't fall nicely into other categories, Enable this
533 option to build the drivers in drivers/misc as part of an SPL
534 build, for those that support building in SPL (not all drivers do).
536 config SPL_ENV_SUPPORT
537 bool "Support an environment"
539 Enable environment support in SPL. The U-Boot environment provides
540 a number of settings (essentially name/value pairs) which can
541 control many aspects of U-Boot's operation. Normally this is not
542 needed in SPL as it has a much simpler task with less
543 configuration. But some boards use this to support 'Falcon' boot
544 on EXT2 and FAT, where SPL boots directly into Linux without
545 starting U-Boot first. Enabling this option will make env_get()
546 and env_set() available in SPL.
549 bool "Support save environment"
550 depends on SPL_ENV_SUPPORT
551 select SPL_MMC_WRITE if ENV_IS_IN_MMC
553 Enable save environment support in SPL after setenv. By default
554 the saveenv option is not provided in SPL, but some boards need
555 this support in 'Falcon' boot, where SPL need to boot from
556 different images based on environment variable set by OS. For
557 example OS may set "reboot_image" environment variable to
558 "recovery" inorder to boot recovery image by SPL. The SPL read
559 "reboot_image" and act accordingly and change the reboot_image
560 to default mode using setenv and save the environment.
562 config SPL_ETH_SUPPORT
563 bool "Support Ethernet"
564 depends on SPL_ENV_SUPPORT
566 Enable access to the network subsystem and associated Ethernet
567 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
568 link rather than from an on-board peripheral. Environment support
569 is required since the network stack uses a number of environment
570 variables. See also SPL_NET_SUPPORT.
573 bool "Support EXT filesystems"
575 Enable support for EXT2/3/4 filesystems with SPL. This permits
576 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
577 filesystem from within SPL. Support for the underlying block
578 device (e.g. MMC or USB) must be enabled separately.
581 bool "Support FAT filesystems"
584 Enable support for FAT and VFAT filesystems with SPL. This
585 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
586 filesystem from within SPL. Support for the underlying block
587 device (e.g. MMC or USB) must be enabled separately.
590 bool "Support write for FAT filesystems"
592 Enable write support for FAT and VFAT filesystems with SPL.
593 Support for the underlying block device (e.g. MMC or USB) must be
596 config SPL_FPGA_SUPPORT
599 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
600 provide software-configurable hardware which is typically used to
601 implement peripherals (such as UARTs, LCD displays, MMC) or
602 accelerate custom processing functions, such as image processing
603 or machine learning. Sometimes it is useful to program the FPGA
604 as early as possible during boot, and this option can enable that
607 config SPL_GPIO_SUPPORT
608 bool "Support GPIO in SPL"
610 Enable support for GPIOs (General-purpose Input/Output) in SPL.
611 GPIOs allow U-Boot to read the state of an input line (high or
612 low) and set the state of an output line. This can be used to
613 drive LEDs, control power to various system parts and read user
614 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
615 for example. Enable this option to build the drivers in
616 drivers/gpio as part of an SPL build.
618 config SPL_I2C_SUPPORT
621 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
622 I2C works with a clock and data line which can be driven by a
623 one or more masters or slaves. It is a fairly complex bus but is
624 widely used as it only needs two lines for communication. Speeds of
625 400kbps are typical but up to 3.4Mbps is supported by some
626 hardware. I2C can be useful in SPL to configure power management
627 ICs (PMICs) before raising the CPU clock speed, for example.
628 Enable this option to build the drivers in drivers/i2c as part of
631 config SPL_LIBCOMMON_SUPPORT
632 bool "Support common libraries"
634 Enable support for common U-Boot libraries within SPL. These
635 libraries include common code to deal with U-Boot images,
636 environment and USB, for example. This option is enabled on many
637 boards. Enable this option to build the code in common/ as part of
640 config SPL_LIBDISK_SUPPORT
641 bool "Support disk partitions"
644 Enable support for disk partitions within SPL. 'Disk' is something
645 of a misnomer as it includes non-spinning media such as flash (as
646 used in MMC and USB sticks). Partitions provide a way for a disk
647 to be split up into separate regions, with a partition table placed
648 at the start or end which describes the location and size of each
649 'partition'. These partitions are typically uses as individual block
650 devices, typically with an EXT2 or FAT filesystem in each. This
651 option enables whatever partition support has been enabled in
652 U-Boot to also be used in SPL. It brings in the code in disk/.
654 config SPL_LIBGENERIC_SUPPORT
655 bool "Support generic libraries"
657 Enable support for generic U-Boot libraries within SPL. These
658 libraries include generic code to deal with device tree, hashing,
659 printf(), compression and the like. This option is enabled on many
660 boards. Enable this option to build the code in lib/ as part of an
663 config SPL_DM_MAILBOX
664 bool "Support Mailbox"
666 Enable support for Mailbox within SPL. This enable the inter
667 processor communication protocols tobe used within SPL. Enable
668 this option to build the drivers in drivers/mailbox as part of
671 config SPL_MMC_SUPPORT
674 select HAVE_BLOCK_DEVICE
676 Enable support for MMC (Multimedia Card) within SPL. This enables
677 the MMC protocol implementation and allows any enabled drivers to
678 be used within SPL. MMC can be used with or without disk partition
679 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
680 this option to build the drivers in drivers/mmc as part of an SPL
683 config SYS_MMCSD_FS_BOOT_PARTITION
684 int "MMC Boot Partition"
687 Partition on the MMC to load U-Boot from when the MMC is being
691 bool "Tiny MMC framework in SPL"
692 depends on SPL_MMC_SUPPORT
695 Enable MMC framework tinification support. This option is useful if
696 if your SPL is extremely size constrained. Heed the warning, enable
697 this option if and only if you know exactly what you are doing, if
698 you are reading this help text, you most likely have no idea :-)
700 The MMC framework is reduced to bare minimum to be useful. No malloc
701 support is needed for the MMC framework operation with this option
702 enabled. The framework supports exactly one MMC device and exactly
703 one MMC driver. The MMC driver can be adjusted to avoid any malloc
704 operations too, which can remove the need for malloc support in SPL
705 and thus further reduce footprint.
708 bool "MMC/SD/SDIO card support for write operations in SPL"
709 depends on SPL_MMC_SUPPORT
712 Enable write access to MMC and SD Cards in SPL
715 config SPL_MPC8XXX_INIT_DDR_SUPPORT
716 bool "Support MPC8XXX DDR init"
718 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
719 random-access memory) on the MPC8XXX family within SPL. This
720 allows DRAM to be set up before loading U-Boot into that DRAM,
723 config SPL_MTD_SUPPORT
724 bool "Support MTD drivers"
726 Enable support for MTD (Memory Technology Device) within SPL. MTD
727 provides a block interface over raw NAND and can also be used with
728 SPI flash. This allows SPL to load U-Boot from supported MTD
729 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
730 to enable specific MTD drivers.
732 config SPL_MUSB_NEW_SUPPORT
733 bool "Support new Mentor Graphics USB"
735 Enable support for Mentor Graphics USB in SPL. This is a new
736 driver used by some boards. Enable this option to build
737 the drivers in drivers/usb/musb-new as part of an SPL build. The
738 old drivers are in drivers/usb/musb.
740 config SPL_NAND_SUPPORT
741 bool "Support NAND flash"
743 Enable support for NAND (Negative AND) flash in SPL. NAND flash
744 can be used to allow SPL to load U-Boot from supported devices.
745 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
748 config SPL_NAND_DRIVERS
749 bool "Use standard NAND driver"
751 SPL uses normal NAND drivers, not minimal drivers.
754 bool "Include standard software ECC in the SPL"
756 config SPL_NAND_SIMPLE
757 bool "Support simple NAND drivers in SPL"
759 Support for NAND boot using simple NAND drivers that
760 expose the cmd_ctrl() interface.
763 depends on SPL_NAND_DRIVERS
764 bool "Use Base NAND Driver"
766 Include nand_base.c in the SPL.
768 config SPL_NAND_IDENT
769 depends on SPL_NAND_BASE
770 bool "Use chip ID to identify NAND flash"
772 SPL uses the chip ID list to identify the NAND flash.
777 Enable support for loading payloads from UBI. See
778 README.ubispl for more info.
783 bool "Support cache drivers in SPL"
785 Enable support for cache drivers in SPL.
788 bool "Support SPI DM drivers in SPL"
790 Enable support for SPI DM drivers in SPL.
792 config SPL_DM_SPI_FLASH
793 bool "Support SPI DM FLASH drivers in SPL"
795 Enable support for SPI DM flash drivers in SPL.
799 config SPL_UBI_LOAD_BY_VOLNAME
800 bool "Support loading volumes by name"
802 This enables support for loading UBI volumes by name. When this
803 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
804 configure the volume name from which to load U-Boot.
806 config SPL_UBI_MAX_VOL_LEBS
807 int "Maximum number of LEBs per volume"
810 The maximum number of logical eraseblocks which a static volume
811 to load can contain. Used for sizing the scan data structure.
813 config SPL_UBI_MAX_PEB_SIZE
814 int "Maximum PEB size"
817 The maximum physical erase block size.
819 config SPL_UBI_MAX_PEBS
820 int "Maximum number of PEBs"
823 The maximum physical erase block size. If not overridden by
824 board code, this value will be used as the actual number of PEBs.
826 config SPL_UBI_PEB_OFFSET
827 int "Offset to first UBI PEB"
830 The offset in number of PEBs from the start of flash to the first
831 PEB part of the UBI image.
833 config SPL_UBI_VID_OFFSET
834 int "Offset to VID header"
837 config SPL_UBI_LEB_START
838 int "Offset to LEB in PEB"
841 The offset in bytes to the LEB within a PEB.
843 config SPL_UBI_INFO_ADDR
844 hex "Address to place UBI scan info"
847 Address for ubispl to place the scan info. Read README.ubispl to
848 determine the required size
850 config SPL_UBI_VOL_IDS
851 int "Maximum volume id"
854 The maximum volume id which can be loaded. Used for sizing the
857 config SPL_UBI_LOAD_MONITOR_ID
858 int "id of U-Boot volume"
861 The UBI volume id from which to load U-Boot
863 config SPL_UBI_LOAD_MONITOR_VOLNAME
864 string "volume name of U-Boot volume"
865 depends on SPL_UBI_LOAD_BY_VOLNAME
867 The UBI volume name from which to load U-Boot
869 config SPL_UBI_LOAD_KERNEL_ID
870 int "id of kernel volume"
871 depends on SPL_OS_BOOT && SPL_UBI
873 The UBI volume id from which to load the kernel
875 config SPL_UBI_LOAD_ARGS_ID
876 int "id of kernel args volume"
877 depends on SPL_OS_BOOT && SPL_UBI
879 The UBI volume id from which to load the device tree
881 config UBI_SPL_SILENCE_MSG
882 bool "silence UBI SPL messages"
885 Disable messages from UBI SPL. This leaves warnings
890 config SPL_NET_SUPPORT
891 bool "Support networking"
893 Enable support for network devices (such as Ethernet) in SPL.
894 This permits SPL to load U-Boot over a network link rather than
895 from an on-board peripheral. Environment support is required since
896 the network stack uses a number of environment variables. See also
900 config SPL_NET_VCI_STRING
901 string "BOOTP Vendor Class Identifier string sent by SPL"
903 As defined by RFC 2132 the vendor class identifier field can be
904 sent by the client to identify the vendor type and configuration
905 of a client. This is often used in practice to allow for the DHCP
906 server to specify different files to load depending on if the ROM,
907 SPL or U-Boot itself makes the request
908 endif # if SPL_NET_SUPPORT
910 config SPL_NO_CPU_SUPPORT
911 bool "Drop CPU code in SPL"
913 This is specific to the ARM926EJ-S CPU. It disables the standard
914 start.S start-up code, presumably so that a replacement can be
915 used on that CPU. You should not enable it unless you know what
918 config SPL_NOR_SUPPORT
919 bool "Support NOR flash"
921 Enable support for loading U-Boot from memory-mapped NOR (Negative
922 OR) flash in SPL. NOR flash is slow to write but fast to read, and
923 a memory-mapped device makes it very easy to access. Loading from
924 NOR is typically achieved with just a memcpy().
926 config SPL_XIP_SUPPORT
930 Enable support for execute in place of U-Boot or kernel image. There
931 is no need to copy image from flash to ram if flash supports execute
932 in place. Its very useful in systems having enough flash but not
933 enough ram to load the image.
935 config SPL_ONENAND_SUPPORT
936 bool "Support OneNAND flash"
938 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
939 a type of NAND flash and therefore can be used to allow SPL to
940 load U-Boot from supported devices. This enables the drivers in
941 drivers/mtd/onenand as part of an SPL build.
944 bool "Activate Falcon Mode"
945 depends on !TI_SECURE_DEVICE
948 Enable booting directly to an OS from SPL.
949 for more info read doc/README.falcon
953 hex "addr, where OS is found"
954 depends on SPL_NOR_SUPPORT
956 Specify the address, where the OS image is found, which
963 default "tpl/u-boot-with-tpl.bin" if TPL
966 Payload for SPL boot. For backward compatibility, default to
967 u-boot.bin, i.e. RAW image without any header. In case of
968 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
972 bool "Support PCI drivers"
974 Enable support for PCI in SPL. For platforms that need PCI to boot,
975 or must perform some init using PCI in SPL, this provides the
976 necessary driver support. This enables the drivers in drivers/pci
977 as part of an SPL build.
979 config SPL_PCH_SUPPORT
980 bool "Support PCH drivers"
982 Enable support for PCH (Platform Controller Hub) devices in SPL.
983 These are used to set up GPIOs and the SPI peripheral early in
984 boot. This enables the drivers in drivers/pch as part of an SPL
987 config SPL_POST_MEM_SUPPORT
988 bool "Support POST drivers"
990 Enable support for POST (Power-on Self Test) in SPL. POST is a
991 procedure that checks that the hardware (CPU or board) appears to
992 be functionally correctly. It is a sanity check that can be
993 performed before booting. This enables the drivers in post/drivers
994 as part of an SPL build.
997 bool "Support reset drivers"
1000 Enable support for reset control in SPL.
1001 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1002 by using the generic reset API provided by driver model.
1003 This enables the drivers in drivers/reset as part of an SPL build.
1005 config SPL_POWER_SUPPORT
1006 bool "Support power drivers"
1008 Enable support for power control in SPL. This includes support
1009 for PMICs (Power-management Integrated Circuits) and some of the
1010 features provided by PMICs. In particular, voltage regulators can
1011 be used to enable/disable power and vary its voltage. That can be
1012 useful in SPL to turn on boot peripherals and adjust CPU voltage
1013 so that the clock speed can be increased. This enables the drivers
1014 in drivers/power, drivers/power/pmic and drivers/power/regulator
1015 as part of an SPL build.
1017 config SPL_POWER_DOMAIN
1018 bool "Support power domain drivers"
1020 Enable support for power domain control in SPL. Many SoCs allow
1021 power to be applied to or removed from portions of the SoC (power
1022 domains). This may be used to save power. This API provides the
1023 means to control such power management hardware. This enables
1024 the drivers in drivers/power/domain as part of a SPL build.
1026 config SPL_RAM_SUPPORT
1027 bool "Support booting from RAM"
1028 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1030 Enable booting of an image in RAM. The image can be preloaded or
1031 it can be loaded by SPL directly into RAM (e.g. using USB).
1033 config SPL_RAM_DEVICE
1034 bool "Support booting from preloaded image in RAM"
1035 depends on SPL_RAM_SUPPORT
1036 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1038 Enable booting of an image already loaded in RAM. The image has to
1039 be already in memory when SPL takes over, e.g. loaded by the boot
1042 config SPL_REMOTEPROC
1043 bool "Support REMOTEPROCS"
1045 Enable support for REMOTEPROCs in SPL. This permits to load
1046 a remote processor firmware in SPL.
1048 config SPL_RTC_SUPPORT
1049 bool "Support RTC drivers"
1051 Enable RTC (Real-time Clock) support in SPL. This includes support
1052 for reading and setting the time. Some RTC devices also have some
1053 non-volatile (battery-backed) memory which is accessible if
1054 needed. This enables the drivers in drivers/rtc as part of an SPL
1057 config SPL_SATA_SUPPORT
1058 bool "Support loading from SATA"
1060 Enable support for SATA (Serial AT attachment) in SPL. This allows
1061 use of SATA devices such as hard drives and flash drivers for
1062 loading U-Boot. SATA is used in higher-end embedded systems and
1063 can provide higher performance than MMC , at somewhat higher
1064 expense and power consumption. This enables loading from SATA
1065 using a configured device.
1067 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1068 bool "SATA raw mode: by sector"
1069 depends on SPL_SATA_SUPPORT
1071 Use sector number for specifying U-Boot location on SATA disk in
1074 config SPL_SATA_RAW_U_BOOT_SECTOR
1075 hex "Sector on the SATA disk to load U-Boot from"
1076 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1078 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1079 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1081 config SPL_SERIAL_SUPPORT
1082 bool "Support serial"
1086 Enable support for serial in SPL. This allows use of a serial UART
1087 for displaying messages while SPL is running. It also brings in
1088 printf() and panic() functions. This should normally be enabled
1089 unless there are space reasons not to. Even then, consider
1090 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1092 config SPL_SPI_SUPPORT
1093 bool "Support SPI drivers"
1095 Enable support for using SPI in SPL. This is used for connecting
1096 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1097 more details on that. The SPI driver provides the transport for
1098 data between the SPI flash and the CPU. This option can be used to
1099 enable SPI drivers that are needed for other purposes also, such
1102 config SPL_SPI_FLASH_SUPPORT
1103 bool "Support SPI flash drivers"
1104 depends on SPL_SPI_SUPPORT
1106 Enable support for using SPI flash in SPL, and loading U-Boot from
1107 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1108 the SPI bus that is used to connect it to a system. It is a simple
1109 but fast bidirectional 4-wire bus (clock, chip select and two data
1110 lines). This enables the drivers in drivers/mtd/spi as part of an
1111 SPL build. This normally requires SPL_SPI_SUPPORT.
1113 if SPL_SPI_FLASH_SUPPORT
1115 config SPL_SPI_FLASH_TINY
1116 bool "Enable low footprint SPL SPI Flash support"
1117 depends on !SPI_FLASH_BAR
1118 default y if SPI_FLASH
1120 Enable lightweight SPL SPI Flash support that supports just reading
1121 data/images from flash. No support to write/erase flash. Enable
1122 this if you have SPL size limitations and don't need full
1123 fledged SPI flash support.
1125 config SPL_SPI_FLASH_SFDP_SUPPORT
1126 bool "SFDP table parsing support for SPI NOR flashes"
1127 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1129 Enable support for parsing and auto discovery of parameters for
1130 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1131 tables as per JESD216 standard in SPL.
1133 config SPL_SPI_FLASH_MTD
1134 bool "Support for SPI flash MTD drivers in SPL"
1136 Enable support for SPI flash MTD drivers in SPL.
1139 bool "Support loading from SPI flash"
1141 Enable support for loading next stage, U-Boot or otherwise, from
1142 SPI NOR in U-Boot SPL.
1144 endif # SPL_SPI_FLASH_SUPPORT
1146 config SYS_SPI_U_BOOT_OFFS
1147 hex "address of u-boot payload in SPI flash"
1148 default 0x8000 if ARCH_SUNXI
1150 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1152 Address within SPI-Flash from where the u-boot payload is fetched
1156 bool "Driver support for thermal devices"
1158 Enable support for temperature-sensing devices. Some SoCs have on-chip
1159 temperature sensors to permit warnings, speed throttling or even
1160 automatic power-off when the temperature gets too high or low. Other
1161 devices may be discrete but connected on a suitable bus.
1163 config SPL_USB_HOST_SUPPORT
1164 bool "Support USB host drivers"
1165 select HAVE_BLOCK_DEVICE
1167 Enable access to USB (Universal Serial Bus) host devices so that
1168 SPL can load U-Boot from a connected USB peripheral, such as a USB
1169 flash stick. While USB takes a little longer to start up than most
1170 buses, it is very flexible since many different types of storage
1171 device can be attached. This option enables the drivers in
1172 drivers/usb/host as part of an SPL build.
1174 config SPL_USB_STORAGE
1175 bool "Support loading from USB"
1176 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1178 Enable support for USB devices in SPL. This allows use of USB
1179 devices such as hard drives and flash drivers for loading U-Boot.
1180 The actual drivers are enabled separately using the normal U-Boot
1181 config options. This enables loading from USB using a configured
1184 config SPL_USB_GADGET
1185 bool "Suppport USB Gadget drivers"
1187 Enable USB Gadget API which allows to enable USB device functions
1192 config SPL_USB_ETHER
1193 bool "Support USB Ethernet drivers"
1195 Enable access to the USB network subsystem and associated
1196 drivers in SPL. This permits SPL to load U-Boot over a
1197 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1198 than from an onboard peripheral. Environment support is required
1199 since the network stack uses a number of environment variables.
1200 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1203 bool "Support DFU (Device Firmware Upgrade)"
1204 select SPL_HASH_SUPPORT
1205 select SPL_DFU_NO_RESET
1206 depends on SPL_RAM_SUPPORT
1208 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1209 RAM memory device support. The ROM code will load and execute
1210 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1211 selected device partition from host-pc using dfu-utils.
1212 This feature is useful to flash the binaries to factory or bare-metal
1213 boards using USB interface.
1216 bool "DFU device selection"
1221 depends on SPL_DFU && SPL_RAM_SUPPORT
1223 select RAM/DDR memory device for loading binary images
1224 (u-boot/kernel) to the selected device partition using
1225 DFU and execute the u-boot/kernel from RAM.
1229 config SPL_USB_SDP_SUPPORT
1230 bool "Support SDP (Serial Download Protocol)"
1232 Enable Serial Download Protocol (SDP) device support in SPL. This
1233 allows to download images into memory and execute (jump to) them
1234 using the same protocol as implemented by the i.MX family's boot ROM.
1236 config SPL_SDP_USB_DEV
1237 int "SDP USB controller index"
1239 depends on SPL_USB_SDP_SUPPORT
1241 Some boards have USB controller other than 0. Define this option
1242 so it can be used in compiled environment.
1245 config SPL_WATCHDOG_SUPPORT
1246 bool "Support watchdog drivers"
1247 imply SPL_WDT if !HW_WATCHDOG
1249 Enable support for watchdog drivers in SPL. A watchdog is
1250 typically a hardware peripheral which can reset the system when it
1251 detects no activity for a while (such as a software crash). This
1252 enables the drivers in drivers/watchdog as part of an SPL build.
1254 config SPL_YMODEM_SUPPORT
1255 bool "Support loading using Ymodem"
1256 depends on SPL_SERIAL_SUPPORT
1258 While loading from serial is slow it can be a useful backup when
1259 there is no other option. The Ymodem protocol provides a reliable
1260 means of transmitting U-Boot over a serial line for using in SPL,
1261 with a checksum to ensure correctness.
1264 bool "Support ARM Trusted Firmware"
1267 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1268 is loaded by SPL (which is considered as BL2 in ATF terminology).
1269 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1271 config SPL_ATF_NO_PLATFORM_PARAM
1272 bool "Pass no platform parameter"
1275 While we expect to call a pointer to a valid FDT (or NULL)
1276 as the platform parameter to an ATF, some ATF versions are
1277 not U-Boot aware and have an insufficiently robust parameter
1278 validation to gracefully reject a FDT being passed.
1280 If this option is enabled, the spl_atf os-type handler will
1281 always pass NULL for the platform parameter.
1283 If your ATF is affected, say Y.
1285 config SPL_AM33XX_ENABLE_RTC32K_OSC
1286 bool "Enable the RTC32K OSC on AM33xx based platforms"
1289 Enable access to the AM33xx RTC and select the external 32kHz clock
1293 bool "Support OP-TEE Trusted OS"
1296 OP-TEE is an open source Trusted OS which is loaded by SPL.
1297 More detail at: https://github.com/OP-TEE/optee_os
1300 bool "Support RISC-V OpenSBI"
1301 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1303 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1304 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1305 firmware. It is loaded and started by U-Boot SPL.
1307 More details are available at https://github.com/riscv/opensbi and
1308 https://github.com/riscv/riscv-sbi-doc
1310 config SPL_OPENSBI_LOAD_ADDR
1311 hex "OpenSBI load address"
1312 depends on SPL_OPENSBI
1314 Load address of the OpenSBI binary.
1318 depends on SUPPORT_TPL
1321 If you want to build TPL as well as the normal image and SPL, say Y.
1325 config TPL_SIZE_LIMIT
1326 hex "Maximum size of TPL image"
1330 Specifies the maximum length of the U-Boot TPL image.
1331 If this value is zero, it is ignored.
1333 config TPL_FRAMEWORK
1334 bool "Support TPL based upon the common SPL framework"
1335 default y if SPL_FRAMEWORK
1337 Enable the SPL framework under common/spl/ for TPL builds.
1338 This framework supports MMC, NAND and YMODEM and other methods
1339 loading of U-Boot's SPL stage. If unsure, say Y.
1342 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1343 depends on HANDOFF && TPL_BLOBLIST
1346 This option enables TPL to write handoff information. This can be
1347 used to pass information like the size of SDRAM from TPL to U-Boot
1348 proper. The information is also available to SPL if it is useful
1351 config TPL_BOARD_INIT
1352 bool "Call board-specific initialization in TPL"
1354 If this option is enabled, U-Boot will call the function
1355 spl_board_init() from board_init_r(). This function should be
1356 provided by the board.
1359 string "Linker script for the TPL stage"
1361 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1362 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1364 The TPL stage will usually require a different linker-script
1365 (as it runs from a different memory region) than the regular
1366 U-Boot stage. Set this to the path of the linker-script to
1369 May be left empty to trigger the Makefile infrastructure to
1370 fall back to the linker-script used for the SPL stage.
1372 config TPL_NEEDS_SEPARATE_TEXT_BASE
1373 bool "TPL needs a separate text-base"
1377 Enable, if the TPL stage should not inherit its text-base
1378 from the SPL stage. When enabled, a base address for the
1379 .text sections of the TPL stage has to be set below.
1381 config TPL_NEEDS_SEPARATE_STACK
1382 bool "TPL needs a separate initial stack-pointer"
1386 Enable, if the TPL stage should not inherit its initial
1387 stack-pointer from the settings for the SPL stage.
1389 config TPL_TEXT_BASE
1390 hex "Base address for the .text section of the TPL stage"
1391 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1393 The base address for the .text section of the TPL stage.
1396 int "Maximum size (in bytes) for the TPL stage"
1400 The maximum size (in bytes) of the TPL stage.
1403 hex "Address of the initial stack-pointer for the TPL stage"
1404 depends on TPL_NEEDS_SEPARATE_STACK
1406 The address of the initial stack-pointer for the TPL stage.
1407 Usually this will be the (aligned) top-of-stack.
1409 config TPL_BOOTROM_SUPPORT
1410 bool "Support returning to the BOOTROM (from TPL)"
1412 Some platforms (e.g. the Rockchip RK3368) provide support in their
1413 ROM for loading the next boot-stage after performing basic setup
1416 Enable this option, to return to the BOOTROM through the
1417 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1418 boot device list, if not implemented for a given board)
1420 config TPL_DRIVERS_MISC_SUPPORT
1421 bool "Support misc drivers in TPL"
1423 Enable miscellaneous drivers in TPL. These drivers perform various
1424 tasks that don't fall nicely into other categories, Enable this
1425 option to build the drivers in drivers/misc as part of an TPL
1426 build, for those that support building in TPL (not all drivers do).
1428 config TPL_ENV_SUPPORT
1429 bool "Support an environment"
1431 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1433 config TPL_GPIO_SUPPORT
1434 bool "Support GPIO in TPL"
1436 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1437 GPIOs allow U-Boot to read the state of an input line (high or
1438 low) and set the state of an output line. This can be used to
1439 drive LEDs, control power to various system parts and read user
1440 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1441 for example. Enable this option to build the drivers in
1442 drivers/gpio as part of an TPL build.
1444 config TPL_I2C_SUPPORT
1447 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1450 config TPL_LIBCOMMON_SUPPORT
1451 bool "Support common libraries"
1453 Enable support for common U-Boot libraries within TPL. See
1454 SPL_LIBCOMMON_SUPPORT for details.
1456 config TPL_LIBGENERIC_SUPPORT
1457 bool "Support generic libraries"
1459 Enable support for generic U-Boot libraries within TPL. See
1460 SPL_LIBGENERIC_SUPPORT for details.
1462 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1463 bool "Support MPC8XXX DDR init"
1465 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1466 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1468 config TPL_MMC_SUPPORT
1472 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1474 config TPL_NAND_SUPPORT
1475 bool "Support NAND flash"
1477 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1480 bool "Support PCI drivers"
1482 Enable support for PCI in TPL. For platforms that need PCI to boot,
1483 or must perform some init using PCI in SPL, this provides the
1484 necessary driver support. This enables the drivers in drivers/pci
1485 as part of a TPL build.
1487 config TPL_PCH_SUPPORT
1488 bool "Support PCH drivers"
1490 Enable support for PCH (Platform Controller Hub) devices in TPL.
1491 These are used to set up GPIOs and the SPI peripheral early in
1492 boot. This enables the drivers in drivers/pch as part of a TPL
1495 config TPL_RAM_SUPPORT
1496 bool "Support booting from RAM"
1498 Enable booting of an image in RAM. The image can be preloaded or
1499 it can be loaded by TPL directly into RAM (e.g. using USB).
1501 config TPL_RAM_DEVICE
1502 bool "Support booting from preloaded image in RAM"
1503 depends on TPL_RAM_SUPPORT
1505 Enable booting of an image already loaded in RAM. The image has to
1506 be already in memory when TPL takes over, e.g. loaded by the boot
1509 config TPL_RTC_SUPPORT
1510 bool "Support RTC drivers"
1512 Enable RTC (Real-time Clock) support in TPL. This includes support
1513 for reading and setting the time. Some RTC devices also have some
1514 non-volatile (battery-backed) memory which is accessible if
1515 needed. This enables the drivers in drivers/rtc as part of an TPL
1518 config TPL_SERIAL_SUPPORT
1519 bool "Support serial"
1523 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1526 config TPL_SPI_FLASH_SUPPORT
1527 bool "Support SPI flash drivers"
1529 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1532 config TPL_SPI_FLASH_TINY
1533 bool "Enable low footprint TPL SPI Flash support"
1534 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1535 default y if SPI_FLASH
1537 Enable lightweight TPL SPI Flash support that supports just reading
1538 data/images from flash. No support to write/erase flash. Enable
1539 this if you have TPL size limitations and don't need full-fledged
1543 bool "Support loading from SPI flash"
1544 depends on TPL_SPI_FLASH_SUPPORT
1546 Enable support for loading next stage, U-Boot or otherwise, from
1547 SPI NOR in U-Boot TPL.
1549 config TPL_SPI_SUPPORT
1550 bool "Support SPI drivers"
1552 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1556 bool "Support SPI DM drivers in TPL"
1558 Enable support for SPI DM drivers in TPL.
1560 config TPL_DM_SPI_FLASH
1561 bool "Support SPI DM FLASH drivers in TPL"
1563 Enable support for SPI DM flash drivers in TPL.
1565 config TPL_YMODEM_SUPPORT
1566 bool "Support loading using Ymodem"
1567 depends on TPL_SERIAL_SUPPORT
1569 While loading from serial is slow it can be a useful backup when
1570 there is no other option. The Ymodem protocol provides a reliable
1571 means of transmitting U-Boot over a serial line for using in TPL,
1572 with a checksum to ensure correctness.
1576 config SPL_AT91_MCK_BYPASS
1577 bool "Use external clock signal as a source of main clock for AT91 platforms"
1578 depends on ARCH_AT91
1581 Use external 8 to 24 Mhz clock signal as source of main clock instead
1582 of an external crystal oscillator.
1583 This option disables the internal driving on the XOUT pin.
1584 The external source has to provide a stable clock on the XIN pin.
1585 If this option is disabled, the SoC expects a crystal oscillator
1586 that needs driving on both XIN and XOUT lines.