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.
21 bool "Call board-specific initialization in SPL"
23 If this option is enabled, U-Boot will call the function
24 spl_board_init() from board_init_r(). This function should be
25 provided by the board.
27 config SPL_RAW_IMAGE_SUPPORT
28 bool "Support SPL loading and booting of RAW images"
30 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
31 default y if !TI_SECURE_DEVICE
33 SPL will support loading and booting a RAW image when this option
34 is y. If this is not set, SPL will move on to other available
35 boot media to find a suitable image.
37 config SPL_LEGACY_IMAGE_SUPPORT
38 bool "Support SPL loading and booting of Legacy images"
39 default y if !TI_SECURE_DEVICE
41 SPL will support loading and booting Legacy images when this option
42 is y. If this is not set, SPL will move on to other available
43 boot media to find a suitable image.
45 config SPL_SYS_MALLOC_SIMPLE
48 prompt "Only use malloc_simple functions in the SPL"
50 Say Y here to only use the *_simple malloc functions from
51 malloc_simple.c, rather then using the versions from dlmalloc.c;
52 this will make the SPL binary smaller at the cost of more heap
53 usage as the *_simple malloc functions do not re-use free-ed mem.
57 bool "Enable SDRAM location for SPL stack"
59 SPL starts off execution in SRAM and thus typically has only a small
60 stack available. Since SPL sets up DRAM while in its board_init_f()
61 function, it is possible for the stack to move there before
62 board_init_r() is reached. This option enables a special SDRAM
63 location for the SPL stack. U-Boot SPL switches to this after
64 board_init_f() completes, and before board_init_r() starts.
66 config SPL_STACK_R_ADDR
67 depends on SPL_STACK_R
68 hex "SDRAM location for SPL stack"
70 Specify the address in SDRAM for the SPL stack. This will be set up
71 before board_init_r() is called.
73 config SPL_STACK_R_MALLOC_SIMPLE_LEN
74 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
75 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
78 Specify the amount of the stack to use as memory pool for
79 malloc_simple after switching the stack to DRAM. This may be set
80 to give board_init_r() a larger heap then the initial heap in
81 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
83 config SPL_SEPARATE_BSS
85 bool "BSS section is in a different memory region from text"
87 Some platforms need a large BSS region in SPL and can provide this
88 because RAM is already set up. In this case BSS can be moved to RAM.
89 This option should then be enabled so that the correct device tree
90 location is used. Normally we put the device tree at the end of BSS
91 but with this option enabled, it goes at _image_binary_end.
93 config SPL_DISPLAY_PRINT
95 bool "Display a board-specific message in SPL"
97 If this option is enabled, U-Boot will call the function
98 spl_display_print() immediately after displaying the SPL console
99 banner ("U-Boot SPL ..."). This function should be provided by
102 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
103 bool "MMC raw mode: by sector"
105 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER ||ARCH_MX6 || \
106 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
107 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
108 OMAP44XX || OMAP54XX || AM33XX || AM43XX
110 Use sector number for specifying U-Boot location on MMC/SD in
113 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
114 hex "Address on the MMC to load U-Boot from"
115 depends on SPL && SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
116 default 0x50 if ARCH_SUNXI
117 default 0x75 if ARCH_DAVINCI
118 default 0x8a if ARCH_MX6
119 default 0x100 if ARCH_ROCKCHIP || ARCH_UNIPHIER
120 default 0x140 if ARCH_MVEBU
121 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
122 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
123 OMAP54XX || AM33XX || AM43XX
125 Address on the MMC to load U-Boot from, when the MMC is being used
126 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
128 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
129 bool "MMC Raw mode: by partition"
132 Use a partition for loading U-Boot when using MMC/SD in raw mode.
134 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
135 hex "Partition to use to load U-Boot from"
136 depends on SPL && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
139 Partition on the MMC to load U-Boot from when the MMC is being
142 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
143 bool "MMC raw mode: by partition type"
144 depends on SPL && DOS_PARTITION && \
145 SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
147 Use partition type for specifying U-Boot partition on MMC/SD in
148 raw mode. U-Boot will be loaded from the first partition of this
151 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
152 hex "Partition Type on the MMC to load U-Boot from"
153 depends on SPL && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
155 Partition Type on the MMC to load U-Boot from, when the MMC is being
160 depends on SPL && SUPPORT_TPL
163 If you want to build TPL as well as the normal image and SPL, say Y.
165 config SPL_CRC32_SUPPORT
169 Enable this to support CRC32 in FIT images within SPL. This is a
170 32-bit checksum value that can be used to verify images. This is
171 the least secure type of checksum, suitable for detected
172 accidental image corruption. For secure applications you should
173 consider SHA1 or SHA256.
175 config SPL_MD5_SUPPORT
179 Enable this to support MD5 in FIT images within SPL. An MD5
180 checksum is a 128-bit hash value used to check that the image
181 contents have not been corrupted. Note that MD5 is not considered
182 secure as it is possible (with a brute-force attack) to adjust the
183 image while still retaining the same MD5 hash value. For secure
184 applications where images may be changed maliciously, you should
185 consider SHA1 or SHA256.
187 config SPL_SHA1_SUPPORT
192 Enable this to support SHA1 in FIT images within SPL. A SHA1
193 checksum is a 160-bit (20-byte) hash value used to check that the
194 image contents have not been corrupted or maliciously altered.
195 While SHA1 is fairly secure it is coming to the end of its life
196 due to the expanding computing power avaiable to brute-force
197 attacks. For more security, consider SHA256.
199 config SPL_SHA256_SUPPORT
200 bool "Support SHA256"
204 Enable this to support SHA256 in FIT images within SPL. A SHA256
205 checksum is a 256-bit (32-byte) hash value used to check that the
206 image contents have not been corrupted. SHA256 is recommended for
207 use in secure applications since (as at 2016) there is no known
208 feasible attack that could produce a 'collision' with differing
209 input data. Use this for the highest security. Note that only the
210 SHA256 variant is supported: SHA512 and others are not currently
213 config SPL_CPU_SUPPORT
214 bool "Support CPU drivers"
217 Enable this to support CPU drivers in SPL. These drivers can set
218 up CPUs and provide information about them such as the model and
219 name. This can be useful in SPL since setting up the CPUs earlier
220 may improve boot performance. Enable this option to build the
221 drivers in drivers/cpu as part of an SPL build.
223 config SPL_CRYPTO_SUPPORT
224 bool "Support crypto drivers"
227 Enable crypto drivers in SPL. These drivers can be used to
228 accelerate secure boot processing in secure applications. Enable
229 this option to build the drivers in drivers/crypto as part of an
232 config SPL_HASH_SUPPORT
233 bool "Support hashing drivers"
238 Enable hashing drivers in SPL. These drivers can be used to
239 accelerate secure boot processing in secure applications. Enable
240 this option to build system-specific drivers for hash acceleration
241 as part of an SPL build.
243 config SPL_DMA_SUPPORT
244 bool "Support DMA drivers"
247 Enable DMA (direct-memory-access) drivers in SPL. These drivers
248 can be used to handle memory-to-peripheral data transfer without
249 the CPU moving the data. Enable this option to build the drivers
250 in drivers/dma as part of an SPL build.
252 config SPL_DRIVERS_MISC_SUPPORT
253 bool "Support misc drivers"
256 Enable miscellaneous drivers in SPL. These drivers perform various
257 tasks that don't fall nicely into other categories, Enable this
258 option to build the drivers in drivers/misc as part of an SPL
259 build, for those that support building in SPL (not all drivers do).
261 config SPL_ENV_SUPPORT
262 bool "Support an environment"
265 Enable environment support in SPL. The U-Boot environment provides
266 a number of settings (essentially name/value pairs) which can
267 control many aspects of U-Boot's operation. Normally this is not
268 needed in SPL as it has a much simpler task with less
269 configuration. But some boards use this to support 'Falcon' boot
270 on EXT2 and FAT, where SPL boots directly into Linux without
271 starting U-Boot first. Enabling this option will make getenv()
272 and setenv() available in SPL.
275 bool "Support save environment"
276 depends on SPL && SPL_ENV_SUPPORT
278 Enable save environment support in SPL after setenv. By default
279 the saveenv option is not provided in SPL, but some boards need
280 this support in 'Falcon' boot, where SPL need to boot from
281 different images based on environment variable set by OS. For
282 example OS may set "reboot_image" environment variable to
283 "recovery" inorder to boot recovery image by SPL. The SPL read
284 "reboot_image" and act accordingly and change the reboot_image
285 to default mode using setenv and save the environemnt.
287 config SPL_ETH_SUPPORT
288 bool "Support Ethernet"
289 depends on SPL_ENV_SUPPORT
291 Enable access to the network subsystem and associated Ethernet
292 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
293 link rather than from an on-board peripheral. Environment support
294 is required since the network stack uses a number of environment
295 variables. See also SPL_NET_SUPPORT.
297 config SPL_EXT_SUPPORT
298 bool "Support EXT filesystems"
301 Enable support for EXT2/3/4 filesystems with SPL. This permits
302 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
303 filesystem from within SPL. Support for the underlying block
304 device (e.g. MMC or USB) must be enabled separately.
306 config SPL_FAT_SUPPORT
307 bool "Support FAT filesystems"
310 Enable support for FAT and VFAT filesystems with SPL. This
311 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
312 filesystem from within SPL. Support for the underlying block
313 device (e.g. MMC or USB) must be enabled separately.
315 config SPL_FPGA_SUPPORT
319 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
320 provide software-configurable hardware which is typically used to
321 implement peripherals (such as UARTs, LCD displays, MMC) or
322 accelerate custom processing functions, such as image processing
323 or machine learning. Sometimes it is useful to program the FPGA
324 as early as possible during boot, and this option can enable that
327 config SPL_GPIO_SUPPORT
331 Enable support for GPIOs (General-purpose Input/Output) in SPL.
332 GPIOs allow U-Boot to read the state of an input line (high or
333 low) and set the state of an output line. This can be used to
334 drive LEDs, control power to various system parts and read user
335 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
336 for example. Enable this option to build the drivers in
337 drivers/gpio as part of an SPL build.
339 config SPL_I2C_SUPPORT
343 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
344 I2C works with a clock and data line which can be driven by a
345 one or more masters or slaves. It is a fairly complex bus but is
346 widely used as it only needs two lines for communication. Speeds of
347 400kbps are typical but up to 3.4Mbps is supported by some
348 hardware. I2C can be useful in SPL to configure power management
349 ICs (PMICs) before raising the CPU clock speed, for example.
350 Enable this option to build the drivers in drivers/i2c as part of
353 config SPL_LIBCOMMON_SUPPORT
354 bool "Support common libraries"
357 Enable support for common U-Boot libraries within SPL. These
358 libraries include common code to deal with U-Boot images,
359 environment and USB, for example. This option is enabled on many
360 boards. Enable this option to build the code in common/ as part of
363 config SPL_LIBDISK_SUPPORT
364 bool "Support disk paritions"
367 Enable support for disk partitions within SPL. 'Disk' is something
368 of a misnomer as it includes non-spinning media such as flash (as
369 used in MMC and USB sticks). Partitions provide a way for a disk
370 to be split up into separate regions, with a partition table placed
371 at the start or end which describes the location and size of each
372 'partition'. These partitions are typically uses as individual block
373 devices, typically with an EXT2 or FAT filesystem in each. This
374 option enables whatever partition support has been enabled in
375 U-Boot to also be used in SPL. It brings in the code in disk/.
377 config SPL_LIBGENERIC_SUPPORT
378 bool "Support generic libraries"
381 Enable support for generic U-Boot libraries within SPL. These
382 libraries include generic code to deal with device tree, hashing,
383 printf(), compression and the like. This option is enabled on many
384 boards. Enable this option to build the code in lib/ as part of an
387 config SPL_MMC_SUPPORT
389 depends on SPL && MMC
391 Enable support for MMC (Multimedia Card) within SPL. This enables
392 the MMC protocol implementation and allows any enabled drivers to
393 be used within SPL. MMC can be used with or without disk partition
394 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
395 this option to build the drivers in drivers/mmc as part of an SPL
398 config SPL_MPC8XXX_INIT_DDR_SUPPORT
399 bool "Support MPC8XXX DDR init"
402 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
403 random-access memory) on the MPC8XXX family within SPL. This
404 allows DRAM to be set up before loading U-Boot into that DRAM,
407 config SPL_MTD_SUPPORT
408 bool "Support MTD drivers"
411 Enable support for MTD (Memory Technology Device) within SPL. MTD
412 provides a block interface over raw NAND and can also be used with
413 SPI flash. This allows SPL to load U-Boot from supported MTD
414 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
415 to enable specific MTD drivers.
417 config SPL_MUSB_NEW_SUPPORT
418 bool "Support new Mentor Graphics USB"
421 Enable support for Mentor Graphics USB in SPL. This is a new
422 driver used by some boards. Enable this option to build
423 the drivers in drivers/usb/musb-new as part of an SPL build. The
424 old drivers are in drivers/usb/musb.
426 config SPL_NAND_SUPPORT
427 bool "Support NAND flash"
430 Enable support for NAND (Negative AND) flash in SPL. NAND flash
431 can be used to allow SPL to load U-Boot from supported devices.
432 This enables the drivers in drivers/mtd/nand as part of an SPL
435 config SPL_NET_SUPPORT
436 bool "Support networking"
439 Enable support for network devices (such as Ethernet) in SPL.
440 This permits SPL to load U-Boot over a network link rather than
441 from an on-board peripheral. Environment support is required since
442 the network stack uses a number of environment variables. See also
446 config SPL_NET_VCI_STRING
447 string "BOOTP Vendor Class Identifier string sent by SPL"
449 As defined by RFC 2132 the vendor class identifier field can be
450 sent by the client to identify the vendor type and configuration
451 of a client. This is often used in practice to allow for the DHCP
452 server to specify different files to load depending on if the ROM,
453 SPL or U-Boot itself makes the request
454 endif # if SPL_NET_SUPPORT
456 config SPL_NO_CPU_SUPPORT
457 bool "Drop CPU code in SPL"
460 This is specific to the ARM926EJ-S CPU. It disables the standard
461 start.S start-up code, presumably so that a replacement can be
462 used on that CPU. You should not enable it unless you know what
465 config SPL_NOR_SUPPORT
466 bool "Support NOR flash"
469 Enable support for loading U-Boot from memory-mapped NOR (Negative
470 OR) flash in SPL. NOR flash is slow to write but fast to read, and
471 a memory-mapped device makes it very easy to access. Loading from
472 NOR is typically achieved with just a memcpy().
474 config SPL_ONENAND_SUPPORT
475 bool "Support OneNAND flash"
478 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
479 a type of NAND flash and therefore can be used to allow SPL to
480 load U-Boot from supported devices. This enables the drivers in
481 drivers/mtd/onenand as part of an SPL build.
484 bool "Activate Falcon Mode"
485 depends on SPL && !TI_SECURE_DEVICE
488 Enable booting directly to an OS from SPL.
489 for more info read doc/README.falcon
493 hex "addr, where OS is found"
494 depends on SPL && SPL_NOR_SUPPORT
496 Specify the address, where the OS image is found, which
501 config SPL_PCI_SUPPORT
502 bool "Support PCI drivers"
505 Enable support for PCI in SPL. For platforms that need PCI to boot,
506 or must perform some init using PCI in SPL, this provides the
507 necessary driver support. This enables the drivers in drivers/pci
508 as part of an SPL build.
510 config SPL_PCH_SUPPORT
511 bool "Support PCH drivers"
514 Enable support for PCH (Platform Controller Hub) devices in SPL.
515 These are used to set up GPIOs and the SPI peripheral early in
516 boot. This enables the drivers in drivers/pch as part of an SPL
519 config SPL_POST_MEM_SUPPORT
520 bool "Support POST drivers"
523 Enable support for POST (Power-on Self Test) in SPL. POST is a
524 procedure that checks that the hardware (CPU or board) appears to
525 be functionally correctly. It is a sanity check that can be
526 performed before booting. This enables the drivers in post/drivers
527 as part of an SPL build.
529 config SPL_POWER_SUPPORT
530 bool "Support power drivers"
533 Enable support for power control in SPL. This includes support
534 for PMICs (Power-management Integrated Circuits) and some of the
535 features provided by PMICs. In particular, voltage regulators can
536 be used to enable/disable power and vary its voltage. That can be
537 useful in SPL to turn on boot peripherals and adjust CPU voltage
538 so that the clock speed can be increased. This enables the drivers
539 in drivers/power, drivers/power/pmic and drivers/power/regulator
540 as part of an SPL build.
542 config SPL_RAM_SUPPORT
543 bool "Support booting from RAM"
545 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
547 Enable booting of an image in RAM. The image can be preloaded or
548 it can be loaded by SPL directly into RAM (e.g. using USB).
550 config SPL_RAM_DEVICE
551 bool "Support booting from preloaded image in RAM"
552 depends on SPL_RAM_SUPPORT
553 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
555 Enable booting of an image already loaded in RAM. The image has to
556 be already in memory when SPL takes over, e.g. loaded by the boot
559 config SPL_RTC_SUPPORT
560 bool "Support RTC drivers"
563 Enable RTC (Real-time Clock) support in SPL. This includes support
564 for reading and setting the time. Some RTC devices also have some
565 non-volatile (battery-backed) memory which is accessible if
566 needed. This enables the drivers in drivers/rtc as part of an SPL
569 config SPL_SATA_SUPPORT
570 bool "Support loading from SATA"
573 Enable support for SATA (Serial AT attachment) in SPL. This allows
574 use of SATA devices such as hard drives and flash drivers for
575 loading U-Boot. SATA is used in higher-end embedded systems and
576 can provide higher performance than MMC , at somewhat higher
577 expense and power consumption. This enables loading from SATA
578 using a configured device.
580 config SPL_SERIAL_SUPPORT
581 bool "Support serial"
584 Enable support for serial in SPL. This allows use of a serial UART
585 for displaying messages while SPL is running. It also brings in
586 printf() and panic() functions. This should normally be enabled
587 unless there are space reasons not to. Even then, consider
588 enabling USE_TINY_PRINTF which is a small printf() version.
590 config SPL_SPI_FLASH_SUPPORT
591 bool "Support SPI flash drivers"
594 Enable support for using SPI flash in SPL, and loading U-Boot from
595 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
596 the SPI bus that is used to connect it to a system. It is a simple
597 but fast bidirectional 4-wire bus (clock, chip select and two data
598 lines). This enables the drivers in drivers/mtd/spi as part of an
599 SPL build. This normally requires SPL_SPI_SUPPORT.
601 config SPL_SPI_SUPPORT
602 bool "Support SPI drivers"
605 Enable support for using SPI in SPL. This is used for connecting
606 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
607 more details on that. The SPI driver provides the transport for
608 data between the SPI flash and the CPU. This option can be used to
609 enable SPI drivers that are needed for other purposes also, such
612 config SPL_TIMER_SUPPORT
613 bool "Support timer drivers"
616 Enable support for timer drivers in SPL. These can be used to get
617 a timer value when in SPL, or perhaps for implementing a delay
618 function. This enables the drivers in drivers/timer as part of an
621 config SPL_USB_HOST_SUPPORT
622 bool "Support USB host drivers"
625 Enable access to USB (Universal Serial Bus) host devices so that
626 SPL can load U-Boot from a connected USB peripheral, such as a USB
627 flash stick. While USB takes a little longer to start up than most
628 buses, it is very flexible since many different types of storage
629 device can be attached. This option enables the drivers in
630 drivers/usb/host as part of an SPL build.
632 config SPL_USB_SUPPORT
633 bool "Support loading from USB"
634 depends on SPL_USB_HOST_SUPPORT
636 Enable support for USB devices in SPL. This allows use of USB
637 devices such as hard drives and flash drivers for loading U-Boot.
638 The actual drivers are enabled separately using the normal U-Boot
639 config options. This enables loading from USB using a configured
642 config SPL_USB_GADGET_SUPPORT
643 bool "Suppport USB Gadget drivers"
646 Enable USB Gadget API which allows to enable USB device functions
649 if SPL_USB_GADGET_SUPPORT
651 config SPL_USBETH_SUPPORT
652 bool "Support USB Ethernet drivers"
654 Enable access to the USB network subsystem and associated
655 drivers in SPL. This permits SPL to load U-Boot over a
656 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
657 than from an onboard peripheral. Environment support is required
658 since the network stack uses a number of environment variables.
659 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
661 config SPL_DFU_SUPPORT
662 bool "Support DFU (Device Firmware Upgarde)"
663 select SPL_HASH_SUPPORT
664 select SPL_DFU_NO_RESET
665 depends on SPL_RAM_SUPPORT
667 This feature enables the DFU (Device Firmware Upgarde) in SPL with
668 RAM memory device support. The ROM code will load and execute
669 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
670 selected device partition from host-pc using dfu-utils.
671 This feature is useful to flash the binaries to factory or bare-metal
672 boards using USB interface.
675 bool "DFU device selection"
676 depends on SPL_DFU_SUPPORT
680 depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
682 select RAM/DDR memory device for loading binary images
683 (u-boot/kernel) to the selected device partition using
684 DFU and execute the u-boot/kernel from RAM.
690 config SPL_WATCHDOG_SUPPORT
691 bool "Support watchdog drivers"
694 Enable support for watchdog drivers in SPL. A watchdog is
695 typically a hardware peripheral which can reset the system when it
696 detects no activity for a while (such as a software crash). This
697 enables the drivers in drivers/watchdog as part of an SPL build.
699 config SPL_YMODEM_SUPPORT
700 bool "Support loading using Ymodem"
703 While loading from serial is slow it can be a useful backup when
704 there is no other option. The Ymodem protocol provides a reliable
705 means of transmitting U-Boot over a serial line for using in SPL,
706 with a checksum to ensure correctness.
708 config SPL_ATF_SUPPORT
709 bool "Support ARM Trusted Firmware"
710 depends on SPL && ARM64
712 ATF(ARM Trusted Firmware) is a component for ARM arch64 which which
713 is loaded by SPL(which is considered as BL2 in ATF terminology).
714 More detail at: https://github.com/ARM-software/arm-trusted-firmware
716 config SPL_ATF_TEXT_BASE
717 depends on SPL_ATF_SUPPORT
718 hex "ATF BL31 base address"
720 This is the base address in memory for ATF BL31 text and entry point.
722 config TPL_ENV_SUPPORT
723 bool "Support an environment"
726 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
728 config TPL_I2C_SUPPORT
732 Enable support for the I2C bus in SPL. See SPL_I2C_SUPPORT for
735 config TPL_LIBCOMMON_SUPPORT
736 bool "Support common libraries"
739 Enable support for common U-Boot libraries within TPL. See
740 SPL_LIBCOMMON_SUPPORT for details.
742 config TPL_LIBGENERIC_SUPPORT
743 bool "Support generic libraries"
746 Enable support for generic U-Boot libraries within TPL. See
747 SPL_LIBGENERIC_SUPPORT for details.
749 config TPL_MPC8XXX_INIT_DDR_SUPPORT
750 bool "Support MPC8XXX DDR init"
753 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
754 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
756 config TPL_MMC_SUPPORT
758 depends on TPL && MMC
760 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
762 config TPL_NAND_SUPPORT
763 bool "Support NAND flash"
766 Enable support for NAND in SPL. See SPL_NAND_SUPPORT for details.
768 config TPL_SERIAL_SUPPORT
769 bool "Support serial"
772 Enable support for serial in SPL. See SPL_SERIAL_SUPPORT for
775 config TPL_SPI_FLASH_SUPPORT
776 bool "Support SPI flash drivers"
779 Enable support for using SPI flash in SPL. See SPL_SPI_FLASH_SUPPORT
782 config TPL_SPI_SUPPORT
783 bool "Support SPI drivers"
786 Enable support for using SPI in SPL. See SPL_SPI_SUPPORT for