12 config SPL_DFU_NO_RESET
17 depends on SUPPORT_SPL
20 If you want to build SPL as well as the normal image, say Y.
23 bool "Support SPL based upon the common SPL framework"
27 Enable the SPL framework under common/spl/. This framework
28 supports MMC, NAND and YMODEM and other methods loading of U-Boot
29 and the Linux Kernel. If unsure, say Y.
31 config SPL_FRAMEWORK_BOARD_INIT_F
32 bool "Define a generic function board_init_f"
33 depends on SPL_FRAMEWORK
35 Define a generic function board_init_f that:
36 - initialize the spl (spl_early_init)
37 - initialize the serial (preloader_console_init)
38 Unless you want to provide your own board_init_f, you should say Y.
41 hex "Maximum size of SPL image"
43 default 0x11000 if ARCH_MX6 && !MX6_OCRAM_256KB
44 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
47 Specifies the maximum length of the U-Boot SPL image.
48 If this value is zero, it is ignored.
50 config SPL_SIZE_LIMIT_SUBTRACT_GD
51 bool "SPL image size check: provide space for global data"
52 depends on SPL_SIZE_LIMIT > 0
54 If enabled, aligned size of global data is reserved in
55 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
56 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
57 pre-reloc global data is put into this SRAM, too.
59 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
60 bool "SPL image size check: provide space for malloc() pool before relocation"
61 depends on SPL_SIZE_LIMIT > 0
63 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
64 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
65 describes the size of SRAM available for SPL when pre-reloc malloc
66 pool is put into this SRAM, too.
68 config SPL_SIZE_LIMIT_PROVIDE_STACK
69 hex "SPL image size check: provide stack space before relocation"
70 depends on SPL_SIZE_LIMIT > 0
73 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
74 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
75 of SRAM available for SPL when the stack required before reolcation
79 hex "Maximum size of the SPL image, excluding BSS"
80 default 0x30000 if ARCH_MX6 && MX6_OCRAM_256KB
81 default 0x1b000 if AM33XX && !TI_SECURE_DEVICE
82 default 0x10000 if ARCH_MX6 && !MX6_OCRAM_256KB
83 default 0x7fa0 if SUNXI_SRAM_ADDRESS = 0x10000
84 default 0x7fa0 if SUNXI_SRAM_ADDRESS = 0x20000 && !MACH_SUN50I_H616
85 default 0x7000 if RCAR_GEN3
86 default 0x5fa0 if SUNXI_SRAM_ADDRESS = 0x0
89 Maximum size of the SPL image (text, data, rodata, and linker lists
90 sections), BSS excluded. When defined, the linker checks that the
91 actual size does not exceed it.
94 hex "Offset to which the SPL should be padded before appending the SPL payload"
95 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
96 default 0x11000 if ARCH_MX7 || (ARCH_MX6 && !MX6_OCRAM_256KB)
97 default 0x10000 if ARCH_KEYSTONE
98 default 0x8000 if ARCH_SUNXI && !MACH_SUN50I_H616
99 default TPL_MAX_SIZE if TPL_MAX_SIZE > SPL_MAX_SIZE
102 Image offset to which the SPL should be padded before appending the
103 SPL payload. By default, this is defined as CONFIG_SPL_MAX_SIZE, or 0 if
104 CONFIG_SPL_MAX_SIZE is undefined. CONFIG_SPL_PAD_TO must be either
105 0, meaning to append the SPL payload without any padding, or >=
109 prompt "Enforce SPL BSS limit"
110 depends on SPL && !PPC
111 default SPL_BSS_LIMIT
113 In some platforms we only want to enforce a limit on the size of the
114 BSS in memory. On other platforms we need to enforce a limit on the
115 whole of the memory allocation as we're strictly limited to a small
116 typically non-DRAM location. Finally, other platforms do not enforce
117 a memory limit within SPL.
119 config SPL_NO_BSS_LIMIT
120 bool "Do not enforce a build time limit on the size of the BSS"
123 bool "Enforce a limit on the size of the BSS only"
125 config SPL_FOOTPRINT_LIMIT
126 bool "Enforce a limit on the whole of memory allocated to SPL, BSS included"
130 config SPL_BSS_MAX_SIZE
131 hex "Maximum size in memory allocated to the SPL BSS"
132 depends on SPL_BSS_LIMIT
133 default 0x100000 if ARCH_MX6 || RISCV
134 default 0x80000 if ARCH_OMAP2PLUS || ARCH_SUNXI
136 When non-zero, the linker checks that the actual memory used by SPL
137 from __bss_start to __bss_end does not exceed it.
139 config SPL_MAX_FOOTPRINT
140 hex "Maximum size in memory allocated to the SPL, BSS included"
141 depends on SPL_FOOTPRINT_LIMIT
143 When non-zero, the linker checks that the actual memory used by SPL
144 from _start to __bss_end does not exceed it.
146 config SPL_SYS_STACK_F_CHECK_BYTE
150 Constant used to check the stack
152 config SPL_SYS_REPORT_STACK_F_USAGE
153 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
154 bool "Check and report stack usage in SPL before relocation"
156 If this option is enabled, the initial SPL stack is filled with 0xaa
157 very early, up to the size configured with
158 SPL_SIZE_LIMIT_PROVIDE_STACK.
159 Later when SPL is done using this initial stack and switches to a
160 stack in DRAM, the actually used size of this initial stack is
161 reported by examining the memory and searching for the lowest
162 occurrence of non 0xaa bytes.
163 This default implementation works for stacks growing down only.
165 config SPL_SHOW_ERRORS
166 bool "Show more information when something goes wrong"
168 This enabled more verbose error messages and checking when something
169 goes wrong in SPL. For example, it shows the error code when U-Boot
170 cannot be located. This can help to diagnose the problem and figure
171 out a fix, particularly during development.
173 This adds a small amount to SPL code size, perhaps 100 bytes.
175 config SPL_BINMAN_SYMBOLS
176 bool "Declare binman symbols in SPL"
177 depends on SPL_FRAMEWORK && BINMAN
180 This enables use of symbols in SPL which refer to U-Boot, enabling SPL
181 to obtain the location of U-Boot simply by calling spl_get_image_pos()
182 and spl_get_image_size().
184 For this to work, you must have a U-Boot image in the binman image, so
185 binman can update SPL with the location of it.
187 menu "PowerPC and LayerScape SPL Boot options"
190 bool "Load SPL from NAND flash"
191 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
194 bool "Load SPL from SD Card / eMMC"
195 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
198 bool "Load SPL from SPI flash"
199 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
202 bool "Create SPL in Freescale PBI format"
203 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
206 Create boot binary having SPL binary in PBI format concatenated with
209 config SPL_SYS_CCSR_DO_NOT_RELOCATE
210 bool "Ensures that CCSR is not relocated"
213 If this is defined, then CONFIG_SYS_CCSRBAR_PHYS will be forced to a
214 value that ensures that CCSR is not relocated.
216 config TPL_SYS_CCSR_DO_NOT_RELOCATE
218 depends on SPL_SYS_CCSR_DO_NOT_RELOCATE
222 menu "PowerPC SPL specific options"
223 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
225 config SPL_INIT_MINIMAL
226 bool "Arch init code will be built for a very small image"
228 config SPL_FLUSH_IMAGE
229 bool "Clean dcache and invalidate icache after loading the image"
231 config SPL_SKIP_RELOCATE
232 bool "Skip relocating SPL"
237 bool "Pass hand-off information from SPL to U-Boot proper"
238 depends on SPL && BLOBLIST
240 It is useful to be able to pass information from SPL to U-Boot
241 proper to preserve state that is known in SPL and is needed in U-Boot.
242 Enable this to locate the handoff information in U-Boot proper, early
243 in boot. It is available in gd->handoff. The state state is set up
244 in SPL (or TPL if that is being used).
249 bool "Pass hand-off information from SPL to U-Boot proper"
250 depends on HANDOFF && SPL_BLOBLIST
253 This option enables SPL to write handoff information. This can be
254 used to pass information like the size of SDRAM from SPL to U-Boot
255 proper. Also SPL can receive information from TPL in the same place
259 string "Linker script for the SPL stage"
260 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
262 The SPL stage will usually require a different linker-script
263 (as it runs from a different memory region) than the regular
264 U-Boot stage. Set this to the path of the linker-script to
269 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
270 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
271 default 0x20060 if SUN50I_GEN_H6
272 default 0x00060 if ARCH_SUNXI
273 default 0xfffc0000 if ARCH_ZYNQMP
276 The address in memory that SPL will be running from.
278 config SPL_BOARD_INIT
279 bool "Call board-specific initialization in SPL"
281 If this option is enabled, U-Boot will call the function
282 spl_board_init() from board_init_r(). This function should be
283 provided by the board.
285 config VPL_BOARD_INIT
286 bool "Call board-specific initialization in VPL"
288 If this option is enabled, U-Boot will call the function
289 spl_board_init() from board_init_r(). This function should be
290 provided by the board.
292 config SPL_BOOTROM_SUPPORT
293 bool "Support returning to the BOOTROM"
295 Some platforms (e.g. the Rockchip RK3368) provide support in their
296 ROM for loading the next boot-stage after performing basic setup
299 Enable this option, to return to the BOOTROM through the
300 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
301 boot device list, if not implemented for a given board)
303 config SPL_BOOTCOUNT_LIMIT
304 bool "Support bootcount in SPL"
305 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
307 On some boards, which use 'falcon' mode, it is necessary to check
308 and increment the number of boot attempts. Such boards do not
309 use proper U-Boot for normal boot flow and hence needs those
310 adjustments to be done in the SPL.
312 config SPL_RAW_IMAGE_SUPPORT
313 bool "Support SPL loading and booting of RAW images"
314 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
316 depends on !TI_SECURE_DEVICE
318 SPL will support loading and booting a RAW image when this option
319 is y. If this is not set, SPL will move on to other available
320 boot media to find a suitable image.
322 config SPL_LEGACY_IMAGE_FORMAT
323 bool "Support SPL loading and booting of Legacy images"
324 default y if !SPL_LOAD_FIT
325 depends on !TI_SECURE_DEVICE
327 SPL will support loading and booting Legacy images when this option
328 is y. If this is not set, SPL will move on to other available
329 boot media to find a suitable image.
331 config SPL_LEGACY_IMAGE_CRC_CHECK
332 bool "Check CRC of Legacy images"
333 depends on SPL_LEGACY_IMAGE_FORMAT
336 Enable this to check the CRC of Legacy images. While this increases
337 reliability, it affects both code size and boot duration.
338 If disabled, Legacy images are booted if the image magic and size
339 are correct, without further integrity checks.
341 config SPL_SYS_MALLOC_SIMPLE
343 prompt "Only use malloc_simple functions in the SPL"
345 Say Y here to only use the *_simple malloc functions from
346 malloc_simple.c, rather then using the versions from dlmalloc.c;
347 this will make the SPL binary smaller at the cost of more heap
348 usage as the *_simple malloc functions do not re-use free-ed mem.
350 config TPL_SYS_MALLOC_SIMPLE
352 prompt "Only use malloc_simple functions in the TPL"
355 Say Y here to only use the *_simple malloc functions from
356 malloc_simple.c, rather then using the versions from dlmalloc.c;
357 this will make the TPL binary smaller at the cost of more heap
358 usage as the *_simple malloc functions do not re-use free-ed mem.
360 config SPL_SHARES_INIT_SP_ADDR
361 bool "SPL and U-Boot use the same initial stack pointer location"
362 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
363 default n if ARCH_SUNXI || ARCH_MX6
366 In many cases, we can use the same initial stack pointer address for
367 both SPL and U-Boot itself. If you need to specify a different address
368 however, say N here and then set a different value in CONFIG_SPL_STACK.
371 hex "Initial stack pointer location"
372 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
373 depends on !SPL_SHARES_INIT_SP_ADDR
374 default 0x93ffb8 if ARCH_MX6 && MX6_OCRAM_256KB
375 default 0x91ffb8 if ARCH_MX6 && !MX6_OCRAM_256KB
377 Address of the start of the stack SPL will use before SDRAM is
381 bool "Enable SDRAM location for SPL stack"
383 SPL starts off execution in SRAM and thus typically has only a small
384 stack available. Since SPL sets up DRAM while in its board_init_f()
385 function, it is possible for the stack to move there before
386 board_init_r() is reached. This option enables a special SDRAM
387 location for the SPL stack. U-Boot SPL switches to this after
388 board_init_f() completes, and before board_init_r() starts.
390 config SPL_STACK_R_ADDR
391 depends on SPL_STACK_R
392 hex "SDRAM location for SPL stack"
393 default 0x82000000 if ARCH_OMAP2PLUS
395 Specify the address in SDRAM for the SPL stack. This will be set up
396 before board_init_r() is called.
398 config SPL_STACK_R_MALLOC_SIMPLE_LEN
399 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
400 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
403 Specify the amount of the stack to use as memory pool for
404 malloc_simple after switching the stack to DRAM. This may be set
405 to give board_init_r() a larger heap then the initial heap in
406 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
408 config SPL_SEPARATE_BSS
409 bool "BSS section is in a different memory region from text"
411 Some platforms need a large BSS region in SPL and can provide this
412 because RAM is already set up. In this case BSS can be moved to RAM.
413 This option should then be enabled so that the correct device tree
414 location is used. Normally we put the device tree at the end of BSS
415 but with this option enabled, it goes at _image_binary_end.
419 depends on SPL_OF_PLATDATA
420 # Bind cannot be supported because the udevice structs are in read-only
421 # memory so we cannot update the linked lists.
422 select SPL_OF_PLATDATA_NO_BIND
423 select SPL_OF_PLATDATA_RT
425 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
426 section of memory. This means that of-platdata must make a copy (in
427 writeable memory) of anything it wants to modify, such as
430 config TPL_SEPARATE_BSS
431 bool "BSS section is in a different memory region from text"
432 default y if SPL_SEPARATE_BSS
434 Some platforms need a large BSS region in TPL and can provide this
435 because RAM is already set up. In this case BSS can be moved to RAM.
436 This option should then be enabled so that the correct device tree
437 location is used. Normally we put the device tree at the end of BSS
438 but with this option enabled, it goes at _image_binary_end.
440 config SPL_BANNER_PRINT
441 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
444 If this option is enabled, SPL will print the banner with version
445 info. Disabling this option could be useful to reduce SPL boot time
446 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
448 config TPL_BANNER_PRINT
449 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
453 If this option is enabled, TPL will print the banner with version
454 info. Disabling this option could be useful to reduce TPL boot time
455 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
458 depends on ARM && !ARM64
459 bool "Allows initializing BSS early before entering board_init_f"
461 On some platform we have sufficient memory available early on to
462 allow setting up and using a basic BSS prior to entering
463 board_init_f. Activating this option will also de-activate the
464 clearing of BSS during the SPL relocation process, thus allowing
465 to carry state from board_init_f to board_init_r by way of BSS.
467 config SPL_DISPLAY_PRINT
468 bool "Display a board-specific message in SPL"
470 If this option is enabled, U-Boot will call the function
471 spl_display_print() immediately after displaying the SPL console
472 banner ("U-Boot SPL ..."). This function should be provided by
475 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
476 bool "MMC raw mode: by sector"
477 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
478 ARCH_MX6 || ARCH_MX7 || \
479 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
480 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
481 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
482 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
484 Use sector number for specifying U-Boot location on MMC/SD in
487 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
488 hex "Address on the MMC to load U-Boot from"
489 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
490 default 0x40 if ARCH_SUNXI
491 default 0x75 if ARCH_DAVINCI
492 default 0x8a if ARCH_MX6 || ARCH_MX7
493 default 0x100 if ARCH_UNIPHIER
494 default 0x0 if ARCH_MVEBU
495 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
496 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
497 OMAP54XX || AM33XX || AM43XX || ARCH_K3
498 default 0x4000 if ARCH_ROCKCHIP
499 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
501 Address on the MMC to load U-Boot from, when the MMC is being used
502 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
504 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
505 hex "U-Boot main hardware partition image offset"
506 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
507 default 0x10 if ARCH_SUNXI
510 On some platforms SPL location depends on hardware partition. The ROM
511 code skips the MBR sector when loading SPL from main hardware data
512 partition. This adds offset to the main U-Boot image. Set this symbol
513 to the number of skipped sectors.
515 If unsure, leave the default.
517 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
518 bool "MMC Raw mode: by partition"
520 Use a partition for loading U-Boot when using MMC/SD in raw mode.
522 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
523 hex "Partition to use to load U-Boot from"
524 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
527 Partition on the MMC to load U-Boot from when the MMC is being
530 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
531 bool "MMC raw mode: by partition type"
532 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
534 Use partition type for specifying U-Boot partition on MMC/SD in
535 raw mode. U-Boot will be loaded from the first partition of this
538 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
539 hex "Partition Type on the MMC to load U-Boot from"
540 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
542 Partition Type on the MMC to load U-Boot from, when the MMC is being
545 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
546 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
547 depends on SUPPORT_EMMC_BOOT
549 eMMC boot partition is normally configured by the bits of the EXT_CSD
550 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
551 cases it might be required in SPL to load the image from different
552 partition than the partition selected by EXT_CSC_PART_CONFIG register.
553 Enable this option if you intend to use an eMMC boot partition other
554 then selected via EXT_CSC_PART_CONFIG register and specify the custom
555 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
558 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
559 int "Number of the eMMC boot partition to use"
560 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
563 eMMC boot partition number to use when the eMMC in raw mode and
564 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
565 by user defined partition number.
569 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
570 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
572 Enable this to support CRC32 in uImages or FIT images within SPL.
573 This is a 32-bit checksum value that can be used to verify images.
574 For FIT images, this is the least secure type of checksum, suitable
575 for detected accidental image corruption. For secure applications you
576 should consider SHA1 or SHA256.
582 Enable this to support MD5 in FIT images within SPL. An MD5
583 checksum is a 128-bit hash value used to check that the image
584 contents have not been corrupted. Note that MD5 is not considered
585 secure as it is possible (with a brute-force attack) to adjust the
586 image while still retaining the same MD5 hash value. For secure
587 applications where images may be changed maliciously, you should
588 consider SHA256 or SHA384.
590 config SPL_FIT_IMAGE_TINY
591 bool "Remove functionality from SPL FIT loading to reduce size"
593 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
594 default y if ARCH_IMX8M
596 Enable this to reduce the size of the FIT image loading code
597 in SPL, if space for the SPL binary is very tight.
599 This skips the recording of each loaded payload
600 (i.e. loadable) into the FDT (modifying the loaded FDT to
601 ensure this information is available to the next image
605 bool "Support CACHE drivers"
607 Enable CACHE drivers in SPL. These drivers can keep data so that
608 future requests for that data can be served faster. Enable this option
609 to build the drivers in drivers/cache as part of an SPL build.
612 bool "Support CPU drivers"
614 Enable this to support CPU drivers in SPL. These drivers can set
615 up CPUs and provide information about them such as the model and
616 name. This can be useful in SPL since setting up the CPUs earlier
617 may improve boot performance. Enable this option to build the
618 drivers in drivers/cpu as part of an SPL build.
621 bool "Support crypto drivers"
623 Enable crypto drivers in SPL. These drivers can be used to
624 accelerate secure boot processing in secure applications. Enable
625 this option to build the drivers in drivers/crypto as part of an
629 bool "Support DMA drivers"
631 Enable DMA (direct-memory-access) drivers in SPL. These drivers
632 can be used to handle memory-to-peripheral data transfer without
633 the CPU moving the data. Enable this option to build the drivers
634 in drivers/dma as part of an SPL build.
636 config SPL_DRIVERS_MISC
637 bool "Support misc drivers"
639 Enable miscellaneous drivers in SPL. These drivers perform various
640 tasks that don't fall nicely into other categories, Enable this
641 option to build the drivers in drivers/misc as part of an SPL
642 build, for those that support building in SPL (not all drivers do).
644 config SPL_ENV_SUPPORT
645 bool "Support an environment"
647 Enable environment support in SPL. The U-Boot environment provides
648 a number of settings (essentially name/value pairs) which can
649 control many aspects of U-Boot's operation. Normally this is not
650 needed in SPL as it has a much simpler task with less
651 configuration. But some boards use this to support 'Falcon' boot
652 on EXT2 and FAT, where SPL boots directly into Linux without
653 starting U-Boot first. Enabling this option will make env_get()
654 and env_set() available in SPL.
657 bool "Support save environment"
658 depends on SPL_ENV_SUPPORT
659 select SPL_MMC_WRITE if ENV_IS_IN_MMC
661 Enable save environment support in SPL after setenv. By default
662 the saveenv option is not provided in SPL, but some boards need
663 this support in 'Falcon' boot, where SPL need to boot from
664 different images based on environment variable set by OS. For
665 example OS may set "reboot_image" environment variable to
666 "recovery" inorder to boot recovery image by SPL. The SPL read
667 "reboot_image" and act accordingly and change the reboot_image
668 to default mode using setenv and save the environment.
671 bool "Support Ethernet"
672 depends on SPL_ENV_SUPPORT
675 Enable access to the network subsystem and associated Ethernet
676 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
677 link rather than from an on-board peripheral. Environment support
678 is required since the network stack uses a number of environment
679 variables. See also SPL_NET.
682 bool "Support EXT filesystems"
684 Enable support for EXT2/3/4 filesystems with SPL. This permits
685 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
686 filesystem from within SPL. Support for the underlying block
687 device (e.g. MMC or USB) must be enabled separately.
689 config SPL_FS_SQUASHFS
690 bool "Support SquashFS filesystems"
693 Enable support for SquashFS filesystems with SPL. This permits
694 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
695 filesystem from within SPL. Support for the underlying block
696 device (e.g. MMC or USB) must be enabled separately.
699 bool "Support FAT filesystems"
702 Enable support for FAT and VFAT filesystems with SPL. This
703 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
704 filesystem from within SPL. Support for the underlying block
705 device (e.g. MMC or USB) must be enabled separately.
707 config SPL_FS_LOAD_PAYLOAD_NAME
708 string "File to load for U-Boot from the filesystem"
709 depends on SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS
710 default "tispl.bin" if SYS_K3_SPL_ATF
711 default "u-boot.itb" if SPL_LOAD_FIT
714 Filename to read to load U-Boot when reading from filesystem.
716 config SPL_FS_LOAD_KERNEL_NAME
717 string "File to load for the OS kernel from the filesystem"
718 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
721 Filename to read to load for the OS kernel when reading from the
724 config SPL_FS_LOAD_ARGS_NAME
725 string "File to load for the OS kernel argument parameters from the filesystem"
726 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
729 Filename to read to load for the OS kernel argument parameters from
733 bool "Support write for FAT filesystems"
735 Enable write support for FAT and VFAT filesystems with SPL.
736 Support for the underlying block device (e.g. MMC or USB) must be
742 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
743 provide software-configurable hardware which is typically used to
744 implement peripherals (such as UARTs, LCD displays, MMC) or
745 accelerate custom processing functions, such as image processing
746 or machine learning. Sometimes it is useful to program the FPGA
747 as early as possible during boot, and this option can enable that
751 bool "Support GPIO in SPL"
753 Enable support for GPIOs (General-purpose Input/Output) in SPL.
754 GPIOs allow U-Boot to read the state of an input line (high or
755 low) and set the state of an output line. This can be used to
756 drive LEDs, control power to various system parts and read user
757 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
758 for example. Enable this option to build the drivers in
759 drivers/gpio as part of an SPL build.
764 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
765 I2C works with a clock and data line which can be driven by a
766 one or more masters or slaves. It is a fairly complex bus but is
767 widely used as it only needs two lines for communication. Speeds of
768 400kbps are typical but up to 3.4Mbps is supported by some
769 hardware. I2C can be useful in SPL to configure power management
770 ICs (PMICs) before raising the CPU clock speed, for example.
771 Enable this option to build the drivers in drivers/i2c as part of
774 config SPL_LIBCOMMON_SUPPORT
775 bool "Support common libraries"
777 Enable support for common U-Boot libraries within SPL. These
778 libraries include common code to deal with U-Boot images,
779 environment and USB, for example. This option is enabled on many
780 boards. Enable this option to build the code in common/ as part of
783 config SPL_LIBDISK_SUPPORT
784 bool "Support disk partitions"
787 Enable support for disk partitions within SPL. 'Disk' is something
788 of a misnomer as it includes non-spinning media such as flash (as
789 used in MMC and USB sticks). Partitions provide a way for a disk
790 to be split up into separate regions, with a partition table placed
791 at the start or end which describes the location and size of each
792 'partition'. These partitions are typically uses as individual block
793 devices, typically with an EXT2 or FAT filesystem in each. This
794 option enables whatever partition support has been enabled in
795 U-Boot to also be used in SPL. It brings in the code in disk/.
797 config SPL_LIBGENERIC_SUPPORT
798 bool "Support generic libraries"
800 Enable support for generic U-Boot libraries within SPL. These
801 libraries include generic code to deal with device tree, hashing,
802 printf(), compression and the like. This option is enabled on many
803 boards. Enable this option to build the code in lib/ as part of an
806 config SPL_DM_MAILBOX
807 bool "Support Mailbox"
809 Enable support for Mailbox within SPL. This enable the inter
810 processor communication protocols tobe used within SPL. Enable
811 this option to build the drivers in drivers/mailbox as part of
817 select HAVE_BLOCK_DEVICE
819 Enable support for MMC (Multimedia Card) within SPL. This enables
820 the MMC protocol implementation and allows any enabled drivers to
821 be used within SPL. MMC can be used with or without disk partition
822 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
823 this option to build the drivers in drivers/mmc as part of an SPL
826 config SYS_MMCSD_FS_BOOT_PARTITION
827 int "MMC Boot Partition"
830 Partition on the MMC to load U-Boot from when the MMC is being
832 Use -1 as a special value to use the first bootable partition.
835 bool "Tiny MMC framework in SPL"
838 Enable MMC framework tinification support. This option is useful if
839 if your SPL is extremely size constrained. Heed the warning, enable
840 this option if and only if you know exactly what you are doing, if
841 you are reading this help text, you most likely have no idea :-)
843 The MMC framework is reduced to bare minimum to be useful. No malloc
844 support is needed for the MMC framework operation with this option
845 enabled. The framework supports exactly one MMC device and exactly
846 one MMC driver. The MMC driver can be adjusted to avoid any malloc
847 operations too, which can remove the need for malloc support in SPL
848 and thus further reduce footprint.
851 bool "MMC/SD/SDIO card support for write operations in SPL"
854 Enable write access to MMC and SD Cards in SPL
857 config SPL_MPC8XXX_INIT_DDR
858 bool "Support MPC8XXX DDR init"
860 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
861 random-access memory) on the MPC8XXX family within SPL. This
862 allows DRAM to be set up before loading U-Boot into that DRAM,
865 config SPL_MTD_SUPPORT
866 bool "Support MTD drivers"
868 Enable support for MTD (Memory Technology Device) within SPL. MTD
869 provides a block interface over raw NAND and can also be used with
870 SPI flash. This allows SPL to load U-Boot from supported MTD
871 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
872 to enable specific MTD drivers.
875 bool "Support new Mentor Graphics USB"
877 Enable support for Mentor Graphics USB in SPL. This is a new
878 driver used by some boards. Enable this option to build
879 the drivers in drivers/usb/musb-new as part of an SPL build. The
880 old drivers are in drivers/usb/musb.
882 config SPL_NAND_SUPPORT
883 bool "Support NAND flash"
885 Enable support for NAND (Negative AND) flash in SPL. NAND flash
886 can be used to allow SPL to load U-Boot from supported devices.
887 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
890 config SPL_NAND_RAW_ONLY
891 bool "Support to boot only raw u-boot.bin images"
892 depends on SPL_NAND_SUPPORT
894 Use this only if you need to save space.
896 config SPL_NAND_DRIVERS
897 bool "Use standard NAND driver"
899 SPL uses normal NAND drivers, not minimal drivers.
902 bool "Include standard ECC in SPL"
904 config SPL_NAND_SOFTECC
905 bool "Use software ECC in SPL"
906 depends on SPL_NAND_ECC
908 config SPL_NAND_SIMPLE
909 bool "Support simple NAND drivers in SPL"
911 Support for NAND boot using simple NAND drivers that
912 expose the cmd_ctrl() interface.
915 depends on SPL_NAND_DRIVERS
916 bool "Use Base NAND Driver"
918 Include nand_base.c in the SPL.
920 config SPL_NAND_IDENT
921 depends on SPL_NAND_BASE
922 bool "Use chip ID to identify NAND flash"
924 SPL uses the chip ID list to identify the NAND flash.
929 Enable support for loading payloads from UBI. See
930 README.ubispl for more info.
934 bool "Support SPI DM drivers in SPL"
936 Enable support for SPI DM drivers in SPL.
938 config SPL_DM_SPI_FLASH
939 bool "Support SPI DM FLASH drivers in SPL"
941 Enable support for SPI DM flash drivers in SPL.
945 config SPL_UBI_LOAD_BY_VOLNAME
946 bool "Support loading volumes by name"
948 This enables support for loading UBI volumes by name. When this
949 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
950 configure the volume name from which to load U-Boot.
952 config SPL_UBI_MAX_VOL_LEBS
953 int "Maximum number of LEBs per volume"
956 The maximum number of logical eraseblocks which a static volume
957 to load can contain. Used for sizing the scan data structure.
959 config SPL_UBI_MAX_PEB_SIZE
960 int "Maximum PEB size"
963 The maximum physical erase block size.
965 config SPL_UBI_MAX_PEBS
966 int "Maximum number of PEBs"
969 The maximum physical erase block size. If not overridden by
970 board code, this value will be used as the actual number of PEBs.
972 config SPL_UBI_PEB_OFFSET
973 int "Offset to first UBI PEB"
976 The offset in number of PEBs from the start of flash to the first
977 PEB part of the UBI image.
979 config SPL_UBI_VID_OFFSET
980 int "Offset to VID header"
983 config SPL_UBI_LEB_START
984 int "Offset to LEB in PEB"
987 The offset in bytes to the LEB within a PEB.
989 config SPL_UBI_INFO_ADDR
990 hex "Address to place UBI scan info"
993 Address for ubispl to place the scan info. Read README.ubispl to
994 determine the required size
996 config SPL_UBI_VOL_IDS
997 int "Maximum volume id"
1000 The maximum volume id which can be loaded. Used for sizing the
1001 scan data structure.
1003 config SPL_UBI_LOAD_MONITOR_ID
1004 int "id of U-Boot volume"
1007 The UBI volume id from which to load U-Boot
1009 config SPL_UBI_LOAD_MONITOR_VOLNAME
1010 string "volume name of U-Boot volume"
1011 depends on SPL_UBI_LOAD_BY_VOLNAME
1013 The UBI volume name from which to load U-Boot
1015 config SPL_UBI_LOAD_KERNEL_ID
1016 int "id of kernel volume"
1017 depends on SPL_OS_BOOT && SPL_UBI
1019 The UBI volume id from which to load the kernel
1021 config SPL_UBI_LOAD_ARGS_ID
1022 int "id of kernel args volume"
1023 depends on SPL_OS_BOOT && SPL_UBI
1025 The UBI volume id from which to load the device tree
1027 config UBI_SPL_SILENCE_MSG
1028 bool "silence UBI SPL messages"
1030 Disable messages from UBI SPL. This leaves warnings
1036 bool "Support networking"
1038 Enable support for network devices (such as Ethernet) in SPL.
1039 This permits SPL to load U-Boot over a network link rather than
1040 from an on-board peripheral. Environment support is required since
1041 the network stack uses a number of environment variables. See also
1045 config SPL_NET_VCI_STRING
1046 string "BOOTP Vendor Class Identifier string sent by SPL"
1048 As defined by RFC 2132 the vendor class identifier field can be
1049 sent by the client to identify the vendor type and configuration
1050 of a client. This is often used in practice to allow for the DHCP
1051 server to specify different files to load depending on if the ROM,
1052 SPL or U-Boot itself makes the request
1055 config SPL_NO_CPU_SUPPORT
1056 bool "Drop CPU code in SPL"
1058 This is specific to the ARM926EJ-S CPU. It disables the standard
1059 start.S start-up code, presumably so that a replacement can be
1060 used on that CPU. You should not enable it unless you know what
1063 config SPL_NOR_SUPPORT
1064 bool "Support NOR flash"
1066 Enable support for loading U-Boot from memory-mapped NOR (Negative
1067 OR) flash in SPL. NOR flash is slow to write but fast to read, and
1068 a memory-mapped device makes it very easy to access. Loading from
1069 NOR is typically achieved with just a memcpy().
1071 config SPL_XIP_SUPPORT
1075 Enable support for execute in place of U-Boot or kernel image. There
1076 is no need to copy image from flash to ram if flash supports execute
1077 in place. Its very useful in systems having enough flash but not
1078 enough ram to load the image.
1080 config SPL_ONENAND_SUPPORT
1081 bool "Support OneNAND flash"
1083 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
1084 a type of NAND flash and therefore can be used to allow SPL to
1085 load U-Boot from supported devices. This enables the drivers in
1086 drivers/mtd/onenand as part of an SPL build.
1089 bool "Activate Falcon Mode"
1090 depends on !TI_SECURE_DEVICE
1092 Enable booting directly to an OS from SPL.
1093 for more info read doc/README.falcon
1097 hex "addr, where OS is found"
1098 depends on SPL_NOR_SUPPORT
1100 Specify the address, where the OS image is found, which
1105 config SPL_FALCON_BOOT_MMCSD
1106 bool "Enable Falcon boot from MMC or SD media"
1107 depends on SPL_OS_BOOT && SPL_MMC
1109 Select this if the Falcon mode OS image mode is on MMC or SD media.
1111 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
1112 hex "Falcon mode: Sector to load kernel uImage from MMC"
1113 depends on SPL_FALCON_BOOT_MMCSD
1115 When Falcon mode is used with an MMC or SD media, SPL needs to know
1116 where to look for the kernel uImage. The image is expected to begin
1117 at the raw MMC specified in this config.
1118 Note that the Falcon mode image can also be a FIT, if FIT support is
1122 string "SPL payload"
1123 default "tpl/u-boot-with-tpl.bin" if TPL
1124 default "u-boot.bin"
1126 Payload for SPL boot. For backward compatibility, default to
1127 u-boot.bin, i.e. RAW image without any header. In case of
1128 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
1132 bool "Support PCI drivers"
1134 Enable support for PCI in SPL. For platforms that need PCI to boot,
1135 or must perform some init using PCI in SPL, this provides the
1136 necessary driver support. This enables the drivers in drivers/pci
1137 as part of an SPL build.
1140 bool "Support PCH drivers"
1142 Enable support for PCH (Platform Controller Hub) devices in SPL.
1143 These are used to set up GPIOs and the SPI peripheral early in
1144 boot. This enables the drivers in drivers/pch as part of an SPL
1147 config SPL_POST_MEM_SUPPORT
1148 bool "Support POST drivers"
1150 Enable support for POST (Power-on Self Test) in SPL. POST is a
1151 procedure that checks that the hardware (CPU or board) appears to
1152 be functionally correctly. It is a sanity check that can be
1153 performed before booting. This enables the drivers in post/drivers
1154 as part of an SPL build.
1157 bool "Support reset drivers"
1160 Enable support for reset control in SPL.
1161 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1162 by using the generic reset API provided by driver model.
1163 This enables the drivers in drivers/reset as part of an SPL build.
1166 bool "Support power drivers"
1168 Enable support for power control in SPL. This includes support
1169 for PMICs (Power-management Integrated Circuits) and some of the
1170 features provided by PMICs. In particular, voltage regulators can
1171 be used to enable/disable power and vary its voltage. That can be
1172 useful in SPL to turn on boot peripherals and adjust CPU voltage
1173 so that the clock speed can be increased. This enables the drivers
1174 in drivers/power, drivers/power/pmic and drivers/power/regulator
1175 as part of an SPL build.
1177 config SPL_POWER_DOMAIN
1178 bool "Support power domain drivers"
1181 Enable support for power domain control in SPL. Many SoCs allow
1182 power to be applied to or removed from portions of the SoC (power
1183 domains). This may be used to save power. This API provides the
1184 means to control such power management hardware. This enables
1185 the drivers in drivers/power/domain as part of a SPL build.
1187 config SPL_RAM_SUPPORT
1188 bool "Support booting from RAM"
1189 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1191 Enable booting of an image in RAM. The image can be preloaded or
1192 it can be loaded by SPL directly into RAM (e.g. using USB).
1194 config SPL_RAM_DEVICE
1195 bool "Support booting from preloaded image in RAM"
1196 depends on SPL_RAM_SUPPORT
1197 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1199 Enable booting of an image already loaded in RAM. The image has to
1200 be already in memory when SPL takes over, e.g. loaded by the boot
1203 config SPL_REMOTEPROC
1204 bool "Support REMOTEPROCS"
1206 Enable support for REMOTEPROCs in SPL. This permits to load
1207 a remote processor firmware in SPL.
1210 bool "Support RTC drivers"
1212 Enable RTC (Real-time Clock) support in SPL. This includes support
1213 for reading and setting the time. Some RTC devices also have some
1214 non-volatile (battery-backed) memory which is accessible if
1215 needed. This enables the drivers in drivers/rtc as part of an SPL
1219 bool "Support loading from SATA"
1221 Enable support for SATA (Serial AT attachment) in SPL. This allows
1222 use of SATA devices such as hard drives and flash drivers for
1223 loading U-Boot. SATA is used in higher-end embedded systems and
1224 can provide higher performance than MMC , at somewhat higher
1225 expense and power consumption. This enables loading from SATA
1226 using a configured device.
1228 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1229 bool "SATA raw mode: by sector"
1231 default y if ARCH_MVEBU
1233 Use sector number for specifying U-Boot location on SATA disk in
1236 config SPL_SATA_RAW_U_BOOT_SECTOR
1237 hex "Sector on the SATA disk to load U-Boot from"
1238 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1239 default 0x1 if ARCH_MVEBU
1241 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1242 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1245 bool "Support serial"
1249 Enable support for serial in SPL. This allows use of a serial UART
1250 for displaying messages while SPL is running. It also brings in
1251 printf() and panic() functions. This should normally be enabled
1252 unless there are space reasons not to. Even then, consider
1253 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1256 bool "Support SPI drivers"
1258 Enable support for using SPI in SPL. This is used for connecting
1259 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1260 more details on that. The SPI driver provides the transport for
1261 data between the SPI flash and the CPU. This option can be used to
1262 enable SPI drivers that are needed for other purposes also, such
1265 config SPL_SPI_FLASH_SUPPORT
1266 bool "Support SPI flash drivers"
1269 Enable support for using SPI flash in SPL, and loading U-Boot from
1270 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1271 the SPI bus that is used to connect it to a system. It is a simple
1272 but fast bidirectional 4-wire bus (clock, chip select and two data
1273 lines). This enables the drivers in drivers/mtd/spi as part of an
1274 SPL build. This normally requires SPL_SPI.
1276 if SPL_SPI_FLASH_SUPPORT
1278 config SPL_SPI_FLASH_TINY
1279 bool "Enable low footprint SPL SPI Flash support"
1280 depends on !SPI_FLASH_BAR
1281 default y if SPI_FLASH
1283 Enable lightweight SPL SPI Flash support that supports just reading
1284 data/images from flash. No support to write/erase flash. Enable
1285 this if you have SPL size limitations and don't need full
1286 fledged SPI flash support.
1288 config SPL_SPI_FLASH_SFDP_SUPPORT
1289 bool "SFDP table parsing support for SPI NOR flashes"
1290 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1292 Enable support for parsing and auto discovery of parameters for
1293 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1294 tables as per JESD216 standard in SPL.
1296 config SPL_SPI_FLASH_MTD
1297 bool "Support for SPI flash MTD drivers in SPL"
1299 Enable support for SPI flash MTD drivers in SPL.
1302 bool "Support loading from SPI flash"
1304 Enable support for loading next stage, U-Boot or otherwise, from
1305 SPI NOR in U-Boot SPL.
1307 endif # SPL_SPI_FLASH_SUPPORT
1309 config SYS_SPI_U_BOOT_OFFS
1310 hex "address of u-boot payload in SPI flash"
1311 default 0x8000 if ARCH_SUNXI
1313 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1315 Address within SPI-Flash from where the u-boot payload is fetched
1319 bool "Driver support for thermal devices"
1321 Enable support for temperature-sensing devices. Some SoCs have on-chip
1322 temperature sensors to permit warnings, speed throttling or even
1323 automatic power-off when the temperature gets too high or low. Other
1324 devices may be discrete but connected on a suitable bus.
1327 bool "Support USB host drivers"
1328 select HAVE_BLOCK_DEVICE
1330 Enable access to USB (Universal Serial Bus) host devices so that
1331 SPL can load U-Boot from a connected USB peripheral, such as a USB
1332 flash stick. While USB takes a little longer to start up than most
1333 buses, it is very flexible since many different types of storage
1334 device can be attached. This option enables the drivers in
1335 drivers/usb/host as part of an SPL build.
1337 config SPL_USB_STORAGE
1338 bool "Support loading from USB"
1339 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1341 Enable support for USB devices in SPL. This allows use of USB
1342 devices such as hard drives and flash drivers for loading U-Boot.
1343 The actual drivers are enabled separately using the normal U-Boot
1344 config options. This enables loading from USB using a configured
1347 config SPL_USB_GADGET
1348 bool "Suppport USB Gadget drivers"
1350 Enable USB Gadget API which allows to enable USB device functions
1355 config SPL_USB_ETHER
1356 bool "Support USB Ethernet drivers"
1359 Enable access to the USB network subsystem and associated
1360 drivers in SPL. This permits SPL to load U-Boot over a
1361 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1362 than from an onboard peripheral. Environment support is required
1363 since the network stack uses a number of environment variables.
1364 See also SPL_NET and SPL_ETH.
1367 bool "Support DFU (Device Firmware Upgrade)"
1369 select SPL_DFU_NO_RESET
1370 depends on SPL_RAM_SUPPORT
1372 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1373 RAM memory device support. The ROM code will load and execute
1374 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1375 selected device partition from host-pc using dfu-utils.
1376 This feature is useful to flash the binaries to factory or bare-metal
1377 boards using USB interface.
1380 bool "DFU device selection"
1385 depends on SPL_DFU && SPL_RAM_SUPPORT
1387 select RAM/DDR memory device for loading binary images
1388 (u-boot/kernel) to the selected device partition using
1389 DFU and execute the u-boot/kernel from RAM.
1393 config SPL_USB_SDP_SUPPORT
1394 bool "Support SDP (Serial Download Protocol)"
1395 depends on SPL_SERIAL
1397 Enable Serial Download Protocol (SDP) device support in SPL. This
1398 allows to download images into memory and execute (jump to) them
1399 using the same protocol as implemented by the i.MX family's boot ROM.
1401 config SPL_SDP_USB_DEV
1402 int "SDP USB controller index"
1404 depends on SPL_USB_SDP_SUPPORT
1406 Some boards have USB controller other than 0. Define this option
1407 so it can be used in compiled environment.
1411 bool "Support watchdog drivers"
1412 imply SPL_WDT if !HW_WATCHDOG
1414 Enable support for watchdog drivers in SPL. A watchdog is
1415 typically a hardware peripheral which can reset the system when it
1416 detects no activity for a while (such as a software crash). This
1417 enables the drivers in drivers/watchdog as part of an SPL build.
1419 config SPL_YMODEM_SUPPORT
1420 bool "Support loading using Ymodem"
1421 depends on SPL_SERIAL
1423 While loading from serial is slow it can be a useful backup when
1424 there is no other option. The Ymodem protocol provides a reliable
1425 means of transmitting U-Boot over a serial line for using in SPL,
1426 with a checksum to ensure correctness.
1429 bool "Support ARM Trusted Firmware"
1430 depends on ARM64 && SPL_FIT
1432 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1433 is loaded by SPL (which is considered as BL2 in ATF terminology).
1434 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1436 config SPL_ATF_LOAD_IMAGE_V2
1437 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1440 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1442 If you want to load a bl31 image from the SPL and need the new
1445 config SPL_ATF_NO_PLATFORM_PARAM
1446 bool "Pass no platform parameter"
1449 While we expect to call a pointer to a valid FDT (or NULL)
1450 as the platform parameter to an ATF, some ATF versions are
1451 not U-Boot aware and have an insufficiently robust parameter
1452 validation to gracefully reject a FDT being passed.
1454 If this option is enabled, the spl_atf os-type handler will
1455 always pass NULL for the platform parameter.
1457 If your ATF is affected, say Y.
1459 config SPL_AM33XX_ENABLE_RTC32K_OSC
1460 bool "Enable the RTC32K OSC on AM33xx based platforms"
1463 Enable access to the AM33xx RTC and select the external 32kHz clock
1466 config SPL_OPTEE_IMAGE
1467 bool "Support OP-TEE Trusted OS image in SPL"
1470 OP-TEE is an open source Trusted OS which is loaded by SPL.
1471 More detail at: https://github.com/OP-TEE/optee_os
1474 bool "Support RISC-V OpenSBI"
1475 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1477 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1478 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1479 firmware. It is loaded and started by U-Boot SPL.
1481 More details are available at https://github.com/riscv/opensbi and
1482 https://github.com/riscv/riscv-sbi-doc
1484 config SPL_OPENSBI_LOAD_ADDR
1485 hex "OpenSBI load address"
1486 depends on SPL_OPENSBI
1488 Load address of the OpenSBI binary.
1492 depends on SUPPORT_TPL
1495 If you want to build TPL as well as the normal image and SPL, say Y.
1499 config TPL_SIZE_LIMIT
1500 hex "Maximum size of TPL image"
1504 Specifies the maximum length of the U-Boot TPL image.
1505 If this value is zero, it is ignored.
1507 config TPL_BINMAN_SYMBOLS
1508 bool "Declare binman symbols in TPL"
1509 depends on SPL_FRAMEWORK && BINMAN
1512 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1513 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1514 and spl_get_image_size().
1516 For this to work, you must have a U-Boot image in the binman image, so
1517 binman can update TPL with the location of it.
1519 config TPL_FRAMEWORK
1520 bool "Support TPL based upon the common SPL framework"
1521 default y if SPL_FRAMEWORK
1523 Enable the SPL framework under common/spl/ for TPL builds.
1524 This framework supports MMC, NAND and YMODEM and other methods
1525 loading of U-Boot's SPL stage. If unsure, say Y.
1528 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1529 depends on HANDOFF && TPL_BLOBLIST
1532 This option enables TPL to write handoff information. This can be
1533 used to pass information like the size of SDRAM from TPL to U-Boot
1534 proper. The information is also available to SPL if it is useful
1537 config TPL_BOARD_INIT
1538 bool "Call board-specific initialization in TPL"
1540 If this option is enabled, U-Boot will call the function
1541 spl_board_init() from board_init_r(). This function should be
1542 provided by the board.
1544 config TPL_BOOTCOUNT_LIMIT
1545 bool "Support bootcount in TPL"
1546 depends on TPL_ENV_SUPPORT
1548 If this option is enabled, the TPL will support bootcount.
1549 For example, it may be useful to choose the device to boot.
1552 string "Linker script for the TPL stage"
1554 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1555 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1557 The TPL stage will usually require a different linker-script
1558 (as it runs from a different memory region) than the regular
1559 U-Boot stage. Set this to the path of the linker-script to
1562 May be left empty to trigger the Makefile infrastructure to
1563 fall back to the linker-script used for the SPL stage.
1565 config TPL_NEEDS_SEPARATE_STACK
1566 bool "TPL needs a separate initial stack-pointer"
1569 Enable, if the TPL stage should not inherit its initial
1570 stack-pointer from the settings for the SPL stage.
1573 bool "Support power drivers"
1575 Enable support for power control in TPL. This includes support
1576 for PMICs (Power-management Integrated Circuits) and some of the
1577 features provided by PMICs. In particular, voltage regulators can
1578 be used to enable/disable power and vary its voltage. That can be
1579 useful in TPL to turn on boot peripherals and adjust CPU voltage
1580 so that the clock speed can be increased. This enables the drivers
1581 in drivers/power, drivers/power/pmic and drivers/power/regulator
1582 as part of an TPL build.
1584 config TPL_TEXT_BASE
1585 hex "Base address for the .text section of the TPL stage"
1588 The base address for the .text section of the TPL stage.
1591 hex "Maximum size (in bytes) for the TPL stage"
1592 default 0x2e000 if ROCKCHIP_RK3399
1593 default 0x8000 if ROCKCHIP_RK3288
1594 default 0x7000 if ROCKCHIP_RK322X || ROCKCHIP_RK3328 || ROCKCHIP_RK3368
1595 default 0x2800 if ROCKCHIP_PX30
1598 The maximum size (in bytes) of the TPL stage.
1601 hex "Offset to which the TPL should be padded before appending the TPL payload"
1602 depends on !TPL_FRAMEWORK && PPC
1603 default TPL_MAX_SIZE
1605 Image offset to which the TPL should be padded before appending the
1606 TPL payload. By default, this is defined as CONFIG_TPL_MAX_SIZE, or 0 if
1607 CONFIG_TPL_MAX_SIZE is undefined. CONFIG_TPL_PAD_TO must be either
1608 0, meaning to append the TPL payload without any padding, or >=
1609 CONFIG_TPL_MAX_SIZE.
1612 hex "Address of the initial stack-pointer for the TPL stage"
1613 depends on TPL_NEEDS_SEPARATE_STACK
1615 The address of the initial stack-pointer for the TPL stage.
1616 Usually this will be the (aligned) top-of-stack.
1618 config TPL_READ_ONLY
1620 depends on TPL_OF_PLATDATA
1621 select TPL_OF_PLATDATA_NO_BIND
1622 select TPL_OF_PLATDATA_RT
1624 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1625 section of memory. This means that of-platdata must make a copy (in
1626 writeable memory) of anything it wants to modify, such as
1627 device-private data.
1629 config TPL_BOOTROM_SUPPORT
1630 bool "Support returning to the BOOTROM (from TPL)"
1632 Some platforms (e.g. the Rockchip RK3368) provide support in their
1633 ROM for loading the next boot-stage after performing basic setup
1636 Enable this option, to return to the BOOTROM through the
1637 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1638 boot device list, if not implemented for a given board)
1641 bool "Support CRC32 in TPL"
1642 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1644 Enable this to support CRC32 in uImages or FIT images within SPL.
1645 This is a 32-bit checksum value that can be used to verify images.
1646 For FIT images, this is the least secure type of checksum, suitable
1647 for detected accidental image corruption. For secure applications you
1648 should consider SHA1 or SHA256.
1650 config TPL_DRIVERS_MISC
1651 bool "Support misc drivers in TPL"
1653 Enable miscellaneous drivers in TPL. These drivers perform various
1654 tasks that don't fall nicely into other categories, Enable this
1655 option to build the drivers in drivers/misc as part of an TPL
1656 build, for those that support building in TPL (not all drivers do).
1658 config TPL_ENV_SUPPORT
1659 bool "Support an environment"
1661 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1664 bool "Support GPIO in TPL"
1666 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1667 GPIOs allow U-Boot to read the state of an input line (high or
1668 low) and set the state of an output line. This can be used to
1669 drive LEDs, control power to various system parts and read user
1670 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1671 for example. Enable this option to build the drivers in
1672 drivers/gpio as part of an TPL build.
1677 Enable support for the I2C bus in TPL. See SPL_I2C for
1680 config TPL_LIBCOMMON_SUPPORT
1681 bool "Support common libraries"
1683 Enable support for common U-Boot libraries within TPL. See
1684 SPL_LIBCOMMON_SUPPORT for details.
1686 config TPL_LIBGENERIC_SUPPORT
1687 bool "Support generic libraries"
1689 Enable support for generic U-Boot libraries within TPL. See
1690 SPL_LIBGENERIC_SUPPORT for details.
1692 config TPL_MPC8XXX_INIT_DDR
1693 bool "Support MPC8XXX DDR init"
1695 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1696 SPL_MPC8XXX_INIT_DDR for details.
1702 Enable support for MMC within TPL. See SPL_MMC for details.
1704 config TPL_NAND_SUPPORT
1705 bool "Support NAND flash"
1707 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1710 bool "Support PCI drivers"
1712 Enable support for PCI in TPL. For platforms that need PCI to boot,
1713 or must perform some init using PCI in SPL, this provides the
1714 necessary driver support. This enables the drivers in drivers/pci
1715 as part of a TPL build.
1718 bool "Support PCH drivers"
1720 Enable support for PCH (Platform Controller Hub) devices in TPL.
1721 These are used to set up GPIOs and the SPI peripheral early in
1722 boot. This enables the drivers in drivers/pch as part of a TPL
1725 config TPL_RAM_SUPPORT
1726 bool "Support booting from RAM"
1728 Enable booting of an image in RAM. The image can be preloaded or
1729 it can be loaded by TPL directly into RAM (e.g. using USB).
1731 config TPL_RAM_DEVICE
1732 bool "Support booting from preloaded image in RAM"
1733 depends on TPL_RAM_SUPPORT
1735 Enable booting of an image already loaded in RAM. The image has to
1736 be already in memory when TPL takes over, e.g. loaded by the boot
1740 bool "Support RTC drivers"
1742 Enable RTC (Real-time Clock) support in TPL. This includes support
1743 for reading and setting the time. Some RTC devices also have some
1744 non-volatile (battery-backed) memory which is accessible if
1745 needed. This enables the drivers in drivers/rtc as part of an TPL
1749 bool "Support serial"
1753 Enable support for serial in TPL. See SPL_SERIAL for
1756 config TPL_SPI_FLASH_SUPPORT
1757 bool "Support SPI flash drivers"
1759 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1762 config TPL_SPI_FLASH_TINY
1763 bool "Enable low footprint TPL SPI Flash support"
1764 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1765 default y if SPI_FLASH
1767 Enable lightweight TPL SPI Flash support that supports just reading
1768 data/images from flash. No support to write/erase flash. Enable
1769 this if you have TPL size limitations and don't need full-fledged
1773 bool "Support loading from SPI flash"
1774 depends on TPL_SPI_FLASH_SUPPORT
1776 Enable support for loading next stage, U-Boot or otherwise, from
1777 SPI NOR in U-Boot TPL.
1780 bool "Support SPI drivers"
1782 Enable support for using SPI in TPL. See SPL_SPI for
1786 bool "Support SPI DM drivers in TPL"
1788 Enable support for SPI DM drivers in TPL.
1790 config TPL_DM_SPI_FLASH
1791 bool "Support SPI DM FLASH drivers in TPL"
1793 Enable support for SPI DM flash drivers in TPL.
1795 config TPL_YMODEM_SUPPORT
1796 bool "Support loading using Ymodem"
1797 depends on TPL_SERIAL
1799 While loading from serial is slow it can be a useful backup when
1800 there is no other option. The Ymodem protocol provides a reliable
1801 means of transmitting U-Boot over a serial line for using in TPL,
1802 with a checksum to ensure correctness.
1808 depends on SUPPORT_SPL
1811 If you want to build VPL as well as the normal image, TPL and SPL,
1816 config VPL_BANNER_PRINT
1817 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1821 If this option is enabled, VPL will print the banner with version
1822 info. Disabling this option could be useful to reduce VPL boot time
1823 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1825 config VPL_BOARD_INIT
1826 bool "Call board-specific initialization in VPL"
1828 If this option is enabled, U-Boot will call the function
1829 spl_board_init() from board_init_r(). This function should be
1830 provided by the board.
1834 bool "Support cache drivers in VPL"
1836 Enable support for cache drivers in VPL.
1839 bool "Support CRC32 in VPL"
1840 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1842 Enable this to support CRC32 in uImages or FIT images within VPL.
1843 This is a 32-bit checksum value that can be used to verify images.
1844 For FIT images, this is the least secure type of checksum, suitable
1845 for detected accidental image corruption. For secure applications you
1846 should consider SHA1 or SHA256.
1849 bool "Support SPI DM drivers in VPL"
1851 Enable support for SPI DM drivers in VPL.
1853 config VPL_DM_SPI_FLASH
1854 bool "Support SPI DM FLASH drivers in VPL"
1856 Enable support for SPI DM flash drivers in VPL.
1858 config VPL_FRAMEWORK
1859 bool "Support VPL based upon the common SPL framework"
1862 Enable the SPL framework under common/spl/ for VPL builds.
1863 This framework supports MMC, NAND and YMODEM and other methods
1864 loading of U-Boot's next stage. If unsure, say Y.
1867 bool "Pass hand-off information from VPL to SPL"
1868 depends on HANDOFF && VPL_BLOBLIST
1871 This option enables VPL to write handoff information. This can be
1872 used to pass information like the size of SDRAM from VPL to SPL. Also
1873 VPL can receive information from TPL in the same place if that is
1876 config VPL_LIBCOMMON_SUPPORT
1877 bool "Support common libraries"
1878 default y if SPL_LIBCOMMON_SUPPORT
1880 Enable support for common U-Boot libraries within VPL. See
1881 SPL_LIBCOMMON_SUPPORT for details.
1883 config VPL_LIBGENERIC_SUPPORT
1884 bool "Support generic libraries"
1885 default y if SPL_LIBGENERIC_SUPPORT
1887 Enable support for generic U-Boot libraries within VPL. These
1888 libraries include generic code to deal with device tree, hashing,
1889 printf(), compression and the like. This option is enabled on many
1890 boards. Enable this option to build the code in lib/ as part of a
1893 config VPL_DRIVERS_MISC
1894 bool "Support misc drivers"
1895 default y if TPL_DRIVERS_MISC
1897 Enable miscellaneous drivers in VPL. These drivers perform various
1898 tasks that don't fall nicely into other categories, Enable this
1899 option to build the drivers in drivers/misc as part of a VPL
1900 build, for those that support building in VPL (not all drivers do).
1902 config VPL_ENV_SUPPORT
1903 bool "Support an environment"
1905 Enable environment support in VPL. The U-Boot environment provides
1906 a number of settings (essentially name/value pairs) which can
1907 control many aspects of U-Boot's operation. Enabling this option will
1908 make env_get() and env_set() available in VSPL.
1911 bool "Support GPIO in VPL"
1912 default y if SPL_GPIO
1914 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1915 GPIOs allow U-Boot to read the state of an input line (high or
1916 low) and set the state of an output line. This can be used to
1917 drive LEDs, control power to various system parts and read user
1918 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1919 for example. Enable this option to build the drivers in
1920 drivers/gpio as part of a VPL build.
1923 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1924 depends on HANDOFF && VPL_BLOBLIST
1927 This option enables VPL to write handoff information. This can be
1928 used to pass information like the size of SDRAM from VPL to U-Boot
1929 proper. The information is also available to VPL if it is useful
1933 bool "Support hashing drivers in VPL"
1938 Enable hashing drivers in VPL. These drivers can be used to
1939 accelerate secure boot processing in secure applications. Enable
1940 this option to build system-specific drivers for hash acceleration
1941 as part of a VPL build.
1943 config VPL_I2C_SUPPORT
1944 bool "Support I2C in VPL"
1945 default y if SPL_I2C_SUPPORT
1947 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1950 config VPL_PCH_SUPPORT
1951 bool "Support PCH drivers"
1952 default y if TPL_PCH_SUPPORT
1954 Enable support for PCH (Platform Controller Hub) devices in VPL.
1955 These are used to set up GPIOs and the SPI peripheral early in
1956 boot. This enables the drivers in drivers/pch as part of a VPL
1960 bool "Support PCI drivers"
1961 default y if SPL_PCI
1963 Enable support for PCI in VPL. For platforms that need PCI to boot,
1964 or must perform some init using PCI in VPL, this provides the
1965 necessary driver support. This enables the drivers in drivers/pci
1966 as part of a VPL build.
1969 bool "Support RTC drivers"
1971 Enable RTC (Real-time Clock) support in VPL. This includes support
1972 for reading and setting the time. Some RTC devices also have some
1973 non-volatile (battery-backed) memory which is accessible if
1974 needed. This enables the drivers in drivers/rtc as part of a VPL
1978 bool "Support serial"
1979 default y if TPL_SERIAL
1983 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1986 config VPL_SIZE_LIMIT
1987 hex "Maximum size of VPL image"
1991 Specifies the maximum length of the U-Boot VPL image.
1992 If this value is zero, it is ignored.
1995 bool "Support SPI drivers"
1997 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
2000 config VPL_SPI_FLASH_SUPPORT
2001 bool "Support SPI flash drivers"
2003 Enable support for using SPI flash in VPL, and loading U-Boot from
2004 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
2005 the SPI bus that is used to connect it to a system. It is a simple
2006 but fast bidirectional 4-wire bus (clock, chip select and two data
2007 lines). This enables the drivers in drivers/mtd/spi as part of a
2008 VPL build. This normally requires VPL_SPI_SUPPORT.
2010 config VPL_TEXT_BASE
2014 The address in memory that VPL will be running from.
2018 config SPL_AT91_MCK_BYPASS
2019 bool "Use external clock signal as a source of main clock for AT91 platforms"
2020 depends on ARCH_AT91
2022 Use external 8 to 24 Mhz clock signal as source of main clock instead
2023 of an external crystal oscillator.
2024 This option disables the internal driving on the XOUT pin.
2025 The external source has to provide a stable clock on the XIN pin.
2026 If this option is disabled, the SoC expects a crystal oscillator
2027 that needs driving on both XIN and XOUT lines.