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