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 >=
108 config SPL_SYS_STACK_F_CHECK_BYTE
112 Constant used to check the stack
114 config SPL_SYS_REPORT_STACK_F_USAGE
115 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
116 bool "Check and report stack usage in SPL before relocation"
118 If this option is enabled, the initial SPL stack is filled with 0xaa
119 very early, up to the size configured with
120 SPL_SIZE_LIMIT_PROVIDE_STACK.
121 Later when SPL is done using this initial stack and switches to a
122 stack in DRAM, the actually used size of this initial stack is
123 reported by examining the memory and searching for the lowest
124 occurrence of non 0xaa bytes.
125 This default implementation works for stacks growing down only.
127 config SPL_SHOW_ERRORS
128 bool "Show more information when something goes wrong"
130 This enabled more verbose error messages and checking when something
131 goes wrong in SPL. For example, it shows the error code when U-Boot
132 cannot be located. This can help to diagnose the problem and figure
133 out a fix, particularly during development.
135 This adds a small amount to SPL code size, perhaps 100 bytes.
137 config SPL_BINMAN_SYMBOLS
138 bool "Declare binman symbols in SPL"
139 depends on SPL_FRAMEWORK && BINMAN
142 This enables use of symbols in SPL which refer to U-Boot, enabling SPL
143 to obtain the location of U-Boot simply by calling spl_get_image_pos()
144 and spl_get_image_size().
146 For this to work, you must have a U-Boot image in the binman image, so
147 binman can update SPL with the location of it.
149 menu "PowerPC and LayerScape SPL Boot options"
152 bool "Load SPL from NAND flash"
153 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
156 bool "Load SPL from SD Card / eMMC"
157 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
160 bool "Load SPL from SPI flash"
161 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
164 bool "Create SPL in Freescale PBI format"
165 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
168 Create boot binary having SPL binary in PBI format concatenated with
173 menu "PowerPC SPL specific options"
174 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
176 config SPL_INIT_MINIMAL
177 bool "Arch init code will be built for a very small image"
179 config SPL_FLUSH_IMAGE
180 bool "Clean dcache and invalidate icache after loading the image"
182 config SPL_SKIP_RELOCATE
183 bool "Skip relocating SPL"
188 bool "Pass hand-off information from SPL to U-Boot proper"
189 depends on SPL && BLOBLIST
191 It is useful to be able to pass information from SPL to U-Boot
192 proper to preserve state that is known in SPL and is needed in U-Boot.
193 Enable this to locate the handoff information in U-Boot proper, early
194 in boot. It is available in gd->handoff. The state state is set up
195 in SPL (or TPL if that is being used).
200 bool "Pass hand-off information from SPL to U-Boot proper"
201 depends on HANDOFF && SPL_BLOBLIST
204 This option enables SPL to write handoff information. This can be
205 used to pass information like the size of SDRAM from SPL to U-Boot
206 proper. Also SPL can receive information from TPL in the same place
210 string "Linker script for the SPL stage"
211 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
213 The SPL stage will usually require a different linker-script
214 (as it runs from a different memory region) than the regular
215 U-Boot stage. Set this to the path of the linker-script to
220 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
221 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
222 default 0x20060 if SUN50I_GEN_H6
223 default 0x00060 if ARCH_SUNXI
224 default 0xfffc0000 if ARCH_ZYNQMP
227 The address in memory that SPL will be running from.
229 config SPL_BOARD_INIT
230 bool "Call board-specific initialization in SPL"
232 If this option is enabled, U-Boot will call the function
233 spl_board_init() from board_init_r(). This function should be
234 provided by the board.
236 config VPL_BOARD_INIT
237 bool "Call board-specific initialization in VPL"
239 If this option is enabled, U-Boot will call the function
240 spl_board_init() from board_init_r(). This function should be
241 provided by the board.
243 config SPL_BOOTROM_SUPPORT
244 bool "Support returning to the BOOTROM"
246 Some platforms (e.g. the Rockchip RK3368) provide support in their
247 ROM for loading the next boot-stage after performing basic setup
250 Enable this option, to return to the BOOTROM through the
251 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
252 boot device list, if not implemented for a given board)
254 config SPL_BOOTCOUNT_LIMIT
255 bool "Support bootcount in SPL"
256 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
258 On some boards, which use 'falcon' mode, it is necessary to check
259 and increment the number of boot attempts. Such boards do not
260 use proper U-Boot for normal boot flow and hence needs those
261 adjustments to be done in the SPL.
263 config SPL_RAW_IMAGE_SUPPORT
264 bool "Support SPL loading and booting of RAW images"
265 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
267 depends on !TI_SECURE_DEVICE
269 SPL will support loading and booting a RAW image when this option
270 is y. If this is not set, SPL will move on to other available
271 boot media to find a suitable image.
273 config SPL_LEGACY_IMAGE_FORMAT
274 bool "Support SPL loading and booting of Legacy images"
275 default y if !SPL_LOAD_FIT
276 depends on !TI_SECURE_DEVICE
278 SPL will support loading and booting Legacy images when this option
279 is y. If this is not set, SPL will move on to other available
280 boot media to find a suitable image.
282 config SPL_LEGACY_IMAGE_CRC_CHECK
283 bool "Check CRC of Legacy images"
284 depends on SPL_LEGACY_IMAGE_FORMAT
287 Enable this to check the CRC of Legacy images. While this increases
288 reliability, it affects both code size and boot duration.
289 If disabled, Legacy images are booted if the image magic and size
290 are correct, without further integrity checks.
292 config SPL_SYS_MALLOC_SIMPLE
294 prompt "Only use malloc_simple functions in the SPL"
296 Say Y here to only use the *_simple malloc functions from
297 malloc_simple.c, rather then using the versions from dlmalloc.c;
298 this will make the SPL binary smaller at the cost of more heap
299 usage as the *_simple malloc functions do not re-use free-ed mem.
301 config TPL_SYS_MALLOC_SIMPLE
303 prompt "Only use malloc_simple functions in the TPL"
306 Say Y here to only use the *_simple malloc functions from
307 malloc_simple.c, rather then using the versions from dlmalloc.c;
308 this will make the TPL binary smaller at the cost of more heap
309 usage as the *_simple malloc functions do not re-use free-ed mem.
312 bool "Enable SDRAM location for SPL stack"
314 SPL starts off execution in SRAM and thus typically has only a small
315 stack available. Since SPL sets up DRAM while in its board_init_f()
316 function, it is possible for the stack to move there before
317 board_init_r() is reached. This option enables a special SDRAM
318 location for the SPL stack. U-Boot SPL switches to this after
319 board_init_f() completes, and before board_init_r() starts.
321 config SPL_STACK_R_ADDR
322 depends on SPL_STACK_R
323 hex "SDRAM location for SPL stack"
324 default 0x82000000 if ARCH_OMAP2PLUS
326 Specify the address in SDRAM for the SPL stack. This will be set up
327 before board_init_r() is called.
329 config SPL_STACK_R_MALLOC_SIMPLE_LEN
330 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
331 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
334 Specify the amount of the stack to use as memory pool for
335 malloc_simple after switching the stack to DRAM. This may be set
336 to give board_init_r() a larger heap then the initial heap in
337 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
339 config SPL_SEPARATE_BSS
340 bool "BSS section is in a different memory region from text"
342 Some platforms need a large BSS region in SPL and can provide this
343 because RAM is already set up. In this case BSS can be moved to RAM.
344 This option should then be enabled so that the correct device tree
345 location is used. Normally we put the device tree at the end of BSS
346 but with this option enabled, it goes at _image_binary_end.
350 depends on SPL_OF_PLATDATA
351 # Bind cannot be supported because the udevice structs are in read-only
352 # memory so we cannot update the linked lists.
353 select SPL_OF_PLATDATA_NO_BIND
354 select SPL_OF_PLATDATA_RT
356 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
357 section of memory. This means that of-platdata must make a copy (in
358 writeable memory) of anything it wants to modify, such as
361 config TPL_SEPARATE_BSS
362 bool "BSS section is in a different memory region from text"
363 default y if SPL_SEPARATE_BSS
365 Some platforms need a large BSS region in TPL and can provide this
366 because RAM is already set up. In this case BSS can be moved to RAM.
367 This option should then be enabled so that the correct device tree
368 location is used. Normally we put the device tree at the end of BSS
369 but with this option enabled, it goes at _image_binary_end.
371 config SPL_BANNER_PRINT
372 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
375 If this option is enabled, SPL will print the banner with version
376 info. Disabling this option could be useful to reduce SPL boot time
377 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
379 config TPL_BANNER_PRINT
380 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
384 If this option is enabled, TPL will print the banner with version
385 info. Disabling this option could be useful to reduce TPL boot time
386 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
389 depends on ARM && !ARM64
390 bool "Allows initializing BSS early before entering board_init_f"
392 On some platform we have sufficient memory available early on to
393 allow setting up and using a basic BSS prior to entering
394 board_init_f. Activating this option will also de-activate the
395 clearing of BSS during the SPL relocation process, thus allowing
396 to carry state from board_init_f to board_init_r by way of BSS.
398 config SPL_DISPLAY_PRINT
399 bool "Display a board-specific message in SPL"
401 If this option is enabled, U-Boot will call the function
402 spl_display_print() immediately after displaying the SPL console
403 banner ("U-Boot SPL ..."). This function should be provided by
406 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
407 bool "MMC raw mode: by sector"
408 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
409 ARCH_MX6 || ARCH_MX7 || \
410 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
411 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
412 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
413 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
415 Use sector number for specifying U-Boot location on MMC/SD in
418 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
419 hex "Address on the MMC to load U-Boot from"
420 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
421 default 0x40 if ARCH_SUNXI
422 default 0x75 if ARCH_DAVINCI
423 default 0x8a if ARCH_MX6 || ARCH_MX7
424 default 0x100 if ARCH_UNIPHIER
425 default 0x0 if ARCH_MVEBU
426 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
427 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
428 OMAP54XX || AM33XX || AM43XX || ARCH_K3
429 default 0x4000 if ARCH_ROCKCHIP
430 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
432 Address on the MMC to load U-Boot from, when the MMC is being used
433 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
435 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
436 hex "U-Boot main hardware partition image offset"
437 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
438 default 0x10 if ARCH_SUNXI
441 On some platforms SPL location depends on hardware partition. The ROM
442 code skips the MBR sector when loading SPL from main hardware data
443 partition. This adds offset to the main U-Boot image. Set this symbol
444 to the number of skipped sectors.
446 If unsure, leave the default.
448 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
449 bool "MMC Raw mode: by partition"
451 Use a partition for loading U-Boot when using MMC/SD in raw mode.
453 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
454 hex "Partition to use to load U-Boot from"
455 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
458 Partition on the MMC to load U-Boot from when the MMC is being
461 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
462 bool "MMC raw mode: by partition type"
463 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
465 Use partition type for specifying U-Boot partition on MMC/SD in
466 raw mode. U-Boot will be loaded from the first partition of this
469 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
470 hex "Partition Type on the MMC to load U-Boot from"
471 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
473 Partition Type on the MMC to load U-Boot from, when the MMC is being
476 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
477 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
478 depends on SUPPORT_EMMC_BOOT
480 eMMC boot partition is normally configured by the bits of the EXT_CSD
481 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
482 cases it might be required in SPL to load the image from different
483 partition than the partition selected by EXT_CSC_PART_CONFIG register.
484 Enable this option if you intend to use an eMMC boot partition other
485 then selected via EXT_CSC_PART_CONFIG register and specify the custom
486 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
489 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
490 int "Number of the eMMC boot partition to use"
491 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
494 eMMC boot partition number to use when the eMMC in raw mode and
495 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
496 by user defined partition number.
500 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
501 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
503 Enable this to support CRC32 in uImages or FIT images within SPL.
504 This is a 32-bit checksum value that can be used to verify images.
505 For FIT images, this is the least secure type of checksum, suitable
506 for detected accidental image corruption. For secure applications you
507 should consider SHA1 or SHA256.
513 Enable this to support MD5 in FIT images within SPL. An MD5
514 checksum is a 128-bit hash value used to check that the image
515 contents have not been corrupted. Note that MD5 is not considered
516 secure as it is possible (with a brute-force attack) to adjust the
517 image while still retaining the same MD5 hash value. For secure
518 applications where images may be changed maliciously, you should
519 consider SHA256 or SHA384.
521 config SPL_FIT_IMAGE_TINY
522 bool "Remove functionality from SPL FIT loading to reduce size"
524 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
525 default y if ARCH_IMX8M
527 Enable this to reduce the size of the FIT image loading code
528 in SPL, if space for the SPL binary is very tight.
530 This skips the recording of each loaded payload
531 (i.e. loadable) into the FDT (modifying the loaded FDT to
532 ensure this information is available to the next image
536 bool "Support CACHE drivers"
538 Enable CACHE drivers in SPL. These drivers can keep data so that
539 future requests for that data can be served faster. Enable this option
540 to build the drivers in drivers/cache as part of an SPL build.
543 bool "Support CPU drivers"
545 Enable this to support CPU drivers in SPL. These drivers can set
546 up CPUs and provide information about them such as the model and
547 name. This can be useful in SPL since setting up the CPUs earlier
548 may improve boot performance. Enable this option to build the
549 drivers in drivers/cpu as part of an SPL build.
552 bool "Support crypto drivers"
554 Enable crypto drivers in SPL. These drivers can be used to
555 accelerate secure boot processing in secure applications. Enable
556 this option to build the drivers in drivers/crypto as part of an
560 bool "Support DMA drivers"
562 Enable DMA (direct-memory-access) drivers in SPL. These drivers
563 can be used to handle memory-to-peripheral data transfer without
564 the CPU moving the data. Enable this option to build the drivers
565 in drivers/dma as part of an SPL build.
567 config SPL_DRIVERS_MISC
568 bool "Support misc drivers"
570 Enable miscellaneous drivers in SPL. These drivers perform various
571 tasks that don't fall nicely into other categories, Enable this
572 option to build the drivers in drivers/misc as part of an SPL
573 build, for those that support building in SPL (not all drivers do).
575 config SPL_ENV_SUPPORT
576 bool "Support an environment"
578 Enable environment support in SPL. The U-Boot environment provides
579 a number of settings (essentially name/value pairs) which can
580 control many aspects of U-Boot's operation. Normally this is not
581 needed in SPL as it has a much simpler task with less
582 configuration. But some boards use this to support 'Falcon' boot
583 on EXT2 and FAT, where SPL boots directly into Linux without
584 starting U-Boot first. Enabling this option will make env_get()
585 and env_set() available in SPL.
588 bool "Support save environment"
589 depends on SPL_ENV_SUPPORT
590 select SPL_MMC_WRITE if ENV_IS_IN_MMC
592 Enable save environment support in SPL after setenv. By default
593 the saveenv option is not provided in SPL, but some boards need
594 this support in 'Falcon' boot, where SPL need to boot from
595 different images based on environment variable set by OS. For
596 example OS may set "reboot_image" environment variable to
597 "recovery" inorder to boot recovery image by SPL. The SPL read
598 "reboot_image" and act accordingly and change the reboot_image
599 to default mode using setenv and save the environment.
602 bool "Support Ethernet"
603 depends on SPL_ENV_SUPPORT
606 Enable access to the network subsystem and associated Ethernet
607 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
608 link rather than from an on-board peripheral. Environment support
609 is required since the network stack uses a number of environment
610 variables. See also SPL_NET.
613 bool "Support EXT filesystems"
615 Enable support for EXT2/3/4 filesystems with SPL. This permits
616 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
617 filesystem from within SPL. Support for the underlying block
618 device (e.g. MMC or USB) must be enabled separately.
620 config SPL_FS_SQUASHFS
621 bool "Support SquashFS filesystems"
624 Enable support for SquashFS filesystems with SPL. This permits
625 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
626 filesystem from within SPL. Support for the underlying block
627 device (e.g. MMC or USB) must be enabled separately.
630 bool "Support FAT filesystems"
633 Enable support for FAT and VFAT filesystems with SPL. This
634 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
635 filesystem from within SPL. Support for the underlying block
636 device (e.g. MMC or USB) must be enabled separately.
638 config SPL_FS_LOAD_PAYLOAD_NAME
639 string "File to load for U-Boot from the filesystem"
640 depends on SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS
641 default "tispl.bin" if SYS_K3_SPL_ATF
642 default "u-boot.itb" if SPL_LOAD_FIT
645 Filename to read to load U-Boot when reading from filesystem.
647 config SPL_FS_LOAD_KERNEL_NAME
648 string "File to load for the OS kernel from the filesystem"
649 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
652 Filename to read to load for the OS kernel when reading from the
655 config SPL_FS_LOAD_ARGS_NAME
656 string "File to load for the OS kernel argument parameters from the filesystem"
657 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
660 Filename to read to load for the OS kernel argument parameters from
664 bool "Support write for FAT filesystems"
666 Enable write support for FAT and VFAT filesystems with SPL.
667 Support for the underlying block device (e.g. MMC or USB) must be
673 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
674 provide software-configurable hardware which is typically used to
675 implement peripherals (such as UARTs, LCD displays, MMC) or
676 accelerate custom processing functions, such as image processing
677 or machine learning. Sometimes it is useful to program the FPGA
678 as early as possible during boot, and this option can enable that
682 bool "Support GPIO in SPL"
684 Enable support for GPIOs (General-purpose Input/Output) in SPL.
685 GPIOs allow U-Boot to read the state of an input line (high or
686 low) and set the state of an output line. This can be used to
687 drive LEDs, control power to various system parts and read user
688 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
689 for example. Enable this option to build the drivers in
690 drivers/gpio as part of an SPL build.
695 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
696 I2C works with a clock and data line which can be driven by a
697 one or more masters or slaves. It is a fairly complex bus but is
698 widely used as it only needs two lines for communication. Speeds of
699 400kbps are typical but up to 3.4Mbps is supported by some
700 hardware. I2C can be useful in SPL to configure power management
701 ICs (PMICs) before raising the CPU clock speed, for example.
702 Enable this option to build the drivers in drivers/i2c as part of
705 config SPL_LIBCOMMON_SUPPORT
706 bool "Support common libraries"
708 Enable support for common U-Boot libraries within SPL. These
709 libraries include common code to deal with U-Boot images,
710 environment and USB, for example. This option is enabled on many
711 boards. Enable this option to build the code in common/ as part of
714 config SPL_LIBDISK_SUPPORT
715 bool "Support disk partitions"
718 Enable support for disk partitions within SPL. 'Disk' is something
719 of a misnomer as it includes non-spinning media such as flash (as
720 used in MMC and USB sticks). Partitions provide a way for a disk
721 to be split up into separate regions, with a partition table placed
722 at the start or end which describes the location and size of each
723 'partition'. These partitions are typically uses as individual block
724 devices, typically with an EXT2 or FAT filesystem in each. This
725 option enables whatever partition support has been enabled in
726 U-Boot to also be used in SPL. It brings in the code in disk/.
728 config SPL_LIBGENERIC_SUPPORT
729 bool "Support generic libraries"
731 Enable support for generic U-Boot libraries within SPL. These
732 libraries include generic code to deal with device tree, hashing,
733 printf(), compression and the like. This option is enabled on many
734 boards. Enable this option to build the code in lib/ as part of an
737 config SPL_DM_MAILBOX
738 bool "Support Mailbox"
740 Enable support for Mailbox within SPL. This enable the inter
741 processor communication protocols tobe used within SPL. Enable
742 this option to build the drivers in drivers/mailbox as part of
748 select HAVE_BLOCK_DEVICE
750 Enable support for MMC (Multimedia Card) within SPL. This enables
751 the MMC protocol implementation and allows any enabled drivers to
752 be used within SPL. MMC can be used with or without disk partition
753 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
754 this option to build the drivers in drivers/mmc as part of an SPL
757 config SYS_MMCSD_FS_BOOT_PARTITION
758 int "MMC Boot Partition"
761 Partition on the MMC to load U-Boot from when the MMC is being
763 Use -1 as a special value to use the first bootable partition.
766 bool "Tiny MMC framework in SPL"
769 Enable MMC framework tinification support. This option is useful if
770 if your SPL is extremely size constrained. Heed the warning, enable
771 this option if and only if you know exactly what you are doing, if
772 you are reading this help text, you most likely have no idea :-)
774 The MMC framework is reduced to bare minimum to be useful. No malloc
775 support is needed for the MMC framework operation with this option
776 enabled. The framework supports exactly one MMC device and exactly
777 one MMC driver. The MMC driver can be adjusted to avoid any malloc
778 operations too, which can remove the need for malloc support in SPL
779 and thus further reduce footprint.
782 bool "MMC/SD/SDIO card support for write operations in SPL"
785 Enable write access to MMC and SD Cards in SPL
788 config SPL_MPC8XXX_INIT_DDR
789 bool "Support MPC8XXX DDR init"
791 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
792 random-access memory) on the MPC8XXX family within SPL. This
793 allows DRAM to be set up before loading U-Boot into that DRAM,
796 config SPL_MTD_SUPPORT
797 bool "Support MTD drivers"
799 Enable support for MTD (Memory Technology Device) within SPL. MTD
800 provides a block interface over raw NAND and can also be used with
801 SPI flash. This allows SPL to load U-Boot from supported MTD
802 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
803 to enable specific MTD drivers.
806 bool "Support new Mentor Graphics USB"
808 Enable support for Mentor Graphics USB in SPL. This is a new
809 driver used by some boards. Enable this option to build
810 the drivers in drivers/usb/musb-new as part of an SPL build. The
811 old drivers are in drivers/usb/musb.
813 config SPL_NAND_SUPPORT
814 bool "Support NAND flash"
816 Enable support for NAND (Negative AND) flash in SPL. NAND flash
817 can be used to allow SPL to load U-Boot from supported devices.
818 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
821 config SPL_NAND_RAW_ONLY
822 bool "Support to boot only raw u-boot.bin images"
823 depends on SPL_NAND_SUPPORT
825 Use this only if you need to save space.
827 config SPL_NAND_DRIVERS
828 bool "Use standard NAND driver"
830 SPL uses normal NAND drivers, not minimal drivers.
833 bool "Include standard ECC in SPL"
835 config SPL_NAND_SOFTECC
836 bool "Use software ECC in SPL"
837 depends on SPL_NAND_ECC
839 config SPL_NAND_SIMPLE
840 bool "Support simple NAND drivers in SPL"
842 Support for NAND boot using simple NAND drivers that
843 expose the cmd_ctrl() interface.
846 depends on SPL_NAND_DRIVERS
847 bool "Use Base NAND Driver"
849 Include nand_base.c in the SPL.
851 config SPL_NAND_IDENT
852 depends on SPL_NAND_BASE
853 bool "Use chip ID to identify NAND flash"
855 SPL uses the chip ID list to identify the NAND flash.
860 Enable support for loading payloads from UBI. See
861 README.ubispl for more info.
865 bool "Support SPI DM drivers in SPL"
867 Enable support for SPI DM drivers in SPL.
869 config SPL_DM_SPI_FLASH
870 bool "Support SPI DM FLASH drivers in SPL"
872 Enable support for SPI DM flash drivers in SPL.
876 config SPL_UBI_LOAD_BY_VOLNAME
877 bool "Support loading volumes by name"
879 This enables support for loading UBI volumes by name. When this
880 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
881 configure the volume name from which to load U-Boot.
883 config SPL_UBI_MAX_VOL_LEBS
884 int "Maximum number of LEBs per volume"
887 The maximum number of logical eraseblocks which a static volume
888 to load can contain. Used for sizing the scan data structure.
890 config SPL_UBI_MAX_PEB_SIZE
891 int "Maximum PEB size"
894 The maximum physical erase block size.
896 config SPL_UBI_MAX_PEBS
897 int "Maximum number of PEBs"
900 The maximum physical erase block size. If not overridden by
901 board code, this value will be used as the actual number of PEBs.
903 config SPL_UBI_PEB_OFFSET
904 int "Offset to first UBI PEB"
907 The offset in number of PEBs from the start of flash to the first
908 PEB part of the UBI image.
910 config SPL_UBI_VID_OFFSET
911 int "Offset to VID header"
914 config SPL_UBI_LEB_START
915 int "Offset to LEB in PEB"
918 The offset in bytes to the LEB within a PEB.
920 config SPL_UBI_INFO_ADDR
921 hex "Address to place UBI scan info"
924 Address for ubispl to place the scan info. Read README.ubispl to
925 determine the required size
927 config SPL_UBI_VOL_IDS
928 int "Maximum volume id"
931 The maximum volume id which can be loaded. Used for sizing the
934 config SPL_UBI_LOAD_MONITOR_ID
935 int "id of U-Boot volume"
938 The UBI volume id from which to load U-Boot
940 config SPL_UBI_LOAD_MONITOR_VOLNAME
941 string "volume name of U-Boot volume"
942 depends on SPL_UBI_LOAD_BY_VOLNAME
944 The UBI volume name from which to load U-Boot
946 config SPL_UBI_LOAD_KERNEL_ID
947 int "id of kernel volume"
948 depends on SPL_OS_BOOT && SPL_UBI
950 The UBI volume id from which to load the kernel
952 config SPL_UBI_LOAD_ARGS_ID
953 int "id of kernel args volume"
954 depends on SPL_OS_BOOT && SPL_UBI
956 The UBI volume id from which to load the device tree
958 config UBI_SPL_SILENCE_MSG
959 bool "silence UBI SPL messages"
961 Disable messages from UBI SPL. This leaves warnings
967 bool "Support networking"
969 Enable support for network devices (such as Ethernet) in SPL.
970 This permits SPL to load U-Boot over a network link rather than
971 from an on-board peripheral. Environment support is required since
972 the network stack uses a number of environment variables. See also
976 config SPL_NET_VCI_STRING
977 string "BOOTP Vendor Class Identifier string sent by SPL"
979 As defined by RFC 2132 the vendor class identifier field can be
980 sent by the client to identify the vendor type and configuration
981 of a client. This is often used in practice to allow for the DHCP
982 server to specify different files to load depending on if the ROM,
983 SPL or U-Boot itself makes the request
986 config SPL_NO_CPU_SUPPORT
987 bool "Drop CPU code in SPL"
989 This is specific to the ARM926EJ-S CPU. It disables the standard
990 start.S start-up code, presumably so that a replacement can be
991 used on that CPU. You should not enable it unless you know what
994 config SPL_NOR_SUPPORT
995 bool "Support NOR flash"
997 Enable support for loading U-Boot from memory-mapped NOR (Negative
998 OR) flash in SPL. NOR flash is slow to write but fast to read, and
999 a memory-mapped device makes it very easy to access. Loading from
1000 NOR is typically achieved with just a memcpy().
1002 config SPL_XIP_SUPPORT
1006 Enable support for execute in place of U-Boot or kernel image. There
1007 is no need to copy image from flash to ram if flash supports execute
1008 in place. Its very useful in systems having enough flash but not
1009 enough ram to load the image.
1011 config SPL_ONENAND_SUPPORT
1012 bool "Support OneNAND flash"
1014 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
1015 a type of NAND flash and therefore can be used to allow SPL to
1016 load U-Boot from supported devices. This enables the drivers in
1017 drivers/mtd/onenand as part of an SPL build.
1020 bool "Activate Falcon Mode"
1021 depends on !TI_SECURE_DEVICE
1023 Enable booting directly to an OS from SPL.
1024 for more info read doc/README.falcon
1028 hex "addr, where OS is found"
1029 depends on SPL_NOR_SUPPORT
1031 Specify the address, where the OS image is found, which
1036 config SPL_FALCON_BOOT_MMCSD
1037 bool "Enable Falcon boot from MMC or SD media"
1038 depends on SPL_OS_BOOT && SPL_MMC
1040 Select this if the Falcon mode OS image mode is on MMC or SD media.
1042 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
1043 hex "Falcon mode: Sector to load kernel uImage from MMC"
1044 depends on SPL_FALCON_BOOT_MMCSD
1046 When Falcon mode is used with an MMC or SD media, SPL needs to know
1047 where to look for the kernel uImage. The image is expected to begin
1048 at the raw MMC specified in this config.
1049 Note that the Falcon mode image can also be a FIT, if FIT support is
1053 string "SPL payload"
1054 default "tpl/u-boot-with-tpl.bin" if TPL
1055 default "u-boot.bin"
1057 Payload for SPL boot. For backward compatibility, default to
1058 u-boot.bin, i.e. RAW image without any header. In case of
1059 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
1063 bool "Support PCI drivers"
1065 Enable support for PCI in SPL. For platforms that need PCI to boot,
1066 or must perform some init using PCI in SPL, this provides the
1067 necessary driver support. This enables the drivers in drivers/pci
1068 as part of an SPL build.
1071 bool "Support PCH drivers"
1073 Enable support for PCH (Platform Controller Hub) devices in SPL.
1074 These are used to set up GPIOs and the SPI peripheral early in
1075 boot. This enables the drivers in drivers/pch as part of an SPL
1078 config SPL_POST_MEM_SUPPORT
1079 bool "Support POST drivers"
1081 Enable support for POST (Power-on Self Test) in SPL. POST is a
1082 procedure that checks that the hardware (CPU or board) appears to
1083 be functionally correctly. It is a sanity check that can be
1084 performed before booting. This enables the drivers in post/drivers
1085 as part of an SPL build.
1088 bool "Support reset drivers"
1091 Enable support for reset control in SPL.
1092 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1093 by using the generic reset API provided by driver model.
1094 This enables the drivers in drivers/reset as part of an SPL build.
1097 bool "Support power drivers"
1099 Enable support for power control in SPL. This includes support
1100 for PMICs (Power-management Integrated Circuits) and some of the
1101 features provided by PMICs. In particular, voltage regulators can
1102 be used to enable/disable power and vary its voltage. That can be
1103 useful in SPL to turn on boot peripherals and adjust CPU voltage
1104 so that the clock speed can be increased. This enables the drivers
1105 in drivers/power, drivers/power/pmic and drivers/power/regulator
1106 as part of an SPL build.
1108 config SPL_POWER_DOMAIN
1109 bool "Support power domain drivers"
1112 Enable support for power domain control in SPL. Many SoCs allow
1113 power to be applied to or removed from portions of the SoC (power
1114 domains). This may be used to save power. This API provides the
1115 means to control such power management hardware. This enables
1116 the drivers in drivers/power/domain as part of a SPL build.
1118 config SPL_RAM_SUPPORT
1119 bool "Support booting from RAM"
1120 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1122 Enable booting of an image in RAM. The image can be preloaded or
1123 it can be loaded by SPL directly into RAM (e.g. using USB).
1125 config SPL_RAM_DEVICE
1126 bool "Support booting from preloaded image in RAM"
1127 depends on SPL_RAM_SUPPORT
1128 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1130 Enable booting of an image already loaded in RAM. The image has to
1131 be already in memory when SPL takes over, e.g. loaded by the boot
1134 config SPL_REMOTEPROC
1135 bool "Support REMOTEPROCS"
1137 Enable support for REMOTEPROCs in SPL. This permits to load
1138 a remote processor firmware in SPL.
1141 bool "Support RTC drivers"
1143 Enable RTC (Real-time Clock) support in SPL. This includes support
1144 for reading and setting the time. Some RTC devices also have some
1145 non-volatile (battery-backed) memory which is accessible if
1146 needed. This enables the drivers in drivers/rtc as part of an SPL
1150 bool "Support loading from SATA"
1152 Enable support for SATA (Serial AT attachment) in SPL. This allows
1153 use of SATA devices such as hard drives and flash drivers for
1154 loading U-Boot. SATA is used in higher-end embedded systems and
1155 can provide higher performance than MMC , at somewhat higher
1156 expense and power consumption. This enables loading from SATA
1157 using a configured device.
1159 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1160 bool "SATA raw mode: by sector"
1162 default y if ARCH_MVEBU
1164 Use sector number for specifying U-Boot location on SATA disk in
1167 config SPL_SATA_RAW_U_BOOT_SECTOR
1168 hex "Sector on the SATA disk to load U-Boot from"
1169 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1170 default 0x1 if ARCH_MVEBU
1172 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1173 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1176 bool "Support serial"
1180 Enable support for serial in SPL. This allows use of a serial UART
1181 for displaying messages while SPL is running. It also brings in
1182 printf() and panic() functions. This should normally be enabled
1183 unless there are space reasons not to. Even then, consider
1184 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1187 bool "Support SPI drivers"
1189 Enable support for using SPI in SPL. This is used for connecting
1190 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1191 more details on that. The SPI driver provides the transport for
1192 data between the SPI flash and the CPU. This option can be used to
1193 enable SPI drivers that are needed for other purposes also, such
1196 config SPL_SPI_FLASH_SUPPORT
1197 bool "Support SPI flash drivers"
1200 Enable support for using SPI flash in SPL, and loading U-Boot from
1201 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1202 the SPI bus that is used to connect it to a system. It is a simple
1203 but fast bidirectional 4-wire bus (clock, chip select and two data
1204 lines). This enables the drivers in drivers/mtd/spi as part of an
1205 SPL build. This normally requires SPL_SPI.
1207 if SPL_SPI_FLASH_SUPPORT
1209 config SPL_SPI_FLASH_TINY
1210 bool "Enable low footprint SPL SPI Flash support"
1211 depends on !SPI_FLASH_BAR
1212 default y if SPI_FLASH
1214 Enable lightweight SPL SPI Flash support that supports just reading
1215 data/images from flash. No support to write/erase flash. Enable
1216 this if you have SPL size limitations and don't need full
1217 fledged SPI flash support.
1219 config SPL_SPI_FLASH_SFDP_SUPPORT
1220 bool "SFDP table parsing support for SPI NOR flashes"
1221 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1223 Enable support for parsing and auto discovery of parameters for
1224 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1225 tables as per JESD216 standard in SPL.
1227 config SPL_SPI_FLASH_MTD
1228 bool "Support for SPI flash MTD drivers in SPL"
1230 Enable support for SPI flash MTD drivers in SPL.
1233 bool "Support loading from SPI flash"
1235 Enable support for loading next stage, U-Boot or otherwise, from
1236 SPI NOR in U-Boot SPL.
1238 endif # SPL_SPI_FLASH_SUPPORT
1240 config SYS_SPI_U_BOOT_OFFS
1241 hex "address of u-boot payload in SPI flash"
1242 default 0x8000 if ARCH_SUNXI
1244 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1246 Address within SPI-Flash from where the u-boot payload is fetched
1250 bool "Driver support for thermal devices"
1252 Enable support for temperature-sensing devices. Some SoCs have on-chip
1253 temperature sensors to permit warnings, speed throttling or even
1254 automatic power-off when the temperature gets too high or low. Other
1255 devices may be discrete but connected on a suitable bus.
1258 bool "Support USB host drivers"
1259 select HAVE_BLOCK_DEVICE
1261 Enable access to USB (Universal Serial Bus) host devices so that
1262 SPL can load U-Boot from a connected USB peripheral, such as a USB
1263 flash stick. While USB takes a little longer to start up than most
1264 buses, it is very flexible since many different types of storage
1265 device can be attached. This option enables the drivers in
1266 drivers/usb/host as part of an SPL build.
1268 config SPL_USB_STORAGE
1269 bool "Support loading from USB"
1270 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1272 Enable support for USB devices in SPL. This allows use of USB
1273 devices such as hard drives and flash drivers for loading U-Boot.
1274 The actual drivers are enabled separately using the normal U-Boot
1275 config options. This enables loading from USB using a configured
1278 config SPL_USB_GADGET
1279 bool "Suppport USB Gadget drivers"
1281 Enable USB Gadget API which allows to enable USB device functions
1286 config SPL_USB_ETHER
1287 bool "Support USB Ethernet drivers"
1290 Enable access to the USB network subsystem and associated
1291 drivers in SPL. This permits SPL to load U-Boot over a
1292 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1293 than from an onboard peripheral. Environment support is required
1294 since the network stack uses a number of environment variables.
1295 See also SPL_NET and SPL_ETH.
1298 bool "Support DFU (Device Firmware Upgrade)"
1300 select SPL_DFU_NO_RESET
1301 depends on SPL_RAM_SUPPORT
1303 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1304 RAM memory device support. The ROM code will load and execute
1305 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1306 selected device partition from host-pc using dfu-utils.
1307 This feature is useful to flash the binaries to factory or bare-metal
1308 boards using USB interface.
1311 bool "DFU device selection"
1316 depends on SPL_DFU && SPL_RAM_SUPPORT
1318 select RAM/DDR memory device for loading binary images
1319 (u-boot/kernel) to the selected device partition using
1320 DFU and execute the u-boot/kernel from RAM.
1324 config SPL_USB_SDP_SUPPORT
1325 bool "Support SDP (Serial Download Protocol)"
1326 depends on SPL_SERIAL
1328 Enable Serial Download Protocol (SDP) device support in SPL. This
1329 allows to download images into memory and execute (jump to) them
1330 using the same protocol as implemented by the i.MX family's boot ROM.
1332 config SPL_SDP_USB_DEV
1333 int "SDP USB controller index"
1335 depends on SPL_USB_SDP_SUPPORT
1337 Some boards have USB controller other than 0. Define this option
1338 so it can be used in compiled environment.
1342 bool "Support watchdog drivers"
1343 imply SPL_WDT if !HW_WATCHDOG
1345 Enable support for watchdog drivers in SPL. A watchdog is
1346 typically a hardware peripheral which can reset the system when it
1347 detects no activity for a while (such as a software crash). This
1348 enables the drivers in drivers/watchdog as part of an SPL build.
1350 config SPL_YMODEM_SUPPORT
1351 bool "Support loading using Ymodem"
1352 depends on SPL_SERIAL
1354 While loading from serial is slow it can be a useful backup when
1355 there is no other option. The Ymodem protocol provides a reliable
1356 means of transmitting U-Boot over a serial line for using in SPL,
1357 with a checksum to ensure correctness.
1360 bool "Support ARM Trusted Firmware"
1361 depends on ARM64 && SPL_FIT
1363 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1364 is loaded by SPL (which is considered as BL2 in ATF terminology).
1365 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1367 config SPL_ATF_LOAD_IMAGE_V2
1368 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1371 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1373 If you want to load a bl31 image from the SPL and need the new
1376 config SPL_ATF_NO_PLATFORM_PARAM
1377 bool "Pass no platform parameter"
1380 While we expect to call a pointer to a valid FDT (or NULL)
1381 as the platform parameter to an ATF, some ATF versions are
1382 not U-Boot aware and have an insufficiently robust parameter
1383 validation to gracefully reject a FDT being passed.
1385 If this option is enabled, the spl_atf os-type handler will
1386 always pass NULL for the platform parameter.
1388 If your ATF is affected, say Y.
1390 config SPL_AM33XX_ENABLE_RTC32K_OSC
1391 bool "Enable the RTC32K OSC on AM33xx based platforms"
1394 Enable access to the AM33xx RTC and select the external 32kHz clock
1397 config SPL_OPTEE_IMAGE
1398 bool "Support OP-TEE Trusted OS image in SPL"
1401 OP-TEE is an open source Trusted OS which is loaded by SPL.
1402 More detail at: https://github.com/OP-TEE/optee_os
1405 bool "Support RISC-V OpenSBI"
1406 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1408 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1409 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1410 firmware. It is loaded and started by U-Boot SPL.
1412 More details are available at https://github.com/riscv/opensbi and
1413 https://github.com/riscv/riscv-sbi-doc
1415 config SPL_OPENSBI_LOAD_ADDR
1416 hex "OpenSBI load address"
1417 depends on SPL_OPENSBI
1419 Load address of the OpenSBI binary.
1423 depends on SUPPORT_TPL
1426 If you want to build TPL as well as the normal image and SPL, say Y.
1430 config TPL_SIZE_LIMIT
1431 hex "Maximum size of TPL image"
1435 Specifies the maximum length of the U-Boot TPL image.
1436 If this value is zero, it is ignored.
1438 config TPL_BINMAN_SYMBOLS
1439 bool "Declare binman symbols in TPL"
1440 depends on SPL_FRAMEWORK && BINMAN
1443 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1444 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1445 and spl_get_image_size().
1447 For this to work, you must have a U-Boot image in the binman image, so
1448 binman can update TPL with the location of it.
1450 config TPL_FRAMEWORK
1451 bool "Support TPL based upon the common SPL framework"
1452 default y if SPL_FRAMEWORK
1454 Enable the SPL framework under common/spl/ for TPL builds.
1455 This framework supports MMC, NAND and YMODEM and other methods
1456 loading of U-Boot's SPL stage. If unsure, say Y.
1459 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1460 depends on HANDOFF && TPL_BLOBLIST
1463 This option enables TPL to write handoff information. This can be
1464 used to pass information like the size of SDRAM from TPL to U-Boot
1465 proper. The information is also available to SPL if it is useful
1468 config TPL_BOARD_INIT
1469 bool "Call board-specific initialization in TPL"
1471 If this option is enabled, U-Boot will call the function
1472 spl_board_init() from board_init_r(). This function should be
1473 provided by the board.
1475 config TPL_BOOTCOUNT_LIMIT
1476 bool "Support bootcount in TPL"
1477 depends on TPL_ENV_SUPPORT
1479 If this option is enabled, the TPL will support bootcount.
1480 For example, it may be useful to choose the device to boot.
1483 string "Linker script for the TPL stage"
1485 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1486 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1488 The TPL stage will usually require a different linker-script
1489 (as it runs from a different memory region) than the regular
1490 U-Boot stage. Set this to the path of the linker-script to
1493 May be left empty to trigger the Makefile infrastructure to
1494 fall back to the linker-script used for the SPL stage.
1496 config TPL_NEEDS_SEPARATE_STACK
1497 bool "TPL needs a separate initial stack-pointer"
1500 Enable, if the TPL stage should not inherit its initial
1501 stack-pointer from the settings for the SPL stage.
1504 bool "Support power drivers"
1506 Enable support for power control in TPL. This includes support
1507 for PMICs (Power-management Integrated Circuits) and some of the
1508 features provided by PMICs. In particular, voltage regulators can
1509 be used to enable/disable power and vary its voltage. That can be
1510 useful in TPL to turn on boot peripherals and adjust CPU voltage
1511 so that the clock speed can be increased. This enables the drivers
1512 in drivers/power, drivers/power/pmic and drivers/power/regulator
1513 as part of an TPL build.
1515 config TPL_TEXT_BASE
1516 hex "Base address for the .text section of the TPL stage"
1519 The base address for the .text section of the TPL stage.
1522 hex "Maximum size (in bytes) for the TPL stage"
1523 default 0x2e000 if ROCKCHIP_RK3399
1524 default 0x8000 if ROCKCHIP_RK3288
1525 default 0x7000 if ROCKCHIP_RK322X || ROCKCHIP_RK3328 || ROCKCHIP_RK3368
1526 default 0x2800 if ROCKCHIP_PX30
1529 The maximum size (in bytes) of the TPL stage.
1532 hex "Offset to which the TPL should be padded before appending the TPL payload"
1533 depends on !TPL_FRAMEWORK && PPC
1534 default TPL_MAX_SIZE
1536 Image offset to which the TPL should be padded before appending the
1537 TPL payload. By default, this is defined as CONFIG_TPL_MAX_SIZE, or 0 if
1538 CONFIG_TPL_MAX_SIZE is undefined. CONFIG_TPL_PAD_TO must be either
1539 0, meaning to append the TPL payload without any padding, or >=
1540 CONFIG_TPL_MAX_SIZE.
1543 hex "Address of the initial stack-pointer for the TPL stage"
1544 depends on TPL_NEEDS_SEPARATE_STACK
1546 The address of the initial stack-pointer for the TPL stage.
1547 Usually this will be the (aligned) top-of-stack.
1549 config TPL_READ_ONLY
1551 depends on TPL_OF_PLATDATA
1552 select TPL_OF_PLATDATA_NO_BIND
1553 select TPL_OF_PLATDATA_RT
1555 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1556 section of memory. This means that of-platdata must make a copy (in
1557 writeable memory) of anything it wants to modify, such as
1558 device-private data.
1560 config TPL_BOOTROM_SUPPORT
1561 bool "Support returning to the BOOTROM (from TPL)"
1563 Some platforms (e.g. the Rockchip RK3368) provide support in their
1564 ROM for loading the next boot-stage after performing basic setup
1567 Enable this option, to return to the BOOTROM through the
1568 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1569 boot device list, if not implemented for a given board)
1572 bool "Support CRC32 in TPL"
1573 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1575 Enable this to support CRC32 in uImages or FIT images within SPL.
1576 This is a 32-bit checksum value that can be used to verify images.
1577 For FIT images, this is the least secure type of checksum, suitable
1578 for detected accidental image corruption. For secure applications you
1579 should consider SHA1 or SHA256.
1581 config TPL_DRIVERS_MISC
1582 bool "Support misc drivers in TPL"
1584 Enable miscellaneous drivers in TPL. These drivers perform various
1585 tasks that don't fall nicely into other categories, Enable this
1586 option to build the drivers in drivers/misc as part of an TPL
1587 build, for those that support building in TPL (not all drivers do).
1589 config TPL_ENV_SUPPORT
1590 bool "Support an environment"
1592 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1595 bool "Support GPIO in TPL"
1597 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1598 GPIOs allow U-Boot to read the state of an input line (high or
1599 low) and set the state of an output line. This can be used to
1600 drive LEDs, control power to various system parts and read user
1601 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1602 for example. Enable this option to build the drivers in
1603 drivers/gpio as part of an TPL build.
1608 Enable support for the I2C bus in TPL. See SPL_I2C for
1611 config TPL_LIBCOMMON_SUPPORT
1612 bool "Support common libraries"
1614 Enable support for common U-Boot libraries within TPL. See
1615 SPL_LIBCOMMON_SUPPORT for details.
1617 config TPL_LIBGENERIC_SUPPORT
1618 bool "Support generic libraries"
1620 Enable support for generic U-Boot libraries within TPL. See
1621 SPL_LIBGENERIC_SUPPORT for details.
1623 config TPL_MPC8XXX_INIT_DDR
1624 bool "Support MPC8XXX DDR init"
1626 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1627 SPL_MPC8XXX_INIT_DDR for details.
1633 Enable support for MMC within TPL. See SPL_MMC for details.
1635 config TPL_NAND_SUPPORT
1636 bool "Support NAND flash"
1638 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1641 bool "Support PCI drivers"
1643 Enable support for PCI in TPL. For platforms that need PCI to boot,
1644 or must perform some init using PCI in SPL, this provides the
1645 necessary driver support. This enables the drivers in drivers/pci
1646 as part of a TPL build.
1649 bool "Support PCH drivers"
1651 Enable support for PCH (Platform Controller Hub) devices in TPL.
1652 These are used to set up GPIOs and the SPI peripheral early in
1653 boot. This enables the drivers in drivers/pch as part of a TPL
1656 config TPL_RAM_SUPPORT
1657 bool "Support booting from RAM"
1659 Enable booting of an image in RAM. The image can be preloaded or
1660 it can be loaded by TPL directly into RAM (e.g. using USB).
1662 config TPL_RAM_DEVICE
1663 bool "Support booting from preloaded image in RAM"
1664 depends on TPL_RAM_SUPPORT
1666 Enable booting of an image already loaded in RAM. The image has to
1667 be already in memory when TPL takes over, e.g. loaded by the boot
1671 bool "Support RTC drivers"
1673 Enable RTC (Real-time Clock) support in TPL. This includes support
1674 for reading and setting the time. Some RTC devices also have some
1675 non-volatile (battery-backed) memory which is accessible if
1676 needed. This enables the drivers in drivers/rtc as part of an TPL
1680 bool "Support serial"
1684 Enable support for serial in TPL. See SPL_SERIAL for
1687 config TPL_SPI_FLASH_SUPPORT
1688 bool "Support SPI flash drivers"
1690 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1693 config TPL_SPI_FLASH_TINY
1694 bool "Enable low footprint TPL SPI Flash support"
1695 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1696 default y if SPI_FLASH
1698 Enable lightweight TPL SPI Flash support that supports just reading
1699 data/images from flash. No support to write/erase flash. Enable
1700 this if you have TPL size limitations and don't need full-fledged
1704 bool "Support loading from SPI flash"
1705 depends on TPL_SPI_FLASH_SUPPORT
1707 Enable support for loading next stage, U-Boot or otherwise, from
1708 SPI NOR in U-Boot TPL.
1711 bool "Support SPI drivers"
1713 Enable support for using SPI in TPL. See SPL_SPI for
1717 bool "Support SPI DM drivers in TPL"
1719 Enable support for SPI DM drivers in TPL.
1721 config TPL_DM_SPI_FLASH
1722 bool "Support SPI DM FLASH drivers in TPL"
1724 Enable support for SPI DM flash drivers in TPL.
1726 config TPL_YMODEM_SUPPORT
1727 bool "Support loading using Ymodem"
1728 depends on TPL_SERIAL
1730 While loading from serial is slow it can be a useful backup when
1731 there is no other option. The Ymodem protocol provides a reliable
1732 means of transmitting U-Boot over a serial line for using in TPL,
1733 with a checksum to ensure correctness.
1739 depends on SUPPORT_SPL
1742 If you want to build VPL as well as the normal image, TPL and SPL,
1747 config VPL_BANNER_PRINT
1748 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1752 If this option is enabled, VPL will print the banner with version
1753 info. Disabling this option could be useful to reduce VPL boot time
1754 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1756 config VPL_BOARD_INIT
1757 bool "Call board-specific initialization in VPL"
1759 If this option is enabled, U-Boot will call the function
1760 spl_board_init() from board_init_r(). This function should be
1761 provided by the board.
1765 bool "Support cache drivers in VPL"
1767 Enable support for cache drivers in VPL.
1770 bool "Support CRC32 in VPL"
1771 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1773 Enable this to support CRC32 in uImages or FIT images within VPL.
1774 This is a 32-bit checksum value that can be used to verify images.
1775 For FIT images, this is the least secure type of checksum, suitable
1776 for detected accidental image corruption. For secure applications you
1777 should consider SHA1 or SHA256.
1780 bool "Support SPI DM drivers in VPL"
1782 Enable support for SPI DM drivers in VPL.
1784 config VPL_DM_SPI_FLASH
1785 bool "Support SPI DM FLASH drivers in VPL"
1787 Enable support for SPI DM flash drivers in VPL.
1789 config VPL_FRAMEWORK
1790 bool "Support VPL based upon the common SPL framework"
1793 Enable the SPL framework under common/spl/ for VPL builds.
1794 This framework supports MMC, NAND and YMODEM and other methods
1795 loading of U-Boot's next stage. If unsure, say Y.
1798 bool "Pass hand-off information from VPL to SPL"
1799 depends on HANDOFF && VPL_BLOBLIST
1802 This option enables VPL to write handoff information. This can be
1803 used to pass information like the size of SDRAM from VPL to SPL. Also
1804 VPL can receive information from TPL in the same place if that is
1807 config VPL_LIBCOMMON_SUPPORT
1808 bool "Support common libraries"
1809 default y if SPL_LIBCOMMON_SUPPORT
1811 Enable support for common U-Boot libraries within VPL. See
1812 SPL_LIBCOMMON_SUPPORT for details.
1814 config VPL_LIBGENERIC_SUPPORT
1815 bool "Support generic libraries"
1816 default y if SPL_LIBGENERIC_SUPPORT
1818 Enable support for generic U-Boot libraries within VPL. These
1819 libraries include generic code to deal with device tree, hashing,
1820 printf(), compression and the like. This option is enabled on many
1821 boards. Enable this option to build the code in lib/ as part of a
1824 config VPL_DRIVERS_MISC
1825 bool "Support misc drivers"
1826 default y if TPL_DRIVERS_MISC
1828 Enable miscellaneous drivers in VPL. These drivers perform various
1829 tasks that don't fall nicely into other categories, Enable this
1830 option to build the drivers in drivers/misc as part of a VPL
1831 build, for those that support building in VPL (not all drivers do).
1833 config VPL_ENV_SUPPORT
1834 bool "Support an environment"
1836 Enable environment support in VPL. The U-Boot environment provides
1837 a number of settings (essentially name/value pairs) which can
1838 control many aspects of U-Boot's operation. Enabling this option will
1839 make env_get() and env_set() available in VSPL.
1842 bool "Support GPIO in VPL"
1843 default y if SPL_GPIO
1845 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1846 GPIOs allow U-Boot to read the state of an input line (high or
1847 low) and set the state of an output line. This can be used to
1848 drive LEDs, control power to various system parts and read user
1849 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1850 for example. Enable this option to build the drivers in
1851 drivers/gpio as part of a VPL build.
1854 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1855 depends on HANDOFF && VPL_BLOBLIST
1858 This option enables VPL to write handoff information. This can be
1859 used to pass information like the size of SDRAM from VPL to U-Boot
1860 proper. The information is also available to VPL if it is useful
1864 bool "Support hashing drivers in VPL"
1869 Enable hashing drivers in VPL. These drivers can be used to
1870 accelerate secure boot processing in secure applications. Enable
1871 this option to build system-specific drivers for hash acceleration
1872 as part of a VPL build.
1874 config VPL_I2C_SUPPORT
1875 bool "Support I2C in VPL"
1876 default y if SPL_I2C_SUPPORT
1878 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1881 config VPL_PCH_SUPPORT
1882 bool "Support PCH drivers"
1883 default y if TPL_PCH_SUPPORT
1885 Enable support for PCH (Platform Controller Hub) devices in VPL.
1886 These are used to set up GPIOs and the SPI peripheral early in
1887 boot. This enables the drivers in drivers/pch as part of a VPL
1891 bool "Support PCI drivers"
1892 default y if SPL_PCI
1894 Enable support for PCI in VPL. For platforms that need PCI to boot,
1895 or must perform some init using PCI in VPL, this provides the
1896 necessary driver support. This enables the drivers in drivers/pci
1897 as part of a VPL build.
1900 bool "Support RTC drivers"
1902 Enable RTC (Real-time Clock) support in VPL. This includes support
1903 for reading and setting the time. Some RTC devices also have some
1904 non-volatile (battery-backed) memory which is accessible if
1905 needed. This enables the drivers in drivers/rtc as part of a VPL
1909 bool "Support serial"
1910 default y if TPL_SERIAL
1914 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1917 config VPL_SIZE_LIMIT
1918 hex "Maximum size of VPL image"
1922 Specifies the maximum length of the U-Boot VPL image.
1923 If this value is zero, it is ignored.
1926 bool "Support SPI drivers"
1928 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
1931 config VPL_SPI_FLASH_SUPPORT
1932 bool "Support SPI flash drivers"
1934 Enable support for using SPI flash in VPL, and loading U-Boot from
1935 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1936 the SPI bus that is used to connect it to a system. It is a simple
1937 but fast bidirectional 4-wire bus (clock, chip select and two data
1938 lines). This enables the drivers in drivers/mtd/spi as part of a
1939 VPL build. This normally requires VPL_SPI_SUPPORT.
1941 config VPL_TEXT_BASE
1945 The address in memory that VPL will be running from.
1949 config SPL_AT91_MCK_BYPASS
1950 bool "Use external clock signal as a source of main clock for AT91 platforms"
1951 depends on ARCH_AT91
1953 Use external 8 to 24 Mhz clock signal as source of main clock instead
1954 of an external crystal oscillator.
1955 This option disables the internal driving on the XOUT pin.
1956 The external source has to provide a stable clock on the XIN pin.
1957 If this option is disabled, the SoC expects a crystal oscillator
1958 that needs driving on both XIN and XOUT lines.