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 || ARCH_MX7
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 0x946bb8 if ARCH_MX7
375 default 0x93ffb8 if ARCH_MX6 && MX6_OCRAM_256KB
376 default 0x91ffb8 if ARCH_MX6 && !MX6_OCRAM_256KB
378 Address of the start of the stack SPL will use before SDRAM is
382 bool "Enable SDRAM location for SPL stack"
384 SPL starts off execution in SRAM and thus typically has only a small
385 stack available. Since SPL sets up DRAM while in its board_init_f()
386 function, it is possible for the stack to move there before
387 board_init_r() is reached. This option enables a special SDRAM
388 location for the SPL stack. U-Boot SPL switches to this after
389 board_init_f() completes, and before board_init_r() starts.
391 config SPL_STACK_R_ADDR
392 depends on SPL_STACK_R
393 hex "SDRAM location for SPL stack"
394 default 0x82000000 if ARCH_OMAP2PLUS
396 Specify the address in SDRAM for the SPL stack. This will be set up
397 before board_init_r() is called.
399 config SPL_STACK_R_MALLOC_SIMPLE_LEN
400 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
401 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
404 Specify the amount of the stack to use as memory pool for
405 malloc_simple after switching the stack to DRAM. This may be set
406 to give board_init_r() a larger heap then the initial heap in
407 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
409 config SPL_SEPARATE_BSS
410 bool "BSS section is in a different memory region from text"
412 Some platforms need a large BSS region in SPL and can provide this
413 because RAM is already set up. In this case BSS can be moved to RAM.
414 This option should then be enabled so that the correct device tree
415 location is used. Normally we put the device tree at the end of BSS
416 but with this option enabled, it goes at _image_binary_end.
420 depends on SPL_OF_PLATDATA
421 # Bind cannot be supported because the udevice structs are in read-only
422 # memory so we cannot update the linked lists.
423 select SPL_OF_PLATDATA_NO_BIND
424 select SPL_OF_PLATDATA_RT
426 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
427 section of memory. This means that of-platdata must make a copy (in
428 writeable memory) of anything it wants to modify, such as
431 config TPL_SEPARATE_BSS
432 bool "BSS section is in a different memory region from text"
433 default y if SPL_SEPARATE_BSS
435 Some platforms need a large BSS region in TPL and can provide this
436 because RAM is already set up. In this case BSS can be moved to RAM.
437 This option should then be enabled so that the correct device tree
438 location is used. Normally we put the device tree at the end of BSS
439 but with this option enabled, it goes at _image_binary_end.
441 config SPL_BANNER_PRINT
442 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
445 If this option is enabled, SPL will print the banner with version
446 info. Disabling this option could be useful to reduce SPL boot time
447 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
449 config TPL_BANNER_PRINT
450 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
454 If this option is enabled, TPL will print the banner with version
455 info. Disabling this option could be useful to reduce TPL boot time
456 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
459 depends on ARM && !ARM64
460 bool "Allows initializing BSS early before entering board_init_f"
462 On some platform we have sufficient memory available early on to
463 allow setting up and using a basic BSS prior to entering
464 board_init_f. Activating this option will also de-activate the
465 clearing of BSS during the SPL relocation process, thus allowing
466 to carry state from board_init_f to board_init_r by way of BSS.
468 config SPL_DISPLAY_PRINT
469 bool "Display a board-specific message in SPL"
471 If this option is enabled, U-Boot will call the function
472 spl_display_print() immediately after displaying the SPL console
473 banner ("U-Boot SPL ..."). This function should be provided by
476 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
477 bool "MMC raw mode: by sector"
478 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
479 ARCH_MX6 || ARCH_MX7 || \
480 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
481 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
482 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
483 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
485 Use sector number for specifying U-Boot location on MMC/SD in
488 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
489 hex "Address on the MMC to load U-Boot from"
490 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
491 default 0x40 if ARCH_SUNXI
492 default 0x75 if ARCH_DAVINCI
493 default 0x8a if ARCH_MX6 || ARCH_MX7
494 default 0x100 if ARCH_UNIPHIER
495 default 0x0 if ARCH_MVEBU
496 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
497 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
498 OMAP54XX || AM33XX || AM43XX || ARCH_K3
499 default 0x4000 if ARCH_ROCKCHIP
500 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
502 Address on the MMC to load U-Boot from, when the MMC is being used
503 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
505 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
506 hex "U-Boot main hardware partition image offset"
507 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
508 default 0x10 if ARCH_SUNXI
511 On some platforms SPL location depends on hardware partition. The ROM
512 code skips the MBR sector when loading SPL from main hardware data
513 partition. This adds offset to the main U-Boot image. Set this symbol
514 to the number of skipped sectors.
516 If unsure, leave the default.
518 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
519 bool "MMC Raw mode: by partition"
521 Use a partition for loading U-Boot when using MMC/SD in raw mode.
523 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
524 hex "Partition to use to load U-Boot from"
525 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
528 Partition on the MMC to load U-Boot from when the MMC is being
531 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
532 bool "MMC raw mode: by partition type"
533 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
535 Use partition type for specifying U-Boot partition on MMC/SD in
536 raw mode. U-Boot will be loaded from the first partition of this
539 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
540 hex "Partition Type on the MMC to load U-Boot from"
541 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
543 Partition Type on the MMC to load U-Boot from, when the MMC is being
546 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
547 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
548 depends on SUPPORT_EMMC_BOOT
550 eMMC boot partition is normally configured by the bits of the EXT_CSD
551 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
552 cases it might be required in SPL to load the image from different
553 partition than the partition selected by EXT_CSC_PART_CONFIG register.
554 Enable this option if you intend to use an eMMC boot partition other
555 then selected via EXT_CSC_PART_CONFIG register and specify the custom
556 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
559 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
560 int "Number of the eMMC boot partition to use"
561 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
564 eMMC boot partition number to use when the eMMC in raw mode and
565 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
566 by user defined partition number.
570 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
571 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
573 Enable this to support CRC32 in uImages or FIT images within SPL.
574 This is a 32-bit checksum value that can be used to verify images.
575 For FIT images, this is the least secure type of checksum, suitable
576 for detected accidental image corruption. For secure applications you
577 should consider SHA1 or SHA256.
583 Enable this to support MD5 in FIT images within SPL. An MD5
584 checksum is a 128-bit hash value used to check that the image
585 contents have not been corrupted. Note that MD5 is not considered
586 secure as it is possible (with a brute-force attack) to adjust the
587 image while still retaining the same MD5 hash value. For secure
588 applications where images may be changed maliciously, you should
589 consider SHA256 or SHA384.
591 config SPL_FIT_IMAGE_TINY
592 bool "Remove functionality from SPL FIT loading to reduce size"
594 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
595 default y if ARCH_IMX8M
597 Enable this to reduce the size of the FIT image loading code
598 in SPL, if space for the SPL binary is very tight.
600 This skips the recording of each loaded payload
601 (i.e. loadable) into the FDT (modifying the loaded FDT to
602 ensure this information is available to the next image
606 bool "Support CACHE drivers"
608 Enable CACHE drivers in SPL. These drivers can keep data so that
609 future requests for that data can be served faster. Enable this option
610 to build the drivers in drivers/cache as part of an SPL build.
613 bool "Support CPU drivers"
615 Enable this to support CPU drivers in SPL. These drivers can set
616 up CPUs and provide information about them such as the model and
617 name. This can be useful in SPL since setting up the CPUs earlier
618 may improve boot performance. Enable this option to build the
619 drivers in drivers/cpu as part of an SPL build.
622 bool "Support crypto drivers"
624 Enable crypto drivers in SPL. These drivers can be used to
625 accelerate secure boot processing in secure applications. Enable
626 this option to build the drivers in drivers/crypto as part of an
630 bool "Support DMA drivers"
632 Enable DMA (direct-memory-access) drivers in SPL. These drivers
633 can be used to handle memory-to-peripheral data transfer without
634 the CPU moving the data. Enable this option to build the drivers
635 in drivers/dma as part of an SPL build.
637 config SPL_DRIVERS_MISC
638 bool "Support misc drivers"
640 Enable miscellaneous drivers in SPL. These drivers perform various
641 tasks that don't fall nicely into other categories, Enable this
642 option to build the drivers in drivers/misc as part of an SPL
643 build, for those that support building in SPL (not all drivers do).
645 config SPL_ENV_SUPPORT
646 bool "Support an environment"
648 Enable environment support in SPL. The U-Boot environment provides
649 a number of settings (essentially name/value pairs) which can
650 control many aspects of U-Boot's operation. Normally this is not
651 needed in SPL as it has a much simpler task with less
652 configuration. But some boards use this to support 'Falcon' boot
653 on EXT2 and FAT, where SPL boots directly into Linux without
654 starting U-Boot first. Enabling this option will make env_get()
655 and env_set() available in SPL.
658 bool "Support save environment"
659 depends on SPL_ENV_SUPPORT
660 select SPL_MMC_WRITE if ENV_IS_IN_MMC
662 Enable save environment support in SPL after setenv. By default
663 the saveenv option is not provided in SPL, but some boards need
664 this support in 'Falcon' boot, where SPL need to boot from
665 different images based on environment variable set by OS. For
666 example OS may set "reboot_image" environment variable to
667 "recovery" inorder to boot recovery image by SPL. The SPL read
668 "reboot_image" and act accordingly and change the reboot_image
669 to default mode using setenv and save the environment.
672 bool "Support Ethernet"
673 depends on SPL_ENV_SUPPORT
676 Enable access to the network subsystem and associated Ethernet
677 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
678 link rather than from an on-board peripheral. Environment support
679 is required since the network stack uses a number of environment
680 variables. See also SPL_NET.
683 bool "Support EXT filesystems"
685 Enable support for EXT2/3/4 filesystems with SPL. This permits
686 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
687 filesystem from within SPL. Support for the underlying block
688 device (e.g. MMC or USB) must be enabled separately.
690 config SPL_FS_SQUASHFS
691 bool "Support SquashFS filesystems"
694 Enable support for SquashFS filesystems with SPL. This permits
695 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
696 filesystem from within SPL. Support for the underlying block
697 device (e.g. MMC or USB) must be enabled separately.
700 bool "Support FAT filesystems"
703 Enable support for FAT and VFAT filesystems with SPL. This
704 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
705 filesystem from within SPL. Support for the underlying block
706 device (e.g. MMC or USB) must be enabled separately.
708 config SPL_FS_LOAD_PAYLOAD_NAME
709 string "File to load for U-Boot from the filesystem"
710 depends on SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS
711 default "tispl.bin" if SYS_K3_SPL_ATF
712 default "u-boot.itb" if SPL_LOAD_FIT
715 Filename to read to load U-Boot when reading from filesystem.
717 config SPL_FS_LOAD_KERNEL_NAME
718 string "File to load for the OS kernel from the filesystem"
719 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
722 Filename to read to load for the OS kernel when reading from the
725 config SPL_FS_LOAD_ARGS_NAME
726 string "File to load for the OS kernel argument parameters from the filesystem"
727 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
730 Filename to read to load for the OS kernel argument parameters from
734 bool "Support write for FAT filesystems"
736 Enable write support for FAT and VFAT filesystems with SPL.
737 Support for the underlying block device (e.g. MMC or USB) must be
743 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
744 provide software-configurable hardware which is typically used to
745 implement peripherals (such as UARTs, LCD displays, MMC) or
746 accelerate custom processing functions, such as image processing
747 or machine learning. Sometimes it is useful to program the FPGA
748 as early as possible during boot, and this option can enable that
752 bool "Support GPIO in SPL"
754 Enable support for GPIOs (General-purpose Input/Output) in SPL.
755 GPIOs allow U-Boot to read the state of an input line (high or
756 low) and set the state of an output line. This can be used to
757 drive LEDs, control power to various system parts and read user
758 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
759 for example. Enable this option to build the drivers in
760 drivers/gpio as part of an SPL build.
765 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
766 I2C works with a clock and data line which can be driven by a
767 one or more masters or slaves. It is a fairly complex bus but is
768 widely used as it only needs two lines for communication. Speeds of
769 400kbps are typical but up to 3.4Mbps is supported by some
770 hardware. I2C can be useful in SPL to configure power management
771 ICs (PMICs) before raising the CPU clock speed, for example.
772 Enable this option to build the drivers in drivers/i2c as part of
775 config SPL_LIBCOMMON_SUPPORT
776 bool "Support common libraries"
778 Enable support for common U-Boot libraries within SPL. These
779 libraries include common code to deal with U-Boot images,
780 environment and USB, for example. This option is enabled on many
781 boards. Enable this option to build the code in common/ as part of
784 config SPL_LIBDISK_SUPPORT
785 bool "Support disk partitions"
788 Enable support for disk partitions within SPL. 'Disk' is something
789 of a misnomer as it includes non-spinning media such as flash (as
790 used in MMC and USB sticks). Partitions provide a way for a disk
791 to be split up into separate regions, with a partition table placed
792 at the start or end which describes the location and size of each
793 'partition'. These partitions are typically uses as individual block
794 devices, typically with an EXT2 or FAT filesystem in each. This
795 option enables whatever partition support has been enabled in
796 U-Boot to also be used in SPL. It brings in the code in disk/.
798 config SPL_LIBGENERIC_SUPPORT
799 bool "Support generic libraries"
801 Enable support for generic U-Boot libraries within SPL. These
802 libraries include generic code to deal with device tree, hashing,
803 printf(), compression and the like. This option is enabled on many
804 boards. Enable this option to build the code in lib/ as part of an
807 config SPL_DM_MAILBOX
808 bool "Support Mailbox"
810 Enable support for Mailbox within SPL. This enable the inter
811 processor communication protocols tobe used within SPL. Enable
812 this option to build the drivers in drivers/mailbox as part of
818 select HAVE_BLOCK_DEVICE
820 Enable support for MMC (Multimedia Card) within SPL. This enables
821 the MMC protocol implementation and allows any enabled drivers to
822 be used within SPL. MMC can be used with or without disk partition
823 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
824 this option to build the drivers in drivers/mmc as part of an SPL
827 config SYS_MMCSD_FS_BOOT_PARTITION
828 int "MMC Boot Partition"
831 Partition on the MMC to load U-Boot from when the MMC is being
833 Use -1 as a special value to use the first bootable partition.
836 bool "Tiny MMC framework in SPL"
839 Enable MMC framework tinification support. This option is useful if
840 if your SPL is extremely size constrained. Heed the warning, enable
841 this option if and only if you know exactly what you are doing, if
842 you are reading this help text, you most likely have no idea :-)
844 The MMC framework is reduced to bare minimum to be useful. No malloc
845 support is needed for the MMC framework operation with this option
846 enabled. The framework supports exactly one MMC device and exactly
847 one MMC driver. The MMC driver can be adjusted to avoid any malloc
848 operations too, which can remove the need for malloc support in SPL
849 and thus further reduce footprint.
852 bool "MMC/SD/SDIO card support for write operations in SPL"
855 Enable write access to MMC and SD Cards in SPL
858 config SPL_MPC8XXX_INIT_DDR
859 bool "Support MPC8XXX DDR init"
861 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
862 random-access memory) on the MPC8XXX family within SPL. This
863 allows DRAM to be set up before loading U-Boot into that DRAM,
866 config SPL_MTD_SUPPORT
867 bool "Support MTD drivers"
869 Enable support for MTD (Memory Technology Device) within SPL. MTD
870 provides a block interface over raw NAND and can also be used with
871 SPI flash. This allows SPL to load U-Boot from supported MTD
872 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
873 to enable specific MTD drivers.
876 bool "Support new Mentor Graphics USB"
878 Enable support for Mentor Graphics USB in SPL. This is a new
879 driver used by some boards. Enable this option to build
880 the drivers in drivers/usb/musb-new as part of an SPL build. The
881 old drivers are in drivers/usb/musb.
883 config SPL_NAND_SUPPORT
884 bool "Support NAND flash"
886 Enable support for NAND (Negative AND) flash in SPL. NAND flash
887 can be used to allow SPL to load U-Boot from supported devices.
888 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
891 config SPL_NAND_RAW_ONLY
892 bool "Support to boot only raw u-boot.bin images"
893 depends on SPL_NAND_SUPPORT
895 Use this only if you need to save space.
897 config SPL_NAND_DRIVERS
898 bool "Use standard NAND driver"
900 SPL uses normal NAND drivers, not minimal drivers.
903 bool "Include standard ECC in SPL"
905 config SPL_NAND_SOFTECC
906 bool "Use software ECC in SPL"
907 depends on SPL_NAND_ECC
909 config SPL_NAND_SIMPLE
910 bool "Support simple NAND drivers in SPL"
912 Support for NAND boot using simple NAND drivers that
913 expose the cmd_ctrl() interface.
916 depends on SPL_NAND_DRIVERS
917 bool "Use Base NAND Driver"
919 Include nand_base.c in the SPL.
921 config SPL_NAND_IDENT
922 depends on SPL_NAND_BASE
923 bool "Use chip ID to identify NAND flash"
925 SPL uses the chip ID list to identify the NAND flash.
930 Enable support for loading payloads from UBI. See
931 README.ubispl for more info.
935 bool "Support SPI DM drivers in SPL"
937 Enable support for SPI DM drivers in SPL.
939 config SPL_DM_SPI_FLASH
940 bool "Support SPI DM FLASH drivers in SPL"
942 Enable support for SPI DM flash drivers in SPL.
946 config SPL_UBI_LOAD_BY_VOLNAME
947 bool "Support loading volumes by name"
949 This enables support for loading UBI volumes by name. When this
950 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
951 configure the volume name from which to load U-Boot.
953 config SPL_UBI_MAX_VOL_LEBS
954 int "Maximum number of LEBs per volume"
957 The maximum number of logical eraseblocks which a static volume
958 to load can contain. Used for sizing the scan data structure.
960 config SPL_UBI_MAX_PEB_SIZE
961 int "Maximum PEB size"
964 The maximum physical erase block size.
966 config SPL_UBI_MAX_PEBS
967 int "Maximum number of PEBs"
970 The maximum physical erase block size. If not overridden by
971 board code, this value will be used as the actual number of PEBs.
973 config SPL_UBI_PEB_OFFSET
974 int "Offset to first UBI PEB"
977 The offset in number of PEBs from the start of flash to the first
978 PEB part of the UBI image.
980 config SPL_UBI_VID_OFFSET
981 int "Offset to VID header"
984 config SPL_UBI_LEB_START
985 int "Offset to LEB in PEB"
988 The offset in bytes to the LEB within a PEB.
990 config SPL_UBI_INFO_ADDR
991 hex "Address to place UBI scan info"
994 Address for ubispl to place the scan info. Read README.ubispl to
995 determine the required size
997 config SPL_UBI_VOL_IDS
998 int "Maximum volume id"
1001 The maximum volume id which can be loaded. Used for sizing the
1002 scan data structure.
1004 config SPL_UBI_LOAD_MONITOR_ID
1005 int "id of U-Boot volume"
1008 The UBI volume id from which to load U-Boot
1010 config SPL_UBI_LOAD_MONITOR_VOLNAME
1011 string "volume name of U-Boot volume"
1012 depends on SPL_UBI_LOAD_BY_VOLNAME
1014 The UBI volume name from which to load U-Boot
1016 config SPL_UBI_LOAD_KERNEL_ID
1017 int "id of kernel volume"
1018 depends on SPL_OS_BOOT && SPL_UBI
1020 The UBI volume id from which to load the kernel
1022 config SPL_UBI_LOAD_ARGS_ID
1023 int "id of kernel args volume"
1024 depends on SPL_OS_BOOT && SPL_UBI
1026 The UBI volume id from which to load the device tree
1028 config UBI_SPL_SILENCE_MSG
1029 bool "silence UBI SPL messages"
1031 Disable messages from UBI SPL. This leaves warnings
1037 bool "Support networking"
1039 Enable support for network devices (such as Ethernet) in SPL.
1040 This permits SPL to load U-Boot over a network link rather than
1041 from an on-board peripheral. Environment support is required since
1042 the network stack uses a number of environment variables. See also
1046 config SPL_NET_VCI_STRING
1047 string "BOOTP Vendor Class Identifier string sent by SPL"
1049 As defined by RFC 2132 the vendor class identifier field can be
1050 sent by the client to identify the vendor type and configuration
1051 of a client. This is often used in practice to allow for the DHCP
1052 server to specify different files to load depending on if the ROM,
1053 SPL or U-Boot itself makes the request
1056 config SPL_NO_CPU_SUPPORT
1057 bool "Drop CPU code in SPL"
1059 This is specific to the ARM926EJ-S CPU. It disables the standard
1060 start.S start-up code, presumably so that a replacement can be
1061 used on that CPU. You should not enable it unless you know what
1064 config SPL_NOR_SUPPORT
1065 bool "Support NOR flash"
1067 Enable support for loading U-Boot from memory-mapped NOR (Negative
1068 OR) flash in SPL. NOR flash is slow to write but fast to read, and
1069 a memory-mapped device makes it very easy to access. Loading from
1070 NOR is typically achieved with just a memcpy().
1072 config SPL_XIP_SUPPORT
1076 Enable support for execute in place of U-Boot or kernel image. There
1077 is no need to copy image from flash to ram if flash supports execute
1078 in place. Its very useful in systems having enough flash but not
1079 enough ram to load the image.
1081 config SPL_ONENAND_SUPPORT
1082 bool "Support OneNAND flash"
1084 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
1085 a type of NAND flash and therefore can be used to allow SPL to
1086 load U-Boot from supported devices. This enables the drivers in
1087 drivers/mtd/onenand as part of an SPL build.
1090 bool "Activate Falcon Mode"
1091 depends on !TI_SECURE_DEVICE
1093 Enable booting directly to an OS from SPL.
1094 for more info read doc/README.falcon
1098 hex "addr, where OS is found"
1099 depends on SPL_NOR_SUPPORT
1101 Specify the address, where the OS image is found, which
1106 config SPL_FALCON_BOOT_MMCSD
1107 bool "Enable Falcon boot from MMC or SD media"
1108 depends on SPL_OS_BOOT && SPL_MMC
1110 Select this if the Falcon mode OS image mode is on MMC or SD media.
1112 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
1113 hex "Falcon mode: Sector to load kernel uImage from MMC"
1114 depends on SPL_FALCON_BOOT_MMCSD
1116 When Falcon mode is used with an MMC or SD media, SPL needs to know
1117 where to look for the kernel uImage. The image is expected to begin
1118 at the raw MMC specified in this config.
1119 Note that the Falcon mode image can also be a FIT, if FIT support is
1123 string "SPL payload"
1124 default "tpl/u-boot-with-tpl.bin" if TPL
1125 default "u-boot.bin"
1127 Payload for SPL boot. For backward compatibility, default to
1128 u-boot.bin, i.e. RAW image without any header. In case of
1129 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
1133 bool "Support PCI drivers"
1135 Enable support for PCI in SPL. For platforms that need PCI to boot,
1136 or must perform some init using PCI in SPL, this provides the
1137 necessary driver support. This enables the drivers in drivers/pci
1138 as part of an SPL build.
1141 bool "Support PCH drivers"
1143 Enable support for PCH (Platform Controller Hub) devices in SPL.
1144 These are used to set up GPIOs and the SPI peripheral early in
1145 boot. This enables the drivers in drivers/pch as part of an SPL
1148 config SPL_POST_MEM_SUPPORT
1149 bool "Support POST drivers"
1151 Enable support for POST (Power-on Self Test) in SPL. POST is a
1152 procedure that checks that the hardware (CPU or board) appears to
1153 be functionally correctly. It is a sanity check that can be
1154 performed before booting. This enables the drivers in post/drivers
1155 as part of an SPL build.
1158 bool "Support reset drivers"
1161 Enable support for reset control in SPL.
1162 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1163 by using the generic reset API provided by driver model.
1164 This enables the drivers in drivers/reset as part of an SPL build.
1167 bool "Support power drivers"
1169 Enable support for power control in SPL. This includes support
1170 for PMICs (Power-management Integrated Circuits) and some of the
1171 features provided by PMICs. In particular, voltage regulators can
1172 be used to enable/disable power and vary its voltage. That can be
1173 useful in SPL to turn on boot peripherals and adjust CPU voltage
1174 so that the clock speed can be increased. This enables the drivers
1175 in drivers/power, drivers/power/pmic and drivers/power/regulator
1176 as part of an SPL build.
1178 config SPL_POWER_DOMAIN
1179 bool "Support power domain drivers"
1182 Enable support for power domain control in SPL. Many SoCs allow
1183 power to be applied to or removed from portions of the SoC (power
1184 domains). This may be used to save power. This API provides the
1185 means to control such power management hardware. This enables
1186 the drivers in drivers/power/domain as part of a SPL build.
1188 config SPL_RAM_SUPPORT
1189 bool "Support booting from RAM"
1190 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1192 Enable booting of an image in RAM. The image can be preloaded or
1193 it can be loaded by SPL directly into RAM (e.g. using USB).
1195 config SPL_RAM_DEVICE
1196 bool "Support booting from preloaded image in RAM"
1197 depends on SPL_RAM_SUPPORT
1198 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1200 Enable booting of an image already loaded in RAM. The image has to
1201 be already in memory when SPL takes over, e.g. loaded by the boot
1204 config SPL_REMOTEPROC
1205 bool "Support REMOTEPROCS"
1207 Enable support for REMOTEPROCs in SPL. This permits to load
1208 a remote processor firmware in SPL.
1211 bool "Support RTC drivers"
1213 Enable RTC (Real-time Clock) support in SPL. This includes support
1214 for reading and setting the time. Some RTC devices also have some
1215 non-volatile (battery-backed) memory which is accessible if
1216 needed. This enables the drivers in drivers/rtc as part of an SPL
1220 bool "Support loading from SATA"
1222 Enable support for SATA (Serial AT attachment) in SPL. This allows
1223 use of SATA devices such as hard drives and flash drivers for
1224 loading U-Boot. SATA is used in higher-end embedded systems and
1225 can provide higher performance than MMC , at somewhat higher
1226 expense and power consumption. This enables loading from SATA
1227 using a configured device.
1229 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1230 bool "SATA raw mode: by sector"
1232 default y if ARCH_MVEBU
1234 Use sector number for specifying U-Boot location on SATA disk in
1237 config SPL_SATA_RAW_U_BOOT_SECTOR
1238 hex "Sector on the SATA disk to load U-Boot from"
1239 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1240 default 0x1 if ARCH_MVEBU
1242 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1243 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1246 bool "Support serial"
1250 Enable support for serial in SPL. This allows use of a serial UART
1251 for displaying messages while SPL is running. It also brings in
1252 printf() and panic() functions. This should normally be enabled
1253 unless there are space reasons not to. Even then, consider
1254 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1257 bool "Support SPI drivers"
1259 Enable support for using SPI in SPL. This is used for connecting
1260 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1261 more details on that. The SPI driver provides the transport for
1262 data between the SPI flash and the CPU. This option can be used to
1263 enable SPI drivers that are needed for other purposes also, such
1266 config SPL_SPI_FLASH_SUPPORT
1267 bool "Support SPI flash drivers"
1270 Enable support for using SPI flash in SPL, and loading U-Boot from
1271 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1272 the SPI bus that is used to connect it to a system. It is a simple
1273 but fast bidirectional 4-wire bus (clock, chip select and two data
1274 lines). This enables the drivers in drivers/mtd/spi as part of an
1275 SPL build. This normally requires SPL_SPI.
1277 if SPL_SPI_FLASH_SUPPORT
1279 config SPL_SPI_FLASH_TINY
1280 bool "Enable low footprint SPL SPI Flash support"
1281 depends on !SPI_FLASH_BAR
1282 default y if SPI_FLASH
1284 Enable lightweight SPL SPI Flash support that supports just reading
1285 data/images from flash. No support to write/erase flash. Enable
1286 this if you have SPL size limitations and don't need full
1287 fledged SPI flash support.
1289 config SPL_SPI_FLASH_SFDP_SUPPORT
1290 bool "SFDP table parsing support for SPI NOR flashes"
1291 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1293 Enable support for parsing and auto discovery of parameters for
1294 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1295 tables as per JESD216 standard in SPL.
1297 config SPL_SPI_FLASH_MTD
1298 bool "Support for SPI flash MTD drivers in SPL"
1300 Enable support for SPI flash MTD drivers in SPL.
1303 bool "Support loading from SPI flash"
1305 Enable support for loading next stage, U-Boot or otherwise, from
1306 SPI NOR in U-Boot SPL.
1308 endif # SPL_SPI_FLASH_SUPPORT
1310 config SYS_SPI_U_BOOT_OFFS
1311 hex "address of u-boot payload in SPI flash"
1312 default 0x8000 if ARCH_SUNXI
1314 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1316 Address within SPI-Flash from where the u-boot payload is fetched
1320 bool "Driver support for thermal devices"
1322 Enable support for temperature-sensing devices. Some SoCs have on-chip
1323 temperature sensors to permit warnings, speed throttling or even
1324 automatic power-off when the temperature gets too high or low. Other
1325 devices may be discrete but connected on a suitable bus.
1328 bool "Support USB host drivers"
1329 select HAVE_BLOCK_DEVICE
1331 Enable access to USB (Universal Serial Bus) host devices so that
1332 SPL can load U-Boot from a connected USB peripheral, such as a USB
1333 flash stick. While USB takes a little longer to start up than most
1334 buses, it is very flexible since many different types of storage
1335 device can be attached. This option enables the drivers in
1336 drivers/usb/host as part of an SPL build.
1338 config SPL_USB_STORAGE
1339 bool "Support loading from USB"
1340 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1342 Enable support for USB devices in SPL. This allows use of USB
1343 devices such as hard drives and flash drivers for loading U-Boot.
1344 The actual drivers are enabled separately using the normal U-Boot
1345 config options. This enables loading from USB using a configured
1348 config SPL_USB_GADGET
1349 bool "Suppport USB Gadget drivers"
1351 Enable USB Gadget API which allows to enable USB device functions
1356 config SPL_USB_ETHER
1357 bool "Support USB Ethernet drivers"
1360 Enable access to the USB network subsystem and associated
1361 drivers in SPL. This permits SPL to load U-Boot over a
1362 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1363 than from an onboard peripheral. Environment support is required
1364 since the network stack uses a number of environment variables.
1365 See also SPL_NET and SPL_ETH.
1368 bool "Support DFU (Device Firmware Upgrade)"
1370 select SPL_DFU_NO_RESET
1371 depends on SPL_RAM_SUPPORT
1373 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1374 RAM memory device support. The ROM code will load and execute
1375 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1376 selected device partition from host-pc using dfu-utils.
1377 This feature is useful to flash the binaries to factory or bare-metal
1378 boards using USB interface.
1381 bool "DFU device selection"
1386 depends on SPL_DFU && SPL_RAM_SUPPORT
1388 select RAM/DDR memory device for loading binary images
1389 (u-boot/kernel) to the selected device partition using
1390 DFU and execute the u-boot/kernel from RAM.
1394 config SPL_USB_SDP_SUPPORT
1395 bool "Support SDP (Serial Download Protocol)"
1396 depends on SPL_SERIAL
1398 Enable Serial Download Protocol (SDP) device support in SPL. This
1399 allows to download images into memory and execute (jump to) them
1400 using the same protocol as implemented by the i.MX family's boot ROM.
1402 config SPL_SDP_USB_DEV
1403 int "SDP USB controller index"
1405 depends on SPL_USB_SDP_SUPPORT
1407 Some boards have USB controller other than 0. Define this option
1408 so it can be used in compiled environment.
1412 bool "Support watchdog drivers"
1413 imply SPL_WDT if !HW_WATCHDOG
1415 Enable support for watchdog drivers in SPL. A watchdog is
1416 typically a hardware peripheral which can reset the system when it
1417 detects no activity for a while (such as a software crash). This
1418 enables the drivers in drivers/watchdog as part of an SPL build.
1420 config SPL_YMODEM_SUPPORT
1421 bool "Support loading using Ymodem"
1422 depends on SPL_SERIAL
1424 While loading from serial is slow it can be a useful backup when
1425 there is no other option. The Ymodem protocol provides a reliable
1426 means of transmitting U-Boot over a serial line for using in SPL,
1427 with a checksum to ensure correctness.
1430 bool "Support ARM Trusted Firmware"
1431 depends on ARM64 && SPL_FIT
1433 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1434 is loaded by SPL (which is considered as BL2 in ATF terminology).
1435 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1437 config SPL_ATF_LOAD_IMAGE_V2
1438 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1441 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1443 If you want to load a bl31 image from the SPL and need the new
1446 config SPL_ATF_NO_PLATFORM_PARAM
1447 bool "Pass no platform parameter"
1450 While we expect to call a pointer to a valid FDT (or NULL)
1451 as the platform parameter to an ATF, some ATF versions are
1452 not U-Boot aware and have an insufficiently robust parameter
1453 validation to gracefully reject a FDT being passed.
1455 If this option is enabled, the spl_atf os-type handler will
1456 always pass NULL for the platform parameter.
1458 If your ATF is affected, say Y.
1460 config SPL_AM33XX_ENABLE_RTC32K_OSC
1461 bool "Enable the RTC32K OSC on AM33xx based platforms"
1464 Enable access to the AM33xx RTC and select the external 32kHz clock
1467 config SPL_OPTEE_IMAGE
1468 bool "Support OP-TEE Trusted OS image in SPL"
1471 OP-TEE is an open source Trusted OS which is loaded by SPL.
1472 More detail at: https://github.com/OP-TEE/optee_os
1475 bool "Support RISC-V OpenSBI"
1476 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1478 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1479 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1480 firmware. It is loaded and started by U-Boot SPL.
1482 More details are available at https://github.com/riscv/opensbi and
1483 https://github.com/riscv/riscv-sbi-doc
1485 config SPL_OPENSBI_LOAD_ADDR
1486 hex "OpenSBI load address"
1487 depends on SPL_OPENSBI
1489 Load address of the OpenSBI binary.
1493 depends on SUPPORT_TPL
1496 If you want to build TPL as well as the normal image and SPL, say Y.
1500 config TPL_SIZE_LIMIT
1501 hex "Maximum size of TPL image"
1505 Specifies the maximum length of the U-Boot TPL image.
1506 If this value is zero, it is ignored.
1508 config TPL_BINMAN_SYMBOLS
1509 bool "Declare binman symbols in TPL"
1510 depends on SPL_FRAMEWORK && BINMAN
1513 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1514 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1515 and spl_get_image_size().
1517 For this to work, you must have a U-Boot image in the binman image, so
1518 binman can update TPL with the location of it.
1520 config TPL_FRAMEWORK
1521 bool "Support TPL based upon the common SPL framework"
1522 default y if SPL_FRAMEWORK
1524 Enable the SPL framework under common/spl/ for TPL builds.
1525 This framework supports MMC, NAND and YMODEM and other methods
1526 loading of U-Boot's SPL stage. If unsure, say Y.
1529 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1530 depends on HANDOFF && TPL_BLOBLIST
1533 This option enables TPL to write handoff information. This can be
1534 used to pass information like the size of SDRAM from TPL to U-Boot
1535 proper. The information is also available to SPL if it is useful
1538 config TPL_BOARD_INIT
1539 bool "Call board-specific initialization in TPL"
1541 If this option is enabled, U-Boot will call the function
1542 spl_board_init() from board_init_r(). This function should be
1543 provided by the board.
1545 config TPL_BOOTCOUNT_LIMIT
1546 bool "Support bootcount in TPL"
1547 depends on TPL_ENV_SUPPORT
1549 If this option is enabled, the TPL will support bootcount.
1550 For example, it may be useful to choose the device to boot.
1553 string "Linker script for the TPL stage"
1555 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1556 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1558 The TPL stage will usually require a different linker-script
1559 (as it runs from a different memory region) than the regular
1560 U-Boot stage. Set this to the path of the linker-script to
1563 May be left empty to trigger the Makefile infrastructure to
1564 fall back to the linker-script used for the SPL stage.
1566 config TPL_NEEDS_SEPARATE_STACK
1567 bool "TPL needs a separate initial stack-pointer"
1570 Enable, if the TPL stage should not inherit its initial
1571 stack-pointer from the settings for the SPL stage.
1574 bool "Support power drivers"
1576 Enable support for power control in TPL. This includes support
1577 for PMICs (Power-management Integrated Circuits) and some of the
1578 features provided by PMICs. In particular, voltage regulators can
1579 be used to enable/disable power and vary its voltage. That can be
1580 useful in TPL to turn on boot peripherals and adjust CPU voltage
1581 so that the clock speed can be increased. This enables the drivers
1582 in drivers/power, drivers/power/pmic and drivers/power/regulator
1583 as part of an TPL build.
1585 config TPL_TEXT_BASE
1586 hex "Base address for the .text section of the TPL stage"
1589 The base address for the .text section of the TPL stage.
1592 hex "Maximum size (in bytes) for the TPL stage"
1593 default 0x2e000 if ROCKCHIP_RK3399
1594 default 0x8000 if ROCKCHIP_RK3288
1595 default 0x7000 if ROCKCHIP_RK322X || ROCKCHIP_RK3328 || ROCKCHIP_RK3368
1596 default 0x2800 if ROCKCHIP_PX30
1599 The maximum size (in bytes) of the TPL stage.
1602 hex "Offset to which the TPL should be padded before appending the TPL payload"
1603 depends on !TPL_FRAMEWORK && PPC
1604 default TPL_MAX_SIZE
1606 Image offset to which the TPL should be padded before appending the
1607 TPL payload. By default, this is defined as CONFIG_TPL_MAX_SIZE, or 0 if
1608 CONFIG_TPL_MAX_SIZE is undefined. CONFIG_TPL_PAD_TO must be either
1609 0, meaning to append the TPL payload without any padding, or >=
1610 CONFIG_TPL_MAX_SIZE.
1613 hex "Address of the initial stack-pointer for the TPL stage"
1614 depends on TPL_NEEDS_SEPARATE_STACK
1616 The address of the initial stack-pointer for the TPL stage.
1617 Usually this will be the (aligned) top-of-stack.
1619 config TPL_READ_ONLY
1621 depends on TPL_OF_PLATDATA
1622 select TPL_OF_PLATDATA_NO_BIND
1623 select TPL_OF_PLATDATA_RT
1625 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1626 section of memory. This means that of-platdata must make a copy (in
1627 writeable memory) of anything it wants to modify, such as
1628 device-private data.
1630 config TPL_BOOTROM_SUPPORT
1631 bool "Support returning to the BOOTROM (from TPL)"
1633 Some platforms (e.g. the Rockchip RK3368) provide support in their
1634 ROM for loading the next boot-stage after performing basic setup
1637 Enable this option, to return to the BOOTROM through the
1638 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1639 boot device list, if not implemented for a given board)
1642 bool "Support CRC32 in TPL"
1643 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1645 Enable this to support CRC32 in uImages or FIT images within SPL.
1646 This is a 32-bit checksum value that can be used to verify images.
1647 For FIT images, this is the least secure type of checksum, suitable
1648 for detected accidental image corruption. For secure applications you
1649 should consider SHA1 or SHA256.
1651 config TPL_DRIVERS_MISC
1652 bool "Support misc drivers in TPL"
1654 Enable miscellaneous drivers in TPL. These drivers perform various
1655 tasks that don't fall nicely into other categories, Enable this
1656 option to build the drivers in drivers/misc as part of an TPL
1657 build, for those that support building in TPL (not all drivers do).
1659 config TPL_ENV_SUPPORT
1660 bool "Support an environment"
1662 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1665 bool "Support GPIO in TPL"
1667 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1668 GPIOs allow U-Boot to read the state of an input line (high or
1669 low) and set the state of an output line. This can be used to
1670 drive LEDs, control power to various system parts and read user
1671 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1672 for example. Enable this option to build the drivers in
1673 drivers/gpio as part of an TPL build.
1678 Enable support for the I2C bus in TPL. See SPL_I2C for
1681 config TPL_LIBCOMMON_SUPPORT
1682 bool "Support common libraries"
1684 Enable support for common U-Boot libraries within TPL. See
1685 SPL_LIBCOMMON_SUPPORT for details.
1687 config TPL_LIBGENERIC_SUPPORT
1688 bool "Support generic libraries"
1690 Enable support for generic U-Boot libraries within TPL. See
1691 SPL_LIBGENERIC_SUPPORT for details.
1693 config TPL_MPC8XXX_INIT_DDR
1694 bool "Support MPC8XXX DDR init"
1696 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1697 SPL_MPC8XXX_INIT_DDR for details.
1703 Enable support for MMC within TPL. See SPL_MMC for details.
1705 config TPL_NAND_SUPPORT
1706 bool "Support NAND flash"
1708 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1711 bool "Support PCI drivers"
1713 Enable support for PCI in TPL. For platforms that need PCI to boot,
1714 or must perform some init using PCI in SPL, this provides the
1715 necessary driver support. This enables the drivers in drivers/pci
1716 as part of a TPL build.
1719 bool "Support PCH drivers"
1721 Enable support for PCH (Platform Controller Hub) devices in TPL.
1722 These are used to set up GPIOs and the SPI peripheral early in
1723 boot. This enables the drivers in drivers/pch as part of a TPL
1726 config TPL_RAM_SUPPORT
1727 bool "Support booting from RAM"
1729 Enable booting of an image in RAM. The image can be preloaded or
1730 it can be loaded by TPL directly into RAM (e.g. using USB).
1732 config TPL_RAM_DEVICE
1733 bool "Support booting from preloaded image in RAM"
1734 depends on TPL_RAM_SUPPORT
1736 Enable booting of an image already loaded in RAM. The image has to
1737 be already in memory when TPL takes over, e.g. loaded by the boot
1741 bool "Support RTC drivers"
1743 Enable RTC (Real-time Clock) support in TPL. This includes support
1744 for reading and setting the time. Some RTC devices also have some
1745 non-volatile (battery-backed) memory which is accessible if
1746 needed. This enables the drivers in drivers/rtc as part of an TPL
1750 bool "Support serial"
1754 Enable support for serial in TPL. See SPL_SERIAL for
1757 config TPL_SPI_FLASH_SUPPORT
1758 bool "Support SPI flash drivers"
1760 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1763 config TPL_SPI_FLASH_TINY
1764 bool "Enable low footprint TPL SPI Flash support"
1765 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1766 default y if SPI_FLASH
1768 Enable lightweight TPL SPI Flash support that supports just reading
1769 data/images from flash. No support to write/erase flash. Enable
1770 this if you have TPL size limitations and don't need full-fledged
1774 bool "Support loading from SPI flash"
1775 depends on TPL_SPI_FLASH_SUPPORT
1777 Enable support for loading next stage, U-Boot or otherwise, from
1778 SPI NOR in U-Boot TPL.
1781 bool "Support SPI drivers"
1783 Enable support for using SPI in TPL. See SPL_SPI for
1787 bool "Support SPI DM drivers in TPL"
1789 Enable support for SPI DM drivers in TPL.
1791 config TPL_DM_SPI_FLASH
1792 bool "Support SPI DM FLASH drivers in TPL"
1794 Enable support for SPI DM flash drivers in TPL.
1796 config TPL_YMODEM_SUPPORT
1797 bool "Support loading using Ymodem"
1798 depends on TPL_SERIAL
1800 While loading from serial is slow it can be a useful backup when
1801 there is no other option. The Ymodem protocol provides a reliable
1802 means of transmitting U-Boot over a serial line for using in TPL,
1803 with a checksum to ensure correctness.
1809 depends on SUPPORT_SPL
1812 If you want to build VPL as well as the normal image, TPL and SPL,
1817 config VPL_BANNER_PRINT
1818 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1822 If this option is enabled, VPL will print the banner with version
1823 info. Disabling this option could be useful to reduce VPL boot time
1824 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1826 config VPL_BOARD_INIT
1827 bool "Call board-specific initialization in VPL"
1829 If this option is enabled, U-Boot will call the function
1830 spl_board_init() from board_init_r(). This function should be
1831 provided by the board.
1835 bool "Support cache drivers in VPL"
1837 Enable support for cache drivers in VPL.
1840 bool "Support CRC32 in VPL"
1841 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1843 Enable this to support CRC32 in uImages or FIT images within VPL.
1844 This is a 32-bit checksum value that can be used to verify images.
1845 For FIT images, this is the least secure type of checksum, suitable
1846 for detected accidental image corruption. For secure applications you
1847 should consider SHA1 or SHA256.
1850 bool "Support SPI DM drivers in VPL"
1852 Enable support for SPI DM drivers in VPL.
1854 config VPL_DM_SPI_FLASH
1855 bool "Support SPI DM FLASH drivers in VPL"
1857 Enable support for SPI DM flash drivers in VPL.
1859 config VPL_FRAMEWORK
1860 bool "Support VPL based upon the common SPL framework"
1863 Enable the SPL framework under common/spl/ for VPL builds.
1864 This framework supports MMC, NAND and YMODEM and other methods
1865 loading of U-Boot's next stage. If unsure, say Y.
1868 bool "Pass hand-off information from VPL to SPL"
1869 depends on HANDOFF && VPL_BLOBLIST
1872 This option enables VPL to write handoff information. This can be
1873 used to pass information like the size of SDRAM from VPL to SPL. Also
1874 VPL can receive information from TPL in the same place if that is
1877 config VPL_LIBCOMMON_SUPPORT
1878 bool "Support common libraries"
1879 default y if SPL_LIBCOMMON_SUPPORT
1881 Enable support for common U-Boot libraries within VPL. See
1882 SPL_LIBCOMMON_SUPPORT for details.
1884 config VPL_LIBGENERIC_SUPPORT
1885 bool "Support generic libraries"
1886 default y if SPL_LIBGENERIC_SUPPORT
1888 Enable support for generic U-Boot libraries within VPL. These
1889 libraries include generic code to deal with device tree, hashing,
1890 printf(), compression and the like. This option is enabled on many
1891 boards. Enable this option to build the code in lib/ as part of a
1894 config VPL_DRIVERS_MISC
1895 bool "Support misc drivers"
1896 default y if TPL_DRIVERS_MISC
1898 Enable miscellaneous drivers in VPL. These drivers perform various
1899 tasks that don't fall nicely into other categories, Enable this
1900 option to build the drivers in drivers/misc as part of a VPL
1901 build, for those that support building in VPL (not all drivers do).
1903 config VPL_ENV_SUPPORT
1904 bool "Support an environment"
1906 Enable environment support in VPL. The U-Boot environment provides
1907 a number of settings (essentially name/value pairs) which can
1908 control many aspects of U-Boot's operation. Enabling this option will
1909 make env_get() and env_set() available in VSPL.
1912 bool "Support GPIO in VPL"
1913 default y if SPL_GPIO
1915 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1916 GPIOs allow U-Boot to read the state of an input line (high or
1917 low) and set the state of an output line. This can be used to
1918 drive LEDs, control power to various system parts and read user
1919 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1920 for example. Enable this option to build the drivers in
1921 drivers/gpio as part of a VPL build.
1924 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1925 depends on HANDOFF && VPL_BLOBLIST
1928 This option enables VPL to write handoff information. This can be
1929 used to pass information like the size of SDRAM from VPL to U-Boot
1930 proper. The information is also available to VPL if it is useful
1934 bool "Support hashing drivers in VPL"
1939 Enable hashing drivers in VPL. These drivers can be used to
1940 accelerate secure boot processing in secure applications. Enable
1941 this option to build system-specific drivers for hash acceleration
1942 as part of a VPL build.
1944 config VPL_I2C_SUPPORT
1945 bool "Support I2C in VPL"
1946 default y if SPL_I2C_SUPPORT
1948 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1951 config VPL_PCH_SUPPORT
1952 bool "Support PCH drivers"
1953 default y if TPL_PCH_SUPPORT
1955 Enable support for PCH (Platform Controller Hub) devices in VPL.
1956 These are used to set up GPIOs and the SPI peripheral early in
1957 boot. This enables the drivers in drivers/pch as part of a VPL
1961 bool "Support PCI drivers"
1962 default y if SPL_PCI
1964 Enable support for PCI in VPL. For platforms that need PCI to boot,
1965 or must perform some init using PCI in VPL, this provides the
1966 necessary driver support. This enables the drivers in drivers/pci
1967 as part of a VPL build.
1970 bool "Support RTC drivers"
1972 Enable RTC (Real-time Clock) support in VPL. This includes support
1973 for reading and setting the time. Some RTC devices also have some
1974 non-volatile (battery-backed) memory which is accessible if
1975 needed. This enables the drivers in drivers/rtc as part of a VPL
1979 bool "Support serial"
1980 default y if TPL_SERIAL
1984 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1987 config VPL_SIZE_LIMIT
1988 hex "Maximum size of VPL image"
1992 Specifies the maximum length of the U-Boot VPL image.
1993 If this value is zero, it is ignored.
1996 bool "Support SPI drivers"
1998 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
2001 config VPL_SPI_FLASH_SUPPORT
2002 bool "Support SPI flash drivers"
2004 Enable support for using SPI flash in VPL, and loading U-Boot from
2005 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
2006 the SPI bus that is used to connect it to a system. It is a simple
2007 but fast bidirectional 4-wire bus (clock, chip select and two data
2008 lines). This enables the drivers in drivers/mtd/spi as part of a
2009 VPL build. This normally requires VPL_SPI_SUPPORT.
2011 config VPL_TEXT_BASE
2015 The address in memory that VPL will be running from.
2019 config SPL_AT91_MCK_BYPASS
2020 bool "Use external clock signal as a source of main clock for AT91 platforms"
2021 depends on ARCH_AT91
2023 Use external 8 to 24 Mhz clock signal as source of main clock instead
2024 of an external crystal oscillator.
2025 This option disables the internal driving on the XOUT pin.
2026 The external source has to provide a stable clock on the XIN pin.
2027 If this option is disabled, the SoC expects a crystal oscillator
2028 that needs driving on both XIN and XOUT lines.