9 config SPL_DFU_NO_RESET
14 depends on SUPPORT_SPL
17 If you want to build SPL as well as the normal image, say Y.
20 bool "Support SPL based upon the common SPL framework"
24 Enable the SPL framework under common/spl/. This framework
25 supports MMC, NAND and YMODEM and other methods loading of U-Boot
26 and the Linux Kernel. If unsure, say Y.
28 config SPL_FRAMEWORK_BOARD_INIT_F
29 bool "Define a generic function board_init_f"
30 depends on SPL_FRAMEWORK
32 Define a generic function board_init_f that:
33 - initialize the spl (spl_early_init)
34 - initialize the serial (preloader_console_init)
35 Unless you want to provide your own board_init_f, you should say Y.
38 hex "Maximum size of SPL image"
40 default 69632 if ARCH_MX6 && !MX6_OCRAM_256KB
41 default 200704 if ARCH_MX6 && MX6_OCRAM_256KB
44 Specifies the maximum length of the U-Boot SPL image.
45 If this value is zero, it is ignored.
47 config SPL_SIZE_LIMIT_SUBTRACT_GD
48 bool "SPL image size check: provide space for global data"
49 depends on SPL_SIZE_LIMIT > 0
51 If enabled, aligned size of global data is reserved in
52 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
53 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
54 pre-reloc global data is put into this SRAM, too.
56 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
57 bool "SPL image size check: provide space for malloc() pool before relocation"
58 depends on SPL_SIZE_LIMIT > 0
60 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
61 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
62 describes the size of SRAM available for SPL when pre-reloc malloc
63 pool is put into this SRAM, too.
65 config SPL_SIZE_LIMIT_PROVIDE_STACK
66 hex "SPL image size check: provide stack space before relocation"
67 depends on SPL_SIZE_LIMIT > 0
70 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
71 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
72 of SRAM available for SPL when the stack required before reolcation
75 config SPL_SYS_STACK_F_CHECK_BYTE
79 Constant used to check the stack
81 config SPL_SYS_REPORT_STACK_F_USAGE
82 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
83 bool "Check and report stack usage in SPL before relocation"
85 If this option is enabled, the initial SPL stack is filled with 0xaa
86 very early, up to the size configured with
87 SPL_SIZE_LIMIT_PROVIDE_STACK.
88 Later when SPL is done using this initial stack and switches to a
89 stack in DRAM, the actually used size of this initial stack is
90 reported by examining the memory and searching for the lowest
91 occurrence of non 0xaa bytes.
92 This default implementation works for stacks growing down only.
94 menu "PowerPC SPL Boot options"
95 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
98 bool "Load SPL from NAND flash"
101 bool "Load SPL from SD Card / eMMC"
104 bool "Load SPL from SPI flash"
107 bool "Create SPL in Freescale PBI format"
109 Create boot binary having SPL binary in PBI format concatenated with
115 bool "Pass hand-off information from SPL to U-Boot proper"
118 It is useful to be able to pass information from SPL to U-Boot
119 proper to preserve state that is known in SPL and is needed in U-Boot.
120 Enable this to locate the handoff information in U-Boot proper, early
121 in boot. It is available in gd->handoff. The state state is set up
122 in SPL (or TPL if that is being used).
127 bool "Pass hand-off information from SPL to U-Boot proper"
128 depends on HANDOFF && SPL_BLOBLIST
131 This option enables SPL to write handoff information. This can be
132 used to pass information like the size of SDRAM from SPL to U-Boot
133 proper. Also SPL can receive information from TPL in the same place
137 string "Linker script for the SPL stage"
138 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
140 The SPL stage will usually require a different linker-script
141 (as it runs from a different memory region) than the regular
142 U-Boot stage. Set this to the path of the linker-script to
147 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
148 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
149 default 0x20060 if MACH_SUN50I_H6
150 default 0x00060 if ARCH_SUNXI
151 default 0xfffc0000 if ARCH_ZYNQMP
154 The address in memory that SPL will be running from.
156 config SPL_BOARD_INIT
157 bool "Call board-specific initialization in SPL"
159 If this option is enabled, U-Boot will call the function
160 spl_board_init() from board_init_r(). This function should be
161 provided by the board.
163 config SPL_BOOTROM_SUPPORT
164 bool "Support returning to the BOOTROM"
166 Some platforms (e.g. the Rockchip RK3368) provide support in their
167 ROM for loading the next boot-stage after performing basic setup
170 Enable this option, to return to the BOOTROM through the
171 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
172 boot device list, if not implemented for a given board)
174 config SPL_BOOTCOUNT_LIMIT
175 bool "Support bootcount in SPL"
176 depends on SPL_ENV_SUPPORT
178 On some boards, which use 'falcon' mode, it is necessary to check
179 and increment the number of boot attempts. Such boards do not
180 use proper U-Boot for normal boot flow and hence needs those
181 adjustments to be done in the SPL.
183 config SPL_RAW_IMAGE_SUPPORT
184 bool "Support SPL loading and booting of RAW images"
185 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
186 default y if !TI_SECURE_DEVICE
188 SPL will support loading and booting a RAW image when this option
189 is y. If this is not set, SPL will move on to other available
190 boot media to find a suitable image.
192 config SPL_LEGACY_IMAGE_SUPPORT
193 bool "Support SPL loading and booting of Legacy images"
194 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
196 SPL will support loading and booting Legacy images when this option
197 is y. If this is not set, SPL will move on to other available
198 boot media to find a suitable image.
200 config SPL_LEGACY_IMAGE_CRC_CHECK
201 bool "Check CRC of Legacy images"
202 depends on SPL_LEGACY_IMAGE_SUPPORT
203 select SPL_CRC32_SUPPORT
205 Enable this to check the CRC of Legacy images. While this increases
206 reliability, it affects both code size and boot duration.
207 If disabled, Legacy images are booted if the image magic and size
208 are correct, without further integrity checks.
210 config SPL_SYS_MALLOC_SIMPLE
212 prompt "Only use malloc_simple functions in the SPL"
214 Say Y here to only use the *_simple malloc functions from
215 malloc_simple.c, rather then using the versions from dlmalloc.c;
216 this will make the SPL binary smaller at the cost of more heap
217 usage as the *_simple malloc functions do not re-use free-ed mem.
219 config TPL_SYS_MALLOC_SIMPLE
221 prompt "Only use malloc_simple functions in the TPL"
224 Say Y here to only use the *_simple malloc functions from
225 malloc_simple.c, rather then using the versions from dlmalloc.c;
226 this will make the TPL binary smaller at the cost of more heap
227 usage as the *_simple malloc functions do not re-use free-ed mem.
230 bool "Enable SDRAM location for SPL stack"
232 SPL starts off execution in SRAM and thus typically has only a small
233 stack available. Since SPL sets up DRAM while in its board_init_f()
234 function, it is possible for the stack to move there before
235 board_init_r() is reached. This option enables a special SDRAM
236 location for the SPL stack. U-Boot SPL switches to this after
237 board_init_f() completes, and before board_init_r() starts.
239 config SPL_STACK_R_ADDR
240 depends on SPL_STACK_R
241 hex "SDRAM location for SPL stack"
242 default 0x82000000 if ARCH_OMAP2PLUS
244 Specify the address in SDRAM for the SPL stack. This will be set up
245 before board_init_r() is called.
247 config SPL_STACK_R_MALLOC_SIMPLE_LEN
248 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
249 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
252 Specify the amount of the stack to use as memory pool for
253 malloc_simple after switching the stack to DRAM. This may be set
254 to give board_init_r() a larger heap then the initial heap in
255 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
257 config SPL_SEPARATE_BSS
258 bool "BSS section is in a different memory region from text"
260 Some platforms need a large BSS region in SPL and can provide this
261 because RAM is already set up. In this case BSS can be moved to RAM.
262 This option should then be enabled so that the correct device tree
263 location is used. Normally we put the device tree at the end of BSS
264 but with this option enabled, it goes at _image_binary_end.
266 config SPL_BANNER_PRINT
267 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
270 If this option is enabled, SPL will print the banner with version
271 info. Disabling this option could be useful to reduce TPL boot time
272 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
274 config TPL_BANNER_PRINT
275 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
279 If this option is enabled, SPL will not print the banner with version
280 info. Disabling this option could be useful to reduce SPL boot time
281 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
284 depends on ARM && !ARM64
285 bool "Allows initializing BSS early before entering board_init_f"
287 On some platform we have sufficient memory available early on to
288 allow setting up and using a basic BSS prior to entering
289 board_init_f. Activating this option will also de-activate the
290 clearing of BSS during the SPL relocation process, thus allowing
291 to carry state from board_init_f to board_init_r by way of BSS.
293 config SPL_DISPLAY_PRINT
294 bool "Display a board-specific message in SPL"
296 If this option is enabled, U-Boot will call the function
297 spl_display_print() immediately after displaying the SPL console
298 banner ("U-Boot SPL ..."). This function should be provided by
301 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
302 bool "MMC raw mode: by sector"
303 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
304 ARCH_MX6 || ARCH_MX7 || \
305 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
306 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
307 OMAP44XX || OMAP54XX || AM33XX || AM43XX
309 Use sector number for specifying U-Boot location on MMC/SD in
312 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
313 hex "Address on the MMC to load U-Boot from"
314 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
315 default 0x50 if ARCH_SUNXI
316 default 0x75 if ARCH_DAVINCI
317 default 0x8a if ARCH_MX6 || ARCH_MX7
318 default 0x100 if ARCH_UNIPHIER
319 default 0x140 if ARCH_MVEBU
320 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
321 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
322 OMAP54XX || AM33XX || AM43XX || ARCH_K3
323 default 0x4000 if ARCH_ROCKCHIP
325 Address on the MMC to load U-Boot from, when the MMC is being used
326 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
328 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
329 bool "MMC Raw mode: by partition"
331 Use a partition for loading U-Boot when using MMC/SD in raw mode.
333 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
334 hex "Partition to use to load U-Boot from"
335 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
338 Partition on the MMC to load U-Boot from when the MMC is being
341 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
342 bool "MMC raw mode: by partition type"
343 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
345 Use partition type for specifying U-Boot partition on MMC/SD in
346 raw mode. U-Boot will be loaded from the first partition of this
349 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
350 hex "Partition Type on the MMC to load U-Boot from"
351 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
353 Partition Type on the MMC to load U-Boot from, when the MMC is being
356 config SPL_CRC32_SUPPORT
358 default y if SPL_LEGACY_IMAGE_SUPPORT
360 Enable this to support CRC32 in uImages or FIT images within SPL.
361 This is a 32-bit checksum value that can be used to verify images.
362 For FIT images, this is the least secure type of checksum, suitable
363 for detected accidental image corruption. For secure applications you
364 should consider SHA1 or SHA256.
366 config SPL_MD5_SUPPORT
370 Enable this to support MD5 in FIT images within SPL. An MD5
371 checksum is a 128-bit hash value used to check that the image
372 contents have not been corrupted. Note that MD5 is not considered
373 secure as it is possible (with a brute-force attack) to adjust the
374 image while still retaining the same MD5 hash value. For secure
375 applications where images may be changed maliciously, you should
376 consider SHA1 or SHA256.
378 config SPL_SHA1_SUPPORT
383 Enable this to support SHA1 in FIT images within SPL. A SHA1
384 checksum is a 160-bit (20-byte) hash value used to check that the
385 image contents have not been corrupted or maliciously altered.
386 While SHA1 is fairly secure it is coming to the end of its life
387 due to the expanding computing power available to brute-force
388 attacks. For more security, consider SHA256.
390 config SPL_SHA256_SUPPORT
391 bool "Support SHA256"
395 Enable this to support SHA256 in FIT images within SPL. A SHA256
396 checksum is a 256-bit (32-byte) hash value used to check that the
397 image contents have not been corrupted. SHA256 is recommended for
398 use in secure applications since (as at 2016) there is no known
399 feasible attack that could produce a 'collision' with differing
400 input data. Use this for the highest security. Note that only the
401 SHA256 variant is supported: SHA512 and others are not currently
404 config SPL_FIT_IMAGE_TINY
405 bool "Remove functionality from SPL FIT loading to reduce size"
407 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
408 default y if ARCH_IMX8M
410 Enable this to reduce the size of the FIT image loading code
411 in SPL, if space for the SPL binary is very tight.
413 This removes the detection of image types (which forces the
414 first image to be treated as having a U-Boot style calling
415 convention) and skips the recording of each loaded payload
416 (i.e. loadable) into the FDT (modifying the loaded FDT to
417 ensure this information is available to the next image
420 config SPL_CPU_SUPPORT
421 bool "Support CPU drivers"
423 Enable this to support CPU drivers in SPL. These drivers can set
424 up CPUs and provide information about them such as the model and
425 name. This can be useful in SPL since setting up the CPUs earlier
426 may improve boot performance. Enable this option to build the
427 drivers in drivers/cpu as part of an SPL build.
429 config SPL_CRYPTO_SUPPORT
430 bool "Support crypto drivers"
432 Enable crypto drivers in SPL. These drivers can be used to
433 accelerate secure boot processing in secure applications. Enable
434 this option to build the drivers in drivers/crypto as part of an
437 config SPL_HASH_SUPPORT
438 bool "Support hashing drivers"
442 Enable hashing drivers in SPL. These drivers can be used to
443 accelerate secure boot processing in secure applications. Enable
444 this option to build system-specific drivers for hash acceleration
445 as part of an SPL build.
447 config TPL_HASH_SUPPORT
448 bool "Support hashing drivers in TPL"
453 Enable hashing drivers in SPL. These drivers can be used to
454 accelerate secure boot processing in secure applications. Enable
455 this option to build system-specific drivers for hash acceleration
456 as part of an SPL build.
458 config SPL_DMA_SUPPORT
459 bool "Support DMA drivers"
461 Enable DMA (direct-memory-access) drivers in SPL. These drivers
462 can be used to handle memory-to-peripheral data transfer without
463 the CPU moving the data. Enable this option to build the drivers
464 in drivers/dma as part of an SPL build.
466 config SPL_DRIVERS_MISC_SUPPORT
467 bool "Support misc drivers"
469 Enable miscellaneous drivers in SPL. These drivers perform various
470 tasks that don't fall nicely into other categories, Enable this
471 option to build the drivers in drivers/misc as part of an SPL
472 build, for those that support building in SPL (not all drivers do).
474 config SPL_ENV_SUPPORT
475 bool "Support an environment"
477 Enable environment support in SPL. The U-Boot environment provides
478 a number of settings (essentially name/value pairs) which can
479 control many aspects of U-Boot's operation. Normally this is not
480 needed in SPL as it has a much simpler task with less
481 configuration. But some boards use this to support 'Falcon' boot
482 on EXT2 and FAT, where SPL boots directly into Linux without
483 starting U-Boot first. Enabling this option will make env_get()
484 and env_set() available in SPL.
487 bool "Support save environment"
488 depends on SPL_ENV_SUPPORT
489 select SPL_MMC_WRITE if ENV_IS_IN_MMC
491 Enable save environment support in SPL after setenv. By default
492 the saveenv option is not provided in SPL, but some boards need
493 this support in 'Falcon' boot, where SPL need to boot from
494 different images based on environment variable set by OS. For
495 example OS may set "reboot_image" environment variable to
496 "recovery" inorder to boot recovery image by SPL. The SPL read
497 "reboot_image" and act accordingly and change the reboot_image
498 to default mode using setenv and save the environment.
500 config SPL_ETH_SUPPORT
501 bool "Support Ethernet"
502 depends on SPL_ENV_SUPPORT
504 Enable access to the network subsystem and associated Ethernet
505 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
506 link rather than from an on-board peripheral. Environment support
507 is required since the network stack uses a number of environment
508 variables. See also SPL_NET_SUPPORT.
511 bool "Support EXT filesystems"
513 Enable support for EXT2/3/4 filesystems with SPL. This permits
514 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
515 filesystem from within SPL. Support for the underlying block
516 device (e.g. MMC or USB) must be enabled separately.
519 bool "Support FAT filesystems"
522 Enable support for FAT and VFAT filesystems with SPL. This
523 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
524 filesystem from within SPL. Support for the underlying block
525 device (e.g. MMC or USB) must be enabled separately.
528 bool "Support write for FAT filesystems"
530 Enable write support for FAT and VFAT filesystems with SPL.
531 Support for the underlying block device (e.g. MMC or USB) must be
534 config SPL_FPGA_SUPPORT
537 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
538 provide software-configurable hardware which is typically used to
539 implement peripherals (such as UARTs, LCD displays, MMC) or
540 accelerate custom processing functions, such as image processing
541 or machine learning. Sometimes it is useful to program the FPGA
542 as early as possible during boot, and this option can enable that
545 config SPL_GPIO_SUPPORT
546 bool "Support GPIO in SPL"
548 Enable support for GPIOs (General-purpose Input/Output) in SPL.
549 GPIOs allow U-Boot to read the state of an input line (high or
550 low) and set the state of an output line. This can be used to
551 drive LEDs, control power to various system parts and read user
552 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
553 for example. Enable this option to build the drivers in
554 drivers/gpio as part of an SPL build.
556 config SPL_I2C_SUPPORT
559 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
560 I2C works with a clock and data line which can be driven by a
561 one or more masters or slaves. It is a fairly complex bus but is
562 widely used as it only needs two lines for communication. Speeds of
563 400kbps are typical but up to 3.4Mbps is supported by some
564 hardware. I2C can be useful in SPL to configure power management
565 ICs (PMICs) before raising the CPU clock speed, for example.
566 Enable this option to build the drivers in drivers/i2c as part of
569 config SPL_LIBCOMMON_SUPPORT
570 bool "Support common libraries"
572 Enable support for common U-Boot libraries within SPL. These
573 libraries include common code to deal with U-Boot images,
574 environment and USB, for example. This option is enabled on many
575 boards. Enable this option to build the code in common/ as part of
578 config SPL_LIBDISK_SUPPORT
579 bool "Support disk partitions"
582 Enable support for disk partitions within SPL. 'Disk' is something
583 of a misnomer as it includes non-spinning media such as flash (as
584 used in MMC and USB sticks). Partitions provide a way for a disk
585 to be split up into separate regions, with a partition table placed
586 at the start or end which describes the location and size of each
587 'partition'. These partitions are typically uses as individual block
588 devices, typically with an EXT2 or FAT filesystem in each. This
589 option enables whatever partition support has been enabled in
590 U-Boot to also be used in SPL. It brings in the code in disk/.
592 config SPL_LIBGENERIC_SUPPORT
593 bool "Support generic libraries"
595 Enable support for generic U-Boot libraries within SPL. These
596 libraries include generic code to deal with device tree, hashing,
597 printf(), compression and the like. This option is enabled on many
598 boards. Enable this option to build the code in lib/ as part of an
601 config SPL_DM_MAILBOX
602 bool "Support Mailbox"
604 Enable support for Mailbox within SPL. This enable the inter
605 processor communication protocols tobe used within SPL. Enable
606 this option to build the drivers in drivers/mailbox as part of
609 config SPL_MMC_SUPPORT
612 select HAVE_BLOCK_DEVICE
614 Enable support for MMC (Multimedia Card) within SPL. This enables
615 the MMC protocol implementation and allows any enabled drivers to
616 be used within SPL. MMC can be used with or without disk partition
617 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
618 this option to build the drivers in drivers/mmc as part of an SPL
621 config SPL_FORCE_MMC_BOOT
622 bool "Force SPL booting from MMC"
623 depends on SPL_MMC_SUPPORT
626 Force SPL to use MMC device for Linux kernel booting even when the
627 SoC ROM recognized boot medium is not eMMC/SD. This is crucial for
628 factory or 'falcon mode' booting.
631 bool "Tiny MMC framework in SPL"
632 depends on SPL_MMC_SUPPORT
635 Enable MMC framework tinification support. This option is useful if
636 if your SPL is extremely size constrained. Heed the warning, enable
637 this option if and only if you know exactly what you are doing, if
638 you are reading this help text, you most likely have no idea :-)
640 The MMC framework is reduced to bare minimum to be useful. No malloc
641 support is needed for the MMC framework operation with this option
642 enabled. The framework supports exactly one MMC device and exactly
643 one MMC driver. The MMC driver can be adjusted to avoid any malloc
644 operations too, which can remove the need for malloc support in SPL
645 and thus further reduce footprint.
648 bool "MMC/SD/SDIO card support for write operations in SPL"
649 depends on SPL_MMC_SUPPORT
652 Enable write access to MMC and SD Cards in SPL
655 config SPL_MPC8XXX_INIT_DDR_SUPPORT
656 bool "Support MPC8XXX DDR init"
658 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
659 random-access memory) on the MPC8XXX family within SPL. This
660 allows DRAM to be set up before loading U-Boot into that DRAM,
663 config SPL_MTD_SUPPORT
664 bool "Support MTD drivers"
666 Enable support for MTD (Memory Technology Device) within SPL. MTD
667 provides a block interface over raw NAND and can also be used with
668 SPI flash. This allows SPL to load U-Boot from supported MTD
669 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
670 to enable specific MTD drivers.
672 config SPL_MUSB_NEW_SUPPORT
673 bool "Support new Mentor Graphics USB"
675 Enable support for Mentor Graphics USB in SPL. This is a new
676 driver used by some boards. Enable this option to build
677 the drivers in drivers/usb/musb-new as part of an SPL build. The
678 old drivers are in drivers/usb/musb.
680 config SPL_NAND_SUPPORT
681 bool "Support NAND flash"
683 Enable support for NAND (Negative AND) flash in SPL. NAND flash
684 can be used to allow SPL to load U-Boot from supported devices.
685 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
691 Enable support for loading payloads from UBI. See
692 README.ubispl for more info.
695 config SPL_UBI_LOAD_BY_VOLNAME
696 bool "Support loading volumes by name"
698 This enables support for loading UBI volumes by name. When this
699 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
700 configure the volume name from which to load U-Boot.
702 config SPL_UBI_MAX_VOL_LEBS
703 int "Maximum number of LEBs per volume"
706 The maximum number of logical eraseblocks which a static volume
707 to load can contain. Used for sizing the scan data structure.
709 config SPL_UBI_MAX_PEB_SIZE
710 int "Maximum PEB size"
713 The maximum physical erase block size.
715 config SPL_UBI_MAX_PEBS
716 int "Maximum number of PEBs"
719 The maximum physical erase block size. If not overridden by
720 board code, this value will be used as the actual number of PEBs.
722 config SPL_UBI_PEB_OFFSET
723 int "Offset to first UBI PEB"
726 The offset in number of PEBs from the start of flash to the first
727 PEB part of the UBI image.
729 config SPL_UBI_VID_OFFSET
730 int "Offset to VID header"
733 config SPL_UBI_LEB_START
734 int "Offset to LEB in PEB"
737 The offset in bytes to the LEB within a PEB.
739 config SPL_UBI_INFO_ADDR
740 hex "Address to place UBI scan info"
743 Address for ubispl to place the scan info. Read README.ubispl to
744 determine the required size
746 config SPL_UBI_VOL_IDS
747 int "Maximum volume id"
750 The maximum volume id which can be loaded. Used for sizing the
753 config SPL_UBI_LOAD_MONITOR_ID
754 int "id of U-Boot volume"
757 The UBI volume id from which to load U-Boot
759 config SPL_UBI_LOAD_MONITOR_VOLNAME
760 string "volume name of U-Boot volume"
761 depends on SPL_UBI_LOAD_BY_VOLNAME
763 The UBI volume name from which to load U-Boot
765 config SPL_UBI_LOAD_KERNEL_ID
766 int "id of kernel volume"
767 depends on SPL_OS_BOOT && SPL_UBI
769 The UBI volume id from which to load the kernel
771 config SPL_UBI_LOAD_ARGS_ID
772 int "id of kernel args volume"
773 depends on SPL_OS_BOOT && SPL_UBI
775 The UBI volume id from which to load the device tree
777 config UBI_SPL_SILENCE_MSG
778 bool "silence UBI SPL messages"
781 Disable messages from UBI SPL. This leaves warnings
786 config SPL_NET_SUPPORT
787 bool "Support networking"
789 Enable support for network devices (such as Ethernet) in SPL.
790 This permits SPL to load U-Boot over a network link rather than
791 from an on-board peripheral. Environment support is required since
792 the network stack uses a number of environment variables. See also
796 config SPL_NET_VCI_STRING
797 string "BOOTP Vendor Class Identifier string sent by SPL"
799 As defined by RFC 2132 the vendor class identifier field can be
800 sent by the client to identify the vendor type and configuration
801 of a client. This is often used in practice to allow for the DHCP
802 server to specify different files to load depending on if the ROM,
803 SPL or U-Boot itself makes the request
804 endif # if SPL_NET_SUPPORT
806 config SPL_NO_CPU_SUPPORT
807 bool "Drop CPU code in SPL"
809 This is specific to the ARM926EJ-S CPU. It disables the standard
810 start.S start-up code, presumably so that a replacement can be
811 used on that CPU. You should not enable it unless you know what
814 config SPL_NOR_SUPPORT
815 bool "Support NOR flash"
817 Enable support for loading U-Boot from memory-mapped NOR (Negative
818 OR) flash in SPL. NOR flash is slow to write but fast to read, and
819 a memory-mapped device makes it very easy to access. Loading from
820 NOR is typically achieved with just a memcpy().
822 config SPL_XIP_SUPPORT
826 Enable support for execute in place of U-Boot or kernel image. There
827 is no need to copy image from flash to ram if flash supports execute
828 in place. Its very useful in systems having enough flash but not
829 enough ram to load the image.
831 config SPL_ONENAND_SUPPORT
832 bool "Support OneNAND flash"
834 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
835 a type of NAND flash and therefore can be used to allow SPL to
836 load U-Boot from supported devices. This enables the drivers in
837 drivers/mtd/onenand as part of an SPL build.
840 bool "Activate Falcon Mode"
841 depends on !TI_SECURE_DEVICE
844 Enable booting directly to an OS from SPL.
845 for more info read doc/README.falcon
849 hex "addr, where OS is found"
850 depends on SPL_NOR_SUPPORT
852 Specify the address, where the OS image is found, which
859 default "tpl/u-boot-with-tpl.bin" if TPL
862 Payload for SPL boot. For backward compatibility, default to
863 u-boot.bin, i.e. RAW image without any header. In case of
864 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
868 bool "Support PCI drivers"
870 Enable support for PCI in SPL. For platforms that need PCI to boot,
871 or must perform some init using PCI in SPL, this provides the
872 necessary driver support. This enables the drivers in drivers/pci
873 as part of an SPL build.
875 config SPL_PCH_SUPPORT
876 bool "Support PCH drivers"
878 Enable support for PCH (Platform Controller Hub) devices in SPL.
879 These are used to set up GPIOs and the SPI peripheral early in
880 boot. This enables the drivers in drivers/pch as part of an SPL
883 config SPL_POST_MEM_SUPPORT
884 bool "Support POST drivers"
886 Enable support for POST (Power-on Self Test) in SPL. POST is a
887 procedure that checks that the hardware (CPU or board) appears to
888 be functionally correctly. It is a sanity check that can be
889 performed before booting. This enables the drivers in post/drivers
890 as part of an SPL build.
893 bool "Support reset drivers"
896 Enable support for reset control in SPL.
897 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
898 by using the generic reset API provided by driver model.
899 This enables the drivers in drivers/reset as part of an SPL build.
901 config SPL_POWER_SUPPORT
902 bool "Support power drivers"
904 Enable support for power control in SPL. This includes support
905 for PMICs (Power-management Integrated Circuits) and some of the
906 features provided by PMICs. In particular, voltage regulators can
907 be used to enable/disable power and vary its voltage. That can be
908 useful in SPL to turn on boot peripherals and adjust CPU voltage
909 so that the clock speed can be increased. This enables the drivers
910 in drivers/power, drivers/power/pmic and drivers/power/regulator
911 as part of an SPL build.
913 config SPL_POWER_DOMAIN
914 bool "Support power domain drivers"
916 Enable support for power domain control in SPL. Many SoCs allow
917 power to be applied to or removed from portions of the SoC (power
918 domains). This may be used to save power. This API provides the
919 means to control such power management hardware. This enables
920 the drivers in drivers/power/domain as part of a SPL build.
922 config SPL_RAM_SUPPORT
923 bool "Support booting from RAM"
924 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
926 Enable booting of an image in RAM. The image can be preloaded or
927 it can be loaded by SPL directly into RAM (e.g. using USB).
929 config SPL_RAM_DEVICE
930 bool "Support booting from preloaded image in RAM"
931 depends on SPL_RAM_SUPPORT
932 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
934 Enable booting of an image already loaded in RAM. The image has to
935 be already in memory when SPL takes over, e.g. loaded by the boot
938 config SPL_REMOTEPROC
939 bool "Support REMOTEPROCS"
941 Enable support for REMOTEPROCs in SPL. This permits to load
942 a remote processor firmware in SPL.
944 config SPL_RTC_SUPPORT
945 bool "Support RTC drivers"
947 Enable RTC (Real-time Clock) support in SPL. This includes support
948 for reading and setting the time. Some RTC devices also have some
949 non-volatile (battery-backed) memory which is accessible if
950 needed. This enables the drivers in drivers/rtc as part of an SPL
953 config SPL_SATA_SUPPORT
954 bool "Support loading from SATA"
956 Enable support for SATA (Serial AT attachment) in SPL. This allows
957 use of SATA devices such as hard drives and flash drivers for
958 loading U-Boot. SATA is used in higher-end embedded systems and
959 can provide higher performance than MMC , at somewhat higher
960 expense and power consumption. This enables loading from SATA
961 using a configured device.
963 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
964 bool "SATA raw mode: by sector"
965 depends on SPL_SATA_SUPPORT
967 Use sector number for specifying U-Boot location on SATA disk in
970 config SPL_SATA_RAW_U_BOOT_SECTOR
971 hex "Sector on the SATA disk to load U-Boot from"
972 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
974 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
975 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
977 config SPL_SERIAL_SUPPORT
978 bool "Support serial"
982 Enable support for serial in SPL. This allows use of a serial UART
983 for displaying messages while SPL is running. It also brings in
984 printf() and panic() functions. This should normally be enabled
985 unless there are space reasons not to. Even then, consider
986 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
988 config SPL_SPI_FLASH_SUPPORT
989 bool "Support SPI flash drivers"
991 Enable support for using SPI flash in SPL, and loading U-Boot from
992 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
993 the SPI bus that is used to connect it to a system. It is a simple
994 but fast bidirectional 4-wire bus (clock, chip select and two data
995 lines). This enables the drivers in drivers/mtd/spi as part of an
996 SPL build. This normally requires SPL_SPI_SUPPORT.
998 if SPL_SPI_FLASH_SUPPORT
1000 config SPL_SPI_FLASH_TINY
1001 bool "Enable low footprint SPL SPI Flash support"
1002 depends on !SPI_FLASH_BAR
1003 default y if SPI_FLASH
1005 Enable lightweight SPL SPI Flash support that supports just reading
1006 data/images from flash. No support to write/erase flash. Enable
1007 this if you have SPL size limitations and don't need full
1008 fledged SPI flash support.
1010 config SPL_SPI_FLASH_SFDP_SUPPORT
1011 bool "SFDP table parsing support for SPI NOR flashes"
1012 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1014 Enable support for parsing and auto discovery of parameters for
1015 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1016 tables as per JESD216 standard in SPL.
1019 bool "Support loading from SPI flash"
1021 Enable support for loading next stage, U-Boot or otherwise, from
1022 SPI NOR in U-Boot SPL.
1024 endif # SPL_SPI_FLASH_SUPPORT
1026 config SYS_SPI_U_BOOT_OFFS
1027 hex "address of u-boot payload in SPI flash"
1029 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1031 Address within SPI-Flash from where the u-boot payload is fetched
1034 config SPL_SPI_SUPPORT
1035 bool "Support SPI drivers"
1037 Enable support for using SPI in SPL. This is used for connecting
1038 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1039 more details on that. The SPI driver provides the transport for
1040 data between the SPI flash and the CPU. This option can be used to
1041 enable SPI drivers that are needed for other purposes also, such
1045 bool "Driver support for thermal devices"
1047 Enable support for temperature-sensing devices. Some SoCs have on-chip
1048 temperature sensors to permit warnings, speed throttling or even
1049 automatic power-off when the temperature gets too high or low. Other
1050 devices may be discrete but connected on a suitable bus.
1052 config SPL_USB_HOST_SUPPORT
1053 bool "Support USB host drivers"
1054 select HAVE_BLOCK_DEVICE
1056 Enable access to USB (Universal Serial Bus) host devices so that
1057 SPL can load U-Boot from a connected USB peripheral, such as a USB
1058 flash stick. While USB takes a little longer to start up than most
1059 buses, it is very flexible since many different types of storage
1060 device can be attached. This option enables the drivers in
1061 drivers/usb/host as part of an SPL build.
1063 config SPL_USB_STORAGE
1064 bool "Support loading from USB"
1065 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1067 Enable support for USB devices in SPL. This allows use of USB
1068 devices such as hard drives and flash drivers for loading U-Boot.
1069 The actual drivers are enabled separately using the normal U-Boot
1070 config options. This enables loading from USB using a configured
1073 config SPL_USB_GADGET
1074 bool "Suppport USB Gadget drivers"
1076 Enable USB Gadget API which allows to enable USB device functions
1081 config SPL_USB_ETHER
1082 bool "Support USB Ethernet drivers"
1084 Enable access to the USB network subsystem and associated
1085 drivers in SPL. This permits SPL to load U-Boot over a
1086 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1087 than from an onboard peripheral. Environment support is required
1088 since the network stack uses a number of environment variables.
1089 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1092 bool "Support DFU (Device Firmware Upgrade)"
1093 select SPL_HASH_SUPPORT
1094 select SPL_DFU_NO_RESET
1095 depends on SPL_RAM_SUPPORT
1097 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1098 RAM memory device support. The ROM code will load and execute
1099 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1100 selected device partition from host-pc using dfu-utils.
1101 This feature is useful to flash the binaries to factory or bare-metal
1102 boards using USB interface.
1105 bool "DFU device selection"
1110 depends on SPL_DFU && SPL_RAM_SUPPORT
1112 select RAM/DDR memory device for loading binary images
1113 (u-boot/kernel) to the selected device partition using
1114 DFU and execute the u-boot/kernel from RAM.
1118 config SPL_USB_SDP_SUPPORT
1119 bool "Support SDP (Serial Download Protocol)"
1121 Enable Serial Download Protocol (SDP) device support in SPL. This
1122 allows to download images into memory and execute (jump to) them
1123 using the same protocol as implemented by the i.MX family's boot ROM.
1126 config SPL_WATCHDOG_SUPPORT
1127 bool "Support watchdog drivers"
1128 imply SPL_WDT if !HW_WATCHDOG
1130 Enable support for watchdog drivers in SPL. A watchdog is
1131 typically a hardware peripheral which can reset the system when it
1132 detects no activity for a while (such as a software crash). This
1133 enables the drivers in drivers/watchdog as part of an SPL build.
1135 config SPL_YMODEM_SUPPORT
1136 bool "Support loading using Ymodem"
1137 depends on SPL_SERIAL_SUPPORT
1139 While loading from serial is slow it can be a useful backup when
1140 there is no other option. The Ymodem protocol provides a reliable
1141 means of transmitting U-Boot over a serial line for using in SPL,
1142 with a checksum to ensure correctness.
1145 bool "Support ARM Trusted Firmware"
1148 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1149 is loaded by SPL (which is considered as BL2 in ATF terminology).
1150 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1152 config SPL_ATF_NO_PLATFORM_PARAM
1153 bool "Pass no platform parameter"
1156 While we expect to call a pointer to a valid FDT (or NULL)
1157 as the platform parameter to an ATF, some ATF versions are
1158 not U-Boot aware and have an insufficiently robust parameter
1159 validation to gracefully reject a FDT being passed.
1161 If this option is enabled, the spl_atf os-type handler will
1162 always pass NULL for the platform parameter.
1164 If your ATF is affected, say Y.
1166 config SPL_AM33XX_ENABLE_RTC32K_OSC
1167 bool "Enable the RTC32K OSC on AM33xx based platforms"
1170 Enable access to the AM33xx RTC and select the external 32kHz clock
1174 bool "Support OP-TEE Trusted OS"
1177 OP-TEE is an open source Trusted OS which is loaded by SPL.
1178 More detail at: https://github.com/OP-TEE/optee_os
1181 bool "Support RISC-V OpenSBI"
1182 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1184 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1185 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1186 firmware. It is loaded and started by U-Boot SPL.
1188 More details are available at https://github.com/riscv/opensbi and
1189 https://github.com/riscv/riscv-sbi-doc
1191 config SPL_OPENSBI_LOAD_ADDR
1192 hex "OpenSBI load address"
1193 depends on SPL_OPENSBI
1195 Load address of the OpenSBI binary.
1199 depends on SUPPORT_TPL
1202 If you want to build TPL as well as the normal image and SPL, say Y.
1207 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1208 depends on HANDOFF && TPL_BLOBLIST
1211 This option enables TPL to write handoff information. This can be
1212 used to pass information like the size of SDRAM from TPL to U-Boot
1213 proper. The information is also available to SPL if it is useful
1216 config TPL_BOARD_INIT
1217 bool "Call board-specific initialization in TPL"
1219 If this option is enabled, U-Boot will call the function
1220 spl_board_init() from board_init_r(). This function should be
1221 provided by the board.
1224 string "Linker script for the TPL stage"
1226 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1227 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1229 The TPL stage will usually require a different linker-script
1230 (as it runs from a different memory region) than the regular
1231 U-Boot stage. Set this to the path of the linker-script to
1234 May be left empty to trigger the Makefile infrastructure to
1235 fall back to the linker-script used for the SPL stage.
1237 config TPL_NEEDS_SEPARATE_TEXT_BASE
1238 bool "TPL needs a separate text-base"
1242 Enable, if the TPL stage should not inherit its text-base
1243 from the SPL stage. When enabled, a base address for the
1244 .text sections of the TPL stage has to be set below.
1246 config TPL_NEEDS_SEPARATE_STACK
1247 bool "TPL needs a separate initial stack-pointer"
1251 Enable, if the TPL stage should not inherit its initial
1252 stack-pointer from the settings for the SPL stage.
1254 config TPL_TEXT_BASE
1255 hex "Base address for the .text section of the TPL stage"
1256 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1258 The base address for the .text section of the TPL stage.
1261 int "Maximum size (in bytes) for the TPL stage"
1265 The maximum size (in bytes) of the TPL stage.
1268 hex "Address of the initial stack-pointer for the TPL stage"
1269 depends on TPL_NEEDS_SEPARATE_STACK
1271 The address of the initial stack-pointer for the TPL stage.
1272 Usually this will be the (aligned) top-of-stack.
1274 config TPL_BOOTROM_SUPPORT
1275 bool "Support returning to the BOOTROM (from TPL)"
1277 Some platforms (e.g. the Rockchip RK3368) provide support in their
1278 ROM for loading the next boot-stage after performing basic setup
1281 Enable this option, to return to the BOOTROM through the
1282 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1283 boot device list, if not implemented for a given board)
1285 config TPL_DRIVERS_MISC_SUPPORT
1286 bool "Support misc drivers in TPL"
1288 Enable miscellaneous drivers in TPL. These drivers perform various
1289 tasks that don't fall nicely into other categories, Enable this
1290 option to build the drivers in drivers/misc as part of an TPL
1291 build, for those that support building in TPL (not all drivers do).
1293 config TPL_ENV_SUPPORT
1294 bool "Support an environment"
1296 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1298 config TPL_GPIO_SUPPORT
1299 bool "Support GPIO in TPL"
1301 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1302 GPIOs allow U-Boot to read the state of an input line (high or
1303 low) and set the state of an output line. This can be used to
1304 drive LEDs, control power to various system parts and read user
1305 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1306 for example. Enable this option to build the drivers in
1307 drivers/gpio as part of an TPL build.
1309 config TPL_I2C_SUPPORT
1312 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1315 config TPL_LIBCOMMON_SUPPORT
1316 bool "Support common libraries"
1318 Enable support for common U-Boot libraries within TPL. See
1319 SPL_LIBCOMMON_SUPPORT for details.
1321 config TPL_LIBGENERIC_SUPPORT
1322 bool "Support generic libraries"
1324 Enable support for generic U-Boot libraries within TPL. See
1325 SPL_LIBGENERIC_SUPPORT for details.
1327 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1328 bool "Support MPC8XXX DDR init"
1330 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1331 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1333 config TPL_MMC_SUPPORT
1337 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1339 config TPL_NAND_SUPPORT
1340 bool "Support NAND flash"
1342 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1345 bool "Support PCI drivers"
1347 Enable support for PCI in TPL. For platforms that need PCI to boot,
1348 or must perform some init using PCI in SPL, this provides the
1349 necessary driver support. This enables the drivers in drivers/pci
1350 as part of a TPL build.
1352 config TPL_PCH_SUPPORT
1353 bool "Support PCH drivers"
1355 Enable support for PCH (Platform Controller Hub) devices in TPL.
1356 These are used to set up GPIOs and the SPI peripheral early in
1357 boot. This enables the drivers in drivers/pch as part of a TPL
1360 config TPL_RAM_SUPPORT
1361 bool "Support booting from RAM"
1363 Enable booting of an image in RAM. The image can be preloaded or
1364 it can be loaded by TPL directly into RAM (e.g. using USB).
1366 config TPL_RAM_DEVICE
1367 bool "Support booting from preloaded image in RAM"
1368 depends on TPL_RAM_SUPPORT
1370 Enable booting of an image already loaded in RAM. The image has to
1371 be already in memory when TPL takes over, e.g. loaded by the boot
1374 config TPL_RTC_SUPPORT
1375 bool "Support RTC drivers"
1377 Enable RTC (Real-time Clock) support in TPL. This includes support
1378 for reading and setting the time. Some RTC devices also have some
1379 non-volatile (battery-backed) memory which is accessible if
1380 needed. This enables the drivers in drivers/rtc as part of an TPL
1383 config TPL_SERIAL_SUPPORT
1384 bool "Support serial"
1388 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1391 config TPL_SPI_FLASH_SUPPORT
1392 bool "Support SPI flash drivers"
1394 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1398 bool "Support loading from SPI flash"
1399 depends on TPL_SPI_FLASH_SUPPORT
1401 Enable support for loading next stage, U-Boot or otherwise, from
1402 SPI NOR in U-Boot TPL.
1404 config TPL_SPI_SUPPORT
1405 bool "Support SPI drivers"
1407 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1410 config TPL_YMODEM_SUPPORT
1411 bool "Support loading using Ymodem"
1412 depends on TPL_SERIAL_SUPPORT
1414 While loading from serial is slow it can be a useful backup when
1415 there is no other option. The Ymodem protocol provides a reliable
1416 means of transmitting U-Boot over a serial line for using in TPL,
1417 with a checksum to ensure correctness.
1421 config SPL_AT91_MCK_BYPASS
1422 bool "Use external clock signal as a source of main clock for AT91 platforms"
1423 depends on ARCH_AT91
1426 Use external 8 to 24 Mhz clock signal as source of main clock instead
1427 of an external crystal oscillator.
1428 This option disables the internal driving on the XOUT pin.
1429 The external source has to provide a stable clock on the XIN pin.
1430 If this option is disabled, the SoC expects a crystal oscillator
1431 that needs driving on both XIN and XOUT lines.