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
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
329 Address on the MMC to load U-Boot from, when the MMC is being used
330 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
332 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
333 bool "MMC Raw mode: by partition"
335 Use a partition for loading U-Boot when using MMC/SD in raw mode.
337 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
338 hex "Partition to use to load U-Boot from"
339 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
342 Partition on the MMC to load U-Boot from when the MMC is being
345 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
346 bool "MMC raw mode: by partition type"
347 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
349 Use partition type for specifying U-Boot partition on MMC/SD in
350 raw mode. U-Boot will be loaded from the first partition of this
353 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
354 hex "Partition Type on the MMC to load U-Boot from"
355 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
357 Partition Type on the MMC to load U-Boot from, when the MMC is being
360 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
361 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
362 depends on SUPPORT_EMMC_BOOT
364 eMMC boot partition is normally configured by the bits of the EXT_CSD
365 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
366 cases it might be required in SPL to load the image from different
367 partition than the partition selected by EXT_CSC_PART_CONFIG register.
368 Enable this option if you intend to use an eMMC boot partition other
369 then selected via EXT_CSC_PART_CONFIG register and specify the custom
370 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
373 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
374 int "Number of the eMMC boot partition to use"
375 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
378 eMMC boot partition number to use when the eMMC in raw mode and
379 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
380 by user defined partition number.
382 config SPL_CRC32_SUPPORT
384 default y if SPL_LEGACY_IMAGE_SUPPORT
386 Enable this to support CRC32 in uImages or FIT images within SPL.
387 This is a 32-bit checksum value that can be used to verify images.
388 For FIT images, this is the least secure type of checksum, suitable
389 for detected accidental image corruption. For secure applications you
390 should consider SHA1 or SHA256.
392 config SPL_MD5_SUPPORT
396 Enable this to support MD5 in FIT images within SPL. An MD5
397 checksum is a 128-bit hash value used to check that the image
398 contents have not been corrupted. Note that MD5 is not considered
399 secure as it is possible (with a brute-force attack) to adjust the
400 image while still retaining the same MD5 hash value. For secure
401 applications where images may be changed maliciously, you should
402 consider SHA1 or SHA256.
404 config SPL_SHA1_SUPPORT
409 Enable this to support SHA1 in FIT images within SPL. A SHA1
410 checksum is a 160-bit (20-byte) hash value used to check that the
411 image contents have not been corrupted or maliciously altered.
412 While SHA1 is fairly secure it is coming to the end of its life
413 due to the expanding computing power available to brute-force
414 attacks. For more security, consider SHA256.
416 config SPL_SHA256_SUPPORT
417 bool "Support SHA256"
421 Enable this to support SHA256 in FIT images within SPL. A SHA256
422 checksum is a 256-bit (32-byte) hash value used to check that the
423 image contents have not been corrupted. SHA256 is recommended for
424 use in secure applications since (as at 2016) there is no known
425 feasible attack that could produce a 'collision' with differing
426 input data. Use this for the highest security. Note that only the
427 SHA256 variant is supported: SHA512 and others are not currently
430 config SPL_FIT_IMAGE_TINY
431 bool "Remove functionality from SPL FIT loading to reduce size"
433 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
434 default y if ARCH_IMX8M
436 Enable this to reduce the size of the FIT image loading code
437 in SPL, if space for the SPL binary is very tight.
439 This removes the detection of image types (which forces the
440 first image to be treated as having a U-Boot style calling
441 convention) and skips the recording of each loaded payload
442 (i.e. loadable) into the FDT (modifying the loaded FDT to
443 ensure this information is available to the next image
446 config SPL_CACHE_SUPPORT
447 bool "Support CACHE drivers"
449 Enable CACHE drivers in SPL. These drivers can keep data so that
450 future requests for that data can be served faster. Enable this option
451 to build the drivers in drivers/cache as part of an SPL build.
453 config SPL_CPU_SUPPORT
454 bool "Support CPU drivers"
456 Enable this to support CPU drivers in SPL. These drivers can set
457 up CPUs and provide information about them such as the model and
458 name. This can be useful in SPL since setting up the CPUs earlier
459 may improve boot performance. Enable this option to build the
460 drivers in drivers/cpu as part of an SPL build.
462 config SPL_CRYPTO_SUPPORT
463 bool "Support crypto drivers"
465 Enable crypto drivers in SPL. These drivers can be used to
466 accelerate secure boot processing in secure applications. Enable
467 this option to build the drivers in drivers/crypto as part of an
470 config SPL_HASH_SUPPORT
471 bool "Support hashing drivers"
475 Enable hashing drivers in SPL. These drivers can be used to
476 accelerate secure boot processing in secure applications. Enable
477 this option to build system-specific drivers for hash acceleration
478 as part of an SPL build.
480 config TPL_HASH_SUPPORT
481 bool "Support hashing drivers in TPL"
486 Enable hashing drivers in SPL. These drivers can be used to
487 accelerate secure boot processing in secure applications. Enable
488 this option to build system-specific drivers for hash acceleration
489 as part of an SPL build.
491 config SPL_DMA_SUPPORT
492 bool "Support DMA drivers"
494 Enable DMA (direct-memory-access) drivers in SPL. These drivers
495 can be used to handle memory-to-peripheral data transfer without
496 the CPU moving the data. Enable this option to build the drivers
497 in drivers/dma as part of an SPL build.
500 bool "Support Driver Model GPIO drivers"
501 depends on SPL_GPIO_SUPPORT && DM_GPIO
503 Enable support for Driver Model based GPIO drivers in SPL.
505 config SPL_DRIVERS_MISC_SUPPORT
506 bool "Support misc drivers"
508 Enable miscellaneous drivers in SPL. These drivers perform various
509 tasks that don't fall nicely into other categories, Enable this
510 option to build the drivers in drivers/misc as part of an SPL
511 build, for those that support building in SPL (not all drivers do).
513 config SPL_ENV_SUPPORT
514 bool "Support an environment"
516 Enable environment support in SPL. The U-Boot environment provides
517 a number of settings (essentially name/value pairs) which can
518 control many aspects of U-Boot's operation. Normally this is not
519 needed in SPL as it has a much simpler task with less
520 configuration. But some boards use this to support 'Falcon' boot
521 on EXT2 and FAT, where SPL boots directly into Linux without
522 starting U-Boot first. Enabling this option will make env_get()
523 and env_set() available in SPL.
526 bool "Support save environment"
527 depends on SPL_ENV_SUPPORT
528 select SPL_MMC_WRITE if ENV_IS_IN_MMC
530 Enable save environment support in SPL after setenv. By default
531 the saveenv option is not provided in SPL, but some boards need
532 this support in 'Falcon' boot, where SPL need to boot from
533 different images based on environment variable set by OS. For
534 example OS may set "reboot_image" environment variable to
535 "recovery" inorder to boot recovery image by SPL. The SPL read
536 "reboot_image" and act accordingly and change the reboot_image
537 to default mode using setenv and save the environment.
539 config SPL_ETH_SUPPORT
540 bool "Support Ethernet"
541 depends on SPL_ENV_SUPPORT
543 Enable access to the network subsystem and associated Ethernet
544 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
545 link rather than from an on-board peripheral. Environment support
546 is required since the network stack uses a number of environment
547 variables. See also SPL_NET_SUPPORT.
550 bool "Support EXT filesystems"
552 Enable support for EXT2/3/4 filesystems with SPL. This permits
553 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
554 filesystem from within SPL. Support for the underlying block
555 device (e.g. MMC or USB) must be enabled separately.
558 bool "Support FAT filesystems"
561 Enable support for FAT and VFAT filesystems with SPL. This
562 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
563 filesystem from within SPL. Support for the underlying block
564 device (e.g. MMC or USB) must be enabled separately.
567 bool "Support write for FAT filesystems"
569 Enable write support for FAT and VFAT filesystems with SPL.
570 Support for the underlying block device (e.g. MMC or USB) must be
573 config SPL_FPGA_SUPPORT
576 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
577 provide software-configurable hardware which is typically used to
578 implement peripherals (such as UARTs, LCD displays, MMC) or
579 accelerate custom processing functions, such as image processing
580 or machine learning. Sometimes it is useful to program the FPGA
581 as early as possible during boot, and this option can enable that
584 config SPL_GPIO_SUPPORT
585 bool "Support GPIO in SPL"
587 Enable support for GPIOs (General-purpose Input/Output) in SPL.
588 GPIOs allow U-Boot to read the state of an input line (high or
589 low) and set the state of an output line. This can be used to
590 drive LEDs, control power to various system parts and read user
591 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
592 for example. Enable this option to build the drivers in
593 drivers/gpio as part of an SPL build.
595 config SPL_I2C_SUPPORT
598 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
599 I2C works with a clock and data line which can be driven by a
600 one or more masters or slaves. It is a fairly complex bus but is
601 widely used as it only needs two lines for communication. Speeds of
602 400kbps are typical but up to 3.4Mbps is supported by some
603 hardware. I2C can be useful in SPL to configure power management
604 ICs (PMICs) before raising the CPU clock speed, for example.
605 Enable this option to build the drivers in drivers/i2c as part of
608 config SPL_LIBCOMMON_SUPPORT
609 bool "Support common libraries"
611 Enable support for common U-Boot libraries within SPL. These
612 libraries include common code to deal with U-Boot images,
613 environment and USB, for example. This option is enabled on many
614 boards. Enable this option to build the code in common/ as part of
617 config SPL_LIBDISK_SUPPORT
618 bool "Support disk partitions"
621 Enable support for disk partitions within SPL. 'Disk' is something
622 of a misnomer as it includes non-spinning media such as flash (as
623 used in MMC and USB sticks). Partitions provide a way for a disk
624 to be split up into separate regions, with a partition table placed
625 at the start or end which describes the location and size of each
626 'partition'. These partitions are typically uses as individual block
627 devices, typically with an EXT2 or FAT filesystem in each. This
628 option enables whatever partition support has been enabled in
629 U-Boot to also be used in SPL. It brings in the code in disk/.
631 config SPL_LIBGENERIC_SUPPORT
632 bool "Support generic libraries"
634 Enable support for generic U-Boot libraries within SPL. These
635 libraries include generic code to deal with device tree, hashing,
636 printf(), compression and the like. This option is enabled on many
637 boards. Enable this option to build the code in lib/ as part of an
640 config SPL_DM_MAILBOX
641 bool "Support Mailbox"
643 Enable support for Mailbox within SPL. This enable the inter
644 processor communication protocols tobe used within SPL. Enable
645 this option to build the drivers in drivers/mailbox as part of
648 config SPL_MMC_SUPPORT
651 select HAVE_BLOCK_DEVICE
653 Enable support for MMC (Multimedia Card) within SPL. This enables
654 the MMC protocol implementation and allows any enabled drivers to
655 be used within SPL. MMC can be used with or without disk partition
656 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
657 this option to build the drivers in drivers/mmc as part of an SPL
660 config SPL_FORCE_MMC_BOOT
661 bool "Force SPL booting from MMC"
662 depends on SPL_MMC_SUPPORT
665 Force SPL to use MMC device for Linux kernel booting even when the
666 SoC ROM recognized boot medium is not eMMC/SD. This is crucial for
667 factory or 'falcon mode' booting.
670 bool "Tiny MMC framework in SPL"
671 depends on SPL_MMC_SUPPORT
674 Enable MMC framework tinification support. This option is useful if
675 if your SPL is extremely size constrained. Heed the warning, enable
676 this option if and only if you know exactly what you are doing, if
677 you are reading this help text, you most likely have no idea :-)
679 The MMC framework is reduced to bare minimum to be useful. No malloc
680 support is needed for the MMC framework operation with this option
681 enabled. The framework supports exactly one MMC device and exactly
682 one MMC driver. The MMC driver can be adjusted to avoid any malloc
683 operations too, which can remove the need for malloc support in SPL
684 and thus further reduce footprint.
687 bool "MMC/SD/SDIO card support for write operations in SPL"
688 depends on SPL_MMC_SUPPORT
691 Enable write access to MMC and SD Cards in SPL
694 config SPL_MPC8XXX_INIT_DDR_SUPPORT
695 bool "Support MPC8XXX DDR init"
697 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
698 random-access memory) on the MPC8XXX family within SPL. This
699 allows DRAM to be set up before loading U-Boot into that DRAM,
702 config SPL_MTD_SUPPORT
703 bool "Support MTD drivers"
705 Enable support for MTD (Memory Technology Device) within SPL. MTD
706 provides a block interface over raw NAND and can also be used with
707 SPI flash. This allows SPL to load U-Boot from supported MTD
708 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
709 to enable specific MTD drivers.
711 config SPL_MUSB_NEW_SUPPORT
712 bool "Support new Mentor Graphics USB"
714 Enable support for Mentor Graphics USB in SPL. This is a new
715 driver used by some boards. Enable this option to build
716 the drivers in drivers/usb/musb-new as part of an SPL build. The
717 old drivers are in drivers/usb/musb.
719 config SPL_NAND_SUPPORT
720 bool "Support NAND flash"
722 Enable support for NAND (Negative AND) flash in SPL. NAND flash
723 can be used to allow SPL to load U-Boot from supported devices.
724 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
730 Enable support for loading payloads from UBI. See
731 README.ubispl for more info.
735 bool "Support SPI DM drivers in SPL"
737 Enable support for SPI DM drivers in SPL.
741 config SPL_UBI_LOAD_BY_VOLNAME
742 bool "Support loading volumes by name"
744 This enables support for loading UBI volumes by name. When this
745 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
746 configure the volume name from which to load U-Boot.
748 config SPL_UBI_MAX_VOL_LEBS
749 int "Maximum number of LEBs per volume"
752 The maximum number of logical eraseblocks which a static volume
753 to load can contain. Used for sizing the scan data structure.
755 config SPL_UBI_MAX_PEB_SIZE
756 int "Maximum PEB size"
759 The maximum physical erase block size.
761 config SPL_UBI_MAX_PEBS
762 int "Maximum number of PEBs"
765 The maximum physical erase block size. If not overridden by
766 board code, this value will be used as the actual number of PEBs.
768 config SPL_UBI_PEB_OFFSET
769 int "Offset to first UBI PEB"
772 The offset in number of PEBs from the start of flash to the first
773 PEB part of the UBI image.
775 config SPL_UBI_VID_OFFSET
776 int "Offset to VID header"
779 config SPL_UBI_LEB_START
780 int "Offset to LEB in PEB"
783 The offset in bytes to the LEB within a PEB.
785 config SPL_UBI_INFO_ADDR
786 hex "Address to place UBI scan info"
789 Address for ubispl to place the scan info. Read README.ubispl to
790 determine the required size
792 config SPL_UBI_VOL_IDS
793 int "Maximum volume id"
796 The maximum volume id which can be loaded. Used for sizing the
799 config SPL_UBI_LOAD_MONITOR_ID
800 int "id of U-Boot volume"
803 The UBI volume id from which to load U-Boot
805 config SPL_UBI_LOAD_MONITOR_VOLNAME
806 string "volume name of U-Boot volume"
807 depends on SPL_UBI_LOAD_BY_VOLNAME
809 The UBI volume name from which to load U-Boot
811 config SPL_UBI_LOAD_KERNEL_ID
812 int "id of kernel volume"
813 depends on SPL_OS_BOOT && SPL_UBI
815 The UBI volume id from which to load the kernel
817 config SPL_UBI_LOAD_ARGS_ID
818 int "id of kernel args volume"
819 depends on SPL_OS_BOOT && SPL_UBI
821 The UBI volume id from which to load the device tree
823 config UBI_SPL_SILENCE_MSG
824 bool "silence UBI SPL messages"
827 Disable messages from UBI SPL. This leaves warnings
832 config SPL_NET_SUPPORT
833 bool "Support networking"
835 Enable support for network devices (such as Ethernet) in SPL.
836 This permits SPL to load U-Boot over a network link rather than
837 from an on-board peripheral. Environment support is required since
838 the network stack uses a number of environment variables. See also
842 config SPL_NET_VCI_STRING
843 string "BOOTP Vendor Class Identifier string sent by SPL"
845 As defined by RFC 2132 the vendor class identifier field can be
846 sent by the client to identify the vendor type and configuration
847 of a client. This is often used in practice to allow for the DHCP
848 server to specify different files to load depending on if the ROM,
849 SPL or U-Boot itself makes the request
850 endif # if SPL_NET_SUPPORT
852 config SPL_NO_CPU_SUPPORT
853 bool "Drop CPU code in SPL"
855 This is specific to the ARM926EJ-S CPU. It disables the standard
856 start.S start-up code, presumably so that a replacement can be
857 used on that CPU. You should not enable it unless you know what
860 config SPL_NOR_SUPPORT
861 bool "Support NOR flash"
863 Enable support for loading U-Boot from memory-mapped NOR (Negative
864 OR) flash in SPL. NOR flash is slow to write but fast to read, and
865 a memory-mapped device makes it very easy to access. Loading from
866 NOR is typically achieved with just a memcpy().
868 config SPL_XIP_SUPPORT
872 Enable support for execute in place of U-Boot or kernel image. There
873 is no need to copy image from flash to ram if flash supports execute
874 in place. Its very useful in systems having enough flash but not
875 enough ram to load the image.
877 config SPL_ONENAND_SUPPORT
878 bool "Support OneNAND flash"
880 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
881 a type of NAND flash and therefore can be used to allow SPL to
882 load U-Boot from supported devices. This enables the drivers in
883 drivers/mtd/onenand as part of an SPL build.
886 bool "Activate Falcon Mode"
887 depends on !TI_SECURE_DEVICE
890 Enable booting directly to an OS from SPL.
891 for more info read doc/README.falcon
895 hex "addr, where OS is found"
896 depends on SPL_NOR_SUPPORT
898 Specify the address, where the OS image is found, which
905 default "tpl/u-boot-with-tpl.bin" if TPL
908 Payload for SPL boot. For backward compatibility, default to
909 u-boot.bin, i.e. RAW image without any header. In case of
910 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
914 bool "Support PCI drivers"
916 Enable support for PCI in SPL. For platforms that need PCI to boot,
917 or must perform some init using PCI in SPL, this provides the
918 necessary driver support. This enables the drivers in drivers/pci
919 as part of an SPL build.
921 config SPL_PCH_SUPPORT
922 bool "Support PCH drivers"
924 Enable support for PCH (Platform Controller Hub) devices in SPL.
925 These are used to set up GPIOs and the SPI peripheral early in
926 boot. This enables the drivers in drivers/pch as part of an SPL
929 config SPL_POST_MEM_SUPPORT
930 bool "Support POST drivers"
932 Enable support for POST (Power-on Self Test) in SPL. POST is a
933 procedure that checks that the hardware (CPU or board) appears to
934 be functionally correctly. It is a sanity check that can be
935 performed before booting. This enables the drivers in post/drivers
936 as part of an SPL build.
939 bool "Support reset drivers"
942 Enable support for reset control in SPL.
943 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
944 by using the generic reset API provided by driver model.
945 This enables the drivers in drivers/reset as part of an SPL build.
947 config SPL_POWER_SUPPORT
948 bool "Support power drivers"
950 Enable support for power control in SPL. This includes support
951 for PMICs (Power-management Integrated Circuits) and some of the
952 features provided by PMICs. In particular, voltage regulators can
953 be used to enable/disable power and vary its voltage. That can be
954 useful in SPL to turn on boot peripherals and adjust CPU voltage
955 so that the clock speed can be increased. This enables the drivers
956 in drivers/power, drivers/power/pmic and drivers/power/regulator
957 as part of an SPL build.
959 config SPL_POWER_DOMAIN
960 bool "Support power domain drivers"
962 Enable support for power domain control in SPL. Many SoCs allow
963 power to be applied to or removed from portions of the SoC (power
964 domains). This may be used to save power. This API provides the
965 means to control such power management hardware. This enables
966 the drivers in drivers/power/domain as part of a SPL build.
968 config SPL_RAM_SUPPORT
969 bool "Support booting from RAM"
970 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
972 Enable booting of an image in RAM. The image can be preloaded or
973 it can be loaded by SPL directly into RAM (e.g. using USB).
975 config SPL_RAM_DEVICE
976 bool "Support booting from preloaded image in RAM"
977 depends on SPL_RAM_SUPPORT
978 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
980 Enable booting of an image already loaded in RAM. The image has to
981 be already in memory when SPL takes over, e.g. loaded by the boot
984 config SPL_REMOTEPROC
985 bool "Support REMOTEPROCS"
987 Enable support for REMOTEPROCs in SPL. This permits to load
988 a remote processor firmware in SPL.
990 config SPL_RTC_SUPPORT
991 bool "Support RTC drivers"
993 Enable RTC (Real-time Clock) support in SPL. This includes support
994 for reading and setting the time. Some RTC devices also have some
995 non-volatile (battery-backed) memory which is accessible if
996 needed. This enables the drivers in drivers/rtc as part of an SPL
999 config SPL_SATA_SUPPORT
1000 bool "Support loading from SATA"
1002 Enable support for SATA (Serial AT attachment) in SPL. This allows
1003 use of SATA devices such as hard drives and flash drivers for
1004 loading U-Boot. SATA is used in higher-end embedded systems and
1005 can provide higher performance than MMC , at somewhat higher
1006 expense and power consumption. This enables loading from SATA
1007 using a configured device.
1009 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1010 bool "SATA raw mode: by sector"
1011 depends on SPL_SATA_SUPPORT
1013 Use sector number for specifying U-Boot location on SATA disk in
1016 config SPL_SATA_RAW_U_BOOT_SECTOR
1017 hex "Sector on the SATA disk to load U-Boot from"
1018 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1020 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1021 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1023 config SPL_SERIAL_SUPPORT
1024 bool "Support serial"
1028 Enable support for serial in SPL. This allows use of a serial UART
1029 for displaying messages while SPL is running. It also brings in
1030 printf() and panic() functions. This should normally be enabled
1031 unless there are space reasons not to. Even then, consider
1032 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1034 config SPL_SPI_SUPPORT
1035 bool "Support SPI drivers"
1037 Enable support for using SPI in SPL. This is used for connecting
1038 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1039 more details on that. The SPI driver provides the transport for
1040 data between the SPI flash and the CPU. This option can be used to
1041 enable SPI drivers that are needed for other purposes also, such
1044 config SPL_SPI_FLASH_SUPPORT
1045 bool "Support SPI flash drivers"
1046 depends on SPL_SPI_SUPPORT
1048 Enable support for using SPI flash in SPL, and loading U-Boot from
1049 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1050 the SPI bus that is used to connect it to a system. It is a simple
1051 but fast bidirectional 4-wire bus (clock, chip select and two data
1052 lines). This enables the drivers in drivers/mtd/spi as part of an
1053 SPL build. This normally requires SPL_SPI_SUPPORT.
1055 if SPL_SPI_FLASH_SUPPORT
1057 config SPL_SPI_FLASH_TINY
1058 bool "Enable low footprint SPL SPI Flash support"
1059 depends on !SPI_FLASH_BAR
1060 default y if SPI_FLASH
1062 Enable lightweight SPL SPI Flash support that supports just reading
1063 data/images from flash. No support to write/erase flash. Enable
1064 this if you have SPL size limitations and don't need full
1065 fledged SPI flash support.
1067 config SPL_SPI_FLASH_SFDP_SUPPORT
1068 bool "SFDP table parsing support for SPI NOR flashes"
1069 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1071 Enable support for parsing and auto discovery of parameters for
1072 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1073 tables as per JESD216 standard in SPL.
1076 bool "Support loading from SPI flash"
1078 Enable support for loading next stage, U-Boot or otherwise, from
1079 SPI NOR in U-Boot SPL.
1081 endif # SPL_SPI_FLASH_SUPPORT
1083 config SYS_SPI_U_BOOT_OFFS
1084 hex "address of u-boot payload in SPI flash"
1086 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1088 Address within SPI-Flash from where the u-boot payload is fetched
1092 bool "Driver support for thermal devices"
1094 Enable support for temperature-sensing devices. Some SoCs have on-chip
1095 temperature sensors to permit warnings, speed throttling or even
1096 automatic power-off when the temperature gets too high or low. Other
1097 devices may be discrete but connected on a suitable bus.
1099 config SPL_USB_HOST_SUPPORT
1100 bool "Support USB host drivers"
1101 select HAVE_BLOCK_DEVICE
1103 Enable access to USB (Universal Serial Bus) host devices so that
1104 SPL can load U-Boot from a connected USB peripheral, such as a USB
1105 flash stick. While USB takes a little longer to start up than most
1106 buses, it is very flexible since many different types of storage
1107 device can be attached. This option enables the drivers in
1108 drivers/usb/host as part of an SPL build.
1110 config SPL_USB_STORAGE
1111 bool "Support loading from USB"
1112 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1114 Enable support for USB devices in SPL. This allows use of USB
1115 devices such as hard drives and flash drivers for loading U-Boot.
1116 The actual drivers are enabled separately using the normal U-Boot
1117 config options. This enables loading from USB using a configured
1120 config SPL_USB_GADGET
1121 bool "Suppport USB Gadget drivers"
1123 Enable USB Gadget API which allows to enable USB device functions
1128 config SPL_USB_ETHER
1129 bool "Support USB Ethernet drivers"
1131 Enable access to the USB network subsystem and associated
1132 drivers in SPL. This permits SPL to load U-Boot over a
1133 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1134 than from an onboard peripheral. Environment support is required
1135 since the network stack uses a number of environment variables.
1136 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1139 bool "Support DFU (Device Firmware Upgrade)"
1140 select SPL_HASH_SUPPORT
1141 select SPL_DFU_NO_RESET
1142 depends on SPL_RAM_SUPPORT
1144 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1145 RAM memory device support. The ROM code will load and execute
1146 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1147 selected device partition from host-pc using dfu-utils.
1148 This feature is useful to flash the binaries to factory or bare-metal
1149 boards using USB interface.
1152 bool "DFU device selection"
1157 depends on SPL_DFU && SPL_RAM_SUPPORT
1159 select RAM/DDR memory device for loading binary images
1160 (u-boot/kernel) to the selected device partition using
1161 DFU and execute the u-boot/kernel from RAM.
1165 config SPL_USB_SDP_SUPPORT
1166 bool "Support SDP (Serial Download Protocol)"
1168 Enable Serial Download Protocol (SDP) device support in SPL. This
1169 allows to download images into memory and execute (jump to) them
1170 using the same protocol as implemented by the i.MX family's boot ROM.
1173 config SPL_WATCHDOG_SUPPORT
1174 bool "Support watchdog drivers"
1175 imply SPL_WDT if !HW_WATCHDOG
1177 Enable support for watchdog drivers in SPL. A watchdog is
1178 typically a hardware peripheral which can reset the system when it
1179 detects no activity for a while (such as a software crash). This
1180 enables the drivers in drivers/watchdog as part of an SPL build.
1182 config SPL_YMODEM_SUPPORT
1183 bool "Support loading using Ymodem"
1184 depends on SPL_SERIAL_SUPPORT
1186 While loading from serial is slow it can be a useful backup when
1187 there is no other option. The Ymodem protocol provides a reliable
1188 means of transmitting U-Boot over a serial line for using in SPL,
1189 with a checksum to ensure correctness.
1192 bool "Support ARM Trusted Firmware"
1195 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1196 is loaded by SPL (which is considered as BL2 in ATF terminology).
1197 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1199 config SPL_ATF_NO_PLATFORM_PARAM
1200 bool "Pass no platform parameter"
1203 While we expect to call a pointer to a valid FDT (or NULL)
1204 as the platform parameter to an ATF, some ATF versions are
1205 not U-Boot aware and have an insufficiently robust parameter
1206 validation to gracefully reject a FDT being passed.
1208 If this option is enabled, the spl_atf os-type handler will
1209 always pass NULL for the platform parameter.
1211 If your ATF is affected, say Y.
1213 config SPL_AM33XX_ENABLE_RTC32K_OSC
1214 bool "Enable the RTC32K OSC on AM33xx based platforms"
1217 Enable access to the AM33xx RTC and select the external 32kHz clock
1221 bool "Support OP-TEE Trusted OS"
1224 OP-TEE is an open source Trusted OS which is loaded by SPL.
1225 More detail at: https://github.com/OP-TEE/optee_os
1228 bool "Support RISC-V OpenSBI"
1229 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1231 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1232 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1233 firmware. It is loaded and started by U-Boot SPL.
1235 More details are available at https://github.com/riscv/opensbi and
1236 https://github.com/riscv/riscv-sbi-doc
1238 config SPL_OPENSBI_LOAD_ADDR
1239 hex "OpenSBI load address"
1240 depends on SPL_OPENSBI
1242 Load address of the OpenSBI binary.
1246 depends on SUPPORT_TPL
1249 If you want to build TPL as well as the normal image and SPL, say Y.
1253 config TPL_SIZE_LIMIT
1254 hex "Maximum size of TPL image"
1258 Specifies the maximum length of the U-Boot TPL image.
1259 If this value is zero, it is ignored.
1261 config TPL_FRAMEWORK
1262 bool "Support TPL based upon the common SPL framework"
1263 default y if SPL_FRAMEWORK
1265 Enable the SPL framework under common/spl/ for TPL builds.
1266 This framework supports MMC, NAND and YMODEM and other methods
1267 loading of U-Boot's SPL stage. If unsure, say Y.
1270 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1271 depends on HANDOFF && TPL_BLOBLIST
1274 This option enables TPL to write handoff information. This can be
1275 used to pass information like the size of SDRAM from TPL to U-Boot
1276 proper. The information is also available to SPL if it is useful
1279 config TPL_BOARD_INIT
1280 bool "Call board-specific initialization in TPL"
1282 If this option is enabled, U-Boot will call the function
1283 spl_board_init() from board_init_r(). This function should be
1284 provided by the board.
1287 string "Linker script for the TPL stage"
1289 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1290 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1292 The TPL stage will usually require a different linker-script
1293 (as it runs from a different memory region) than the regular
1294 U-Boot stage. Set this to the path of the linker-script to
1297 May be left empty to trigger the Makefile infrastructure to
1298 fall back to the linker-script used for the SPL stage.
1300 config TPL_NEEDS_SEPARATE_TEXT_BASE
1301 bool "TPL needs a separate text-base"
1305 Enable, if the TPL stage should not inherit its text-base
1306 from the SPL stage. When enabled, a base address for the
1307 .text sections of the TPL stage has to be set below.
1309 config TPL_NEEDS_SEPARATE_STACK
1310 bool "TPL needs a separate initial stack-pointer"
1314 Enable, if the TPL stage should not inherit its initial
1315 stack-pointer from the settings for the SPL stage.
1317 config TPL_TEXT_BASE
1318 hex "Base address for the .text section of the TPL stage"
1319 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1321 The base address for the .text section of the TPL stage.
1324 int "Maximum size (in bytes) for the TPL stage"
1328 The maximum size (in bytes) of the TPL stage.
1331 hex "Address of the initial stack-pointer for the TPL stage"
1332 depends on TPL_NEEDS_SEPARATE_STACK
1334 The address of the initial stack-pointer for the TPL stage.
1335 Usually this will be the (aligned) top-of-stack.
1337 config TPL_BOOTROM_SUPPORT
1338 bool "Support returning to the BOOTROM (from TPL)"
1340 Some platforms (e.g. the Rockchip RK3368) provide support in their
1341 ROM for loading the next boot-stage after performing basic setup
1344 Enable this option, to return to the BOOTROM through the
1345 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1346 boot device list, if not implemented for a given board)
1348 config TPL_DRIVERS_MISC_SUPPORT
1349 bool "Support misc drivers in TPL"
1351 Enable miscellaneous drivers in TPL. These drivers perform various
1352 tasks that don't fall nicely into other categories, Enable this
1353 option to build the drivers in drivers/misc as part of an TPL
1354 build, for those that support building in TPL (not all drivers do).
1356 config TPL_ENV_SUPPORT
1357 bool "Support an environment"
1359 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1361 config TPL_GPIO_SUPPORT
1362 bool "Support GPIO in TPL"
1364 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1365 GPIOs allow U-Boot to read the state of an input line (high or
1366 low) and set the state of an output line. This can be used to
1367 drive LEDs, control power to various system parts and read user
1368 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1369 for example. Enable this option to build the drivers in
1370 drivers/gpio as part of an TPL build.
1372 config TPL_I2C_SUPPORT
1375 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1378 config TPL_LIBCOMMON_SUPPORT
1379 bool "Support common libraries"
1381 Enable support for common U-Boot libraries within TPL. See
1382 SPL_LIBCOMMON_SUPPORT for details.
1384 config TPL_LIBGENERIC_SUPPORT
1385 bool "Support generic libraries"
1387 Enable support for generic U-Boot libraries within TPL. See
1388 SPL_LIBGENERIC_SUPPORT for details.
1390 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1391 bool "Support MPC8XXX DDR init"
1393 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1394 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1396 config TPL_MMC_SUPPORT
1400 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1402 config TPL_NAND_SUPPORT
1403 bool "Support NAND flash"
1405 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1408 bool "Support PCI drivers"
1410 Enable support for PCI in TPL. For platforms that need PCI to boot,
1411 or must perform some init using PCI in SPL, this provides the
1412 necessary driver support. This enables the drivers in drivers/pci
1413 as part of a TPL build.
1415 config TPL_PCH_SUPPORT
1416 bool "Support PCH drivers"
1418 Enable support for PCH (Platform Controller Hub) devices in TPL.
1419 These are used to set up GPIOs and the SPI peripheral early in
1420 boot. This enables the drivers in drivers/pch as part of a TPL
1423 config TPL_RAM_SUPPORT
1424 bool "Support booting from RAM"
1426 Enable booting of an image in RAM. The image can be preloaded or
1427 it can be loaded by TPL directly into RAM (e.g. using USB).
1429 config TPL_RAM_DEVICE
1430 bool "Support booting from preloaded image in RAM"
1431 depends on TPL_RAM_SUPPORT
1433 Enable booting of an image already loaded in RAM. The image has to
1434 be already in memory when TPL takes over, e.g. loaded by the boot
1437 config TPL_RTC_SUPPORT
1438 bool "Support RTC drivers"
1440 Enable RTC (Real-time Clock) support in TPL. This includes support
1441 for reading and setting the time. Some RTC devices also have some
1442 non-volatile (battery-backed) memory which is accessible if
1443 needed. This enables the drivers in drivers/rtc as part of an TPL
1446 config TPL_SERIAL_SUPPORT
1447 bool "Support serial"
1451 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1454 config TPL_SPI_FLASH_SUPPORT
1455 bool "Support SPI flash drivers"
1457 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1461 bool "Support loading from SPI flash"
1462 depends on TPL_SPI_FLASH_SUPPORT
1464 Enable support for loading next stage, U-Boot or otherwise, from
1465 SPI NOR in U-Boot TPL.
1467 config TPL_SPI_SUPPORT
1468 bool "Support SPI drivers"
1470 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1473 config TPL_YMODEM_SUPPORT
1474 bool "Support loading using Ymodem"
1475 depends on TPL_SERIAL_SUPPORT
1477 While loading from serial is slow it can be a useful backup when
1478 there is no other option. The Ymodem protocol provides a reliable
1479 means of transmitting U-Boot over a serial line for using in TPL,
1480 with a checksum to ensure correctness.
1484 config SPL_AT91_MCK_BYPASS
1485 bool "Use external clock signal as a source of main clock for AT91 platforms"
1486 depends on ARCH_AT91
1489 Use external 8 to 24 Mhz clock signal as source of main clock instead
1490 of an external crystal oscillator.
1491 This option disables the internal driving on the XOUT pin.
1492 The external source has to provide a stable clock on the XIN pin.
1493 If this option is disabled, the SoC expects a crystal oscillator
1494 that needs driving on both XIN and XOUT lines.