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.
22 bool "Call board-specific initialization in SPL"
24 If this option is enabled, U-Boot will call the function
25 spl_board_init() from board_init_r(). This function should be
26 provided by the board.
28 config SPL_RAW_IMAGE_SUPPORT
29 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
47 prompt "Only use malloc_simple functions in the SPL"
49 Say Y here to only use the *_simple malloc functions from
50 malloc_simple.c, rather then using the versions from dlmalloc.c;
51 this will make the SPL binary smaller at the cost of more heap
52 usage as the *_simple malloc functions do not re-use free-ed mem.
55 bool "Enable SDRAM location for SPL stack"
57 SPL starts off execution in SRAM and thus typically has only a small
58 stack available. Since SPL sets up DRAM while in its board_init_f()
59 function, it is possible for the stack to move there before
60 board_init_r() is reached. This option enables a special SDRAM
61 location for the SPL stack. U-Boot SPL switches to this after
62 board_init_f() completes, and before board_init_r() starts.
64 config SPL_STACK_R_ADDR
65 depends on SPL_STACK_R
66 hex "SDRAM location for SPL stack"
68 Specify the address in SDRAM for the SPL stack. This will be set up
69 before board_init_r() is called.
71 config SPL_STACK_R_MALLOC_SIMPLE_LEN
72 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
73 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
76 Specify the amount of the stack to use as memory pool for
77 malloc_simple after switching the stack to DRAM. This may be set
78 to give board_init_r() a larger heap then the initial heap in
79 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
81 config SPL_SEPARATE_BSS
82 bool "BSS section is in a different memory region from text"
84 Some platforms need a large BSS region in SPL and can provide this
85 because RAM is already set up. In this case BSS can be moved to RAM.
86 This option should then be enabled so that the correct device tree
87 location is used. Normally we put the device tree at the end of BSS
88 but with this option enabled, it goes at _image_binary_end.
90 config SPL_DISPLAY_PRINT
91 bool "Display a board-specific message in SPL"
93 If this option is enabled, U-Boot will call the function
94 spl_display_print() immediately after displaying the SPL console
95 banner ("U-Boot SPL ..."). This function should be provided by
98 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
99 bool "MMC raw mode: by sector"
100 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER ||ARCH_MX6 || \
101 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
102 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
103 OMAP44XX || OMAP54XX || AM33XX || AM43XX
105 Use sector number for specifying U-Boot location on MMC/SD in
108 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
109 hex "Address on the MMC to load U-Boot from"
110 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
111 default 0x50 if ARCH_SUNXI
112 default 0x75 if ARCH_DAVINCI
113 default 0x8a if ARCH_MX6
114 default 0x100 if ARCH_ROCKCHIP || ARCH_UNIPHIER
115 default 0x140 if ARCH_MVEBU
116 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
117 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
118 OMAP54XX || AM33XX || AM43XX
120 Address on the MMC to load U-Boot from, when the MMC is being used
121 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
123 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
124 bool "MMC Raw mode: by partition"
126 Use a partition for loading U-Boot when using MMC/SD in raw mode.
128 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
129 hex "Partition to use to load U-Boot from"
130 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
133 Partition on the MMC to load U-Boot from when the MMC is being
136 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
137 bool "MMC raw mode: by partition type"
138 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
140 Use partition type for specifying U-Boot partition on MMC/SD in
141 raw mode. U-Boot will be loaded from the first partition of this
144 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
145 hex "Partition Type on the MMC to load U-Boot from"
146 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
148 Partition Type on the MMC to load U-Boot from, when the MMC is being
151 config SPL_CRC32_SUPPORT
155 Enable this to support CRC32 in FIT images within SPL. This is a
156 32-bit checksum value that can be used to verify images. This is
157 the least secure type of checksum, suitable for detected
158 accidental image corruption. For secure applications you should
159 consider SHA1 or SHA256.
161 config SPL_MD5_SUPPORT
165 Enable this to support MD5 in FIT images within SPL. An MD5
166 checksum is a 128-bit hash value used to check that the image
167 contents have not been corrupted. Note that MD5 is not considered
168 secure as it is possible (with a brute-force attack) to adjust the
169 image while still retaining the same MD5 hash value. For secure
170 applications where images may be changed maliciously, you should
171 consider SHA1 or SHA256.
173 config SPL_SHA1_SUPPORT
178 Enable this to support SHA1 in FIT images within SPL. A SHA1
179 checksum is a 160-bit (20-byte) hash value used to check that the
180 image contents have not been corrupted or maliciously altered.
181 While SHA1 is fairly secure it is coming to the end of its life
182 due to the expanding computing power avaiable to brute-force
183 attacks. For more security, consider SHA256.
185 config SPL_SHA256_SUPPORT
186 bool "Support SHA256"
190 Enable this to support SHA256 in FIT images within SPL. A SHA256
191 checksum is a 256-bit (32-byte) hash value used to check that the
192 image contents have not been corrupted. SHA256 is recommended for
193 use in secure applications since (as at 2016) there is no known
194 feasible attack that could produce a 'collision' with differing
195 input data. Use this for the highest security. Note that only the
196 SHA256 variant is supported: SHA512 and others are not currently
199 config SPL_CPU_SUPPORT
200 bool "Support CPU drivers"
202 Enable this to support CPU drivers in SPL. These drivers can set
203 up CPUs and provide information about them such as the model and
204 name. This can be useful in SPL since setting up the CPUs earlier
205 may improve boot performance. Enable this option to build the
206 drivers in drivers/cpu as part of an SPL build.
208 config SPL_CRYPTO_SUPPORT
209 bool "Support crypto drivers"
211 Enable crypto drivers in SPL. These drivers can be used to
212 accelerate secure boot processing in secure applications. Enable
213 this option to build the drivers in drivers/crypto as part of an
216 config SPL_HASH_SUPPORT
217 bool "Support hashing drivers"
221 Enable hashing drivers in SPL. These drivers can be used to
222 accelerate secure boot processing in secure applications. Enable
223 this option to build system-specific drivers for hash acceleration
224 as part of an SPL build.
226 config SPL_DMA_SUPPORT
227 bool "Support DMA drivers"
229 Enable DMA (direct-memory-access) drivers in SPL. These drivers
230 can be used to handle memory-to-peripheral data transfer without
231 the CPU moving the data. Enable this option to build the drivers
232 in drivers/dma as part of an SPL build.
234 config SPL_DRIVERS_MISC_SUPPORT
235 bool "Support misc drivers"
237 Enable miscellaneous drivers in SPL. These drivers perform various
238 tasks that don't fall nicely into other categories, Enable this
239 option to build the drivers in drivers/misc as part of an SPL
240 build, for those that support building in SPL (not all drivers do).
242 config SPL_ENV_SUPPORT
243 bool "Support an environment"
245 Enable environment support in SPL. The U-Boot environment provides
246 a number of settings (essentially name/value pairs) which can
247 control many aspects of U-Boot's operation. Normally this is not
248 needed in SPL as it has a much simpler task with less
249 configuration. But some boards use this to support 'Falcon' boot
250 on EXT2 and FAT, where SPL boots directly into Linux without
251 starting U-Boot first. Enabling this option will make getenv()
252 and setenv() available in SPL.
255 bool "Support save environment"
256 depends on SPL_ENV_SUPPORT
258 Enable save environment support in SPL after setenv. By default
259 the saveenv option is not provided in SPL, but some boards need
260 this support in 'Falcon' boot, where SPL need to boot from
261 different images based on environment variable set by OS. For
262 example OS may set "reboot_image" environment variable to
263 "recovery" inorder to boot recovery image by SPL. The SPL read
264 "reboot_image" and act accordingly and change the reboot_image
265 to default mode using setenv and save the environemnt.
267 config SPL_ETH_SUPPORT
268 bool "Support Ethernet"
269 depends on SPL_ENV_SUPPORT
271 Enable access to the network subsystem and associated Ethernet
272 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
273 link rather than from an on-board peripheral. Environment support
274 is required since the network stack uses a number of environment
275 variables. See also SPL_NET_SUPPORT.
277 config SPL_EXT_SUPPORT
278 bool "Support EXT filesystems"
280 Enable support for EXT2/3/4 filesystems with SPL. This permits
281 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
282 filesystem from within SPL. Support for the underlying block
283 device (e.g. MMC or USB) must be enabled separately.
285 config SPL_FAT_SUPPORT
286 bool "Support FAT filesystems"
289 Enable support for FAT and VFAT filesystems with SPL. This
290 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
291 filesystem from within SPL. Support for the underlying block
292 device (e.g. MMC or USB) must be enabled separately.
294 config SPL_FPGA_SUPPORT
297 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
298 provide software-configurable hardware which is typically used to
299 implement peripherals (such as UARTs, LCD displays, MMC) or
300 accelerate custom processing functions, such as image processing
301 or machine learning. Sometimes it is useful to program the FPGA
302 as early as possible during boot, and this option can enable that
305 config SPL_GPIO_SUPPORT
308 Enable support for GPIOs (General-purpose Input/Output) in SPL.
309 GPIOs allow U-Boot to read the state of an input line (high or
310 low) and set the state of an output line. This can be used to
311 drive LEDs, control power to various system parts and read user
312 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
313 for example. Enable this option to build the drivers in
314 drivers/gpio as part of an SPL build.
316 config SPL_I2C_SUPPORT
319 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
320 I2C works with a clock and data line which can be driven by a
321 one or more masters or slaves. It is a fairly complex bus but is
322 widely used as it only needs two lines for communication. Speeds of
323 400kbps are typical but up to 3.4Mbps is supported by some
324 hardware. I2C can be useful in SPL to configure power management
325 ICs (PMICs) before raising the CPU clock speed, for example.
326 Enable this option to build the drivers in drivers/i2c as part of
329 config SPL_LIBCOMMON_SUPPORT
330 bool "Support common libraries"
332 Enable support for common U-Boot libraries within SPL. These
333 libraries include common code to deal with U-Boot images,
334 environment and USB, for example. This option is enabled on many
335 boards. Enable this option to build the code in common/ as part of
338 config SPL_LIBDISK_SUPPORT
339 bool "Support disk paritions"
341 Enable support for disk partitions within SPL. 'Disk' is something
342 of a misnomer as it includes non-spinning media such as flash (as
343 used in MMC and USB sticks). Partitions provide a way for a disk
344 to be split up into separate regions, with a partition table placed
345 at the start or end which describes the location and size of each
346 'partition'. These partitions are typically uses as individual block
347 devices, typically with an EXT2 or FAT filesystem in each. This
348 option enables whatever partition support has been enabled in
349 U-Boot to also be used in SPL. It brings in the code in disk/.
351 config SPL_LIBGENERIC_SUPPORT
352 bool "Support generic libraries"
354 Enable support for generic U-Boot libraries within SPL. These
355 libraries include generic code to deal with device tree, hashing,
356 printf(), compression and the like. This option is enabled on many
357 boards. Enable this option to build the code in lib/ as part of an
360 config SPL_MMC_SUPPORT
364 Enable support for MMC (Multimedia Card) within SPL. This enables
365 the MMC protocol implementation and allows any enabled drivers to
366 be used within SPL. MMC can be used with or without disk partition
367 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
368 this option to build the drivers in drivers/mmc as part of an SPL
371 config SPL_MPC8XXX_INIT_DDR_SUPPORT
372 bool "Support MPC8XXX DDR init"
374 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
375 random-access memory) on the MPC8XXX family within SPL. This
376 allows DRAM to be set up before loading U-Boot into that DRAM,
379 config SPL_MTD_SUPPORT
380 bool "Support MTD drivers"
382 Enable support for MTD (Memory Technology Device) within SPL. MTD
383 provides a block interface over raw NAND and can also be used with
384 SPI flash. This allows SPL to load U-Boot from supported MTD
385 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
386 to enable specific MTD drivers.
388 config SPL_MUSB_NEW_SUPPORT
389 bool "Support new Mentor Graphics USB"
391 Enable support for Mentor Graphics USB in SPL. This is a new
392 driver used by some boards. Enable this option to build
393 the drivers in drivers/usb/musb-new as part of an SPL build. The
394 old drivers are in drivers/usb/musb.
396 config SPL_NAND_SUPPORT
397 bool "Support NAND flash"
399 Enable support for NAND (Negative AND) flash in SPL. NAND flash
400 can be used to allow SPL to load U-Boot from supported devices.
401 This enables the drivers in drivers/mtd/nand as part of an SPL
404 config SPL_NET_SUPPORT
405 bool "Support networking"
407 Enable support for network devices (such as Ethernet) in SPL.
408 This permits SPL to load U-Boot over a network link rather than
409 from an on-board peripheral. Environment support is required since
410 the network stack uses a number of environment variables. See also
414 config SPL_NET_VCI_STRING
415 string "BOOTP Vendor Class Identifier string sent by SPL"
417 As defined by RFC 2132 the vendor class identifier field can be
418 sent by the client to identify the vendor type and configuration
419 of a client. This is often used in practice to allow for the DHCP
420 server to specify different files to load depending on if the ROM,
421 SPL or U-Boot itself makes the request
422 endif # if SPL_NET_SUPPORT
424 config SPL_NO_CPU_SUPPORT
425 bool "Drop CPU code in SPL"
427 This is specific to the ARM926EJ-S CPU. It disables the standard
428 start.S start-up code, presumably so that a replacement can be
429 used on that CPU. You should not enable it unless you know what
432 config SPL_NOR_SUPPORT
433 bool "Support NOR flash"
435 Enable support for loading U-Boot from memory-mapped NOR (Negative
436 OR) flash in SPL. NOR flash is slow to write but fast to read, and
437 a memory-mapped device makes it very easy to access. Loading from
438 NOR is typically achieved with just a memcpy().
440 config SPL_XIP_SUPPORT
444 Enable support for execute in place of U-Boot or kernel image. There
445 is no need to copy image from flash to ram if flash supports execute
446 in place. Its very useful in systems having enough flash but not
447 enough ram to load the image.
449 config SPL_ONENAND_SUPPORT
450 bool "Support OneNAND flash"
452 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
453 a type of NAND flash and therefore can be used to allow SPL to
454 load U-Boot from supported devices. This enables the drivers in
455 drivers/mtd/onenand as part of an SPL build.
458 bool "Activate Falcon Mode"
459 depends on !TI_SECURE_DEVICE
462 Enable booting directly to an OS from SPL.
463 for more info read doc/README.falcon
467 hex "addr, where OS is found"
468 depends on SPL_NOR_SUPPORT
470 Specify the address, where the OS image is found, which
475 config SPL_PCI_SUPPORT
476 bool "Support PCI drivers"
478 Enable support for PCI in SPL. For platforms that need PCI to boot,
479 or must perform some init using PCI in SPL, this provides the
480 necessary driver support. This enables the drivers in drivers/pci
481 as part of an SPL build.
483 config SPL_PCH_SUPPORT
484 bool "Support PCH drivers"
486 Enable support for PCH (Platform Controller Hub) devices in SPL.
487 These are used to set up GPIOs and the SPI peripheral early in
488 boot. This enables the drivers in drivers/pch as part of an SPL
491 config SPL_POST_MEM_SUPPORT
492 bool "Support POST drivers"
494 Enable support for POST (Power-on Self Test) in SPL. POST is a
495 procedure that checks that the hardware (CPU or board) appears to
496 be functionally correctly. It is a sanity check that can be
497 performed before booting. This enables the drivers in post/drivers
498 as part of an SPL build.
500 config SPL_POWER_SUPPORT
501 bool "Support power drivers"
503 Enable support for power control in SPL. This includes support
504 for PMICs (Power-management Integrated Circuits) and some of the
505 features provided by PMICs. In particular, voltage regulators can
506 be used to enable/disable power and vary its voltage. That can be
507 useful in SPL to turn on boot peripherals and adjust CPU voltage
508 so that the clock speed can be increased. This enables the drivers
509 in drivers/power, drivers/power/pmic and drivers/power/regulator
510 as part of an SPL build.
512 config SPL_RAM_SUPPORT
513 bool "Support booting from RAM"
514 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
516 Enable booting of an image in RAM. The image can be preloaded or
517 it can be loaded by SPL directly into RAM (e.g. using USB).
519 config SPL_RAM_DEVICE
520 bool "Support booting from preloaded image in RAM"
521 depends on SPL_RAM_SUPPORT
522 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
524 Enable booting of an image already loaded in RAM. The image has to
525 be already in memory when SPL takes over, e.g. loaded by the boot
528 config SPL_RTC_SUPPORT
529 bool "Support RTC drivers"
531 Enable RTC (Real-time Clock) support in SPL. This includes support
532 for reading and setting the time. Some RTC devices also have some
533 non-volatile (battery-backed) memory which is accessible if
534 needed. This enables the drivers in drivers/rtc as part of an SPL
537 config SPL_SATA_SUPPORT
538 bool "Support loading from SATA"
540 Enable support for SATA (Serial AT attachment) in SPL. This allows
541 use of SATA devices such as hard drives and flash drivers for
542 loading U-Boot. SATA is used in higher-end embedded systems and
543 can provide higher performance than MMC , at somewhat higher
544 expense and power consumption. This enables loading from SATA
545 using a configured device.
547 config SPL_SERIAL_SUPPORT
548 bool "Support serial"
550 Enable support for serial in SPL. This allows use of a serial UART
551 for displaying messages while SPL is running. It also brings in
552 printf() and panic() functions. This should normally be enabled
553 unless there are space reasons not to. Even then, consider
554 enabling USE_TINY_PRINTF which is a small printf() version.
556 config SPL_SPI_FLASH_SUPPORT
557 bool "Support SPI flash drivers"
559 Enable support for using SPI flash in SPL, and loading U-Boot from
560 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
561 the SPI bus that is used to connect it to a system. It is a simple
562 but fast bidirectional 4-wire bus (clock, chip select and two data
563 lines). This enables the drivers in drivers/mtd/spi as part of an
564 SPL build. This normally requires SPL_SPI_SUPPORT.
566 config SPL_SPI_SUPPORT
567 bool "Support SPI drivers"
569 Enable support for using SPI in SPL. This is used for connecting
570 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
571 more details on that. The SPI driver provides the transport for
572 data between the SPI flash and the CPU. This option can be used to
573 enable SPI drivers that are needed for other purposes also, such
576 config SPL_TIMER_SUPPORT
577 bool "Support timer drivers"
579 Enable support for timer drivers in SPL. These can be used to get
580 a timer value when in SPL, or perhaps for implementing a delay
581 function. This enables the drivers in drivers/timer as part of an
584 config SPL_USB_HOST_SUPPORT
585 bool "Support USB host drivers"
587 Enable access to USB (Universal Serial Bus) host devices so that
588 SPL can load U-Boot from a connected USB peripheral, such as a USB
589 flash stick. While USB takes a little longer to start up than most
590 buses, it is very flexible since many different types of storage
591 device can be attached. This option enables the drivers in
592 drivers/usb/host as part of an SPL build.
594 config SPL_USB_SUPPORT
595 bool "Support loading from USB"
596 depends on SPL_USB_HOST_SUPPORT
598 Enable support for USB devices in SPL. This allows use of USB
599 devices such as hard drives and flash drivers for loading U-Boot.
600 The actual drivers are enabled separately using the normal U-Boot
601 config options. This enables loading from USB using a configured
604 config SPL_USB_GADGET_SUPPORT
605 bool "Suppport USB Gadget drivers"
607 Enable USB Gadget API which allows to enable USB device functions
610 if SPL_USB_GADGET_SUPPORT
612 config SPL_USBETH_SUPPORT
613 bool "Support USB Ethernet drivers"
615 Enable access to the USB network subsystem and associated
616 drivers in SPL. This permits SPL to load U-Boot over a
617 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
618 than from an onboard peripheral. Environment support is required
619 since the network stack uses a number of environment variables.
620 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
622 config SPL_DFU_SUPPORT
623 bool "Support DFU (Device Firmware Upgarde)"
624 select SPL_HASH_SUPPORT
625 select SPL_DFU_NO_RESET
626 depends on SPL_RAM_SUPPORT
628 This feature enables the DFU (Device Firmware Upgarde) in SPL with
629 RAM memory device support. The ROM code will load and execute
630 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
631 selected device partition from host-pc using dfu-utils.
632 This feature is useful to flash the binaries to factory or bare-metal
633 boards using USB interface.
636 bool "DFU device selection"
637 depends on SPL_DFU_SUPPORT
641 depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
643 select RAM/DDR memory device for loading binary images
644 (u-boot/kernel) to the selected device partition using
645 DFU and execute the u-boot/kernel from RAM.
651 config SPL_WATCHDOG_SUPPORT
652 bool "Support watchdog drivers"
654 Enable support for watchdog drivers in SPL. A watchdog is
655 typically a hardware peripheral which can reset the system when it
656 detects no activity for a while (such as a software crash). This
657 enables the drivers in drivers/watchdog as part of an SPL build.
659 config SPL_YMODEM_SUPPORT
660 bool "Support loading using Ymodem"
662 While loading from serial is slow it can be a useful backup when
663 there is no other option. The Ymodem protocol provides a reliable
664 means of transmitting U-Boot over a serial line for using in SPL,
665 with a checksum to ensure correctness.
667 config SPL_ATF_SUPPORT
668 bool "Support ARM Trusted Firmware"
671 ATF(ARM Trusted Firmware) is a component for ARM arch64 which which
672 is loaded by SPL(which is considered as BL2 in ATF terminology).
673 More detail at: https://github.com/ARM-software/arm-trusted-firmware
675 config SPL_ATF_TEXT_BASE
676 depends on SPL_ATF_SUPPORT
677 hex "ATF BL31 base address"
679 This is the base address in memory for ATF BL31 text and entry point.
683 depends on SUPPORT_TPL
686 If you want to build TPL as well as the normal image and SPL, say Y.
690 config TPL_ENV_SUPPORT
691 bool "Support an environment"
693 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
695 config TPL_I2C_SUPPORT
698 Enable support for the I2C bus in SPL. See SPL_I2C_SUPPORT for
701 config TPL_LIBCOMMON_SUPPORT
702 bool "Support common libraries"
704 Enable support for common U-Boot libraries within TPL. See
705 SPL_LIBCOMMON_SUPPORT for details.
707 config TPL_LIBGENERIC_SUPPORT
708 bool "Support generic libraries"
710 Enable support for generic U-Boot libraries within TPL. See
711 SPL_LIBGENERIC_SUPPORT for details.
713 config TPL_MPC8XXX_INIT_DDR_SUPPORT
714 bool "Support MPC8XXX DDR init"
716 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
717 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
719 config TPL_MMC_SUPPORT
723 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
725 config TPL_NAND_SUPPORT
726 bool "Support NAND flash"
728 Enable support for NAND in SPL. See SPL_NAND_SUPPORT for details.
730 config TPL_SERIAL_SUPPORT
731 bool "Support serial"
733 Enable support for serial in SPL. See SPL_SERIAL_SUPPORT for
736 config TPL_SPI_FLASH_SUPPORT
737 bool "Support SPI flash drivers"
739 Enable support for using SPI flash in SPL. See SPL_SPI_FLASH_SUPPORT
742 config TPL_SPI_SUPPORT
743 bool "Support SPI drivers"
745 Enable support for using SPI in SPL. See SPL_SPI_SUPPORT for