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_DATA_PART_OFFSET
333 hex "U-Boot main hardware partition image offset"
334 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
337 On some platforms SPL location depends on hardware partition. The ROM
338 code skips the MBR sector when loading SPL from main hardware data
339 partition. This adds offset to the main U-Boot image. Set this symbol
340 to the number of skipped sectors.
342 If unsure, leave the default.
344 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
345 bool "MMC Raw mode: by partition"
347 Use a partition for loading U-Boot when using MMC/SD in raw mode.
349 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
350 hex "Partition to use to load U-Boot from"
351 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
354 Partition on the MMC to load U-Boot from when the MMC is being
357 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
358 bool "MMC raw mode: by partition type"
359 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
361 Use partition type for specifying U-Boot partition on MMC/SD in
362 raw mode. U-Boot will be loaded from the first partition of this
365 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
366 hex "Partition Type on the MMC to load U-Boot from"
367 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
369 Partition Type on the MMC to load U-Boot from, when the MMC is being
372 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
373 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
374 depends on SUPPORT_EMMC_BOOT
376 eMMC boot partition is normally configured by the bits of the EXT_CSD
377 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
378 cases it might be required in SPL to load the image from different
379 partition than the partition selected by EXT_CSC_PART_CONFIG register.
380 Enable this option if you intend to use an eMMC boot partition other
381 then selected via EXT_CSC_PART_CONFIG register and specify the custom
382 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
385 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
386 int "Number of the eMMC boot partition to use"
387 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
390 eMMC boot partition number to use when the eMMC in raw mode and
391 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
392 by user defined partition number.
394 config SPL_CRC32_SUPPORT
396 default y if SPL_LEGACY_IMAGE_SUPPORT
398 Enable this to support CRC32 in uImages or FIT images within SPL.
399 This is a 32-bit checksum value that can be used to verify images.
400 For FIT images, this is the least secure type of checksum, suitable
401 for detected accidental image corruption. For secure applications you
402 should consider SHA1 or SHA256.
404 config SPL_MD5_SUPPORT
408 Enable this to support MD5 in FIT images within SPL. An MD5
409 checksum is a 128-bit hash value used to check that the image
410 contents have not been corrupted. Note that MD5 is not considered
411 secure as it is possible (with a brute-force attack) to adjust the
412 image while still retaining the same MD5 hash value. For secure
413 applications where images may be changed maliciously, you should
414 consider SHA1 or SHA256.
416 config SPL_SHA1_SUPPORT
421 Enable this to support SHA1 in FIT images within SPL. A SHA1
422 checksum is a 160-bit (20-byte) hash value used to check that the
423 image contents have not been corrupted or maliciously altered.
424 While SHA1 is fairly secure it is coming to the end of its life
425 due to the expanding computing power available to brute-force
426 attacks. For more security, consider SHA256.
428 config SPL_SHA256_SUPPORT
429 bool "Support SHA256"
433 Enable this to support SHA256 in FIT images within SPL. A SHA256
434 checksum is a 256-bit (32-byte) hash value used to check that the
435 image contents have not been corrupted. SHA256 is recommended for
436 use in secure applications since (as at 2016) there is no known
437 feasible attack that could produce a 'collision' with differing
438 input data. Use this for the highest security. Note that only the
439 SHA256 variant is supported: SHA512 and others are not currently
442 config SPL_FIT_IMAGE_TINY
443 bool "Remove functionality from SPL FIT loading to reduce size"
445 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
446 default y if ARCH_IMX8M
448 Enable this to reduce the size of the FIT image loading code
449 in SPL, if space for the SPL binary is very tight.
451 This removes the detection of image types (which forces the
452 first image to be treated as having a U-Boot style calling
453 convention) and skips the recording of each loaded payload
454 (i.e. loadable) into the FDT (modifying the loaded FDT to
455 ensure this information is available to the next image
458 config SPL_CACHE_SUPPORT
459 bool "Support CACHE drivers"
461 Enable CACHE drivers in SPL. These drivers can keep data so that
462 future requests for that data can be served faster. Enable this option
463 to build the drivers in drivers/cache as part of an SPL build.
465 config SPL_CPU_SUPPORT
466 bool "Support CPU drivers"
468 Enable this to support CPU drivers in SPL. These drivers can set
469 up CPUs and provide information about them such as the model and
470 name. This can be useful in SPL since setting up the CPUs earlier
471 may improve boot performance. Enable this option to build the
472 drivers in drivers/cpu as part of an SPL build.
474 config SPL_CRYPTO_SUPPORT
475 bool "Support crypto drivers"
477 Enable crypto drivers in SPL. These drivers can be used to
478 accelerate secure boot processing in secure applications. Enable
479 this option to build the drivers in drivers/crypto as part of an
482 config SPL_HASH_SUPPORT
483 bool "Support hashing drivers"
487 Enable hashing drivers in SPL. These drivers can be used to
488 accelerate secure boot processing in secure applications. Enable
489 this option to build system-specific drivers for hash acceleration
490 as part of an SPL build.
492 config TPL_HASH_SUPPORT
493 bool "Support hashing drivers in TPL"
498 Enable hashing drivers in SPL. These drivers can be used to
499 accelerate secure boot processing in secure applications. Enable
500 this option to build system-specific drivers for hash acceleration
501 as part of an SPL build.
504 bool "Support DMA drivers"
506 Enable DMA (direct-memory-access) drivers in SPL. These drivers
507 can be used to handle memory-to-peripheral data transfer without
508 the CPU moving the data. Enable this option to build the drivers
509 in drivers/dma as part of an SPL build.
512 bool "Support Driver Model GPIO drivers"
513 depends on SPL_GPIO_SUPPORT && DM_GPIO
515 Enable support for Driver Model based GPIO drivers in SPL.
517 config SPL_DRIVERS_MISC_SUPPORT
518 bool "Support misc drivers"
520 Enable miscellaneous drivers in SPL. These drivers perform various
521 tasks that don't fall nicely into other categories, Enable this
522 option to build the drivers in drivers/misc as part of an SPL
523 build, for those that support building in SPL (not all drivers do).
525 config SPL_ENV_SUPPORT
526 bool "Support an environment"
528 Enable environment support in SPL. The U-Boot environment provides
529 a number of settings (essentially name/value pairs) which can
530 control many aspects of U-Boot's operation. Normally this is not
531 needed in SPL as it has a much simpler task with less
532 configuration. But some boards use this to support 'Falcon' boot
533 on EXT2 and FAT, where SPL boots directly into Linux without
534 starting U-Boot first. Enabling this option will make env_get()
535 and env_set() available in SPL.
538 bool "Support save environment"
539 depends on SPL_ENV_SUPPORT
540 select SPL_MMC_WRITE if ENV_IS_IN_MMC
542 Enable save environment support in SPL after setenv. By default
543 the saveenv option is not provided in SPL, but some boards need
544 this support in 'Falcon' boot, where SPL need to boot from
545 different images based on environment variable set by OS. For
546 example OS may set "reboot_image" environment variable to
547 "recovery" inorder to boot recovery image by SPL. The SPL read
548 "reboot_image" and act accordingly and change the reboot_image
549 to default mode using setenv and save the environment.
551 config SPL_ETH_SUPPORT
552 bool "Support Ethernet"
553 depends on SPL_ENV_SUPPORT
555 Enable access to the network subsystem and associated Ethernet
556 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
557 link rather than from an on-board peripheral. Environment support
558 is required since the network stack uses a number of environment
559 variables. See also SPL_NET_SUPPORT.
562 bool "Support EXT filesystems"
564 Enable support for EXT2/3/4 filesystems with SPL. This permits
565 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
566 filesystem from within SPL. Support for the underlying block
567 device (e.g. MMC or USB) must be enabled separately.
570 bool "Support FAT filesystems"
573 Enable support for FAT and VFAT filesystems with SPL. This
574 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
575 filesystem from within SPL. Support for the underlying block
576 device (e.g. MMC or USB) must be enabled separately.
579 bool "Support write for FAT filesystems"
581 Enable write support for FAT and VFAT filesystems with SPL.
582 Support for the underlying block device (e.g. MMC or USB) must be
585 config SPL_FPGA_SUPPORT
588 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
589 provide software-configurable hardware which is typically used to
590 implement peripherals (such as UARTs, LCD displays, MMC) or
591 accelerate custom processing functions, such as image processing
592 or machine learning. Sometimes it is useful to program the FPGA
593 as early as possible during boot, and this option can enable that
596 config SPL_GPIO_SUPPORT
597 bool "Support GPIO in SPL"
599 Enable support for GPIOs (General-purpose Input/Output) in SPL.
600 GPIOs allow U-Boot to read the state of an input line (high or
601 low) and set the state of an output line. This can be used to
602 drive LEDs, control power to various system parts and read user
603 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
604 for example. Enable this option to build the drivers in
605 drivers/gpio as part of an SPL build.
607 config SPL_I2C_SUPPORT
610 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
611 I2C works with a clock and data line which can be driven by a
612 one or more masters or slaves. It is a fairly complex bus but is
613 widely used as it only needs two lines for communication. Speeds of
614 400kbps are typical but up to 3.4Mbps is supported by some
615 hardware. I2C can be useful in SPL to configure power management
616 ICs (PMICs) before raising the CPU clock speed, for example.
617 Enable this option to build the drivers in drivers/i2c as part of
620 config SPL_LIBCOMMON_SUPPORT
621 bool "Support common libraries"
623 Enable support for common U-Boot libraries within SPL. These
624 libraries include common code to deal with U-Boot images,
625 environment and USB, for example. This option is enabled on many
626 boards. Enable this option to build the code in common/ as part of
629 config SPL_LIBDISK_SUPPORT
630 bool "Support disk partitions"
633 Enable support for disk partitions within SPL. 'Disk' is something
634 of a misnomer as it includes non-spinning media such as flash (as
635 used in MMC and USB sticks). Partitions provide a way for a disk
636 to be split up into separate regions, with a partition table placed
637 at the start or end which describes the location and size of each
638 'partition'. These partitions are typically uses as individual block
639 devices, typically with an EXT2 or FAT filesystem in each. This
640 option enables whatever partition support has been enabled in
641 U-Boot to also be used in SPL. It brings in the code in disk/.
643 config SPL_LIBGENERIC_SUPPORT
644 bool "Support generic libraries"
646 Enable support for generic U-Boot libraries within SPL. These
647 libraries include generic code to deal with device tree, hashing,
648 printf(), compression and the like. This option is enabled on many
649 boards. Enable this option to build the code in lib/ as part of an
652 config SPL_DM_MAILBOX
653 bool "Support Mailbox"
655 Enable support for Mailbox within SPL. This enable the inter
656 processor communication protocols tobe used within SPL. Enable
657 this option to build the drivers in drivers/mailbox as part of
660 config SPL_MMC_SUPPORT
663 select HAVE_BLOCK_DEVICE
665 Enable support for MMC (Multimedia Card) within SPL. This enables
666 the MMC protocol implementation and allows any enabled drivers to
667 be used within SPL. MMC can be used with or without disk partition
668 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
669 this option to build the drivers in drivers/mmc as part of an SPL
672 config SPL_FORCE_MMC_BOOT
673 bool "Force SPL booting from MMC"
674 depends on SPL_MMC_SUPPORT
677 Force SPL to use MMC device for Linux kernel booting even when the
678 SoC ROM recognized boot medium is not eMMC/SD. This is crucial for
679 factory or 'falcon mode' booting.
682 bool "Tiny MMC framework in SPL"
683 depends on SPL_MMC_SUPPORT
686 Enable MMC framework tinification support. This option is useful if
687 if your SPL is extremely size constrained. Heed the warning, enable
688 this option if and only if you know exactly what you are doing, if
689 you are reading this help text, you most likely have no idea :-)
691 The MMC framework is reduced to bare minimum to be useful. No malloc
692 support is needed for the MMC framework operation with this option
693 enabled. The framework supports exactly one MMC device and exactly
694 one MMC driver. The MMC driver can be adjusted to avoid any malloc
695 operations too, which can remove the need for malloc support in SPL
696 and thus further reduce footprint.
699 bool "MMC/SD/SDIO card support for write operations in SPL"
700 depends on SPL_MMC_SUPPORT
703 Enable write access to MMC and SD Cards in SPL
706 config SPL_MPC8XXX_INIT_DDR_SUPPORT
707 bool "Support MPC8XXX DDR init"
709 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
710 random-access memory) on the MPC8XXX family within SPL. This
711 allows DRAM to be set up before loading U-Boot into that DRAM,
714 config SPL_MTD_SUPPORT
715 bool "Support MTD drivers"
717 Enable support for MTD (Memory Technology Device) within SPL. MTD
718 provides a block interface over raw NAND and can also be used with
719 SPI flash. This allows SPL to load U-Boot from supported MTD
720 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
721 to enable specific MTD drivers.
723 config SPL_MUSB_NEW_SUPPORT
724 bool "Support new Mentor Graphics USB"
726 Enable support for Mentor Graphics USB in SPL. This is a new
727 driver used by some boards. Enable this option to build
728 the drivers in drivers/usb/musb-new as part of an SPL build. The
729 old drivers are in drivers/usb/musb.
731 config SPL_NAND_SUPPORT
732 bool "Support NAND flash"
734 Enable support for NAND (Negative AND) flash in SPL. NAND flash
735 can be used to allow SPL to load U-Boot from supported devices.
736 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
742 Enable support for loading payloads from UBI. See
743 README.ubispl for more info.
748 bool "Support cache drivers in SPL"
750 Enable support for cache drivers in SPL.
753 bool "Support SPI DM drivers in SPL"
755 Enable support for SPI DM drivers in SPL.
759 config SPL_UBI_LOAD_BY_VOLNAME
760 bool "Support loading volumes by name"
762 This enables support for loading UBI volumes by name. When this
763 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
764 configure the volume name from which to load U-Boot.
766 config SPL_UBI_MAX_VOL_LEBS
767 int "Maximum number of LEBs per volume"
770 The maximum number of logical eraseblocks which a static volume
771 to load can contain. Used for sizing the scan data structure.
773 config SPL_UBI_MAX_PEB_SIZE
774 int "Maximum PEB size"
777 The maximum physical erase block size.
779 config SPL_UBI_MAX_PEBS
780 int "Maximum number of PEBs"
783 The maximum physical erase block size. If not overridden by
784 board code, this value will be used as the actual number of PEBs.
786 config SPL_UBI_PEB_OFFSET
787 int "Offset to first UBI PEB"
790 The offset in number of PEBs from the start of flash to the first
791 PEB part of the UBI image.
793 config SPL_UBI_VID_OFFSET
794 int "Offset to VID header"
797 config SPL_UBI_LEB_START
798 int "Offset to LEB in PEB"
801 The offset in bytes to the LEB within a PEB.
803 config SPL_UBI_INFO_ADDR
804 hex "Address to place UBI scan info"
807 Address for ubispl to place the scan info. Read README.ubispl to
808 determine the required size
810 config SPL_UBI_VOL_IDS
811 int "Maximum volume id"
814 The maximum volume id which can be loaded. Used for sizing the
817 config SPL_UBI_LOAD_MONITOR_ID
818 int "id of U-Boot volume"
821 The UBI volume id from which to load U-Boot
823 config SPL_UBI_LOAD_MONITOR_VOLNAME
824 string "volume name of U-Boot volume"
825 depends on SPL_UBI_LOAD_BY_VOLNAME
827 The UBI volume name from which to load U-Boot
829 config SPL_UBI_LOAD_KERNEL_ID
830 int "id of kernel volume"
831 depends on SPL_OS_BOOT && SPL_UBI
833 The UBI volume id from which to load the kernel
835 config SPL_UBI_LOAD_ARGS_ID
836 int "id of kernel args volume"
837 depends on SPL_OS_BOOT && SPL_UBI
839 The UBI volume id from which to load the device tree
841 config UBI_SPL_SILENCE_MSG
842 bool "silence UBI SPL messages"
845 Disable messages from UBI SPL. This leaves warnings
850 config SPL_NET_SUPPORT
851 bool "Support networking"
853 Enable support for network devices (such as Ethernet) in SPL.
854 This permits SPL to load U-Boot over a network link rather than
855 from an on-board peripheral. Environment support is required since
856 the network stack uses a number of environment variables. See also
860 config SPL_NET_VCI_STRING
861 string "BOOTP Vendor Class Identifier string sent by SPL"
863 As defined by RFC 2132 the vendor class identifier field can be
864 sent by the client to identify the vendor type and configuration
865 of a client. This is often used in practice to allow for the DHCP
866 server to specify different files to load depending on if the ROM,
867 SPL or U-Boot itself makes the request
868 endif # if SPL_NET_SUPPORT
870 config SPL_NO_CPU_SUPPORT
871 bool "Drop CPU code in SPL"
873 This is specific to the ARM926EJ-S CPU. It disables the standard
874 start.S start-up code, presumably so that a replacement can be
875 used on that CPU. You should not enable it unless you know what
878 config SPL_NOR_SUPPORT
879 bool "Support NOR flash"
881 Enable support for loading U-Boot from memory-mapped NOR (Negative
882 OR) flash in SPL. NOR flash is slow to write but fast to read, and
883 a memory-mapped device makes it very easy to access. Loading from
884 NOR is typically achieved with just a memcpy().
886 config SPL_XIP_SUPPORT
890 Enable support for execute in place of U-Boot or kernel image. There
891 is no need to copy image from flash to ram if flash supports execute
892 in place. Its very useful in systems having enough flash but not
893 enough ram to load the image.
895 config SPL_ONENAND_SUPPORT
896 bool "Support OneNAND flash"
898 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
899 a type of NAND flash and therefore can be used to allow SPL to
900 load U-Boot from supported devices. This enables the drivers in
901 drivers/mtd/onenand as part of an SPL build.
904 bool "Activate Falcon Mode"
905 depends on !TI_SECURE_DEVICE
908 Enable booting directly to an OS from SPL.
909 for more info read doc/README.falcon
913 hex "addr, where OS is found"
914 depends on SPL_NOR_SUPPORT
916 Specify the address, where the OS image is found, which
923 default "tpl/u-boot-with-tpl.bin" if TPL
926 Payload for SPL boot. For backward compatibility, default to
927 u-boot.bin, i.e. RAW image without any header. In case of
928 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
932 bool "Support PCI drivers"
934 Enable support for PCI in SPL. For platforms that need PCI to boot,
935 or must perform some init using PCI in SPL, this provides the
936 necessary driver support. This enables the drivers in drivers/pci
937 as part of an SPL build.
939 config SPL_PCH_SUPPORT
940 bool "Support PCH drivers"
942 Enable support for PCH (Platform Controller Hub) devices in SPL.
943 These are used to set up GPIOs and the SPI peripheral early in
944 boot. This enables the drivers in drivers/pch as part of an SPL
947 config SPL_POST_MEM_SUPPORT
948 bool "Support POST drivers"
950 Enable support for POST (Power-on Self Test) in SPL. POST is a
951 procedure that checks that the hardware (CPU or board) appears to
952 be functionally correctly. It is a sanity check that can be
953 performed before booting. This enables the drivers in post/drivers
954 as part of an SPL build.
957 bool "Support reset drivers"
960 Enable support for reset control in SPL.
961 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
962 by using the generic reset API provided by driver model.
963 This enables the drivers in drivers/reset as part of an SPL build.
965 config SPL_POWER_SUPPORT
966 bool "Support power drivers"
968 Enable support for power control in SPL. This includes support
969 for PMICs (Power-management Integrated Circuits) and some of the
970 features provided by PMICs. In particular, voltage regulators can
971 be used to enable/disable power and vary its voltage. That can be
972 useful in SPL to turn on boot peripherals and adjust CPU voltage
973 so that the clock speed can be increased. This enables the drivers
974 in drivers/power, drivers/power/pmic and drivers/power/regulator
975 as part of an SPL build.
977 config SPL_POWER_DOMAIN
978 bool "Support power domain drivers"
980 Enable support for power domain control in SPL. Many SoCs allow
981 power to be applied to or removed from portions of the SoC (power
982 domains). This may be used to save power. This API provides the
983 means to control such power management hardware. This enables
984 the drivers in drivers/power/domain as part of a SPL build.
986 config SPL_RAM_SUPPORT
987 bool "Support booting from RAM"
988 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
990 Enable booting of an image in RAM. The image can be preloaded or
991 it can be loaded by SPL directly into RAM (e.g. using USB).
993 config SPL_RAM_DEVICE
994 bool "Support booting from preloaded image in RAM"
995 depends on SPL_RAM_SUPPORT
996 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
998 Enable booting of an image already loaded in RAM. The image has to
999 be already in memory when SPL takes over, e.g. loaded by the boot
1002 config SPL_REMOTEPROC
1003 bool "Support REMOTEPROCS"
1005 Enable support for REMOTEPROCs in SPL. This permits to load
1006 a remote processor firmware in SPL.
1008 config SPL_RTC_SUPPORT
1009 bool "Support RTC drivers"
1011 Enable RTC (Real-time Clock) support in SPL. This includes support
1012 for reading and setting the time. Some RTC devices also have some
1013 non-volatile (battery-backed) memory which is accessible if
1014 needed. This enables the drivers in drivers/rtc as part of an SPL
1017 config SPL_SATA_SUPPORT
1018 bool "Support loading from SATA"
1020 Enable support for SATA (Serial AT attachment) in SPL. This allows
1021 use of SATA devices such as hard drives and flash drivers for
1022 loading U-Boot. SATA is used in higher-end embedded systems and
1023 can provide higher performance than MMC , at somewhat higher
1024 expense and power consumption. This enables loading from SATA
1025 using a configured device.
1027 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1028 bool "SATA raw mode: by sector"
1029 depends on SPL_SATA_SUPPORT
1031 Use sector number for specifying U-Boot location on SATA disk in
1034 config SPL_SATA_RAW_U_BOOT_SECTOR
1035 hex "Sector on the SATA disk to load U-Boot from"
1036 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1038 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1039 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1041 config SPL_SERIAL_SUPPORT
1042 bool "Support serial"
1046 Enable support for serial in SPL. This allows use of a serial UART
1047 for displaying messages while SPL is running. It also brings in
1048 printf() and panic() functions. This should normally be enabled
1049 unless there are space reasons not to. Even then, consider
1050 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1052 config SPL_SPI_SUPPORT
1053 bool "Support SPI drivers"
1055 Enable support for using SPI in SPL. This is used for connecting
1056 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1057 more details on that. The SPI driver provides the transport for
1058 data between the SPI flash and the CPU. This option can be used to
1059 enable SPI drivers that are needed for other purposes also, such
1062 config SPL_SPI_FLASH_SUPPORT
1063 bool "Support SPI flash drivers"
1064 depends on SPL_SPI_SUPPORT
1066 Enable support for using SPI flash in SPL, and loading U-Boot from
1067 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1068 the SPI bus that is used to connect it to a system. It is a simple
1069 but fast bidirectional 4-wire bus (clock, chip select and two data
1070 lines). This enables the drivers in drivers/mtd/spi as part of an
1071 SPL build. This normally requires SPL_SPI_SUPPORT.
1073 if SPL_SPI_FLASH_SUPPORT
1075 config SPL_SPI_FLASH_TINY
1076 bool "Enable low footprint SPL SPI Flash support"
1077 depends on !SPI_FLASH_BAR
1078 default y if SPI_FLASH
1080 Enable lightweight SPL SPI Flash support that supports just reading
1081 data/images from flash. No support to write/erase flash. Enable
1082 this if you have SPL size limitations and don't need full
1083 fledged SPI flash support.
1085 config SPL_SPI_FLASH_SFDP_SUPPORT
1086 bool "SFDP table parsing support for SPI NOR flashes"
1087 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1089 Enable support for parsing and auto discovery of parameters for
1090 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1091 tables as per JESD216 standard in SPL.
1094 bool "Support loading from SPI flash"
1096 Enable support for loading next stage, U-Boot or otherwise, from
1097 SPI NOR in U-Boot SPL.
1099 endif # SPL_SPI_FLASH_SUPPORT
1101 config SYS_SPI_U_BOOT_OFFS
1102 hex "address of u-boot payload in SPI flash"
1104 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1106 Address within SPI-Flash from where the u-boot payload is fetched
1110 bool "Driver support for thermal devices"
1112 Enable support for temperature-sensing devices. Some SoCs have on-chip
1113 temperature sensors to permit warnings, speed throttling or even
1114 automatic power-off when the temperature gets too high or low. Other
1115 devices may be discrete but connected on a suitable bus.
1117 config SPL_USB_HOST_SUPPORT
1118 bool "Support USB host drivers"
1119 select HAVE_BLOCK_DEVICE
1121 Enable access to USB (Universal Serial Bus) host devices so that
1122 SPL can load U-Boot from a connected USB peripheral, such as a USB
1123 flash stick. While USB takes a little longer to start up than most
1124 buses, it is very flexible since many different types of storage
1125 device can be attached. This option enables the drivers in
1126 drivers/usb/host as part of an SPL build.
1128 config SPL_USB_STORAGE
1129 bool "Support loading from USB"
1130 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1132 Enable support for USB devices in SPL. This allows use of USB
1133 devices such as hard drives and flash drivers for loading U-Boot.
1134 The actual drivers are enabled separately using the normal U-Boot
1135 config options. This enables loading from USB using a configured
1138 config SPL_USB_GADGET
1139 bool "Suppport USB Gadget drivers"
1141 Enable USB Gadget API which allows to enable USB device functions
1146 config SPL_USB_ETHER
1147 bool "Support USB Ethernet drivers"
1149 Enable access to the USB network subsystem and associated
1150 drivers in SPL. This permits SPL to load U-Boot over a
1151 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1152 than from an onboard peripheral. Environment support is required
1153 since the network stack uses a number of environment variables.
1154 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1157 bool "Support DFU (Device Firmware Upgrade)"
1158 select SPL_HASH_SUPPORT
1159 select SPL_DFU_NO_RESET
1160 depends on SPL_RAM_SUPPORT
1162 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1163 RAM memory device support. The ROM code will load and execute
1164 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1165 selected device partition from host-pc using dfu-utils.
1166 This feature is useful to flash the binaries to factory or bare-metal
1167 boards using USB interface.
1170 bool "DFU device selection"
1175 depends on SPL_DFU && SPL_RAM_SUPPORT
1177 select RAM/DDR memory device for loading binary images
1178 (u-boot/kernel) to the selected device partition using
1179 DFU and execute the u-boot/kernel from RAM.
1183 config SPL_USB_SDP_SUPPORT
1184 bool "Support SDP (Serial Download Protocol)"
1186 Enable Serial Download Protocol (SDP) device support in SPL. This
1187 allows to download images into memory and execute (jump to) them
1188 using the same protocol as implemented by the i.MX family's boot ROM.
1191 config SPL_WATCHDOG_SUPPORT
1192 bool "Support watchdog drivers"
1193 imply SPL_WDT if !HW_WATCHDOG
1195 Enable support for watchdog drivers in SPL. A watchdog is
1196 typically a hardware peripheral which can reset the system when it
1197 detects no activity for a while (such as a software crash). This
1198 enables the drivers in drivers/watchdog as part of an SPL build.
1200 config SPL_YMODEM_SUPPORT
1201 bool "Support loading using Ymodem"
1202 depends on SPL_SERIAL_SUPPORT
1204 While loading from serial is slow it can be a useful backup when
1205 there is no other option. The Ymodem protocol provides a reliable
1206 means of transmitting U-Boot over a serial line for using in SPL,
1207 with a checksum to ensure correctness.
1210 bool "Support ARM Trusted Firmware"
1213 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1214 is loaded by SPL (which is considered as BL2 in ATF terminology).
1215 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1217 config SPL_ATF_NO_PLATFORM_PARAM
1218 bool "Pass no platform parameter"
1221 While we expect to call a pointer to a valid FDT (or NULL)
1222 as the platform parameter to an ATF, some ATF versions are
1223 not U-Boot aware and have an insufficiently robust parameter
1224 validation to gracefully reject a FDT being passed.
1226 If this option is enabled, the spl_atf os-type handler will
1227 always pass NULL for the platform parameter.
1229 If your ATF is affected, say Y.
1231 config SPL_AM33XX_ENABLE_RTC32K_OSC
1232 bool "Enable the RTC32K OSC on AM33xx based platforms"
1235 Enable access to the AM33xx RTC and select the external 32kHz clock
1239 bool "Support OP-TEE Trusted OS"
1242 OP-TEE is an open source Trusted OS which is loaded by SPL.
1243 More detail at: https://github.com/OP-TEE/optee_os
1246 bool "Support RISC-V OpenSBI"
1247 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1249 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1250 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1251 firmware. It is loaded and started by U-Boot SPL.
1253 More details are available at https://github.com/riscv/opensbi and
1254 https://github.com/riscv/riscv-sbi-doc
1256 config SPL_OPENSBI_LOAD_ADDR
1257 hex "OpenSBI load address"
1258 depends on SPL_OPENSBI
1260 Load address of the OpenSBI binary.
1264 depends on SUPPORT_TPL
1267 If you want to build TPL as well as the normal image and SPL, say Y.
1271 config TPL_SIZE_LIMIT
1272 hex "Maximum size of TPL image"
1276 Specifies the maximum length of the U-Boot TPL image.
1277 If this value is zero, it is ignored.
1279 config TPL_FRAMEWORK
1280 bool "Support TPL based upon the common SPL framework"
1281 default y if SPL_FRAMEWORK
1283 Enable the SPL framework under common/spl/ for TPL builds.
1284 This framework supports MMC, NAND and YMODEM and other methods
1285 loading of U-Boot's SPL stage. If unsure, say Y.
1288 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1289 depends on HANDOFF && TPL_BLOBLIST
1292 This option enables TPL to write handoff information. This can be
1293 used to pass information like the size of SDRAM from TPL to U-Boot
1294 proper. The information is also available to SPL if it is useful
1297 config TPL_BOARD_INIT
1298 bool "Call board-specific initialization in TPL"
1300 If this option is enabled, U-Boot will call the function
1301 spl_board_init() from board_init_r(). This function should be
1302 provided by the board.
1305 string "Linker script for the TPL stage"
1307 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1308 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1310 The TPL stage will usually require a different linker-script
1311 (as it runs from a different memory region) than the regular
1312 U-Boot stage. Set this to the path of the linker-script to
1315 May be left empty to trigger the Makefile infrastructure to
1316 fall back to the linker-script used for the SPL stage.
1318 config TPL_NEEDS_SEPARATE_TEXT_BASE
1319 bool "TPL needs a separate text-base"
1323 Enable, if the TPL stage should not inherit its text-base
1324 from the SPL stage. When enabled, a base address for the
1325 .text sections of the TPL stage has to be set below.
1327 config TPL_NEEDS_SEPARATE_STACK
1328 bool "TPL needs a separate initial stack-pointer"
1332 Enable, if the TPL stage should not inherit its initial
1333 stack-pointer from the settings for the SPL stage.
1335 config TPL_TEXT_BASE
1336 hex "Base address for the .text section of the TPL stage"
1337 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1339 The base address for the .text section of the TPL stage.
1342 int "Maximum size (in bytes) for the TPL stage"
1346 The maximum size (in bytes) of the TPL stage.
1349 hex "Address of the initial stack-pointer for the TPL stage"
1350 depends on TPL_NEEDS_SEPARATE_STACK
1352 The address of the initial stack-pointer for the TPL stage.
1353 Usually this will be the (aligned) top-of-stack.
1355 config TPL_BOOTROM_SUPPORT
1356 bool "Support returning to the BOOTROM (from TPL)"
1358 Some platforms (e.g. the Rockchip RK3368) provide support in their
1359 ROM for loading the next boot-stage after performing basic setup
1362 Enable this option, to return to the BOOTROM through the
1363 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1364 boot device list, if not implemented for a given board)
1366 config TPL_DRIVERS_MISC_SUPPORT
1367 bool "Support misc drivers in TPL"
1369 Enable miscellaneous drivers in TPL. These drivers perform various
1370 tasks that don't fall nicely into other categories, Enable this
1371 option to build the drivers in drivers/misc as part of an TPL
1372 build, for those that support building in TPL (not all drivers do).
1374 config TPL_ENV_SUPPORT
1375 bool "Support an environment"
1377 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1379 config TPL_GPIO_SUPPORT
1380 bool "Support GPIO in TPL"
1382 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1383 GPIOs allow U-Boot to read the state of an input line (high or
1384 low) and set the state of an output line. This can be used to
1385 drive LEDs, control power to various system parts and read user
1386 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1387 for example. Enable this option to build the drivers in
1388 drivers/gpio as part of an TPL build.
1390 config TPL_I2C_SUPPORT
1393 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1396 config TPL_LIBCOMMON_SUPPORT
1397 bool "Support common libraries"
1399 Enable support for common U-Boot libraries within TPL. See
1400 SPL_LIBCOMMON_SUPPORT for details.
1402 config TPL_LIBGENERIC_SUPPORT
1403 bool "Support generic libraries"
1405 Enable support for generic U-Boot libraries within TPL. See
1406 SPL_LIBGENERIC_SUPPORT for details.
1408 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1409 bool "Support MPC8XXX DDR init"
1411 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1412 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1414 config TPL_MMC_SUPPORT
1418 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1420 config TPL_NAND_SUPPORT
1421 bool "Support NAND flash"
1423 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1426 bool "Support PCI drivers"
1428 Enable support for PCI in TPL. For platforms that need PCI to boot,
1429 or must perform some init using PCI in SPL, this provides the
1430 necessary driver support. This enables the drivers in drivers/pci
1431 as part of a TPL build.
1433 config TPL_PCH_SUPPORT
1434 bool "Support PCH drivers"
1436 Enable support for PCH (Platform Controller Hub) devices in TPL.
1437 These are used to set up GPIOs and the SPI peripheral early in
1438 boot. This enables the drivers in drivers/pch as part of a TPL
1441 config TPL_RAM_SUPPORT
1442 bool "Support booting from RAM"
1444 Enable booting of an image in RAM. The image can be preloaded or
1445 it can be loaded by TPL directly into RAM (e.g. using USB).
1447 config TPL_RAM_DEVICE
1448 bool "Support booting from preloaded image in RAM"
1449 depends on TPL_RAM_SUPPORT
1451 Enable booting of an image already loaded in RAM. The image has to
1452 be already in memory when TPL takes over, e.g. loaded by the boot
1455 config TPL_RTC_SUPPORT
1456 bool "Support RTC drivers"
1458 Enable RTC (Real-time Clock) support in TPL. This includes support
1459 for reading and setting the time. Some RTC devices also have some
1460 non-volatile (battery-backed) memory which is accessible if
1461 needed. This enables the drivers in drivers/rtc as part of an TPL
1464 config TPL_SERIAL_SUPPORT
1465 bool "Support serial"
1469 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1472 config TPL_SPI_FLASH_SUPPORT
1473 bool "Support SPI flash drivers"
1475 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1479 bool "Support loading from SPI flash"
1480 depends on TPL_SPI_FLASH_SUPPORT
1482 Enable support for loading next stage, U-Boot or otherwise, from
1483 SPI NOR in U-Boot TPL.
1485 config TPL_SPI_SUPPORT
1486 bool "Support SPI drivers"
1488 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1491 config TPL_YMODEM_SUPPORT
1492 bool "Support loading using Ymodem"
1493 depends on TPL_SERIAL_SUPPORT
1495 While loading from serial is slow it can be a useful backup when
1496 there is no other option. The Ymodem protocol provides a reliable
1497 means of transmitting U-Boot over a serial line for using in TPL,
1498 with a checksum to ensure correctness.
1502 config SPL_AT91_MCK_BYPASS
1503 bool "Use external clock signal as a source of main clock for AT91 platforms"
1504 depends on ARCH_AT91
1507 Use external 8 to 24 Mhz clock signal as source of main clock instead
1508 of an external crystal oscillator.
1509 This option disables the internal driving on the XOUT pin.
1510 The external source has to provide a stable clock on the XIN pin.
1511 If this option is disabled, the SoC expects a crystal oscillator
1512 that needs driving on both XIN and XOUT lines.