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 SPL Boot options"
95 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
98 bool "Load SPL from NAND flash"
101 bool "Load SPL from SD Card / eMMC"
104 bool "Load SPL from SPI flash"
107 bool "Create SPL in Freescale PBI format"
109 Create boot binary having SPL binary in PBI format concatenated with
115 bool "Pass hand-off information from SPL to U-Boot proper"
118 It is useful to be able to pass information from SPL to U-Boot
119 proper to preserve state that is known in SPL and is needed in U-Boot.
120 Enable this to locate the handoff information in U-Boot proper, early
121 in boot. It is available in gd->handoff. The state state is set up
122 in SPL (or TPL if that is being used).
127 bool "Pass hand-off information from SPL to U-Boot proper"
128 depends on HANDOFF && SPL_BLOBLIST
131 This option enables SPL to write handoff information. This can be
132 used to pass information like the size of SDRAM from SPL to U-Boot
133 proper. Also SPL can receive information from TPL in the same place
137 string "Linker script for the SPL stage"
138 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
140 The SPL stage will usually require a different linker-script
141 (as it runs from a different memory region) than the regular
142 U-Boot stage. Set this to the path of the linker-script to
147 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
148 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
149 default 0x20060 if MACH_SUN50I_H6
150 default 0x00060 if ARCH_SUNXI
151 default 0xfffc0000 if ARCH_ZYNQMP
154 The address in memory that SPL will be running from.
156 config SPL_BOARD_INIT
157 bool "Call board-specific initialization in SPL"
159 If this option is enabled, U-Boot will call the function
160 spl_board_init() from board_init_r(). This function should be
161 provided by the board.
163 config SPL_BOOTROM_SUPPORT
164 bool "Support returning to the BOOTROM"
166 Some platforms (e.g. the Rockchip RK3368) provide support in their
167 ROM for loading the next boot-stage after performing basic setup
170 Enable this option, to return to the BOOTROM through the
171 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
172 boot device list, if not implemented for a given board)
174 config SPL_BOOTCOUNT_LIMIT
175 bool "Support bootcount in SPL"
176 depends on SPL_ENV_SUPPORT
178 On some boards, which use 'falcon' mode, it is necessary to check
179 and increment the number of boot attempts. Such boards do not
180 use proper U-Boot for normal boot flow and hence needs those
181 adjustments to be done in the SPL.
183 config SPL_RAW_IMAGE_SUPPORT
184 bool "Support SPL loading and booting of RAW images"
185 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
186 default y if !TI_SECURE_DEVICE
188 SPL will support loading and booting a RAW image when this option
189 is y. If this is not set, SPL will move on to other available
190 boot media to find a suitable image.
192 config SPL_LEGACY_IMAGE_SUPPORT
193 bool "Support SPL loading and booting of Legacy images"
194 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
196 SPL will support loading and booting Legacy images when this option
197 is y. If this is not set, SPL will move on to other available
198 boot media to find a suitable image.
200 config SPL_LEGACY_IMAGE_CRC_CHECK
201 bool "Check CRC of Legacy images"
202 depends on SPL_LEGACY_IMAGE_SUPPORT
203 select SPL_CRC32_SUPPORT
205 Enable this to check the CRC of Legacy images. While this increases
206 reliability, it affects both code size and boot duration.
207 If disabled, Legacy images are booted if the image magic and size
208 are correct, without further integrity checks.
210 config SPL_SYS_MALLOC_SIMPLE
212 prompt "Only use malloc_simple functions in the SPL"
214 Say Y here to only use the *_simple malloc functions from
215 malloc_simple.c, rather then using the versions from dlmalloc.c;
216 this will make the SPL binary smaller at the cost of more heap
217 usage as the *_simple malloc functions do not re-use free-ed mem.
219 config TPL_SYS_MALLOC_SIMPLE
221 prompt "Only use malloc_simple functions in the TPL"
224 Say Y here to only use the *_simple malloc functions from
225 malloc_simple.c, rather then using the versions from dlmalloc.c;
226 this will make the TPL binary smaller at the cost of more heap
227 usage as the *_simple malloc functions do not re-use free-ed mem.
230 bool "Enable SDRAM location for SPL stack"
232 SPL starts off execution in SRAM and thus typically has only a small
233 stack available. Since SPL sets up DRAM while in its board_init_f()
234 function, it is possible for the stack to move there before
235 board_init_r() is reached. This option enables a special SDRAM
236 location for the SPL stack. U-Boot SPL switches to this after
237 board_init_f() completes, and before board_init_r() starts.
239 config SPL_STACK_R_ADDR
240 depends on SPL_STACK_R
241 hex "SDRAM location for SPL stack"
242 default 0x82000000 if ARCH_OMAP2PLUS
244 Specify the address in SDRAM for the SPL stack. This will be set up
245 before board_init_r() is called.
247 config SPL_STACK_R_MALLOC_SIMPLE_LEN
248 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
249 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
252 Specify the amount of the stack to use as memory pool for
253 malloc_simple after switching the stack to DRAM. This may be set
254 to give board_init_r() a larger heap then the initial heap in
255 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
257 config SPL_SEPARATE_BSS
258 bool "BSS section is in a different memory region from text"
260 Some platforms need a large BSS region in SPL and can provide this
261 because RAM is already set up. In this case BSS can be moved to RAM.
262 This option should then be enabled so that the correct device tree
263 location is used. Normally we put the device tree at the end of BSS
264 but with this option enabled, it goes at _image_binary_end.
266 config SPL_BANNER_PRINT
267 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
270 If this option is enabled, SPL will print the banner with version
271 info. Disabling this option could be useful to reduce TPL boot time
272 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
274 config TPL_BANNER_PRINT
275 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
279 If this option is enabled, SPL will not print the banner with version
280 info. Disabling this option could be useful to reduce SPL boot time
281 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
284 depends on ARM && !ARM64
285 bool "Allows initializing BSS early before entering board_init_f"
287 On some platform we have sufficient memory available early on to
288 allow setting up and using a basic BSS prior to entering
289 board_init_f. Activating this option will also de-activate the
290 clearing of BSS during the SPL relocation process, thus allowing
291 to carry state from board_init_f to board_init_r by way of BSS.
293 config SPL_DISPLAY_PRINT
294 bool "Display a board-specific message in SPL"
296 If this option is enabled, U-Boot will call the function
297 spl_display_print() immediately after displaying the SPL console
298 banner ("U-Boot SPL ..."). This function should be provided by
301 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
302 bool "MMC raw mode: by sector"
303 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
304 ARCH_MX6 || ARCH_MX7 || \
305 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
306 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
307 OMAP44XX || OMAP54XX || AM33XX || AM43XX
309 Use sector number for specifying U-Boot location on MMC/SD in
312 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
313 hex "Address on the MMC to load U-Boot from"
314 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
315 default 0x50 if ARCH_SUNXI
316 default 0x75 if ARCH_DAVINCI
317 default 0x8a if ARCH_MX6 || ARCH_MX7
318 default 0x100 if ARCH_UNIPHIER
319 default 0x140 if ARCH_MVEBU
320 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
321 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
322 OMAP54XX || AM33XX || AM43XX || ARCH_K3
323 default 0x4000 if ARCH_ROCKCHIP
325 Address on the MMC to load U-Boot from, when the MMC is being used
326 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
328 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
329 int "Number of the eMMC boot partition to use"
332 eMMC boot partition number to use when the eMMC in raw mode.
334 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
335 bool "MMC Raw mode: by partition"
337 Use a partition for loading U-Boot when using MMC/SD in raw mode.
339 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
340 hex "Partition to use to load U-Boot from"
341 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
344 Partition on the MMC to load U-Boot from when the MMC is being
347 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
348 bool "MMC raw mode: by partition type"
349 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
351 Use partition type for specifying U-Boot partition on MMC/SD in
352 raw mode. U-Boot will be loaded from the first partition of this
355 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
356 hex "Partition Type on the MMC to load U-Boot from"
357 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
359 Partition Type on the MMC to load U-Boot from, when the MMC is being
362 config SPL_CRC32_SUPPORT
364 default y if SPL_LEGACY_IMAGE_SUPPORT
366 Enable this to support CRC32 in uImages or FIT images within SPL.
367 This is a 32-bit checksum value that can be used to verify images.
368 For FIT images, this is the least secure type of checksum, suitable
369 for detected accidental image corruption. For secure applications you
370 should consider SHA1 or SHA256.
372 config SPL_MD5_SUPPORT
376 Enable this to support MD5 in FIT images within SPL. An MD5
377 checksum is a 128-bit hash value used to check that the image
378 contents have not been corrupted. Note that MD5 is not considered
379 secure as it is possible (with a brute-force attack) to adjust the
380 image while still retaining the same MD5 hash value. For secure
381 applications where images may be changed maliciously, you should
382 consider SHA1 or SHA256.
384 config SPL_SHA1_SUPPORT
389 Enable this to support SHA1 in FIT images within SPL. A SHA1
390 checksum is a 160-bit (20-byte) hash value used to check that the
391 image contents have not been corrupted or maliciously altered.
392 While SHA1 is fairly secure it is coming to the end of its life
393 due to the expanding computing power available to brute-force
394 attacks. For more security, consider SHA256.
396 config SPL_SHA256_SUPPORT
397 bool "Support SHA256"
401 Enable this to support SHA256 in FIT images within SPL. A SHA256
402 checksum is a 256-bit (32-byte) hash value used to check that the
403 image contents have not been corrupted. SHA256 is recommended for
404 use in secure applications since (as at 2016) there is no known
405 feasible attack that could produce a 'collision' with differing
406 input data. Use this for the highest security. Note that only the
407 SHA256 variant is supported: SHA512 and others are not currently
410 config SPL_FIT_IMAGE_TINY
411 bool "Remove functionality from SPL FIT loading to reduce size"
413 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
414 default y if ARCH_IMX8M
416 Enable this to reduce the size of the FIT image loading code
417 in SPL, if space for the SPL binary is very tight.
419 This removes the detection of image types (which forces the
420 first image to be treated as having a U-Boot style calling
421 convention) and skips the recording of each loaded payload
422 (i.e. loadable) into the FDT (modifying the loaded FDT to
423 ensure this information is available to the next image
426 config SPL_CPU_SUPPORT
427 bool "Support CPU drivers"
429 Enable this to support CPU drivers in SPL. These drivers can set
430 up CPUs and provide information about them such as the model and
431 name. This can be useful in SPL since setting up the CPUs earlier
432 may improve boot performance. Enable this option to build the
433 drivers in drivers/cpu as part of an SPL build.
435 config SPL_CRYPTO_SUPPORT
436 bool "Support crypto drivers"
438 Enable crypto drivers in SPL. These drivers can be used to
439 accelerate secure boot processing in secure applications. Enable
440 this option to build the drivers in drivers/crypto as part of an
443 config SPL_HASH_SUPPORT
444 bool "Support hashing drivers"
448 Enable hashing drivers in SPL. These drivers can be used to
449 accelerate secure boot processing in secure applications. Enable
450 this option to build system-specific drivers for hash acceleration
451 as part of an SPL build.
453 config TPL_HASH_SUPPORT
454 bool "Support hashing drivers in TPL"
459 Enable hashing drivers in SPL. These drivers can be used to
460 accelerate secure boot processing in secure applications. Enable
461 this option to build system-specific drivers for hash acceleration
462 as part of an SPL build.
464 config SPL_DMA_SUPPORT
465 bool "Support DMA drivers"
467 Enable DMA (direct-memory-access) drivers in SPL. These drivers
468 can be used to handle memory-to-peripheral data transfer without
469 the CPU moving the data. Enable this option to build the drivers
470 in drivers/dma as part of an SPL build.
472 config SPL_DRIVERS_MISC_SUPPORT
473 bool "Support misc drivers"
475 Enable miscellaneous drivers in SPL. These drivers perform various
476 tasks that don't fall nicely into other categories, Enable this
477 option to build the drivers in drivers/misc as part of an SPL
478 build, for those that support building in SPL (not all drivers do).
480 config SPL_ENV_SUPPORT
481 bool "Support an environment"
483 Enable environment support in SPL. The U-Boot environment provides
484 a number of settings (essentially name/value pairs) which can
485 control many aspects of U-Boot's operation. Normally this is not
486 needed in SPL as it has a much simpler task with less
487 configuration. But some boards use this to support 'Falcon' boot
488 on EXT2 and FAT, where SPL boots directly into Linux without
489 starting U-Boot first. Enabling this option will make env_get()
490 and env_set() available in SPL.
493 bool "Support save environment"
494 depends on SPL_ENV_SUPPORT
495 select SPL_MMC_WRITE if ENV_IS_IN_MMC
497 Enable save environment support in SPL after setenv. By default
498 the saveenv option is not provided in SPL, but some boards need
499 this support in 'Falcon' boot, where SPL need to boot from
500 different images based on environment variable set by OS. For
501 example OS may set "reboot_image" environment variable to
502 "recovery" inorder to boot recovery image by SPL. The SPL read
503 "reboot_image" and act accordingly and change the reboot_image
504 to default mode using setenv and save the environment.
506 config SPL_ETH_SUPPORT
507 bool "Support Ethernet"
508 depends on SPL_ENV_SUPPORT
510 Enable access to the network subsystem and associated Ethernet
511 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
512 link rather than from an on-board peripheral. Environment support
513 is required since the network stack uses a number of environment
514 variables. See also SPL_NET_SUPPORT.
517 bool "Support EXT filesystems"
519 Enable support for EXT2/3/4 filesystems with SPL. This permits
520 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
521 filesystem from within SPL. Support for the underlying block
522 device (e.g. MMC or USB) must be enabled separately.
525 bool "Support FAT filesystems"
528 Enable support for FAT and VFAT filesystems with SPL. This
529 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
530 filesystem from within SPL. Support for the underlying block
531 device (e.g. MMC or USB) must be enabled separately.
534 bool "Support write for FAT filesystems"
536 Enable write support for FAT and VFAT filesystems with SPL.
537 Support for the underlying block device (e.g. MMC or USB) must be
540 config SPL_FPGA_SUPPORT
543 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
544 provide software-configurable hardware which is typically used to
545 implement peripherals (such as UARTs, LCD displays, MMC) or
546 accelerate custom processing functions, such as image processing
547 or machine learning. Sometimes it is useful to program the FPGA
548 as early as possible during boot, and this option can enable that
551 config SPL_GPIO_SUPPORT
552 bool "Support GPIO in SPL"
554 Enable support for GPIOs (General-purpose Input/Output) in SPL.
555 GPIOs allow U-Boot to read the state of an input line (high or
556 low) and set the state of an output line. This can be used to
557 drive LEDs, control power to various system parts and read user
558 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
559 for example. Enable this option to build the drivers in
560 drivers/gpio as part of an SPL build.
562 config SPL_I2C_SUPPORT
565 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
566 I2C works with a clock and data line which can be driven by a
567 one or more masters or slaves. It is a fairly complex bus but is
568 widely used as it only needs two lines for communication. Speeds of
569 400kbps are typical but up to 3.4Mbps is supported by some
570 hardware. I2C can be useful in SPL to configure power management
571 ICs (PMICs) before raising the CPU clock speed, for example.
572 Enable this option to build the drivers in drivers/i2c as part of
575 config SPL_LIBCOMMON_SUPPORT
576 bool "Support common libraries"
578 Enable support for common U-Boot libraries within SPL. These
579 libraries include common code to deal with U-Boot images,
580 environment and USB, for example. This option is enabled on many
581 boards. Enable this option to build the code in common/ as part of
584 config SPL_LIBDISK_SUPPORT
585 bool "Support disk partitions"
588 Enable support for disk partitions within SPL. 'Disk' is something
589 of a misnomer as it includes non-spinning media such as flash (as
590 used in MMC and USB sticks). Partitions provide a way for a disk
591 to be split up into separate regions, with a partition table placed
592 at the start or end which describes the location and size of each
593 'partition'. These partitions are typically uses as individual block
594 devices, typically with an EXT2 or FAT filesystem in each. This
595 option enables whatever partition support has been enabled in
596 U-Boot to also be used in SPL. It brings in the code in disk/.
598 config SPL_LIBGENERIC_SUPPORT
599 bool "Support generic libraries"
601 Enable support for generic U-Boot libraries within SPL. These
602 libraries include generic code to deal with device tree, hashing,
603 printf(), compression and the like. This option is enabled on many
604 boards. Enable this option to build the code in lib/ as part of an
607 config SPL_DM_MAILBOX
608 bool "Support Mailbox"
610 Enable support for Mailbox within SPL. This enable the inter
611 processor communication protocols tobe used within SPL. Enable
612 this option to build the drivers in drivers/mailbox as part of
615 config SPL_MMC_SUPPORT
618 select HAVE_BLOCK_DEVICE
620 Enable support for MMC (Multimedia Card) within SPL. This enables
621 the MMC protocol implementation and allows any enabled drivers to
622 be used within SPL. MMC can be used with or without disk partition
623 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
624 this option to build the drivers in drivers/mmc as part of an SPL
627 config SPL_FORCE_MMC_BOOT
628 bool "Force SPL booting from MMC"
629 depends on SPL_MMC_SUPPORT
632 Force SPL to use MMC device for Linux kernel booting even when the
633 SoC ROM recognized boot medium is not eMMC/SD. This is crucial for
634 factory or 'falcon mode' booting.
637 bool "Tiny MMC framework in SPL"
638 depends on SPL_MMC_SUPPORT
641 Enable MMC framework tinification support. This option is useful if
642 if your SPL is extremely size constrained. Heed the warning, enable
643 this option if and only if you know exactly what you are doing, if
644 you are reading this help text, you most likely have no idea :-)
646 The MMC framework is reduced to bare minimum to be useful. No malloc
647 support is needed for the MMC framework operation with this option
648 enabled. The framework supports exactly one MMC device and exactly
649 one MMC driver. The MMC driver can be adjusted to avoid any malloc
650 operations too, which can remove the need for malloc support in SPL
651 and thus further reduce footprint.
654 bool "MMC/SD/SDIO card support for write operations in SPL"
655 depends on SPL_MMC_SUPPORT
658 Enable write access to MMC and SD Cards in SPL
661 config SPL_MPC8XXX_INIT_DDR_SUPPORT
662 bool "Support MPC8XXX DDR init"
664 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
665 random-access memory) on the MPC8XXX family within SPL. This
666 allows DRAM to be set up before loading U-Boot into that DRAM,
669 config SPL_MTD_SUPPORT
670 bool "Support MTD drivers"
672 Enable support for MTD (Memory Technology Device) within SPL. MTD
673 provides a block interface over raw NAND and can also be used with
674 SPI flash. This allows SPL to load U-Boot from supported MTD
675 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
676 to enable specific MTD drivers.
678 config SPL_MUSB_NEW_SUPPORT
679 bool "Support new Mentor Graphics USB"
681 Enable support for Mentor Graphics USB in SPL. This is a new
682 driver used by some boards. Enable this option to build
683 the drivers in drivers/usb/musb-new as part of an SPL build. The
684 old drivers are in drivers/usb/musb.
686 config SPL_NAND_SUPPORT
687 bool "Support NAND flash"
689 Enable support for NAND (Negative AND) flash in SPL. NAND flash
690 can be used to allow SPL to load U-Boot from supported devices.
691 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
697 Enable support for loading payloads from UBI. See
698 README.ubispl for more info.
702 bool "Support SPI DM drivers in SPL"
704 Enable support for SPI DM drivers in SPL.
708 config SPL_UBI_LOAD_BY_VOLNAME
709 bool "Support loading volumes by name"
711 This enables support for loading UBI volumes by name. When this
712 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
713 configure the volume name from which to load U-Boot.
715 config SPL_UBI_MAX_VOL_LEBS
716 int "Maximum number of LEBs per volume"
719 The maximum number of logical eraseblocks which a static volume
720 to load can contain. Used for sizing the scan data structure.
722 config SPL_UBI_MAX_PEB_SIZE
723 int "Maximum PEB size"
726 The maximum physical erase block size.
728 config SPL_UBI_MAX_PEBS
729 int "Maximum number of PEBs"
732 The maximum physical erase block size. If not overridden by
733 board code, this value will be used as the actual number of PEBs.
735 config SPL_UBI_PEB_OFFSET
736 int "Offset to first UBI PEB"
739 The offset in number of PEBs from the start of flash to the first
740 PEB part of the UBI image.
742 config SPL_UBI_VID_OFFSET
743 int "Offset to VID header"
746 config SPL_UBI_LEB_START
747 int "Offset to LEB in PEB"
750 The offset in bytes to the LEB within a PEB.
752 config SPL_UBI_INFO_ADDR
753 hex "Address to place UBI scan info"
756 Address for ubispl to place the scan info. Read README.ubispl to
757 determine the required size
759 config SPL_UBI_VOL_IDS
760 int "Maximum volume id"
763 The maximum volume id which can be loaded. Used for sizing the
766 config SPL_UBI_LOAD_MONITOR_ID
767 int "id of U-Boot volume"
770 The UBI volume id from which to load U-Boot
772 config SPL_UBI_LOAD_MONITOR_VOLNAME
773 string "volume name of U-Boot volume"
774 depends on SPL_UBI_LOAD_BY_VOLNAME
776 The UBI volume name from which to load U-Boot
778 config SPL_UBI_LOAD_KERNEL_ID
779 int "id of kernel volume"
780 depends on SPL_OS_BOOT && SPL_UBI
782 The UBI volume id from which to load the kernel
784 config SPL_UBI_LOAD_ARGS_ID
785 int "id of kernel args volume"
786 depends on SPL_OS_BOOT && SPL_UBI
788 The UBI volume id from which to load the device tree
790 config UBI_SPL_SILENCE_MSG
791 bool "silence UBI SPL messages"
794 Disable messages from UBI SPL. This leaves warnings
799 config SPL_NET_SUPPORT
800 bool "Support networking"
802 Enable support for network devices (such as Ethernet) in SPL.
803 This permits SPL to load U-Boot over a network link rather than
804 from an on-board peripheral. Environment support is required since
805 the network stack uses a number of environment variables. See also
809 config SPL_NET_VCI_STRING
810 string "BOOTP Vendor Class Identifier string sent by SPL"
812 As defined by RFC 2132 the vendor class identifier field can be
813 sent by the client to identify the vendor type and configuration
814 of a client. This is often used in practice to allow for the DHCP
815 server to specify different files to load depending on if the ROM,
816 SPL or U-Boot itself makes the request
817 endif # if SPL_NET_SUPPORT
819 config SPL_NO_CPU_SUPPORT
820 bool "Drop CPU code in SPL"
822 This is specific to the ARM926EJ-S CPU. It disables the standard
823 start.S start-up code, presumably so that a replacement can be
824 used on that CPU. You should not enable it unless you know what
827 config SPL_NOR_SUPPORT
828 bool "Support NOR flash"
830 Enable support for loading U-Boot from memory-mapped NOR (Negative
831 OR) flash in SPL. NOR flash is slow to write but fast to read, and
832 a memory-mapped device makes it very easy to access. Loading from
833 NOR is typically achieved with just a memcpy().
835 config SPL_XIP_SUPPORT
839 Enable support for execute in place of U-Boot or kernel image. There
840 is no need to copy image from flash to ram if flash supports execute
841 in place. Its very useful in systems having enough flash but not
842 enough ram to load the image.
844 config SPL_ONENAND_SUPPORT
845 bool "Support OneNAND flash"
847 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
848 a type of NAND flash and therefore can be used to allow SPL to
849 load U-Boot from supported devices. This enables the drivers in
850 drivers/mtd/onenand as part of an SPL build.
853 bool "Activate Falcon Mode"
854 depends on !TI_SECURE_DEVICE
857 Enable booting directly to an OS from SPL.
858 for more info read doc/README.falcon
862 hex "addr, where OS is found"
863 depends on SPL_NOR_SUPPORT
865 Specify the address, where the OS image is found, which
872 default "tpl/u-boot-with-tpl.bin" if TPL
875 Payload for SPL boot. For backward compatibility, default to
876 u-boot.bin, i.e. RAW image without any header. In case of
877 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
881 bool "Support PCI drivers"
883 Enable support for PCI in SPL. For platforms that need PCI to boot,
884 or must perform some init using PCI in SPL, this provides the
885 necessary driver support. This enables the drivers in drivers/pci
886 as part of an SPL build.
888 config SPL_PCH_SUPPORT
889 bool "Support PCH drivers"
891 Enable support for PCH (Platform Controller Hub) devices in SPL.
892 These are used to set up GPIOs and the SPI peripheral early in
893 boot. This enables the drivers in drivers/pch as part of an SPL
896 config SPL_POST_MEM_SUPPORT
897 bool "Support POST drivers"
899 Enable support for POST (Power-on Self Test) in SPL. POST is a
900 procedure that checks that the hardware (CPU or board) appears to
901 be functionally correctly. It is a sanity check that can be
902 performed before booting. This enables the drivers in post/drivers
903 as part of an SPL build.
906 bool "Support reset drivers"
909 Enable support for reset control in SPL.
910 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
911 by using the generic reset API provided by driver model.
912 This enables the drivers in drivers/reset as part of an SPL build.
914 config SPL_POWER_SUPPORT
915 bool "Support power drivers"
917 Enable support for power control in SPL. This includes support
918 for PMICs (Power-management Integrated Circuits) and some of the
919 features provided by PMICs. In particular, voltage regulators can
920 be used to enable/disable power and vary its voltage. That can be
921 useful in SPL to turn on boot peripherals and adjust CPU voltage
922 so that the clock speed can be increased. This enables the drivers
923 in drivers/power, drivers/power/pmic and drivers/power/regulator
924 as part of an SPL build.
926 config SPL_POWER_DOMAIN
927 bool "Support power domain drivers"
929 Enable support for power domain control in SPL. Many SoCs allow
930 power to be applied to or removed from portions of the SoC (power
931 domains). This may be used to save power. This API provides the
932 means to control such power management hardware. This enables
933 the drivers in drivers/power/domain as part of a SPL build.
935 config SPL_RAM_SUPPORT
936 bool "Support booting from RAM"
937 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
939 Enable booting of an image in RAM. The image can be preloaded or
940 it can be loaded by SPL directly into RAM (e.g. using USB).
942 config SPL_RAM_DEVICE
943 bool "Support booting from preloaded image in RAM"
944 depends on SPL_RAM_SUPPORT
945 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
947 Enable booting of an image already loaded in RAM. The image has to
948 be already in memory when SPL takes over, e.g. loaded by the boot
951 config SPL_REMOTEPROC
952 bool "Support REMOTEPROCS"
954 Enable support for REMOTEPROCs in SPL. This permits to load
955 a remote processor firmware in SPL.
957 config SPL_RTC_SUPPORT
958 bool "Support RTC drivers"
960 Enable RTC (Real-time Clock) support in SPL. This includes support
961 for reading and setting the time. Some RTC devices also have some
962 non-volatile (battery-backed) memory which is accessible if
963 needed. This enables the drivers in drivers/rtc as part of an SPL
966 config SPL_SATA_SUPPORT
967 bool "Support loading from SATA"
969 Enable support for SATA (Serial AT attachment) in SPL. This allows
970 use of SATA devices such as hard drives and flash drivers for
971 loading U-Boot. SATA is used in higher-end embedded systems and
972 can provide higher performance than MMC , at somewhat higher
973 expense and power consumption. This enables loading from SATA
974 using a configured device.
976 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
977 bool "SATA raw mode: by sector"
978 depends on SPL_SATA_SUPPORT
980 Use sector number for specifying U-Boot location on SATA disk in
983 config SPL_SATA_RAW_U_BOOT_SECTOR
984 hex "Sector on the SATA disk to load U-Boot from"
985 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
987 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
988 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
990 config SPL_SERIAL_SUPPORT
991 bool "Support serial"
995 Enable support for serial in SPL. This allows use of a serial UART
996 for displaying messages while SPL is running. It also brings in
997 printf() and panic() functions. This should normally be enabled
998 unless there are space reasons not to. Even then, consider
999 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1001 config SPL_SPI_FLASH_SUPPORT
1002 bool "Support SPI flash drivers"
1004 Enable support for using SPI flash in SPL, and loading U-Boot from
1005 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1006 the SPI bus that is used to connect it to a system. It is a simple
1007 but fast bidirectional 4-wire bus (clock, chip select and two data
1008 lines). This enables the drivers in drivers/mtd/spi as part of an
1009 SPL build. This normally requires SPL_SPI_SUPPORT.
1011 if SPL_SPI_FLASH_SUPPORT
1013 config SPL_SPI_FLASH_TINY
1014 bool "Enable low footprint SPL SPI Flash support"
1015 depends on !SPI_FLASH_BAR
1016 default y if SPI_FLASH
1018 Enable lightweight SPL SPI Flash support that supports just reading
1019 data/images from flash. No support to write/erase flash. Enable
1020 this if you have SPL size limitations and don't need full
1021 fledged SPI flash support.
1023 config SPL_SPI_FLASH_SFDP_SUPPORT
1024 bool "SFDP table parsing support for SPI NOR flashes"
1025 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1027 Enable support for parsing and auto discovery of parameters for
1028 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1029 tables as per JESD216 standard in SPL.
1032 bool "Support loading from SPI flash"
1034 Enable support for loading next stage, U-Boot or otherwise, from
1035 SPI NOR in U-Boot SPL.
1037 endif # SPL_SPI_FLASH_SUPPORT
1039 config SYS_SPI_U_BOOT_OFFS
1040 hex "address of u-boot payload in SPI flash"
1042 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1044 Address within SPI-Flash from where the u-boot payload is fetched
1047 config SPL_SPI_SUPPORT
1048 bool "Support SPI drivers"
1050 Enable support for using SPI in SPL. This is used for connecting
1051 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1052 more details on that. The SPI driver provides the transport for
1053 data between the SPI flash and the CPU. This option can be used to
1054 enable SPI drivers that are needed for other purposes also, such
1058 bool "Driver support for thermal devices"
1060 Enable support for temperature-sensing devices. Some SoCs have on-chip
1061 temperature sensors to permit warnings, speed throttling or even
1062 automatic power-off when the temperature gets too high or low. Other
1063 devices may be discrete but connected on a suitable bus.
1065 config SPL_USB_HOST_SUPPORT
1066 bool "Support USB host drivers"
1067 select HAVE_BLOCK_DEVICE
1069 Enable access to USB (Universal Serial Bus) host devices so that
1070 SPL can load U-Boot from a connected USB peripheral, such as a USB
1071 flash stick. While USB takes a little longer to start up than most
1072 buses, it is very flexible since many different types of storage
1073 device can be attached. This option enables the drivers in
1074 drivers/usb/host as part of an SPL build.
1076 config SPL_USB_STORAGE
1077 bool "Support loading from USB"
1078 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1080 Enable support for USB devices in SPL. This allows use of USB
1081 devices such as hard drives and flash drivers for loading U-Boot.
1082 The actual drivers are enabled separately using the normal U-Boot
1083 config options. This enables loading from USB using a configured
1086 config SPL_USB_GADGET
1087 bool "Suppport USB Gadget drivers"
1089 Enable USB Gadget API which allows to enable USB device functions
1094 config SPL_USB_ETHER
1095 bool "Support USB Ethernet drivers"
1097 Enable access to the USB network subsystem and associated
1098 drivers in SPL. This permits SPL to load U-Boot over a
1099 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1100 than from an onboard peripheral. Environment support is required
1101 since the network stack uses a number of environment variables.
1102 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1105 bool "Support DFU (Device Firmware Upgrade)"
1106 select SPL_HASH_SUPPORT
1107 select SPL_DFU_NO_RESET
1108 depends on SPL_RAM_SUPPORT
1110 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1111 RAM memory device support. The ROM code will load and execute
1112 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1113 selected device partition from host-pc using dfu-utils.
1114 This feature is useful to flash the binaries to factory or bare-metal
1115 boards using USB interface.
1118 bool "DFU device selection"
1123 depends on SPL_DFU && SPL_RAM_SUPPORT
1125 select RAM/DDR memory device for loading binary images
1126 (u-boot/kernel) to the selected device partition using
1127 DFU and execute the u-boot/kernel from RAM.
1131 config SPL_USB_SDP_SUPPORT
1132 bool "Support SDP (Serial Download Protocol)"
1134 Enable Serial Download Protocol (SDP) device support in SPL. This
1135 allows to download images into memory and execute (jump to) them
1136 using the same protocol as implemented by the i.MX family's boot ROM.
1139 config SPL_WATCHDOG_SUPPORT
1140 bool "Support watchdog drivers"
1141 imply SPL_WDT if !HW_WATCHDOG
1143 Enable support for watchdog drivers in SPL. A watchdog is
1144 typically a hardware peripheral which can reset the system when it
1145 detects no activity for a while (such as a software crash). This
1146 enables the drivers in drivers/watchdog as part of an SPL build.
1148 config SPL_YMODEM_SUPPORT
1149 bool "Support loading using Ymodem"
1150 depends on SPL_SERIAL_SUPPORT
1152 While loading from serial is slow it can be a useful backup when
1153 there is no other option. The Ymodem protocol provides a reliable
1154 means of transmitting U-Boot over a serial line for using in SPL,
1155 with a checksum to ensure correctness.
1158 bool "Support ARM Trusted Firmware"
1161 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1162 is loaded by SPL (which is considered as BL2 in ATF terminology).
1163 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1165 config SPL_ATF_NO_PLATFORM_PARAM
1166 bool "Pass no platform parameter"
1169 While we expect to call a pointer to a valid FDT (or NULL)
1170 as the platform parameter to an ATF, some ATF versions are
1171 not U-Boot aware and have an insufficiently robust parameter
1172 validation to gracefully reject a FDT being passed.
1174 If this option is enabled, the spl_atf os-type handler will
1175 always pass NULL for the platform parameter.
1177 If your ATF is affected, say Y.
1179 config SPL_AM33XX_ENABLE_RTC32K_OSC
1180 bool "Enable the RTC32K OSC on AM33xx based platforms"
1183 Enable access to the AM33xx RTC and select the external 32kHz clock
1187 bool "Support OP-TEE Trusted OS"
1190 OP-TEE is an open source Trusted OS which is loaded by SPL.
1191 More detail at: https://github.com/OP-TEE/optee_os
1194 bool "Support RISC-V OpenSBI"
1195 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1197 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1198 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1199 firmware. It is loaded and started by U-Boot SPL.
1201 More details are available at https://github.com/riscv/opensbi and
1202 https://github.com/riscv/riscv-sbi-doc
1204 config SPL_OPENSBI_LOAD_ADDR
1205 hex "OpenSBI load address"
1206 depends on SPL_OPENSBI
1208 Load address of the OpenSBI binary.
1212 depends on SUPPORT_TPL
1215 If you want to build TPL as well as the normal image and SPL, say Y.
1220 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1221 depends on HANDOFF && TPL_BLOBLIST
1224 This option enables TPL to write handoff information. This can be
1225 used to pass information like the size of SDRAM from TPL to U-Boot
1226 proper. The information is also available to SPL if it is useful
1229 config TPL_BOARD_INIT
1230 bool "Call board-specific initialization in TPL"
1232 If this option is enabled, U-Boot will call the function
1233 spl_board_init() from board_init_r(). This function should be
1234 provided by the board.
1237 string "Linker script for the TPL stage"
1239 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1240 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1242 The TPL stage will usually require a different linker-script
1243 (as it runs from a different memory region) than the regular
1244 U-Boot stage. Set this to the path of the linker-script to
1247 May be left empty to trigger the Makefile infrastructure to
1248 fall back to the linker-script used for the SPL stage.
1250 config TPL_NEEDS_SEPARATE_TEXT_BASE
1251 bool "TPL needs a separate text-base"
1255 Enable, if the TPL stage should not inherit its text-base
1256 from the SPL stage. When enabled, a base address for the
1257 .text sections of the TPL stage has to be set below.
1259 config TPL_NEEDS_SEPARATE_STACK
1260 bool "TPL needs a separate initial stack-pointer"
1264 Enable, if the TPL stage should not inherit its initial
1265 stack-pointer from the settings for the SPL stage.
1267 config TPL_TEXT_BASE
1268 hex "Base address for the .text section of the TPL stage"
1269 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1271 The base address for the .text section of the TPL stage.
1274 int "Maximum size (in bytes) for the TPL stage"
1278 The maximum size (in bytes) of the TPL stage.
1281 hex "Address of the initial stack-pointer for the TPL stage"
1282 depends on TPL_NEEDS_SEPARATE_STACK
1284 The address of the initial stack-pointer for the TPL stage.
1285 Usually this will be the (aligned) top-of-stack.
1287 config TPL_BOOTROM_SUPPORT
1288 bool "Support returning to the BOOTROM (from TPL)"
1290 Some platforms (e.g. the Rockchip RK3368) provide support in their
1291 ROM for loading the next boot-stage after performing basic setup
1294 Enable this option, to return to the BOOTROM through the
1295 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1296 boot device list, if not implemented for a given board)
1298 config TPL_DRIVERS_MISC_SUPPORT
1299 bool "Support misc drivers in TPL"
1301 Enable miscellaneous drivers in TPL. These drivers perform various
1302 tasks that don't fall nicely into other categories, Enable this
1303 option to build the drivers in drivers/misc as part of an TPL
1304 build, for those that support building in TPL (not all drivers do).
1306 config TPL_ENV_SUPPORT
1307 bool "Support an environment"
1309 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1311 config TPL_GPIO_SUPPORT
1312 bool "Support GPIO in TPL"
1314 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1315 GPIOs allow U-Boot to read the state of an input line (high or
1316 low) and set the state of an output line. This can be used to
1317 drive LEDs, control power to various system parts and read user
1318 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1319 for example. Enable this option to build the drivers in
1320 drivers/gpio as part of an TPL build.
1322 config TPL_I2C_SUPPORT
1325 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1328 config TPL_LIBCOMMON_SUPPORT
1329 bool "Support common libraries"
1331 Enable support for common U-Boot libraries within TPL. See
1332 SPL_LIBCOMMON_SUPPORT for details.
1334 config TPL_LIBGENERIC_SUPPORT
1335 bool "Support generic libraries"
1337 Enable support for generic U-Boot libraries within TPL. See
1338 SPL_LIBGENERIC_SUPPORT for details.
1340 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1341 bool "Support MPC8XXX DDR init"
1343 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1344 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1346 config TPL_MMC_SUPPORT
1350 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1352 config TPL_NAND_SUPPORT
1353 bool "Support NAND flash"
1355 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1358 bool "Support PCI drivers"
1360 Enable support for PCI in TPL. For platforms that need PCI to boot,
1361 or must perform some init using PCI in SPL, this provides the
1362 necessary driver support. This enables the drivers in drivers/pci
1363 as part of a TPL build.
1365 config TPL_PCH_SUPPORT
1366 bool "Support PCH drivers"
1368 Enable support for PCH (Platform Controller Hub) devices in TPL.
1369 These are used to set up GPIOs and the SPI peripheral early in
1370 boot. This enables the drivers in drivers/pch as part of a TPL
1373 config TPL_RAM_SUPPORT
1374 bool "Support booting from RAM"
1376 Enable booting of an image in RAM. The image can be preloaded or
1377 it can be loaded by TPL directly into RAM (e.g. using USB).
1379 config TPL_RAM_DEVICE
1380 bool "Support booting from preloaded image in RAM"
1381 depends on TPL_RAM_SUPPORT
1383 Enable booting of an image already loaded in RAM. The image has to
1384 be already in memory when TPL takes over, e.g. loaded by the boot
1387 config TPL_RTC_SUPPORT
1388 bool "Support RTC drivers"
1390 Enable RTC (Real-time Clock) support in TPL. This includes support
1391 for reading and setting the time. Some RTC devices also have some
1392 non-volatile (battery-backed) memory which is accessible if
1393 needed. This enables the drivers in drivers/rtc as part of an TPL
1396 config TPL_SERIAL_SUPPORT
1397 bool "Support serial"
1401 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1404 config TPL_SPI_FLASH_SUPPORT
1405 bool "Support SPI flash drivers"
1407 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1411 bool "Support loading from SPI flash"
1412 depends on TPL_SPI_FLASH_SUPPORT
1414 Enable support for loading next stage, U-Boot or otherwise, from
1415 SPI NOR in U-Boot TPL.
1417 config TPL_SPI_SUPPORT
1418 bool "Support SPI drivers"
1420 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1423 config TPL_YMODEM_SUPPORT
1424 bool "Support loading using Ymodem"
1425 depends on TPL_SERIAL_SUPPORT
1427 While loading from serial is slow it can be a useful backup when
1428 there is no other option. The Ymodem protocol provides a reliable
1429 means of transmitting U-Boot over a serial line for using in TPL,
1430 with a checksum to ensure correctness.
1434 config SPL_AT91_MCK_BYPASS
1435 bool "Use external clock signal as a source of main clock for AT91 platforms"
1436 depends on ARCH_AT91
1439 Use external 8 to 24 Mhz clock signal as source of main clock instead
1440 of an external crystal oscillator.
1441 This option disables the internal driving on the XOUT pin.
1442 The external source has to provide a stable clock on the XIN pin.
1443 If this option is disabled, the SoC expects a crystal oscillator
1444 that needs driving on both XIN and XOUT lines.