common/spl/Kconfig

   1 menu "SPL / TPL"
   2
   3 config SUPPORT_SPL
   4         bool
   5
   6 config SUPPORT_TPL
   7         bool
   8
   9 config SPL_DFU_NO_RESET
  10         bool
  11
  12 config SPL
  13         bool
  14         depends on SUPPORT_SPL
  15         prompt "Enable SPL"
  16         help
  17           If you want to build SPL as well as the normal image, say Y.
  18
  19 if SPL
  20
  21 config SPL_LDSCRIPT
  22         string "Linker script for the SPL stage"
  23         default "arch/$(ARCH)/cpu/u-boot-spl.lds"
  24         depends on SPL
  25         help
  26           The SPL stage will usually require a different linker-script
  27           (as it runs from a different memory region) than the regular
  28           U-Boot stage.  Set this to the path of the linker-script to
  29           be used for SPL.
  30
  31 config SPL_BOARD_INIT
  32         bool "Call board-specific initialization in SPL"
  33         help
  34           If this option is enabled, U-Boot will call the function
  35           spl_board_init() from board_init_r(). This function should be
  36           provided by the board.
  37
  38 config SPL_BOOTROM_SUPPORT
  39         bool "Support returning to the BOOTROM"
  40         help
  41           Some platforms (e.g. the Rockchip RK3368) provide support in their
  42           ROM for loading the next boot-stage after performing basic setup
  43           from the SPL stage.
  44
  45           Enable this option, to return to the BOOTROM through the
  46           BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
  47           boot device list, if not implemented for a given board)
  48
  49 config SPL_RAW_IMAGE_SUPPORT
  50         bool "Support SPL loading and booting of RAW images"
  51         default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
  52         default y if !TI_SECURE_DEVICE
  53         help
  54           SPL will support loading and booting a RAW image when this option
  55           is y. If this is not set, SPL will move on to other available
  56           boot media to find a suitable image.
  57
  58 config SPL_LEGACY_IMAGE_SUPPORT
  59         bool "Support SPL loading and booting of Legacy images"
  60         default y if !TI_SECURE_DEVICE
  61         help
  62           SPL will support loading and booting Legacy images when this option
  63           is y. If this is not set, SPL will move on to other available
  64           boot media to find a suitable image.
  65
  66 config SPL_SYS_MALLOC_SIMPLE
  67         bool
  68         prompt "Only use malloc_simple functions in the SPL"
  69         help
  70           Say Y here to only use the *_simple malloc functions from
  71           malloc_simple.c, rather then using the versions from dlmalloc.c;
  72           this will make the SPL binary smaller at the cost of more heap
  73           usage as the *_simple malloc functions do not re-use free-ed mem.
  74
  75 config TPL_SYS_MALLOC_SIMPLE
  76         bool
  77         prompt "Only use malloc_simple functions in the TPL"
  78         help
  79           Say Y here to only use the *_simple malloc functions from
  80           malloc_simple.c, rather then using the versions from dlmalloc.c;
  81           this will make the TPL binary smaller at the cost of more heap
  82           usage as the *_simple malloc functions do not re-use free-ed mem.
  83
  84 config SPL_STACK_R
  85         bool "Enable SDRAM location for SPL stack"
  86         help
  87           SPL starts off execution in SRAM and thus typically has only a small
  88           stack available. Since SPL sets up DRAM while in its board_init_f()
  89           function, it is possible for the stack to move there before
  90           board_init_r() is reached. This option enables a special SDRAM
  91           location for the SPL stack. U-Boot SPL switches to this after
  92           board_init_f() completes, and before board_init_r() starts.
  93
  94 config SPL_STACK_R_ADDR
  95         depends on SPL_STACK_R
  96         hex "SDRAM location for SPL stack"
  97         default 0x82000000 if ARCH_OMAP2PLUS
  98         help
  99           Specify the address in SDRAM for the SPL stack. This will be set up
 100           before board_init_r() is called.
 101
 102 config SPL_STACK_R_MALLOC_SIMPLE_LEN
 103         depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
 104         hex "Size of malloc_simple heap after switching to DRAM SPL stack"
 105         default 0x100000
 106         help
 107           Specify the amount of the stack to use as memory pool for
 108           malloc_simple after switching the stack to DRAM. This may be set
 109           to give board_init_r() a larger heap then the initial heap in
 110           SRAM which is limited to SYS_MALLOC_F_LEN bytes.
 111
 112 config SPL_SEPARATE_BSS
 113         bool "BSS section is in a different memory region from text"
 114         help
 115           Some platforms need a large BSS region in SPL and can provide this
 116           because RAM is already set up. In this case BSS can be moved to RAM.
 117           This option should then be enabled so that the correct device tree
 118           location is used. Normally we put the device tree at the end of BSS
 119           but with this option enabled, it goes at _image_binary_end.
 120
 121 config SPL_DISPLAY_PRINT
 122         bool "Display a board-specific message in SPL"
 123         help
 124           If this option is enabled, U-Boot will call the function
 125           spl_display_print() immediately after displaying the SPL console
 126           banner ("U-Boot SPL ..."). This function should be provided by
 127           the board.
 128
 129 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
 130         bool "MMC raw mode: by sector"
 131         default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER ||ARCH_MX6 || \
 132                      ARCH_ROCKCHIP || ARCH_MVEBU ||  ARCH_SOCFPGA || \
 133                      ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
 134                      OMAP44XX || OMAP54XX || AM33XX || AM43XX
 135         help
 136           Use sector number for specifying U-Boot location on MMC/SD in
 137           raw mode.
 138
 139 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
 140         hex "Address on the MMC to load U-Boot from"
 141         depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
 142         default 0x50 if ARCH_SUNXI
 143         default 0x75 if ARCH_DAVINCI
 144         default 0x8a if ARCH_MX6
 145         default 0x100 if ARCH_UNIPHIER
 146         default 0x140 if ARCH_MVEBU
 147         default 0x200 if ARCH_SOCFPGA || ARCH_AT91
 148         default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
 149                          OMAP54XX || AM33XX || AM43XX
 150         default 0x4000 if ARCH_ROCKCHIP
 151         help
 152           Address on the MMC to load U-Boot from, when the MMC is being used
 153           in raw mode. Units: MMC sectors (1 sector = 512 bytes).
 154
 155 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
 156         bool "MMC Raw mode: by partition"
 157         help
 158           Use a partition for loading U-Boot when using MMC/SD in raw mode.
 159
 160 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
 161         hex "Partition to use to load U-Boot from"
 162         depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
 163         default 1
 164         help
 165           Partition on the MMC to load U-Boot from when the MMC is being
 166           used in raw mode
 167
 168 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
 169         bool "MMC raw mode: by partition type"
 170         depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
 171         help
 172           Use partition type for specifying U-Boot partition on MMC/SD in
 173           raw mode. U-Boot will be loaded from the first partition of this
 174           type to be found.
 175
 176 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
 177         hex "Partition Type on the MMC to load U-Boot from"
 178         depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
 179         help
 180           Partition Type on the MMC to load U-Boot from, when the MMC is being
 181           used in raw mode.
 182
 183 config SPL_CRC32_SUPPORT
 184         bool "Support CRC32"
 185         depends on SPL_FIT
 186         help
 187           Enable this to support CRC32 in FIT images within SPL. This is a
 188           32-bit checksum value that can be used to verify images. This is
 189           the least secure type of checksum, suitable for detected
 190           accidental image corruption. For secure applications you should
 191           consider SHA1 or SHA256.
 192
 193 config SPL_MD5_SUPPORT
 194         bool "Support MD5"
 195         depends on SPL_FIT
 196         help
 197           Enable this to support MD5 in FIT images within SPL. An MD5
 198           checksum is a 128-bit hash value used to check that the image
 199           contents have not been corrupted. Note that MD5 is not considered
 200           secure as it is possible (with a brute-force attack) to adjust the
 201           image while still retaining the same MD5 hash value. For secure
 202           applications where images may be changed maliciously, you should
 203           consider SHA1 or SHA256.
 204
 205 config SPL_SHA1_SUPPORT
 206         bool "Support SHA1"
 207         depends on SPL_FIT
 208         select SHA1
 209         help
 210           Enable this to support SHA1 in FIT images within SPL. A SHA1
 211           checksum is a 160-bit (20-byte) hash value used to check that the
 212           image contents have not been corrupted or maliciously altered.
 213           While SHA1 is fairly secure it is coming to the end of its life
 214           due to the expanding computing power avaiable to brute-force
 215           attacks. For more security, consider SHA256.
 216
 217 config SPL_SHA256_SUPPORT
 218         bool "Support SHA256"
 219         depends on SPL_FIT
 220         select SHA256
 221         help
 222           Enable this to support SHA256 in FIT images within SPL. A SHA256
 223           checksum is a 256-bit (32-byte) hash value used to check that the
 224           image contents have not been corrupted. SHA256 is recommended for
 225           use in secure applications since (as at 2016) there is no known
 226           feasible attack that could produce a 'collision' with differing
 227           input data. Use this for the highest security. Note that only the
 228           SHA256 variant is supported: SHA512 and others are not currently
 229           supported in U-Boot.
 230
 231 config SPL_FIT_IMAGE_TINY
 232         bool "Remove functionality from SPL FIT loading to reduce size"
 233         depends on SPL_FIT
 234         default y if MACH_SUN50I || MACH_SUN50I_H5
 235         default y if ARCH_OMAP2PLUS
 236         help
 237           Enable this to reduce the size of the FIT image loading code
 238           in SPL, if space for the SPL binary is very tight.
 239
 240           This removes the detection of image types (which forces the
 241           first image to be treated as having a U-Boot style calling
 242           convention) and skips the recording of each loaded payload
 243           (i.e. loadable) into the FDT (modifying the loaded FDT to
 244           ensure this information is available to the next image
 245           invoked).
 246
 247 config SPL_CPU_SUPPORT
 248         bool "Support CPU drivers"
 249         help
 250           Enable this to support CPU drivers in SPL. These drivers can set
 251           up CPUs and provide information about them such as the model and
 252           name. This can be useful in SPL since setting up the CPUs earlier
 253           may improve boot performance. Enable this option to build the
 254           drivers in drivers/cpu as part of an SPL build.
 255
 256 config SPL_CRYPTO_SUPPORT
 257         bool "Support crypto drivers"
 258         help
 259           Enable crypto drivers in SPL. These drivers can be used to
 260           accelerate secure boot processing in secure applications. Enable
 261           this option to build the drivers in drivers/crypto as part of an
 262           SPL build.
 263
 264 config SPL_HASH_SUPPORT
 265         bool "Support hashing drivers"
 266         select SHA1
 267         select SHA256
 268         help
 269           Enable hashing drivers in SPL. These drivers can be used to
 270           accelerate secure boot processing in secure applications. Enable
 271           this option to build system-specific drivers for hash acceleration
 272           as part of an SPL build.
 273
 274 config SPL_DMA_SUPPORT
 275         bool "Support DMA drivers"
 276         help
 277           Enable DMA (direct-memory-access) drivers in SPL. These drivers
 278           can be used to handle memory-to-peripheral data transfer without
 279           the CPU moving the data. Enable this option to build the drivers
 280           in drivers/dma as part of an SPL build.
 281
 282 config SPL_DRIVERS_MISC_SUPPORT
 283         bool "Support misc drivers"
 284         help
 285           Enable miscellaneous drivers in SPL. These drivers perform various
 286           tasks that don't fall nicely into other categories, Enable this
 287           option to build the drivers in drivers/misc as part of an SPL
 288           build, for those that support building in SPL (not all drivers do).
 289
 290 config SPL_ENV_SUPPORT
 291         bool "Support an environment"
 292         help
 293           Enable environment support in SPL. The U-Boot environment provides
 294           a number of settings (essentially name/value pairs) which can
 295           control many aspects of U-Boot's operation. Normally this is not
 296           needed in SPL as it has a much simpler task with less
 297           configuration. But some boards use this to support 'Falcon' boot
 298           on EXT2 and FAT, where SPL boots directly into Linux without
 299           starting U-Boot first. Enabling this option will make env_get()
 300           and env_set() available in SPL.
 301
 302 config SPL_SAVEENV
 303         bool "Support save environment"
 304         depends on SPL_ENV_SUPPORT
 305         help
 306           Enable save environment support in SPL after setenv. By default
 307           the saveenv option is not provided in SPL, but some boards need
 308           this support in 'Falcon' boot, where SPL need to boot from
 309           different images based on environment variable set by OS. For
 310           example OS may set "reboot_image" environment variable to
 311           "recovery" inorder to boot recovery image by SPL. The SPL read
 312           "reboot_image" and act accordingly and change the reboot_image
 313           to default mode using setenv and save the environemnt.
 314
 315 config SPL_ETH_SUPPORT
 316         bool "Support Ethernet"
 317         depends on SPL_ENV_SUPPORT
 318         help
 319           Enable access to the network subsystem and associated Ethernet
 320           drivers in SPL. This permits SPL to load U-Boot over an Ethernet
 321           link rather than from an on-board peripheral. Environment support
 322           is required since the network stack uses a number of environment
 323           variables. See also SPL_NET_SUPPORT.
 324
 325 config SPL_EXT_SUPPORT
 326         bool "Support EXT filesystems"
 327         help
 328           Enable support for EXT2/3/4 filesystems with SPL. This permits
 329           U-Boot (or Linux in Falcon mode) to be loaded from an EXT
 330           filesystem from within SPL. Support for the underlying block
 331           device (e.g. MMC or USB) must be enabled separately.
 332
 333 config SPL_FAT_SUPPORT
 334         bool "Support FAT filesystems"
 335         select FS_FAT
 336         help
 337           Enable support for FAT and VFAT filesystems with SPL. This
 338           permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
 339           filesystem from within SPL. Support for the underlying block
 340           device (e.g. MMC or USB) must be enabled separately.
 341
 342 config SPL_FPGA_SUPPORT
 343         bool "Support FPGAs"
 344         help
 345           Enable support for FPGAs in SPL. Field-programmable Gate Arrays
 346           provide software-configurable hardware which is typically used to
 347           implement peripherals (such as UARTs, LCD displays, MMC) or
 348           accelerate custom processing functions, such as image processing
 349           or machine learning. Sometimes it is useful to program the FPGA
 350           as early as possible during boot, and this option can enable that
 351           within SPL.
 352
 353 config SPL_GPIO_SUPPORT
 354         bool "Support GPIO"
 355         help
 356           Enable support for GPIOs (General-purpose Input/Output) in SPL.
 357           GPIOs allow U-Boot to read the state of an input line (high or
 358           low) and set the state of an output line. This can be used to
 359           drive LEDs, control power to various system parts and read user
 360           input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
 361           for example. Enable this option to build the drivers in
 362           drivers/gpio as part of an SPL build.
 363
 364 config SPL_I2C_SUPPORT
 365         bool "Support I2C"
 366         help
 367           Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
 368           I2C works with a clock and data line which can be driven by a
 369           one or more masters or slaves. It is a fairly complex bus but is
 370           widely used as it only needs two lines for communication. Speeds of
 371           400kbps are typical but up to 3.4Mbps is supported by some
 372           hardware. I2C can be useful in SPL to configure power management
 373           ICs (PMICs) before raising the CPU clock speed, for example.
 374           Enable this option to build the drivers in drivers/i2c as part of
 375           an SPL build.
 376
 377 config SPL_LIBCOMMON_SUPPORT
 378         bool "Support common libraries"
 379         help
 380           Enable support for common U-Boot libraries within SPL. These
 381           libraries include common code to deal with U-Boot images,
 382           environment and USB, for example. This option is enabled on many
 383           boards. Enable this option to build the code in common/ as part of
 384           an SPL build.
 385
 386 config SPL_LIBDISK_SUPPORT
 387         bool "Support disk paritions"
 388         help
 389           Enable support for disk partitions within SPL. 'Disk' is something
 390           of a misnomer as it includes non-spinning media such as flash (as
 391           used in MMC and USB sticks). Partitions provide a way for a disk
 392           to be split up into separate regions, with a partition table placed
 393           at the start or end which describes the location and size of each
 394           'partition'. These partitions are typically uses as individual block
 395           devices, typically with an EXT2 or FAT filesystem in each. This
 396           option enables whatever partition support has been enabled in
 397           U-Boot to also be used in SPL. It brings in the code in disk/.
 398
 399 config SPL_LIBGENERIC_SUPPORT
 400         bool "Support generic libraries"
 401         help
 402           Enable support for generic U-Boot libraries within SPL. These
 403           libraries include generic code to deal with device tree, hashing,
 404           printf(), compression and the like. This option is enabled on many
 405           boards. Enable this option to build the code in lib/ as part of an
 406           SPL build.
 407
 408 config SPL_MMC_SUPPORT
 409         bool "Support MMC"
 410         depends on MMC
 411         help
 412           Enable support for MMC (Multimedia Card) within SPL. This enables
 413           the MMC protocol implementation and allows any enabled drivers to
 414           be used within SPL. MMC can be used with or without disk partition
 415           support depending on the application (SPL_LIBDISK_SUPPORT). Enable
 416           this option to build the drivers in drivers/mmc as part of an SPL
 417           build.
 418
 419 config SPL_MPC8XXX_INIT_DDR_SUPPORT
 420         bool "Support MPC8XXX DDR init"
 421         help
 422           Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
 423           random-access memory) on the MPC8XXX family within SPL. This
 424           allows DRAM to be set up before loading U-Boot into that DRAM,
 425           where it can run.
 426
 427 config SPL_MTD_SUPPORT
 428         bool "Support MTD drivers"
 429         help
 430           Enable support for MTD (Memory Technology Device) within SPL. MTD
 431           provides a block interface over raw NAND and can also be used with
 432           SPI flash. This allows SPL to load U-Boot from supported MTD
 433           devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
 434           to enable specific MTD drivers.
 435
 436 config SPL_MUSB_NEW_SUPPORT
 437         bool "Support new Mentor Graphics USB"
 438         help
 439           Enable support for Mentor Graphics USB in SPL. This is a new
 440           driver used by some boards. Enable this option to build
 441           the drivers in drivers/usb/musb-new as part of an SPL build. The
 442           old drivers are in drivers/usb/musb.
 443
 444 config SPL_NAND_SUPPORT
 445         bool "Support NAND flash"
 446         help
 447           Enable support for NAND (Negative AND) flash in SPL. NAND flash
 448           can be used to allow SPL to load U-Boot from supported devices.
 449           This enables the drivers in drivers/mtd/nand as part of an SPL
 450           build.
 451
 452 config SPL_NET_SUPPORT
 453         bool "Support networking"
 454         help
 455           Enable support for network devices (such as Ethernet) in SPL.
 456           This permits SPL to load U-Boot over a network link rather than
 457           from an on-board peripheral. Environment support is required since
 458           the network stack uses a number of environment variables. See also
 459           SPL_ETH_SUPPORT.
 460
 461 if SPL_NET_SUPPORT
 462 config SPL_NET_VCI_STRING
 463         string "BOOTP Vendor Class Identifier string sent by SPL"
 464         help
 465           As defined by RFC 2132 the vendor class identifier field can be
 466           sent by the client to identify the vendor type and configuration
 467           of a client.  This is often used in practice to allow for the DHCP
 468           server to specify different files to load depending on if the ROM,
 469           SPL or U-Boot itself makes the request
 470 endif   # if SPL_NET_SUPPORT
 471
 472 config SPL_NO_CPU_SUPPORT
 473         bool "Drop CPU code in SPL"
 474         help
 475           This is specific to the ARM926EJ-S CPU. It disables the standard
 476           start.S start-up code, presumably so that a replacement can be
 477           used on that CPU. You should not enable it unless you know what
 478           you are doing.
 479
 480 config SPL_NOR_SUPPORT
 481         bool "Support NOR flash"
 482         help
 483           Enable support for loading U-Boot from memory-mapped NOR (Negative
 484           OR) flash in SPL. NOR flash is slow to write but fast to read, and
 485           a memory-mapped device makes it very easy to access. Loading from
 486           NOR is typically achieved with just a memcpy().
 487
 488 config SPL_XIP_SUPPORT
 489         bool "Support XIP"
 490         depends on SPL
 491         help
 492           Enable support for execute in place of U-Boot or kernel image. There
 493           is no need to copy image from flash to ram if flash supports execute
 494           in place. Its very useful in systems having enough flash but not
 495           enough ram to load the image.
 496
 497 config SPL_ONENAND_SUPPORT
 498         bool "Support OneNAND flash"
 499         help
 500           Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
 501           a type of NAND flash and therefore can be used to allow SPL to
 502           load U-Boot from supported devices. This enables the drivers in
 503           drivers/mtd/onenand as part of an SPL build.
 504
 505 config SPL_OS_BOOT
 506         bool "Activate Falcon Mode"
 507         depends on !TI_SECURE_DEVICE
 508         default n
 509         help
 510           Enable booting directly to an OS from SPL.
 511           for more info read doc/README.falcon
 512
 513 if SPL_OS_BOOT
 514 config SYS_OS_BASE
 515         hex "addr, where OS is found"
 516         depends on SPL_NOR_SUPPORT
 517         help
 518           Specify the address, where the OS image is found, which
 519           gets booted.
 520
 521 endif # SPL_OS_BOOT
 522
 523 config SPL_PCI_SUPPORT
 524         bool "Support PCI drivers"
 525         help
 526           Enable support for PCI in SPL. For platforms that need PCI to boot,
 527           or must perform some init using PCI in SPL, this provides the
 528           necessary driver support. This enables the drivers in drivers/pci
 529           as part of an SPL build.
 530
 531 config SPL_PCH_SUPPORT
 532         bool "Support PCH drivers"
 533         help
 534           Enable support for PCH (Platform Controller Hub) devices in SPL.
 535           These are used to set up GPIOs and the SPI peripheral early in
 536           boot. This enables the drivers in drivers/pch as part of an SPL
 537           build.
 538
 539 config SPL_POST_MEM_SUPPORT
 540         bool "Support POST drivers"
 541         help
 542           Enable support for POST (Power-on Self Test) in SPL. POST is a
 543           procedure that checks that the hardware (CPU or board) appears to
 544           be functionally correctly. It is a sanity check that can be
 545           performed before booting. This enables the drivers in post/drivers
 546           as part of an SPL build.
 547
 548 config SPL_POWER_SUPPORT
 549         bool "Support power drivers"
 550         help
 551           Enable support for power control in SPL. This includes support
 552           for PMICs (Power-management Integrated Circuits) and some of the
 553           features provided by PMICs. In particular, voltage regulators can
 554           be used to enable/disable power and vary its voltage. That can be
 555           useful in SPL to turn on boot peripherals and adjust CPU voltage
 556           so that the clock speed can be increased. This enables the drivers
 557           in drivers/power, drivers/power/pmic and drivers/power/regulator
 558           as part of an SPL build.
 559
 560 config SPL_RAM_SUPPORT
 561         bool "Support booting from RAM"
 562         default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
 563         help
 564           Enable booting of an image in RAM. The image can be preloaded or
 565           it can be loaded by SPL directly into RAM (e.g. using USB).
 566
 567 config SPL_RAM_DEVICE
 568         bool "Support booting from preloaded image in RAM"
 569         depends on SPL_RAM_SUPPORT
 570         default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
 571         help
 572           Enable booting of an image already loaded in RAM. The image has to
 573           be already in memory when SPL takes over, e.g. loaded by the boot
 574           ROM.
 575
 576 config SPL_RTC_SUPPORT
 577         bool "Support RTC drivers"
 578         help
 579           Enable RTC (Real-time Clock) support in SPL. This includes support
 580           for reading and setting the time. Some RTC devices also have some
 581           non-volatile (battery-backed) memory which is accessible if
 582           needed. This enables the drivers in drivers/rtc as part of an SPL
 583           build.
 584
 585 config SPL_SATA_SUPPORT
 586         bool "Support loading from SATA"
 587         help
 588           Enable support for SATA (Serial AT attachment) in SPL. This allows
 589           use of SATA devices such as hard drives and flash drivers for
 590           loading U-Boot. SATA is used in higher-end embedded systems and
 591           can provide higher performance than MMC , at somewhat higher
 592           expense and power consumption. This enables loading from SATA
 593           using a configured device.
 594
 595 config SPL_SERIAL_SUPPORT
 596         bool "Support serial"
 597         help
 598           Enable support for serial in SPL. This allows use of a serial UART
 599           for displaying messages while SPL is running. It also brings in
 600           printf() and panic() functions. This should normally be enabled
 601           unless there are space reasons not to. Even then, consider
 602           enabling USE_TINY_PRINTF which is a small printf() version.
 603
 604 config SPL_SPI_FLASH_SUPPORT
 605         bool "Support SPI flash drivers"
 606         help
 607           Enable support for using SPI flash in SPL, and loading U-Boot from
 608           SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
 609           the SPI bus that is used to connect it to a system. It is a simple
 610           but fast bidirectional 4-wire bus (clock, chip select and two data
 611           lines). This enables the drivers in drivers/mtd/spi as part of an
 612           SPL build. This normally requires SPL_SPI_SUPPORT.
 613
 614 config SPL_SPI_SUPPORT
 615         bool "Support SPI drivers"
 616         help
 617           Enable support for using SPI in SPL. This is used for connecting
 618           to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
 619           more details on that. The SPI driver provides the transport for
 620           data between the SPI flash and the CPU. This option can be used to
 621           enable SPI drivers that are needed for other purposes also, such
 622           as a SPI PMIC.
 623
 624 config SPL_THERMAL
 625         bool "Driver support for thermal devices"
 626         help
 627           Enable support for temperature-sensing devices. Some SoCs have on-chip
 628           temperature sensors to permit warnings, speed throttling or even
 629           automatic power-off when the temperature gets too high or low. Other
 630           devices may be discrete but connected on a suitable bus.
 631
 632 config SPL_USB_HOST_SUPPORT
 633         bool "Support USB host drivers"
 634         help
 635           Enable access to USB (Universal Serial Bus) host devices so that
 636           SPL can load U-Boot from a connected USB peripheral, such as a USB
 637           flash stick. While USB takes a little longer to start up than most
 638           buses, it is very flexible since many different types of storage
 639           device can be attached. This option enables the drivers in
 640           drivers/usb/host as part of an SPL build.
 641
 642 config SPL_USB_SUPPORT
 643         bool "Support loading from USB"
 644         depends on SPL_USB_HOST_SUPPORT
 645         help
 646           Enable support for USB devices in SPL. This allows use of USB
 647           devices such as hard drives and flash drivers for loading U-Boot.
 648           The actual drivers are enabled separately using the normal U-Boot
 649           config options. This enables loading from USB using a configured
 650           device.
 651
 652 config SPL_USB_GADGET_SUPPORT
 653         bool "Suppport USB Gadget drivers"
 654         help
 655           Enable USB Gadget API which allows to enable USB device functions
 656           in SPL.
 657
 658 if SPL_USB_GADGET_SUPPORT
 659
 660 config SPL_USBETH_SUPPORT
 661         bool "Support USB Ethernet drivers"
 662         help
 663           Enable access to the USB network subsystem and associated
 664           drivers in SPL. This permits SPL to load U-Boot over a
 665           USB-connected Ethernet link (such as a USB Ethernet dongle) rather
 666           than from an onboard peripheral. Environment support is required
 667           since the network stack uses a number of environment variables.
 668           See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
 669
 670 config SPL_DFU_SUPPORT
 671         bool "Support DFU (Device Firmware Upgarde)"
 672         select SPL_HASH_SUPPORT
 673         select SPL_DFU_NO_RESET
 674         depends on SPL_RAM_SUPPORT
 675         help
 676           This feature enables the DFU (Device Firmware Upgarde) in SPL with
 677           RAM memory device support. The ROM code will load and execute
 678           the SPL built with dfu. The user can load binaries (u-boot/kernel) to
 679           selected device partition from host-pc using dfu-utils.
 680           This feature is useful to flash the binaries to factory or bare-metal
 681           boards using USB interface.
 682
 683 choice
 684         bool "DFU device selection"
 685         depends on SPL_DFU_SUPPORT
 686
 687 config SPL_DFU_RAM
 688         bool "RAM device"
 689         depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
 690         help
 691          select RAM/DDR memory device for loading binary images
 692          (u-boot/kernel) to the selected device partition using
 693          DFU and execute the u-boot/kernel from RAM.
 694
 695 endchoice
 696
 697 config SPL_USB_SDP_SUPPORT
 698         bool "Support SDP (Serial Download Protocol)"
 699         help
 700           Enable Serial Download Protocol (SDP) device support in SPL. This
 701           allows to download images into memory and execute (jump to) them
 702           using the same protocol as implemented by the i.MX family's boot ROM.
 703 endif
 704
 705 config SPL_WATCHDOG_SUPPORT
 706         bool "Support watchdog drivers"
 707         help
 708           Enable support for watchdog drivers in SPL. A watchdog is
 709           typically a hardware peripheral which can reset the system when it
 710           detects no activity for a while (such as a software crash). This
 711           enables the drivers in drivers/watchdog as part of an SPL build.
 712
 713 config SPL_YMODEM_SUPPORT
 714         bool "Support loading using Ymodem"
 715         help
 716           While loading from serial is slow it can be a useful backup when
 717           there is no other option. The Ymodem protocol provides a reliable
 718           means of transmitting U-Boot over a serial line for using in SPL,
 719           with a checksum to ensure correctness.
 720
 721 config SPL_ATF
 722         bool "Support ARM Trusted Firmware"
 723         depends on ARM64
 724         help
 725           ATF(ARM Trusted Firmware) is a component for ARM arch64 which
 726           is loaded by SPL(which is considered as BL2 in ATF terminology).
 727           More detail at: https://github.com/ARM-software/arm-trusted-firmware
 728
 729 config TPL
 730         bool
 731         depends on SUPPORT_TPL
 732         prompt "Enable TPL"
 733         help
 734           If you want to build TPL as well as the normal image and SPL, say Y.
 735
 736 if TPL
 737
 738 config TPL_LDSCRIPT
 739         string "Linker script for the TPL stage"
 740         depends on TPL
 741         help
 742           The TPL stage will usually require a different linker-script
 743           (as it runs from a different memory region) than the regular
 744           U-Boot stage.  Set this to the path of the linker-script to
 745           be used for TPL.
 746
 747           May be left empty to trigger the Makefile infrastructure to
 748           fall back to the linker-script used for the SPL stage.
 749
 750 config TPL_NEEDS_SEPARATE_TEXT_BASE
 751         bool "TPL needs a separate text-base"
 752         default n
 753         depends on TPL
 754         help
 755           Enable, if the TPL stage should not inherit its text-base
 756           from the SPL stage.  When enabled, a base address for the
 757           .text sections of the TPL stage has to be set below.
 758
 759 config TPL_NEEDS_SEPARATE_STACK
 760         bool "TPL needs a separate initial stack-pointer"
 761         default n
 762         depends on TPL
 763         help
 764           Enable, if the TPL stage should not inherit its initial
 765           stack-pointer from the settings for the SPL stage.
 766
 767 config TPL_TEXT_BASE
 768         hex "Base address for the .text section of the TPL stage"
 769         depends on TPL_NEEDS_SEPARATE_TEXT_BASE
 770         help
 771           The base address for the .text section of the TPL stage.
 772
 773 config TPL_MAX_SIZE
 774         int "Maximum size (in bytes) for the TPL stage"
 775         default 0
 776         depends on TPL
 777         help
 778           The maximum size (in bytes) of the TPL stage.
 779
 780 config TPL_STACK
 781         hex "Address of the initial stack-pointer for the TPL stage"
 782         depends on TPL_NEEDS_SEPARATE_STACK
 783         help
 784           The address of the initial stack-pointer for the TPL stage.
 785           Usually this will be the (aligned) top-of-stack.
 786
 787 config TPL_BOOTROM_SUPPORT
 788         bool "Support returning to the BOOTROM (from TPL)"
 789         help
 790           Some platforms (e.g. the Rockchip RK3368) provide support in their
 791           ROM for loading the next boot-stage after performing basic setup
 792           from the TPL stage.
 793
 794           Enable this option, to return to the BOOTROM through the
 795           BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
 796           boot device list, if not implemented for a given board)
 797
 798 config TPL_DRIVERS_MISC_SUPPORT
 799         bool "Support misc drivers in TPL"
 800         help
 801           Enable miscellaneous drivers in TPL. These drivers perform various
 802           tasks that don't fall nicely into other categories, Enable this
 803           option to build the drivers in drivers/misc as part of an TPL
 804           build, for those that support building in TPL (not all drivers do).
 805
 806 config TPL_ENV_SUPPORT
 807         bool "Support an environment"
 808         help
 809           Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
 810
 811 config TPL_I2C_SUPPORT
 812         bool "Support I2C"
 813         help
 814           Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
 815           details.
 816
 817 config TPL_LIBCOMMON_SUPPORT
 818         bool "Support common libraries"
 819         help
 820           Enable support for common U-Boot libraries within TPL. See
 821           SPL_LIBCOMMON_SUPPORT for details.
 822
 823 config TPL_LIBGENERIC_SUPPORT
 824         bool "Support generic libraries"
 825         help
 826           Enable support for generic U-Boot libraries within TPL. See
 827           SPL_LIBGENERIC_SUPPORT for details.
 828
 829 config TPL_MPC8XXX_INIT_DDR_SUPPORT
 830         bool "Support MPC8XXX DDR init"
 831         help
 832           Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
 833           SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
 834
 835 config TPL_MMC_SUPPORT
 836         bool "Support MMC"
 837         depends on MMC
 838         help
 839           Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
 840
 841 config TPL_NAND_SUPPORT
 842         bool "Support NAND flash"
 843         help
 844           Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
 845
 846 config TPL_SERIAL_SUPPORT
 847         bool "Support serial"
 848         help
 849           Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
 850           details.
 851
 852 config TPL_SPI_FLASH_SUPPORT
 853         bool "Support SPI flash drivers"
 854         help
 855           Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
 856           for details.
 857
 858 config TPL_SPI_SUPPORT
 859         bool "Support SPI drivers"
 860         help
 861           Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
 862           details.
 863
 864 endif # TPL
 865
 866 endif # SPL
 867 endmenu