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_HAS_BSS_LINKER_SECTION
109 depends on SPL_FRAMEWORK
110 bool "Use a specific address for the BSS via the linker script"
111 default y if ARCH_SUNXI || ARCH_MX6 || ARCH_OMAP2PLUS || MIPS || RISCV
113 config SPL_BSS_START_ADDR
114 hex "Link address for the BSS within the SPL binary"
115 depends on SPL_HAS_BSS_LINKER_SECTION
116 default 0x88200000 if (ARCH_MX6 && (MX6SX || MX6SL || MX6UL || MX6ULL)) || ARCH_MX7
117 default 0x18200000 if ARCH_MX6 && !(MX6SX || MX6SL || MX6UL || MX6ULL)
118 default 0x80a00000 if ARCH_OMAP2PLUS
119 default 0x81f80000 if ARCH_SUNXI && MACH_SUNIV
120 default 0x4ff80000 if ARCH_SUNXI && !(MACH_SUN9I || MACH_SUNIV)
121 default 0x2ff80000 if ARCH_SUNXI && MACH_SUN9I
124 prompt "Enforce SPL BSS limit"
125 depends on SPL && !PPC
126 default SPL_BSS_LIMIT
128 In some platforms we only want to enforce a limit on the size of the
129 BSS in memory. On other platforms we need to enforce a limit on the
130 whole of the memory allocation as we're strictly limited to a small
131 typically non-DRAM location. Finally, other platforms do not enforce
132 a memory limit within SPL.
134 config SPL_NO_BSS_LIMIT
135 bool "Do not enforce a build time limit on the size of the BSS"
138 bool "Enforce a limit on the size of the BSS only"
140 config SPL_FOOTPRINT_LIMIT
141 bool "Enforce a limit on the whole of memory allocated to SPL, BSS included"
145 config SPL_BSS_MAX_SIZE
146 hex "Maximum size in memory allocated to the SPL BSS"
147 depends on SPL_BSS_LIMIT
148 default 0x100000 if ARCH_MX6 || RISCV
149 default 0x80000 if ARCH_OMAP2PLUS || ARCH_SUNXI
151 When non-zero, the linker checks that the actual memory used by SPL
152 from __bss_start to __bss_end does not exceed it.
154 config SPL_MAX_FOOTPRINT
155 hex "Maximum size in memory allocated to the SPL, BSS included"
156 depends on SPL_FOOTPRINT_LIMIT
158 When non-zero, the linker checks that the actual memory used by SPL
159 from _start to __bss_end does not exceed it.
161 config SPL_SYS_STACK_F_CHECK_BYTE
165 Constant used to check the stack
167 config SPL_SYS_REPORT_STACK_F_USAGE
168 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
169 bool "Check and report stack usage in SPL before relocation"
171 If this option is enabled, the initial SPL stack is filled with 0xaa
172 very early, up to the size configured with
173 SPL_SIZE_LIMIT_PROVIDE_STACK.
174 Later when SPL is done using this initial stack and switches to a
175 stack in DRAM, the actually used size of this initial stack is
176 reported by examining the memory and searching for the lowest
177 occurrence of non 0xaa bytes.
178 This default implementation works for stacks growing down only.
180 config SPL_SHOW_ERRORS
181 bool "Show more information when something goes wrong"
183 This enabled more verbose error messages and checking when something
184 goes wrong in SPL. For example, it shows the error code when U-Boot
185 cannot be located. This can help to diagnose the problem and figure
186 out a fix, particularly during development.
188 This adds a small amount to SPL code size, perhaps 100 bytes.
190 config SPL_BINMAN_SYMBOLS
191 bool "Declare binman symbols in SPL"
192 depends on SPL_FRAMEWORK && BINMAN
195 This enables use of symbols in SPL which refer to U-Boot, enabling SPL
196 to obtain the location of U-Boot simply by calling spl_get_image_pos()
197 and spl_get_image_size().
199 For this to work, you must have a U-Boot image in the binman image, so
200 binman can update SPL with the location of it.
202 menu "PowerPC and LayerScape SPL Boot options"
205 bool "Load SPL from NAND flash"
206 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
209 bool "Load SPL from SD Card / eMMC"
210 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
213 bool "Load SPL from SPI flash"
214 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
217 bool "Create SPL in Freescale PBI format"
218 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
221 Create boot binary having SPL binary in PBI format concatenated with
224 config SPL_SYS_CCSR_DO_NOT_RELOCATE
225 bool "Ensures that CCSR is not relocated"
228 If this is defined, then CONFIG_SYS_CCSRBAR_PHYS will be forced to a
229 value that ensures that CCSR is not relocated.
231 config TPL_SYS_CCSR_DO_NOT_RELOCATE
233 depends on SPL_SYS_CCSR_DO_NOT_RELOCATE
237 menu "PowerPC SPL / TPL specific options"
238 depends on PPC && (SPL && !SPL_FRAMEWORK)
240 config SPL_INIT_MINIMAL
241 bool "Arch init code will be built for a very small image"
243 config SPL_FLUSH_IMAGE
244 bool "Clean dcache and invalidate icache after loading the image"
246 config SPL_SKIP_RELOCATE
247 bool "Skip relocating SPL"
249 config SPL_RELOC_TEXT_BASE
250 hex "Address to relocate SPL to"
251 default SPL_TEXT_BASE
253 If unspecified, this is equal to CONFIG_SPL_TEXT_BASE (i.e. no
256 config SPL_RELOC_STACK
257 hex "Address of the start of the stack SPL will use after relocation."
259 If unspecified, this is equal to CONFIG_SYS_SPL_MALLOC_START. Starting
260 address of the malloc pool used in SPL. When this option is set the full
261 malloc is used in SPL and it is set up by spl_init() and before that, the
262 simple malloc() can be used if CONFIG_SYS_MALLOC_F is defined.
264 config SPL_RELOC_MALLOC
265 bool "SPL has malloc pool after relocation"
267 config SPL_RELOC_MALLOC_ADDR
268 hex "Address of malloc pool in SPL"
269 depends on SPL_RELOC_MALLOC
271 config SPL_RELOC_MALLOC_SIZE
272 hex "Size of malloc pool in SPL"
273 depends on SPL_RELOC_MALLOC
275 config TPL_RELOC_TEXT_BASE
276 hex "Address to relocate TPL to"
278 default TPL_TEXT_BASE
280 If unspecified, this is equal to CONFIG_TPL_TEXT_BASE (i.e. no
283 config TPL_RELOC_STACK
284 hex "Address of the start of the stack TPL will use after relocation."
287 If unspecified, this is equal to CONFIG_SYS_TPL_MALLOC_START. Starting
288 address of the malloc pool used in TPL. When this option is set the full
289 malloc is used in TPL and it is set up by spl_init() and before that, the
290 simple malloc() can be used if CONFIG_SYS_MALLOC_F is defined.
292 config TPL_RELOC_MALLOC
293 bool "TPL has malloc pool after relocation"
296 config TPL_RELOC_MALLOC_ADDR
297 hex "Address of malloc pool in TPL"
298 depends on TPL_RELOC_MALLOC
300 config TPL_RELOC_MALLOC_SIZE
301 hex "Size of malloc pool in TPL"
302 depends on TPL_RELOC_MALLOC
307 bool "Pass hand-off information from SPL to U-Boot proper"
308 depends on SPL && BLOBLIST
310 It is useful to be able to pass information from SPL to U-Boot
311 proper to preserve state that is known in SPL and is needed in U-Boot.
312 Enable this to locate the handoff information in U-Boot proper, early
313 in boot. It is available in gd->handoff. The state state is set up
314 in SPL (or TPL if that is being used).
319 bool "Pass hand-off information from SPL to U-Boot proper"
320 depends on HANDOFF && SPL_BLOBLIST
323 This option enables SPL to write handoff information. This can be
324 used to pass information like the size of SDRAM from SPL to U-Boot
325 proper. Also SPL can receive information from TPL in the same place
329 string "Linker script for the SPL stage"
330 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
332 The SPL stage will usually require a different linker-script
333 (as it runs from a different memory region) than the regular
334 U-Boot stage. Set this to the path of the linker-script to
339 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
340 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
341 default 0x20060 if SUN50I_GEN_H6
342 default 0x00060 if ARCH_SUNXI
343 default 0xfffc0000 if ARCH_ZYNQMP
346 The address in memory that SPL will be running from.
348 config SPL_BOARD_INIT
349 bool "Call board-specific initialization in SPL"
351 If this option is enabled, U-Boot will call the function
352 spl_board_init() from board_init_r(). This function should be
353 provided by the board.
355 config VPL_BOARD_INIT
356 bool "Call board-specific initialization in VPL"
358 If this option is enabled, U-Boot will call the function
359 spl_board_init() from board_init_r(). This function should be
360 provided by the board.
362 config SPL_BOOTROM_SUPPORT
363 bool "Support returning to the BOOTROM"
365 Some platforms (e.g. the Rockchip RK3368) provide support in their
366 ROM for loading the next boot-stage after performing basic setup
369 Enable this option, to return to the BOOTROM through the
370 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
371 boot device list, if not implemented for a given board)
373 config SPL_BOOTCOUNT_LIMIT
374 bool "Support bootcount in SPL"
375 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
377 On some boards, which use 'falcon' mode, it is necessary to check
378 and increment the number of boot attempts. Such boards do not
379 use proper U-Boot for normal boot flow and hence needs those
380 adjustments to be done in the SPL.
382 config SPL_RAW_IMAGE_SUPPORT
383 bool "Support SPL loading and booting of RAW images"
384 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
386 depends on !TI_SECURE_DEVICE
388 SPL will support loading and booting a RAW image when this option
389 is y. If this is not set, SPL will move on to other available
390 boot media to find a suitable image.
392 config SPL_LEGACY_IMAGE_FORMAT
393 bool "Support SPL loading and booting of Legacy images"
394 default y if !SPL_LOAD_FIT
395 depends on !TI_SECURE_DEVICE
397 SPL will support loading and booting Legacy images when this option
398 is y. If this is not set, SPL will move on to other available
399 boot media to find a suitable image.
401 config SPL_LEGACY_IMAGE_CRC_CHECK
402 bool "Check CRC of Legacy images"
403 depends on SPL_LEGACY_IMAGE_FORMAT
406 Enable this to check the CRC of Legacy images. While this increases
407 reliability, it affects both code size and boot duration.
408 If disabled, Legacy images are booted if the image magic and size
409 are correct, without further integrity checks.
411 config SPL_SYS_MALLOC_SIMPLE
413 prompt "Only use malloc_simple functions in the SPL"
415 Say Y here to only use the *_simple malloc functions from
416 malloc_simple.c, rather then using the versions from dlmalloc.c;
417 this will make the SPL binary smaller at the cost of more heap
418 usage as the *_simple malloc functions do not re-use free-ed mem.
420 config TPL_SYS_MALLOC_SIMPLE
422 prompt "Only use malloc_simple functions in the TPL"
425 Say Y here to only use the *_simple malloc functions from
426 malloc_simple.c, rather then using the versions from dlmalloc.c;
427 this will make the TPL binary smaller at the cost of more heap
428 usage as the *_simple malloc functions do not re-use free-ed mem.
430 config SPL_SHARES_INIT_SP_ADDR
431 bool "SPL and U-Boot use the same initial stack pointer location"
432 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
433 default n if ARCH_SUNXI || ARCH_MX6 || ARCH_MX7
436 In many cases, we can use the same initial stack pointer address for
437 both SPL and U-Boot itself. If you need to specify a different address
438 however, say N here and then set a different value in CONFIG_SPL_STACK.
441 hex "Initial stack pointer location"
442 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
443 depends on !SPL_SHARES_INIT_SP_ADDR
444 default 0x946bb8 if ARCH_MX7
445 default 0x93ffb8 if ARCH_MX6 && MX6_OCRAM_256KB
446 default 0x91ffb8 if ARCH_MX6 && !MX6_OCRAM_256KB
448 Address of the start of the stack SPL will use before SDRAM is
452 bool "Enable SDRAM location for SPL stack"
454 SPL starts off execution in SRAM and thus typically has only a small
455 stack available. Since SPL sets up DRAM while in its board_init_f()
456 function, it is possible for the stack to move there before
457 board_init_r() is reached. This option enables a special SDRAM
458 location for the SPL stack. U-Boot SPL switches to this after
459 board_init_f() completes, and before board_init_r() starts.
461 config SPL_STACK_R_ADDR
462 depends on SPL_STACK_R
463 hex "SDRAM location for SPL stack"
464 default 0x82000000 if ARCH_OMAP2PLUS
466 Specify the address in SDRAM for the SPL stack. This will be set up
467 before board_init_r() is called.
469 config SPL_STACK_R_MALLOC_SIMPLE_LEN
470 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
471 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
474 Specify the amount of the stack to use as memory pool for
475 malloc_simple after switching the stack to DRAM. This may be set
476 to give board_init_r() a larger heap then the initial heap in
477 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
479 config SPL_SEPARATE_BSS
480 bool "BSS section is in a different memory region from text"
482 Some platforms need a large BSS region in SPL and can provide this
483 because RAM is already set up. In this case BSS can be moved to RAM.
484 This option should then be enabled so that the correct device tree
485 location is used. Normally we put the device tree at the end of BSS
486 but with this option enabled, it goes at _image_binary_end.
488 config SYS_SPL_MALLOC
489 bool "Enable malloc pool in SPL"
490 depends on SPL_FRAMEWORK
492 config HAS_CUSTOM_SPL_MALLOC_START
493 bool "For the SPL malloc pool, define a custom starting address"
494 depends on SYS_SPL_MALLOC
496 config CUSTOM_SYS_SPL_MALLOC_ADDR
497 hex "SPL malloc addr"
498 depends on HAS_CUSTOM_SPL_MALLOC_START
500 config SYS_SPL_MALLOC_SIZE
501 hex "Size of the SPL malloc pool"
502 depends on SYS_SPL_MALLOC
507 depends on SPL_OF_PLATDATA
508 # Bind cannot be supported because the udevice structs are in read-only
509 # memory so we cannot update the linked lists.
510 select SPL_OF_PLATDATA_NO_BIND
511 select SPL_OF_PLATDATA_RT
513 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
514 section of memory. This means that of-platdata must make a copy (in
515 writeable memory) of anything it wants to modify, such as
518 config TPL_SEPARATE_BSS
519 bool "BSS section is in a different memory region from text"
520 default y if SPL_SEPARATE_BSS
522 Some platforms need a large BSS region in TPL and can provide this
523 because RAM is already set up. In this case BSS can be moved to RAM.
524 This option should then be enabled so that the correct device tree
525 location is used. Normally we put the device tree at the end of BSS
526 but with this option enabled, it goes at _image_binary_end.
528 config SPL_BANNER_PRINT
529 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
532 If this option is enabled, SPL will print the banner with version
533 info. Disabling this option could be useful to reduce SPL boot time
534 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
536 config TPL_BANNER_PRINT
537 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
541 If this option is enabled, TPL will print the banner with version
542 info. Disabling this option could be useful to reduce TPL boot time
543 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
546 depends on ARM && !ARM64
547 bool "Allows initializing BSS early before entering board_init_f"
549 On some platform we have sufficient memory available early on to
550 allow setting up and using a basic BSS prior to entering
551 board_init_f. Activating this option will also de-activate the
552 clearing of BSS during the SPL relocation process, thus allowing
553 to carry state from board_init_f to board_init_r by way of BSS.
555 config SPL_DISPLAY_PRINT
556 bool "Display a board-specific message in SPL"
558 If this option is enabled, U-Boot will call the function
559 spl_display_print() immediately after displaying the SPL console
560 banner ("U-Boot SPL ..."). This function should be provided by
563 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
564 bool "MMC raw mode: by sector"
565 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
566 ARCH_MX6 || ARCH_MX7 || \
567 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
568 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
569 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
570 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
572 Use sector number for specifying U-Boot location on MMC/SD in
575 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
576 hex "Address on the MMC to load U-Boot from"
577 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
578 default 0x40 if ARCH_SUNXI
579 default 0x75 if ARCH_DAVINCI
580 default 0x8a if ARCH_MX6 || ARCH_MX7
581 default 0x100 if ARCH_UNIPHIER
582 default 0x0 if ARCH_MVEBU
583 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
584 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
585 OMAP54XX || AM33XX || AM43XX || ARCH_K3
586 default 0x4000 if ARCH_ROCKCHIP
587 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
589 Address on the MMC to load U-Boot from, when the MMC is being used
590 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
592 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
593 hex "U-Boot main hardware partition image offset"
594 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
595 default 0x10 if ARCH_SUNXI
598 On some platforms SPL location depends on hardware partition. The ROM
599 code skips the MBR sector when loading SPL from main hardware data
600 partition. This adds offset to the main U-Boot image. Set this symbol
601 to the number of skipped sectors.
603 If unsure, leave the default.
605 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
606 bool "MMC Raw mode: by partition"
608 Use a partition for loading U-Boot when using MMC/SD in raw mode.
610 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
611 hex "Partition to use to load U-Boot from"
612 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
615 Partition on the MMC to load U-Boot from when the MMC is being
618 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
619 bool "MMC raw mode: by partition type"
620 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
622 Use partition type for specifying U-Boot partition on MMC/SD in
623 raw mode. U-Boot will be loaded from the first partition of this
626 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
627 hex "Partition Type on the MMC to load U-Boot from"
628 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
630 Partition Type on the MMC to load U-Boot from, when the MMC is being
633 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
634 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
635 depends on SUPPORT_EMMC_BOOT
637 eMMC boot partition is normally configured by the bits of the EXT_CSD
638 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
639 cases it might be required in SPL to load the image from different
640 partition than the partition selected by EXT_CSC_PART_CONFIG register.
641 Enable this option if you intend to use an eMMC boot partition other
642 then selected via EXT_CSC_PART_CONFIG register and specify the custom
643 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
646 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
647 int "Number of the eMMC boot partition to use"
648 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
651 eMMC boot partition number to use when the eMMC in raw mode and
652 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
653 by user defined partition number.
657 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
658 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
660 Enable this to support CRC32 in uImages or FIT images within SPL.
661 This is a 32-bit checksum value that can be used to verify images.
662 For FIT images, this is the least secure type of checksum, suitable
663 for detected accidental image corruption. For secure applications you
664 should consider SHA1 or SHA256.
670 Enable this to support MD5 in FIT images within SPL. An MD5
671 checksum is a 128-bit hash value used to check that the image
672 contents have not been corrupted. Note that MD5 is not considered
673 secure as it is possible (with a brute-force attack) to adjust the
674 image while still retaining the same MD5 hash value. For secure
675 applications where images may be changed maliciously, you should
676 consider SHA256 or SHA384.
678 config SPL_FIT_IMAGE_TINY
679 bool "Remove functionality from SPL FIT loading to reduce size"
681 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
682 default y if ARCH_IMX8M
684 Enable this to reduce the size of the FIT image loading code
685 in SPL, if space for the SPL binary is very tight.
687 This skips the recording of each loaded payload
688 (i.e. loadable) into the FDT (modifying the loaded FDT to
689 ensure this information is available to the next image
693 bool "Support CACHE drivers"
695 Enable CACHE drivers in SPL. These drivers can keep data so that
696 future requests for that data can be served faster. Enable this option
697 to build the drivers in drivers/cache as part of an SPL build.
700 bool "Support CPU drivers"
702 Enable this to support CPU drivers in SPL. These drivers can set
703 up CPUs and provide information about them such as the model and
704 name. This can be useful in SPL since setting up the CPUs earlier
705 may improve boot performance. Enable this option to build the
706 drivers in drivers/cpu as part of an SPL build.
709 bool "Support crypto drivers"
711 Enable crypto drivers in SPL. These drivers can be used to
712 accelerate secure boot processing in secure applications. Enable
713 this option to build the drivers in drivers/crypto as part of an
717 bool "Support DMA drivers"
719 Enable DMA (direct-memory-access) drivers in SPL. These drivers
720 can be used to handle memory-to-peripheral data transfer without
721 the CPU moving the data. Enable this option to build the drivers
722 in drivers/dma as part of an SPL build.
724 config SPL_DRIVERS_MISC
725 bool "Support misc drivers"
727 Enable miscellaneous drivers in SPL. These drivers perform various
728 tasks that don't fall nicely into other categories, Enable this
729 option to build the drivers in drivers/misc as part of an SPL
730 build, for those that support building in SPL (not all drivers do).
732 config SPL_ENV_SUPPORT
733 bool "Support an environment"
735 Enable environment support in SPL. The U-Boot environment provides
736 a number of settings (essentially name/value pairs) which can
737 control many aspects of U-Boot's operation. Normally this is not
738 needed in SPL as it has a much simpler task with less
739 configuration. But some boards use this to support 'Falcon' boot
740 on EXT2 and FAT, where SPL boots directly into Linux without
741 starting U-Boot first. Enabling this option will make env_get()
742 and env_set() available in SPL.
745 bool "Support save environment"
746 depends on SPL_ENV_SUPPORT
747 select SPL_MMC_WRITE if ENV_IS_IN_MMC
749 Enable save environment support in SPL after setenv. By default
750 the saveenv option is not provided in SPL, but some boards need
751 this support in 'Falcon' boot, where SPL need to boot from
752 different images based on environment variable set by OS. For
753 example OS may set "reboot_image" environment variable to
754 "recovery" inorder to boot recovery image by SPL. The SPL read
755 "reboot_image" and act accordingly and change the reboot_image
756 to default mode using setenv and save the environment.
759 bool "Support Ethernet"
760 depends on SPL_ENV_SUPPORT
763 Enable access to the network subsystem and associated Ethernet
764 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
765 link rather than from an on-board peripheral. Environment support
766 is required since the network stack uses a number of environment
767 variables. See also SPL_NET.
770 bool "Support EXT filesystems"
772 Enable support for EXT2/3/4 filesystems with SPL. This permits
773 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
774 filesystem from within SPL. Support for the underlying block
775 device (e.g. MMC or USB) must be enabled separately.
777 config SPL_FS_SQUASHFS
778 bool "Support SquashFS filesystems"
781 Enable support for SquashFS filesystems with SPL. This permits
782 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
783 filesystem from within SPL. Support for the underlying block
784 device (e.g. MMC or USB) must be enabled separately.
787 bool "Support FAT filesystems"
790 Enable support for FAT and VFAT filesystems with SPL. This
791 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
792 filesystem from within SPL. Support for the underlying block
793 device (e.g. MMC or USB) must be enabled separately.
795 config SPL_FS_LOAD_PAYLOAD_NAME
796 string "File to load for U-Boot from the filesystem"
797 depends on SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS
798 default "tispl.bin" if SYS_K3_SPL_ATF
799 default "u-boot.itb" if SPL_LOAD_FIT
802 Filename to read to load U-Boot when reading from filesystem.
804 config SPL_FS_LOAD_KERNEL_NAME
805 string "File to load for the OS kernel from the filesystem"
806 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
809 Filename to read to load for the OS kernel when reading from the
812 config SPL_FS_LOAD_ARGS_NAME
813 string "File to load for the OS kernel argument parameters from the filesystem"
814 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
817 Filename to read to load for the OS kernel argument parameters from
821 bool "Support write for FAT filesystems"
823 Enable write support for FAT and VFAT filesystems with SPL.
824 Support for the underlying block device (e.g. MMC or USB) must be
830 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
831 provide software-configurable hardware which is typically used to
832 implement peripherals (such as UARTs, LCD displays, MMC) or
833 accelerate custom processing functions, such as image processing
834 or machine learning. Sometimes it is useful to program the FPGA
835 as early as possible during boot, and this option can enable that
839 bool "Support GPIO in SPL"
841 Enable support for GPIOs (General-purpose Input/Output) in SPL.
842 GPIOs allow U-Boot to read the state of an input line (high or
843 low) and set the state of an output line. This can be used to
844 drive LEDs, control power to various system parts and read user
845 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
846 for example. Enable this option to build the drivers in
847 drivers/gpio as part of an SPL build.
852 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
853 I2C works with a clock and data line which can be driven by a
854 one or more masters or slaves. It is a fairly complex bus but is
855 widely used as it only needs two lines for communication. Speeds of
856 400kbps are typical but up to 3.4Mbps is supported by some
857 hardware. I2C can be useful in SPL to configure power management
858 ICs (PMICs) before raising the CPU clock speed, for example.
859 Enable this option to build the drivers in drivers/i2c as part of
862 config SPL_LIBCOMMON_SUPPORT
863 bool "Support common libraries"
865 Enable support for common U-Boot libraries within SPL. These
866 libraries include common code to deal with U-Boot images,
867 environment and USB, for example. This option is enabled on many
868 boards. Enable this option to build the code in common/ as part of
871 config SPL_LIBDISK_SUPPORT
872 bool "Support disk partitions"
875 Enable support for disk partitions within SPL. 'Disk' is something
876 of a misnomer as it includes non-spinning media such as flash (as
877 used in MMC and USB sticks). Partitions provide a way for a disk
878 to be split up into separate regions, with a partition table placed
879 at the start or end which describes the location and size of each
880 'partition'. These partitions are typically uses as individual block
881 devices, typically with an EXT2 or FAT filesystem in each. This
882 option enables whatever partition support has been enabled in
883 U-Boot to also be used in SPL. It brings in the code in disk/.
885 config SPL_LIBGENERIC_SUPPORT
886 bool "Support generic libraries"
888 Enable support for generic U-Boot libraries within SPL. These
889 libraries include generic code to deal with device tree, hashing,
890 printf(), compression and the like. This option is enabled on many
891 boards. Enable this option to build the code in lib/ as part of an
894 config SPL_DM_MAILBOX
895 bool "Support Mailbox"
897 Enable support for Mailbox within SPL. This enable the inter
898 processor communication protocols tobe used within SPL. Enable
899 this option to build the drivers in drivers/mailbox as part of
905 select HAVE_BLOCK_DEVICE
907 Enable support for MMC (Multimedia Card) within SPL. This enables
908 the MMC protocol implementation and allows any enabled drivers to
909 be used within SPL. MMC can be used with or without disk partition
910 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
911 this option to build the drivers in drivers/mmc as part of an SPL
914 config SYS_MMCSD_FS_BOOT_PARTITION
915 int "MMC Boot Partition"
918 Partition on the MMC to load U-Boot from when the MMC is being
920 Use -1 as a special value to use the first bootable partition.
923 bool "Tiny MMC framework in SPL"
926 Enable MMC framework tinification support. This option is useful if
927 if your SPL is extremely size constrained. Heed the warning, enable
928 this option if and only if you know exactly what you are doing, if
929 you are reading this help text, you most likely have no idea :-)
931 The MMC framework is reduced to bare minimum to be useful. No malloc
932 support is needed for the MMC framework operation with this option
933 enabled. The framework supports exactly one MMC device and exactly
934 one MMC driver. The MMC driver can be adjusted to avoid any malloc
935 operations too, which can remove the need for malloc support in SPL
936 and thus further reduce footprint.
939 bool "MMC/SD/SDIO card support for write operations in SPL"
942 Enable write access to MMC and SD Cards in SPL
945 config SPL_MPC8XXX_INIT_DDR
946 bool "Support MPC8XXX DDR init"
948 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
949 random-access memory) on the MPC8XXX family within SPL. This
950 allows DRAM to be set up before loading U-Boot into that DRAM,
953 config SPL_MTD_SUPPORT
954 bool "Support MTD drivers"
956 Enable support for MTD (Memory Technology Device) within SPL. MTD
957 provides a block interface over raw NAND and can also be used with
958 SPI flash. This allows SPL to load U-Boot from supported MTD
959 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
960 to enable specific MTD drivers.
963 bool "Support new Mentor Graphics USB"
965 Enable support for Mentor Graphics USB in SPL. This is a new
966 driver used by some boards. Enable this option to build
967 the drivers in drivers/usb/musb-new as part of an SPL build. The
968 old drivers are in drivers/usb/musb.
970 config SPL_NAND_SUPPORT
971 bool "Support NAND flash"
973 Enable support for NAND (Negative AND) flash in SPL. NAND flash
974 can be used to allow SPL to load U-Boot from supported devices.
975 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
978 config SPL_NAND_RAW_ONLY
979 bool "Support to boot only raw u-boot.bin images"
980 depends on SPL_NAND_SUPPORT
982 Use this only if you need to save space.
984 config SPL_NAND_DRIVERS
985 bool "Use standard NAND driver"
987 SPL uses normal NAND drivers, not minimal drivers.
990 bool "Include standard ECC in SPL"
992 config SPL_NAND_SOFTECC
993 bool "Use software ECC in SPL"
994 depends on SPL_NAND_ECC
996 config SPL_NAND_SIMPLE
997 bool "Support simple NAND drivers in SPL"
999 Support for NAND boot using simple NAND drivers that
1000 expose the cmd_ctrl() interface.
1002 config SPL_NAND_BASE
1003 depends on SPL_NAND_DRIVERS
1004 bool "Use Base NAND Driver"
1006 Include nand_base.c in the SPL.
1008 config SPL_NAND_IDENT
1009 depends on SPL_NAND_BASE
1010 bool "Use chip ID to identify NAND flash"
1012 SPL uses the chip ID list to identify the NAND flash.
1017 Enable support for loading payloads from UBI. See
1018 README.ubispl for more info.
1022 bool "Support SPI DM drivers in SPL"
1024 Enable support for SPI DM drivers in SPL.
1026 config SPL_DM_SPI_FLASH
1027 bool "Support SPI DM FLASH drivers in SPL"
1029 Enable support for SPI DM flash drivers in SPL.
1033 config SPL_UBI_LOAD_BY_VOLNAME
1034 bool "Support loading volumes by name"
1036 This enables support for loading UBI volumes by name. When this
1037 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
1038 configure the volume name from which to load U-Boot.
1040 config SPL_UBI_MAX_VOL_LEBS
1041 int "Maximum number of LEBs per volume"
1044 The maximum number of logical eraseblocks which a static volume
1045 to load can contain. Used for sizing the scan data structure.
1047 config SPL_UBI_MAX_PEB_SIZE
1048 int "Maximum PEB size"
1051 The maximum physical erase block size.
1053 config SPL_UBI_MAX_PEBS
1054 int "Maximum number of PEBs"
1057 The maximum physical erase block size. If not overridden by
1058 board code, this value will be used as the actual number of PEBs.
1060 config SPL_UBI_PEB_OFFSET
1061 int "Offset to first UBI PEB"
1064 The offset in number of PEBs from the start of flash to the first
1065 PEB part of the UBI image.
1067 config SPL_UBI_VID_OFFSET
1068 int "Offset to VID header"
1071 config SPL_UBI_LEB_START
1072 int "Offset to LEB in PEB"
1075 The offset in bytes to the LEB within a PEB.
1077 config SPL_UBI_INFO_ADDR
1078 hex "Address to place UBI scan info"
1081 Address for ubispl to place the scan info. Read README.ubispl to
1082 determine the required size
1084 config SPL_UBI_VOL_IDS
1085 int "Maximum volume id"
1088 The maximum volume id which can be loaded. Used for sizing the
1089 scan data structure.
1091 config SPL_UBI_LOAD_MONITOR_ID
1092 int "id of U-Boot volume"
1095 The UBI volume id from which to load U-Boot
1097 config SPL_UBI_LOAD_MONITOR_VOLNAME
1098 string "volume name of U-Boot volume"
1099 depends on SPL_UBI_LOAD_BY_VOLNAME
1101 The UBI volume name from which to load U-Boot
1103 config SPL_UBI_LOAD_KERNEL_ID
1104 int "id of kernel volume"
1105 depends on SPL_OS_BOOT && SPL_UBI
1107 The UBI volume id from which to load the kernel
1109 config SPL_UBI_LOAD_ARGS_ID
1110 int "id of kernel args volume"
1111 depends on SPL_OS_BOOT && SPL_UBI
1113 The UBI volume id from which to load the device tree
1115 config UBI_SPL_SILENCE_MSG
1116 bool "silence UBI SPL messages"
1118 Disable messages from UBI SPL. This leaves warnings
1124 bool "Support networking"
1126 Enable support for network devices (such as Ethernet) in SPL.
1127 This permits SPL to load U-Boot over a network link rather than
1128 from an on-board peripheral. Environment support is required since
1129 the network stack uses a number of environment variables. See also
1133 config SPL_NET_VCI_STRING
1134 string "BOOTP Vendor Class Identifier string sent by SPL"
1136 As defined by RFC 2132 the vendor class identifier field can be
1137 sent by the client to identify the vendor type and configuration
1138 of a client. This is often used in practice to allow for the DHCP
1139 server to specify different files to load depending on if the ROM,
1140 SPL or U-Boot itself makes the request
1143 config SPL_NO_CPU_SUPPORT
1144 bool "Drop CPU code in SPL"
1146 This is specific to the ARM926EJ-S CPU. It disables the standard
1147 start.S start-up code, presumably so that a replacement can be
1148 used on that CPU. You should not enable it unless you know what
1151 config SPL_NOR_SUPPORT
1152 bool "Support NOR flash"
1154 Enable support for loading U-Boot from memory-mapped NOR (Negative
1155 OR) flash in SPL. NOR flash is slow to write but fast to read, and
1156 a memory-mapped device makes it very easy to access. Loading from
1157 NOR is typically achieved with just a memcpy().
1159 config SPL_XIP_SUPPORT
1163 Enable support for execute in place of U-Boot or kernel image. There
1164 is no need to copy image from flash to ram if flash supports execute
1165 in place. Its very useful in systems having enough flash but not
1166 enough ram to load the image.
1168 config SPL_ONENAND_SUPPORT
1169 bool "Support OneNAND flash"
1171 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
1172 a type of NAND flash and therefore can be used to allow SPL to
1173 load U-Boot from supported devices. This enables the drivers in
1174 drivers/mtd/onenand as part of an SPL build.
1177 bool "Activate Falcon Mode"
1178 depends on !TI_SECURE_DEVICE
1180 Enable booting directly to an OS from SPL.
1181 for more info read doc/README.falcon
1185 hex "addr, where OS is found"
1186 depends on SPL_NOR_SUPPORT
1188 Specify the address, where the OS image is found, which
1193 config SPL_FALCON_BOOT_MMCSD
1194 bool "Enable Falcon boot from MMC or SD media"
1195 depends on SPL_OS_BOOT && SPL_MMC
1197 Select this if the Falcon mode OS image mode is on MMC or SD media.
1199 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
1200 hex "Falcon mode: Sector to load kernel uImage from MMC"
1201 depends on SPL_FALCON_BOOT_MMCSD
1203 When Falcon mode is used with an MMC or SD media, SPL needs to know
1204 where to look for the kernel uImage. The image is expected to begin
1205 at the raw MMC specified in this config.
1206 Note that the Falcon mode image can also be a FIT, if FIT support is
1210 string "SPL payload"
1211 default "tpl/u-boot-with-tpl.bin" if TPL
1212 default "u-boot.bin"
1214 Payload for SPL boot. For backward compatibility, default to
1215 u-boot.bin, i.e. RAW image without any header. In case of
1216 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
1220 bool "Support PCI drivers"
1222 Enable support for PCI in SPL. For platforms that need PCI to boot,
1223 or must perform some init using PCI in SPL, this provides the
1224 necessary driver support. This enables the drivers in drivers/pci
1225 as part of an SPL build.
1228 bool "Support PCH drivers"
1230 Enable support for PCH (Platform Controller Hub) devices in SPL.
1231 These are used to set up GPIOs and the SPI peripheral early in
1232 boot. This enables the drivers in drivers/pch as part of an SPL
1235 config SPL_POST_MEM_SUPPORT
1236 bool "Support POST drivers"
1238 Enable support for POST (Power-on Self Test) in SPL. POST is a
1239 procedure that checks that the hardware (CPU or board) appears to
1240 be functionally correctly. It is a sanity check that can be
1241 performed before booting. This enables the drivers in post/drivers
1242 as part of an SPL build.
1245 bool "Support reset drivers"
1248 Enable support for reset control in SPL.
1249 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1250 by using the generic reset API provided by driver model.
1251 This enables the drivers in drivers/reset as part of an SPL build.
1254 bool "Support power drivers"
1256 Enable support for power control in SPL. This includes support
1257 for PMICs (Power-management Integrated Circuits) and some of the
1258 features provided by PMICs. In particular, voltage regulators can
1259 be used to enable/disable power and vary its voltage. That can be
1260 useful in SPL to turn on boot peripherals and adjust CPU voltage
1261 so that the clock speed can be increased. This enables the drivers
1262 in drivers/power, drivers/power/pmic and drivers/power/regulator
1263 as part of an SPL build.
1265 config SPL_POWER_DOMAIN
1266 bool "Support power domain drivers"
1269 Enable support for power domain control in SPL. Many SoCs allow
1270 power to be applied to or removed from portions of the SoC (power
1271 domains). This may be used to save power. This API provides the
1272 means to control such power management hardware. This enables
1273 the drivers in drivers/power/domain as part of a SPL build.
1275 config SPL_RAM_SUPPORT
1276 bool "Support booting from RAM"
1277 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1279 Enable booting of an image in RAM. The image can be preloaded or
1280 it can be loaded by SPL directly into RAM (e.g. using USB).
1282 config SPL_RAM_DEVICE
1283 bool "Support booting from preloaded image in RAM"
1284 depends on SPL_RAM_SUPPORT
1285 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1287 Enable booting of an image already loaded in RAM. The image has to
1288 be already in memory when SPL takes over, e.g. loaded by the boot
1291 config SPL_REMOTEPROC
1292 bool "Support REMOTEPROCS"
1294 Enable support for REMOTEPROCs in SPL. This permits to load
1295 a remote processor firmware in SPL.
1298 bool "Support RTC drivers"
1300 Enable RTC (Real-time Clock) support in SPL. This includes support
1301 for reading and setting the time. Some RTC devices also have some
1302 non-volatile (battery-backed) memory which is accessible if
1303 needed. This enables the drivers in drivers/rtc as part of an SPL
1307 bool "Support loading from SATA"
1309 Enable support for SATA (Serial AT attachment) in SPL. This allows
1310 use of SATA devices such as hard drives and flash drivers for
1311 loading U-Boot. SATA is used in higher-end embedded systems and
1312 can provide higher performance than MMC , at somewhat higher
1313 expense and power consumption. This enables loading from SATA
1314 using a configured device.
1316 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1317 bool "SATA raw mode: by sector"
1319 default y if ARCH_MVEBU
1321 Use sector number for specifying U-Boot location on SATA disk in
1324 config SPL_SATA_RAW_U_BOOT_SECTOR
1325 hex "Sector on the SATA disk to load U-Boot from"
1326 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1327 default 0x1 if ARCH_MVEBU
1329 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1330 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1333 bool "Support serial"
1337 Enable support for serial in SPL. This allows use of a serial UART
1338 for displaying messages while SPL is running. It also brings in
1339 printf() and panic() functions. This should normally be enabled
1340 unless there are space reasons not to. Even then, consider
1341 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1344 bool "Support SPI drivers"
1346 Enable support for using SPI in SPL. This is used for connecting
1347 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1348 more details on that. The SPI driver provides the transport for
1349 data between the SPI flash and the CPU. This option can be used to
1350 enable SPI drivers that are needed for other purposes also, such
1353 config SPL_SPI_FLASH_SUPPORT
1354 bool "Support SPI flash drivers"
1357 Enable support for using SPI flash in SPL, and loading U-Boot from
1358 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1359 the SPI bus that is used to connect it to a system. It is a simple
1360 but fast bidirectional 4-wire bus (clock, chip select and two data
1361 lines). This enables the drivers in drivers/mtd/spi as part of an
1362 SPL build. This normally requires SPL_SPI.
1364 if SPL_SPI_FLASH_SUPPORT
1366 config SPL_SPI_FLASH_TINY
1367 bool "Enable low footprint SPL SPI Flash support"
1368 depends on !SPI_FLASH_BAR
1369 default y if SPI_FLASH
1371 Enable lightweight SPL SPI Flash support that supports just reading
1372 data/images from flash. No support to write/erase flash. Enable
1373 this if you have SPL size limitations and don't need full
1374 fledged SPI flash support.
1376 config SPL_SPI_FLASH_SFDP_SUPPORT
1377 bool "SFDP table parsing support for SPI NOR flashes"
1378 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1380 Enable support for parsing and auto discovery of parameters for
1381 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1382 tables as per JESD216 standard in SPL.
1384 config SPL_SPI_FLASH_MTD
1385 bool "Support for SPI flash MTD drivers in SPL"
1387 Enable support for SPI flash MTD drivers in SPL.
1390 bool "Support loading from SPI flash"
1392 Enable support for loading next stage, U-Boot or otherwise, from
1393 SPI NOR in U-Boot SPL.
1395 endif # SPL_SPI_FLASH_SUPPORT
1397 config SYS_SPI_U_BOOT_OFFS
1398 hex "address of u-boot payload in SPI flash"
1399 default 0x8000 if ARCH_SUNXI
1401 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1403 Address within SPI-Flash from where the u-boot payload is fetched
1407 bool "Driver support for thermal devices"
1409 Enable support for temperature-sensing devices. Some SoCs have on-chip
1410 temperature sensors to permit warnings, speed throttling or even
1411 automatic power-off when the temperature gets too high or low. Other
1412 devices may be discrete but connected on a suitable bus.
1415 bool "Support USB host drivers"
1416 select HAVE_BLOCK_DEVICE
1418 Enable access to USB (Universal Serial Bus) host devices so that
1419 SPL can load U-Boot from a connected USB peripheral, such as a USB
1420 flash stick. While USB takes a little longer to start up than most
1421 buses, it is very flexible since many different types of storage
1422 device can be attached. This option enables the drivers in
1423 drivers/usb/host as part of an SPL build.
1425 config SPL_USB_STORAGE
1426 bool "Support loading from USB"
1427 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1429 Enable support for USB devices in SPL. This allows use of USB
1430 devices such as hard drives and flash drivers for loading U-Boot.
1431 The actual drivers are enabled separately using the normal U-Boot
1432 config options. This enables loading from USB using a configured
1435 config SPL_USB_GADGET
1436 bool "Suppport USB Gadget drivers"
1438 Enable USB Gadget API which allows to enable USB device functions
1443 config SPL_USB_ETHER
1444 bool "Support USB Ethernet drivers"
1447 Enable access to the USB network subsystem and associated
1448 drivers in SPL. This permits SPL to load U-Boot over a
1449 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1450 than from an onboard peripheral. Environment support is required
1451 since the network stack uses a number of environment variables.
1452 See also SPL_NET and SPL_ETH.
1455 bool "Support DFU (Device Firmware Upgrade)"
1457 select SPL_DFU_NO_RESET
1458 depends on SPL_RAM_SUPPORT
1460 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1461 RAM memory device support. The ROM code will load and execute
1462 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1463 selected device partition from host-pc using dfu-utils.
1464 This feature is useful to flash the binaries to factory or bare-metal
1465 boards using USB interface.
1468 bool "DFU device selection"
1473 depends on SPL_DFU && SPL_RAM_SUPPORT
1475 select RAM/DDR memory device for loading binary images
1476 (u-boot/kernel) to the selected device partition using
1477 DFU and execute the u-boot/kernel from RAM.
1481 config SPL_USB_SDP_SUPPORT
1482 bool "Support SDP (Serial Download Protocol)"
1483 depends on SPL_SERIAL
1485 Enable Serial Download Protocol (SDP) device support in SPL. This
1486 allows to download images into memory and execute (jump to) them
1487 using the same protocol as implemented by the i.MX family's boot ROM.
1489 config SPL_SDP_USB_DEV
1490 int "SDP USB controller index"
1492 depends on SPL_USB_SDP_SUPPORT
1494 Some boards have USB controller other than 0. Define this option
1495 so it can be used in compiled environment.
1499 bool "Support watchdog drivers"
1500 imply SPL_WDT if !HW_WATCHDOG
1502 Enable support for watchdog drivers in SPL. A watchdog is
1503 typically a hardware peripheral which can reset the system when it
1504 detects no activity for a while (such as a software crash). This
1505 enables the drivers in drivers/watchdog as part of an SPL build.
1507 config SPL_YMODEM_SUPPORT
1508 bool "Support loading using Ymodem"
1509 depends on SPL_SERIAL
1511 While loading from serial is slow it can be a useful backup when
1512 there is no other option. The Ymodem protocol provides a reliable
1513 means of transmitting U-Boot over a serial line for using in SPL,
1514 with a checksum to ensure correctness.
1517 bool "Support ARM Trusted Firmware"
1518 depends on ARM64 && SPL_FIT
1520 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1521 is loaded by SPL (which is considered as BL2 in ATF terminology).
1522 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1524 config SPL_ATF_LOAD_IMAGE_V2
1525 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1528 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1530 If you want to load a bl31 image from the SPL and need the new
1533 config SPL_ATF_NO_PLATFORM_PARAM
1534 bool "Pass no platform parameter"
1537 While we expect to call a pointer to a valid FDT (or NULL)
1538 as the platform parameter to an ATF, some ATF versions are
1539 not U-Boot aware and have an insufficiently robust parameter
1540 validation to gracefully reject a FDT being passed.
1542 If this option is enabled, the spl_atf os-type handler will
1543 always pass NULL for the platform parameter.
1545 If your ATF is affected, say Y.
1547 config SPL_AM33XX_ENABLE_RTC32K_OSC
1548 bool "Enable the RTC32K OSC on AM33xx based platforms"
1551 Enable access to the AM33xx RTC and select the external 32kHz clock
1554 config SPL_OPTEE_IMAGE
1555 bool "Support OP-TEE Trusted OS image in SPL"
1558 OP-TEE is an open source Trusted OS which is loaded by SPL.
1559 More detail at: https://github.com/OP-TEE/optee_os
1562 bool "Support RISC-V OpenSBI"
1563 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1565 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1566 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1567 firmware. It is loaded and started by U-Boot SPL.
1569 More details are available at https://github.com/riscv/opensbi and
1570 https://github.com/riscv/riscv-sbi-doc
1572 config SPL_OPENSBI_LOAD_ADDR
1573 hex "OpenSBI load address"
1574 depends on SPL_OPENSBI
1576 Load address of the OpenSBI binary.
1580 depends on SUPPORT_TPL
1583 If you want to build TPL as well as the normal image and SPL, say Y.
1587 config TPL_SIZE_LIMIT
1588 hex "Maximum size of TPL image"
1592 Specifies the maximum length of the U-Boot TPL image.
1593 If this value is zero, it is ignored.
1595 config TPL_BINMAN_SYMBOLS
1596 bool "Declare binman symbols in TPL"
1597 depends on SPL_FRAMEWORK && BINMAN
1600 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1601 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1602 and spl_get_image_size().
1604 For this to work, you must have a U-Boot image in the binman image, so
1605 binman can update TPL with the location of it.
1607 config TPL_FRAMEWORK
1608 bool "Support TPL based upon the common SPL framework"
1609 default y if SPL_FRAMEWORK
1611 Enable the SPL framework under common/spl/ for TPL builds.
1612 This framework supports MMC, NAND and YMODEM and other methods
1613 loading of U-Boot's SPL stage. If unsure, say Y.
1616 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1617 depends on HANDOFF && TPL_BLOBLIST
1620 This option enables TPL to write handoff information. This can be
1621 used to pass information like the size of SDRAM from TPL to U-Boot
1622 proper. The information is also available to SPL if it is useful
1625 config TPL_BOARD_INIT
1626 bool "Call board-specific initialization in TPL"
1628 If this option is enabled, U-Boot will call the function
1629 spl_board_init() from board_init_r(). This function should be
1630 provided by the board.
1632 config TPL_BOOTCOUNT_LIMIT
1633 bool "Support bootcount in TPL"
1634 depends on TPL_ENV_SUPPORT
1636 If this option is enabled, the TPL will support bootcount.
1637 For example, it may be useful to choose the device to boot.
1640 string "Linker script for the TPL stage"
1642 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1643 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1645 The TPL stage will usually require a different linker-script
1646 (as it runs from a different memory region) than the regular
1647 U-Boot stage. Set this to the path of the linker-script to
1650 May be left empty to trigger the Makefile infrastructure to
1651 fall back to the linker-script used for the SPL stage.
1653 config TPL_NEEDS_SEPARATE_STACK
1654 bool "TPL needs a separate initial stack-pointer"
1657 Enable, if the TPL stage should not inherit its initial
1658 stack-pointer from the settings for the SPL stage.
1661 bool "Support power drivers"
1663 Enable support for power control in TPL. This includes support
1664 for PMICs (Power-management Integrated Circuits) and some of the
1665 features provided by PMICs. In particular, voltage regulators can
1666 be used to enable/disable power and vary its voltage. That can be
1667 useful in TPL to turn on boot peripherals and adjust CPU voltage
1668 so that the clock speed can be increased. This enables the drivers
1669 in drivers/power, drivers/power/pmic and drivers/power/regulator
1670 as part of an TPL build.
1672 config TPL_TEXT_BASE
1673 hex "Base address for the .text section of the TPL stage"
1676 The base address for the .text section of the TPL stage.
1679 hex "Maximum size (in bytes) for the TPL stage"
1680 default 0x2e000 if ROCKCHIP_RK3399
1681 default 0x8000 if ROCKCHIP_RK3288
1682 default 0x7000 if ROCKCHIP_RK322X || ROCKCHIP_RK3328 || ROCKCHIP_RK3368
1683 default 0x2800 if ROCKCHIP_PX30
1686 The maximum size (in bytes) of the TPL stage.
1689 hex "Offset to which the TPL should be padded before appending the TPL payload"
1690 depends on !TPL_FRAMEWORK && PPC
1691 default TPL_MAX_SIZE
1693 Image offset to which the TPL should be padded before appending the
1694 TPL payload. By default, this is defined as CONFIG_TPL_MAX_SIZE, or 0 if
1695 CONFIG_TPL_MAX_SIZE is undefined. CONFIG_TPL_PAD_TO must be either
1696 0, meaning to append the TPL payload without any padding, or >=
1697 CONFIG_TPL_MAX_SIZE.
1700 hex "Address of the initial stack-pointer for the TPL stage"
1701 depends on TPL_NEEDS_SEPARATE_STACK
1703 The address of the initial stack-pointer for the TPL stage.
1704 Usually this will be the (aligned) top-of-stack.
1706 config TPL_READ_ONLY
1708 depends on TPL_OF_PLATDATA
1709 select TPL_OF_PLATDATA_NO_BIND
1710 select TPL_OF_PLATDATA_RT
1712 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1713 section of memory. This means that of-platdata must make a copy (in
1714 writeable memory) of anything it wants to modify, such as
1715 device-private data.
1717 config TPL_BOOTROM_SUPPORT
1718 bool "Support returning to the BOOTROM (from TPL)"
1720 Some platforms (e.g. the Rockchip RK3368) provide support in their
1721 ROM for loading the next boot-stage after performing basic setup
1724 Enable this option, to return to the BOOTROM through the
1725 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1726 boot device list, if not implemented for a given board)
1729 bool "Support CRC32 in TPL"
1730 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1732 Enable this to support CRC32 in uImages or FIT images within SPL.
1733 This is a 32-bit checksum value that can be used to verify images.
1734 For FIT images, this is the least secure type of checksum, suitable
1735 for detected accidental image corruption. For secure applications you
1736 should consider SHA1 or SHA256.
1738 config TPL_DRIVERS_MISC
1739 bool "Support misc drivers in TPL"
1741 Enable miscellaneous drivers in TPL. These drivers perform various
1742 tasks that don't fall nicely into other categories, Enable this
1743 option to build the drivers in drivers/misc as part of an TPL
1744 build, for those that support building in TPL (not all drivers do).
1746 config TPL_ENV_SUPPORT
1747 bool "Support an environment"
1749 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1752 bool "Support GPIO in TPL"
1754 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1755 GPIOs allow U-Boot to read the state of an input line (high or
1756 low) and set the state of an output line. This can be used to
1757 drive LEDs, control power to various system parts and read user
1758 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1759 for example. Enable this option to build the drivers in
1760 drivers/gpio as part of an TPL build.
1765 Enable support for the I2C bus in TPL. See SPL_I2C for
1768 config TPL_LIBCOMMON_SUPPORT
1769 bool "Support common libraries"
1771 Enable support for common U-Boot libraries within TPL. See
1772 SPL_LIBCOMMON_SUPPORT for details.
1774 config TPL_LIBGENERIC_SUPPORT
1775 bool "Support generic libraries"
1777 Enable support for generic U-Boot libraries within TPL. See
1778 SPL_LIBGENERIC_SUPPORT for details.
1780 config TPL_MPC8XXX_INIT_DDR
1781 bool "Support MPC8XXX DDR init"
1783 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1784 SPL_MPC8XXX_INIT_DDR for details.
1790 Enable support for MMC within TPL. See SPL_MMC for details.
1792 config TPL_NAND_SUPPORT
1793 bool "Support NAND flash"
1795 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1798 bool "Support PCI drivers"
1800 Enable support for PCI in TPL. For platforms that need PCI to boot,
1801 or must perform some init using PCI in SPL, this provides the
1802 necessary driver support. This enables the drivers in drivers/pci
1803 as part of a TPL build.
1806 bool "Support PCH drivers"
1808 Enable support for PCH (Platform Controller Hub) devices in TPL.
1809 These are used to set up GPIOs and the SPI peripheral early in
1810 boot. This enables the drivers in drivers/pch as part of a TPL
1813 config TPL_RAM_SUPPORT
1814 bool "Support booting from RAM"
1816 Enable booting of an image in RAM. The image can be preloaded or
1817 it can be loaded by TPL directly into RAM (e.g. using USB).
1819 config TPL_RAM_DEVICE
1820 bool "Support booting from preloaded image in RAM"
1821 depends on TPL_RAM_SUPPORT
1823 Enable booting of an image already loaded in RAM. The image has to
1824 be already in memory when TPL takes over, e.g. loaded by the boot
1828 bool "Support RTC drivers"
1830 Enable RTC (Real-time Clock) support in TPL. This includes support
1831 for reading and setting the time. Some RTC devices also have some
1832 non-volatile (battery-backed) memory which is accessible if
1833 needed. This enables the drivers in drivers/rtc as part of an TPL
1837 bool "Support serial"
1841 Enable support for serial in TPL. See SPL_SERIAL for
1844 config TPL_SPI_FLASH_SUPPORT
1845 bool "Support SPI flash drivers"
1847 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1850 config TPL_SPI_FLASH_TINY
1851 bool "Enable low footprint TPL SPI Flash support"
1852 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1853 default y if SPI_FLASH
1855 Enable lightweight TPL SPI Flash support that supports just reading
1856 data/images from flash. No support to write/erase flash. Enable
1857 this if you have TPL size limitations and don't need full-fledged
1861 bool "Support loading from SPI flash"
1862 depends on TPL_SPI_FLASH_SUPPORT
1864 Enable support for loading next stage, U-Boot or otherwise, from
1865 SPI NOR in U-Boot TPL.
1868 bool "Support SPI drivers"
1870 Enable support for using SPI in TPL. See SPL_SPI for
1874 bool "Support SPI DM drivers in TPL"
1876 Enable support for SPI DM drivers in TPL.
1878 config TPL_DM_SPI_FLASH
1879 bool "Support SPI DM FLASH drivers in TPL"
1881 Enable support for SPI DM flash drivers in TPL.
1883 config TPL_YMODEM_SUPPORT
1884 bool "Support loading using Ymodem"
1885 depends on TPL_SERIAL
1887 While loading from serial is slow it can be a useful backup when
1888 there is no other option. The Ymodem protocol provides a reliable
1889 means of transmitting U-Boot over a serial line for using in TPL,
1890 with a checksum to ensure correctness.
1896 depends on SUPPORT_SPL
1899 If you want to build VPL as well as the normal image, TPL and SPL,
1904 config VPL_BANNER_PRINT
1905 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1909 If this option is enabled, VPL will print the banner with version
1910 info. Disabling this option could be useful to reduce VPL boot time
1911 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1913 config VPL_BOARD_INIT
1914 bool "Call board-specific initialization in VPL"
1916 If this option is enabled, U-Boot will call the function
1917 spl_board_init() from board_init_r(). This function should be
1918 provided by the board.
1922 bool "Support cache drivers in VPL"
1924 Enable support for cache drivers in VPL.
1927 bool "Support CRC32 in VPL"
1928 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1930 Enable this to support CRC32 in uImages or FIT images within VPL.
1931 This is a 32-bit checksum value that can be used to verify images.
1932 For FIT images, this is the least secure type of checksum, suitable
1933 for detected accidental image corruption. For secure applications you
1934 should consider SHA1 or SHA256.
1937 bool "Support SPI DM drivers in VPL"
1939 Enable support for SPI DM drivers in VPL.
1941 config VPL_DM_SPI_FLASH
1942 bool "Support SPI DM FLASH drivers in VPL"
1944 Enable support for SPI DM flash drivers in VPL.
1946 config VPL_FRAMEWORK
1947 bool "Support VPL based upon the common SPL framework"
1950 Enable the SPL framework under common/spl/ for VPL builds.
1951 This framework supports MMC, NAND and YMODEM and other methods
1952 loading of U-Boot's next stage. If unsure, say Y.
1955 bool "Pass hand-off information from VPL to SPL"
1956 depends on HANDOFF && VPL_BLOBLIST
1959 This option enables VPL to write handoff information. This can be
1960 used to pass information like the size of SDRAM from VPL to SPL. Also
1961 VPL can receive information from TPL in the same place if that is
1964 config VPL_LIBCOMMON_SUPPORT
1965 bool "Support common libraries"
1966 default y if SPL_LIBCOMMON_SUPPORT
1968 Enable support for common U-Boot libraries within VPL. See
1969 SPL_LIBCOMMON_SUPPORT for details.
1971 config VPL_LIBGENERIC_SUPPORT
1972 bool "Support generic libraries"
1973 default y if SPL_LIBGENERIC_SUPPORT
1975 Enable support for generic U-Boot libraries within VPL. These
1976 libraries include generic code to deal with device tree, hashing,
1977 printf(), compression and the like. This option is enabled on many
1978 boards. Enable this option to build the code in lib/ as part of a
1981 config VPL_DRIVERS_MISC
1982 bool "Support misc drivers"
1983 default y if TPL_DRIVERS_MISC
1985 Enable miscellaneous drivers in VPL. These drivers perform various
1986 tasks that don't fall nicely into other categories, Enable this
1987 option to build the drivers in drivers/misc as part of a VPL
1988 build, for those that support building in VPL (not all drivers do).
1990 config VPL_ENV_SUPPORT
1991 bool "Support an environment"
1993 Enable environment support in VPL. The U-Boot environment provides
1994 a number of settings (essentially name/value pairs) which can
1995 control many aspects of U-Boot's operation. Enabling this option will
1996 make env_get() and env_set() available in VSPL.
1999 bool "Support GPIO in VPL"
2000 default y if SPL_GPIO
2002 Enable support for GPIOs (General-purpose Input/Output) in VPL.
2003 GPIOs allow U-Boot to read the state of an input line (high or
2004 low) and set the state of an output line. This can be used to
2005 drive LEDs, control power to various system parts and read user
2006 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
2007 for example. Enable this option to build the drivers in
2008 drivers/gpio as part of a VPL build.
2011 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
2012 depends on HANDOFF && VPL_BLOBLIST
2015 This option enables VPL to write handoff information. This can be
2016 used to pass information like the size of SDRAM from VPL to U-Boot
2017 proper. The information is also available to VPL if it is useful
2021 bool "Support hashing drivers in VPL"
2026 Enable hashing drivers in VPL. These drivers can be used to
2027 accelerate secure boot processing in secure applications. Enable
2028 this option to build system-specific drivers for hash acceleration
2029 as part of a VPL build.
2031 config VPL_I2C_SUPPORT
2032 bool "Support I2C in VPL"
2033 default y if SPL_I2C_SUPPORT
2035 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
2038 config VPL_PCH_SUPPORT
2039 bool "Support PCH drivers"
2040 default y if TPL_PCH_SUPPORT
2042 Enable support for PCH (Platform Controller Hub) devices in VPL.
2043 These are used to set up GPIOs and the SPI peripheral early in
2044 boot. This enables the drivers in drivers/pch as part of a VPL
2048 bool "Support PCI drivers"
2049 default y if SPL_PCI
2051 Enable support for PCI in VPL. For platforms that need PCI to boot,
2052 or must perform some init using PCI in VPL, this provides the
2053 necessary driver support. This enables the drivers in drivers/pci
2054 as part of a VPL build.
2057 bool "Support RTC drivers"
2059 Enable RTC (Real-time Clock) support in VPL. This includes support
2060 for reading and setting the time. Some RTC devices also have some
2061 non-volatile (battery-backed) memory which is accessible if
2062 needed. This enables the drivers in drivers/rtc as part of a VPL
2066 bool "Support serial"
2067 default y if TPL_SERIAL
2071 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
2074 config VPL_SIZE_LIMIT
2075 hex "Maximum size of VPL image"
2079 Specifies the maximum length of the U-Boot VPL image.
2080 If this value is zero, it is ignored.
2083 bool "Support SPI drivers"
2085 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
2088 config VPL_SPI_FLASH_SUPPORT
2089 bool "Support SPI flash drivers"
2091 Enable support for using SPI flash in VPL, and loading U-Boot from
2092 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
2093 the SPI bus that is used to connect it to a system. It is a simple
2094 but fast bidirectional 4-wire bus (clock, chip select and two data
2095 lines). This enables the drivers in drivers/mtd/spi as part of a
2096 VPL build. This normally requires VPL_SPI_SUPPORT.
2098 config VPL_TEXT_BASE
2102 The address in memory that VPL will be running from.
2106 config SPL_AT91_MCK_BYPASS
2107 bool "Use external clock signal as a source of main clock for AT91 platforms"
2108 depends on ARCH_AT91
2110 Use external 8 to 24 Mhz clock signal as source of main clock instead
2111 of an external crystal oscillator.
2112 This option disables the internal driving on the XOUT pin.
2113 The external source has to provide a stable clock on the XIN pin.
2114 If this option is disabled, the SoC expects a crystal oscillator
2115 that needs driving on both XIN and XOUT lines.