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 config SPL_FRAMEWORK
  20         bool "Support SPL based upon the common SPL framework"
  21         depends on SPL
  22         default y
  23         help
  24           Enable the SPL framework under common/spl/.  This framework
  25           supports MMC, NAND and YMODEM and other methods loading of U-Boot
  26           and the Linux Kernel.  If unsure, say Y.
  27
  28 config SPL_SIZE_LIMIT
  29         int "Maximum size of SPL image"
  30         depends on SPL
  31         default 69632 if ARCH_MX6
  32         default 0
  33         help
  34           Specifies the maximum length of the U-Boot SPL image.
  35           If this value is zero, it is ignored.
  36
  37 config SPL_SIZE_LIMIT_SUBTRACT_GD
  38         bool "SPL image size check: provide space for global data"
  39         depends on SPL_SIZE_LIMIT > 0
  40         help
  41           If enabled, aligned size of global data is reserved in
  42           SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
  43           if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
  44           pre-reloc global data is put into this SRAM, too.
  45
  46 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
  47         bool "SPL image size check: provide space for malloc() pool before relocation"
  48         depends on SPL_SIZE_LIMIT > 0
  49         help
  50           If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
  51           to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
  52           describes the size of SRAM available for SPL when pre-reloc malloc
  53           pool is put into this SRAM, too.
  54
  55 config SPL_SIZE_LIMIT_PROVIDE_STACK
  56         hex "SPL image size check: provide stack space before relocation"
  57         depends on SPL_SIZE_LIMIT > 0
  58         default 0
  59         help
  60           If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
  61           an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
  62           of SRAM available for SPL when the stack required before reolcation
  63           uses this SRAM, too.
  64
  65 menu "PowerPC SPL Boot options"
  66         depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
  67
  68 config SPL_NAND_BOOT
  69         bool "Load SPL from NAND flash"
  70
  71 config SPL_MMC_BOOT
  72         bool "Load SPL from SD Card / eMMC"
  73
  74 config SPL_SPI_BOOT
  75         bool "Load SPL from SPI flash"
  76
  77 config SPL_FSL_PBL
  78         bool "Create SPL in Freescale PBI format"
  79         help
  80           Create boot binary having SPL binary in PBI format concatenated with
  81           u-boot binary.
  82
  83 endmenu
  84
  85 config HANDOFF
  86         bool "Pass hand-off information from SPL to U-Boot proper"
  87         depends on BLOBLIST
  88         help
  89           It is useful to be able to pass information from SPL to U-Boot
  90           proper to preserve state that is known in SPL and is needed in U-Boot.
  91           Enable this to locate the handoff information in U-Boot proper, early
  92           in boot. It is available in gd->handoff. The state state is set up
  93           in SPL (or TPL if that is being used).
  94
  95 if SPL
  96
  97 config SPL_HANDOFF
  98         bool "Pass hand-off information from SPL to U-Boot proper"
  99         depends on HANDOFF
 100         default y
 101         help
 102           This option enables SPL to write handoff information. This can be
 103           used to pass information like the size of SDRAM from SPL to U-Boot
 104           proper. Also SPL can receive information from TPL in the same place
 105           if that is enabled.
 106
 107 config SPL_LDSCRIPT
 108         string "Linker script for the SPL stage"
 109         default "arch/$(ARCH)/cpu/u-boot-spl.lds"
 110         help
 111           The SPL stage will usually require a different linker-script
 112           (as it runs from a different memory region) than the regular
 113           U-Boot stage.  Set this to the path of the linker-script to
 114           be used for SPL.
 115
 116 config SPL_TEXT_BASE
 117         hex "SPL Text Base"
 118         default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
 119         default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
 120         default 0x20060 if MACH_SUN50I_H6
 121         default 0x00060 if ARCH_SUNXI
 122         default 0x0
 123         help
 124           The address in memory that SPL will be running from.
 125
 126 config SPL_BOARD_INIT
 127         bool "Call board-specific initialization in SPL"
 128         help
 129           If this option is enabled, U-Boot will call the function
 130           spl_board_init() from board_init_r(). This function should be
 131           provided by the board.
 132
 133 config SPL_BOOTROM_SUPPORT
 134         bool "Support returning to the BOOTROM"
 135         help
 136           Some platforms (e.g. the Rockchip RK3368) provide support in their
 137           ROM for loading the next boot-stage after performing basic setup
 138           from the SPL stage.
 139
 140           Enable this option, to return to the BOOTROM through the
 141           BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
 142           boot device list, if not implemented for a given board)
 143
 144 config SPL_BOOTCOUNT_LIMIT
 145         bool "Support bootcount in SPL"
 146         depends on SPL_ENV_SUPPORT
 147         help
 148           On some boards, which use 'falcon' mode, it is necessary to check
 149           and increment the number of boot attempts. Such boards do not
 150           use proper U-Boot for normal boot flow and hence needs those
 151           adjustments to be done in the SPL.
 152
 153 config SPL_RAW_IMAGE_SUPPORT
 154         bool "Support SPL loading and booting of RAW images"
 155         default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
 156         default y if !TI_SECURE_DEVICE
 157         help
 158           SPL will support loading and booting a RAW image when this option
 159           is y. If this is not set, SPL will move on to other available
 160           boot media to find a suitable image.
 161
 162 config SPL_LEGACY_IMAGE_SUPPORT
 163         bool "Support SPL loading and booting of Legacy images"
 164         default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
 165         help
 166           SPL will support loading and booting Legacy images when this option
 167           is y. If this is not set, SPL will move on to other available
 168           boot media to find a suitable image.
 169
 170 config SPL_LEGACY_IMAGE_CRC_CHECK
 171         bool "Check CRC of Legacy images"
 172         depends on SPL_LEGACY_IMAGE_SUPPORT
 173         select SPL_CRC32_SUPPORT
 174         help
 175           Enable this to check the CRC of Legacy images. While this increases
 176           reliability, it affects both code size and boot duration.
 177           If disabled, Legacy images are booted if the image magic and size
 178           are correct, without further integrity checks.
 179
 180 config SPL_SYS_MALLOC_SIMPLE
 181         bool
 182         prompt "Only use malloc_simple functions in the SPL"
 183         help
 184           Say Y here to only use the *_simple malloc functions from
 185           malloc_simple.c, rather then using the versions from dlmalloc.c;
 186           this will make the SPL binary smaller at the cost of more heap
 187           usage as the *_simple malloc functions do not re-use free-ed mem.
 188
 189 config TPL_SYS_MALLOC_SIMPLE
 190         bool
 191         prompt "Only use malloc_simple functions in the TPL"
 192         help
 193           Say Y here to only use the *_simple malloc functions from
 194           malloc_simple.c, rather then using the versions from dlmalloc.c;
 195           this will make the TPL binary smaller at the cost of more heap
 196           usage as the *_simple malloc functions do not re-use free-ed mem.
 197
 198 config SPL_STACK_R
 199         bool "Enable SDRAM location for SPL stack"
 200         help
 201           SPL starts off execution in SRAM and thus typically has only a small
 202           stack available. Since SPL sets up DRAM while in its board_init_f()
 203           function, it is possible for the stack to move there before
 204           board_init_r() is reached. This option enables a special SDRAM
 205           location for the SPL stack. U-Boot SPL switches to this after
 206           board_init_f() completes, and before board_init_r() starts.
 207
 208 config SPL_STACK_R_ADDR
 209         depends on SPL_STACK_R
 210         hex "SDRAM location for SPL stack"
 211         default 0x82000000 if ARCH_OMAP2PLUS
 212         help
 213           Specify the address in SDRAM for the SPL stack. This will be set up
 214           before board_init_r() is called.
 215
 216 config SPL_STACK_R_MALLOC_SIMPLE_LEN
 217         depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
 218         hex "Size of malloc_simple heap after switching to DRAM SPL stack"
 219         default 0x100000
 220         help
 221           Specify the amount of the stack to use as memory pool for
 222           malloc_simple after switching the stack to DRAM. This may be set
 223           to give board_init_r() a larger heap then the initial heap in
 224           SRAM which is limited to SYS_MALLOC_F_LEN bytes.
 225
 226 config SPL_SEPARATE_BSS
 227         bool "BSS section is in a different memory region from text"
 228         help
 229           Some platforms need a large BSS region in SPL and can provide this
 230           because RAM is already set up. In this case BSS can be moved to RAM.
 231           This option should then be enabled so that the correct device tree
 232           location is used. Normally we put the device tree at the end of BSS
 233           but with this option enabled, it goes at _image_binary_end.
 234
 235 config SPL_BANNER_PRINT
 236         bool "Enable output of the SPL banner 'U-Boot SPL ...'"
 237         default y
 238         help
 239           If this option is enabled, SPL will print the banner with version
 240           info. Disabling this option could be useful to reduce TPL boot time
 241           (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
 242
 243 config TPL_BANNER_PRINT
 244         bool "Enable output of the TPL banner 'U-Boot TPL ...'"
 245         default y
 246         help
 247           If this option is enabled, SPL will not print the banner with version
 248           info. Disabling this option could be useful to reduce SPL boot time
 249           (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
 250
 251 config SPL_EARLY_BSS
 252         depends on ARM && !ARM64
 253         bool "Allows initializing BSS early before entering board_init_f"
 254         help
 255           On some platform we have sufficient memory available early on to
 256           allow setting up and using a basic BSS prior to entering
 257           board_init_f. Activating this option will also de-activate the
 258           clearing of BSS during the SPL relocation process, thus allowing
 259           to carry state from board_init_f to board_init_r by way of BSS.
 260
 261 config SPL_DISPLAY_PRINT
 262         bool "Display a board-specific message in SPL"
 263         help
 264           If this option is enabled, U-Boot will call the function
 265           spl_display_print() immediately after displaying the SPL console
 266           banner ("U-Boot SPL ..."). This function should be provided by
 267           the board.
 268
 269 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
 270         bool "MMC raw mode: by sector"
 271         default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
 272                      ARCH_MX6 || ARCH_MX7 || \
 273                      ARCH_ROCKCHIP || ARCH_MVEBU ||  ARCH_SOCFPGA || \
 274                      ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
 275                      OMAP44XX || OMAP54XX || AM33XX || AM43XX
 276         help
 277           Use sector number for specifying U-Boot location on MMC/SD in
 278           raw mode.
 279
 280 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
 281         hex "Address on the MMC to load U-Boot from"
 282         depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
 283         default 0x50 if ARCH_SUNXI
 284         default 0x75 if ARCH_DAVINCI
 285         default 0x8a if ARCH_MX6 || ARCH_MX7
 286         default 0x100 if ARCH_UNIPHIER
 287         default 0x140 if ARCH_MVEBU
 288         default 0x200 if ARCH_SOCFPGA || ARCH_AT91
 289         default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
 290                          OMAP54XX || AM33XX || AM43XX || ARCH_K3
 291         default 0x4000 if ARCH_ROCKCHIP
 292         help
 293           Address on the MMC to load U-Boot from, when the MMC is being used
 294           in raw mode. Units: MMC sectors (1 sector = 512 bytes).
 295
 296 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
 297         bool "MMC Raw mode: by partition"
 298         help
 299           Use a partition for loading U-Boot when using MMC/SD in raw mode.
 300
 301 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
 302         hex "Partition to use to load U-Boot from"
 303         depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
 304         default 1
 305         help
 306           Partition on the MMC to load U-Boot from when the MMC is being
 307           used in raw mode
 308
 309 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
 310         bool "MMC raw mode: by partition type"
 311         depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
 312         help
 313           Use partition type for specifying U-Boot partition on MMC/SD in
 314           raw mode. U-Boot will be loaded from the first partition of this
 315           type to be found.
 316
 317 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
 318         hex "Partition Type on the MMC to load U-Boot from"
 319         depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
 320         help
 321           Partition Type on the MMC to load U-Boot from, when the MMC is being
 322           used in raw mode.
 323
 324 config SPL_CRC32_SUPPORT
 325         bool "Support CRC32"
 326         default y if SPL_LEGACY_IMAGE_SUPPORT
 327         help
 328           Enable this to support CRC32 in uImages or FIT images within SPL.
 329           This is a 32-bit checksum value that can be used to verify images.
 330           For FIT images, this is the least secure type of checksum, suitable
 331           for detected accidental image corruption. For secure applications you
 332           should consider SHA1 or SHA256.
 333
 334 config SPL_MD5_SUPPORT
 335         bool "Support MD5"
 336         depends on SPL_FIT
 337         help
 338           Enable this to support MD5 in FIT images within SPL. An MD5
 339           checksum is a 128-bit hash value used to check that the image
 340           contents have not been corrupted. Note that MD5 is not considered
 341           secure as it is possible (with a brute-force attack) to adjust the
 342           image while still retaining the same MD5 hash value. For secure
 343           applications where images may be changed maliciously, you should
 344           consider SHA1 or SHA256.
 345
 346 config SPL_SHA1_SUPPORT
 347         bool "Support SHA1"
 348         depends on SPL_FIT
 349         select SHA1
 350         help
 351           Enable this to support SHA1 in FIT images within SPL. A SHA1
 352           checksum is a 160-bit (20-byte) hash value used to check that the
 353           image contents have not been corrupted or maliciously altered.
 354           While SHA1 is fairly secure it is coming to the end of its life
 355           due to the expanding computing power available to brute-force
 356           attacks. For more security, consider SHA256.
 357
 358 config SPL_SHA256_SUPPORT
 359         bool "Support SHA256"
 360         depends on SPL_FIT
 361         select SHA256
 362         help
 363           Enable this to support SHA256 in FIT images within SPL. A SHA256
 364           checksum is a 256-bit (32-byte) hash value used to check that the
 365           image contents have not been corrupted. SHA256 is recommended for
 366           use in secure applications since (as at 2016) there is no known
 367           feasible attack that could produce a 'collision' with differing
 368           input data. Use this for the highest security. Note that only the
 369           SHA256 variant is supported: SHA512 and others are not currently
 370           supported in U-Boot.
 371
 372 config SPL_FIT_IMAGE_TINY
 373         bool "Remove functionality from SPL FIT loading to reduce size"
 374         depends on SPL_FIT
 375         default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
 376         default y if ARCH_IMX8M
 377         help
 378           Enable this to reduce the size of the FIT image loading code
 379           in SPL, if space for the SPL binary is very tight.
 380
 381           This removes the detection of image types (which forces the
 382           first image to be treated as having a U-Boot style calling
 383           convention) and skips the recording of each loaded payload
 384           (i.e. loadable) into the FDT (modifying the loaded FDT to
 385           ensure this information is available to the next image
 386           invoked).
 387
 388 config SPL_CPU_SUPPORT
 389         bool "Support CPU drivers"
 390         help
 391           Enable this to support CPU drivers in SPL. These drivers can set
 392           up CPUs and provide information about them such as the model and
 393           name. This can be useful in SPL since setting up the CPUs earlier
 394           may improve boot performance. Enable this option to build the
 395           drivers in drivers/cpu as part of an SPL build.
 396
 397 config SPL_CRYPTO_SUPPORT
 398         bool "Support crypto drivers"
 399         help
 400           Enable crypto drivers in SPL. These drivers can be used to
 401           accelerate secure boot processing in secure applications. Enable
 402           this option to build the drivers in drivers/crypto as part of an
 403           SPL build.
 404
 405 config SPL_HASH_SUPPORT
 406         bool "Support hashing drivers"
 407         select SHA1
 408         select SHA256
 409         help
 410           Enable hashing drivers in SPL. These drivers can be used to
 411           accelerate secure boot processing in secure applications. Enable
 412           this option to build system-specific drivers for hash acceleration
 413           as part of an SPL build.
 414
 415 config TPL_HASH_SUPPORT
 416         bool "Support hashing drivers in TPL"
 417         select SHA1
 418         select SHA256
 419         help
 420           Enable hashing drivers in SPL. These drivers can be used to
 421           accelerate secure boot processing in secure applications. Enable
 422           this option to build system-specific drivers for hash acceleration
 423           as part of an SPL build.
 424
 425 config SPL_DMA_SUPPORT
 426         bool "Support DMA drivers"
 427         help
 428           Enable DMA (direct-memory-access) drivers in SPL. These drivers
 429           can be used to handle memory-to-peripheral data transfer without
 430           the CPU moving the data. Enable this option to build the drivers
 431           in drivers/dma as part of an SPL build.
 432
 433 config SPL_DRIVERS_MISC_SUPPORT
 434         bool "Support misc drivers"
 435         help
 436           Enable miscellaneous drivers in SPL. These drivers perform various
 437           tasks that don't fall nicely into other categories, Enable this
 438           option to build the drivers in drivers/misc as part of an SPL
 439           build, for those that support building in SPL (not all drivers do).
 440
 441 config SPL_ENV_SUPPORT
 442         bool "Support an environment"
 443         help
 444           Enable environment support in SPL. The U-Boot environment provides
 445           a number of settings (essentially name/value pairs) which can
 446           control many aspects of U-Boot's operation. Normally this is not
 447           needed in SPL as it has a much simpler task with less
 448           configuration. But some boards use this to support 'Falcon' boot
 449           on EXT2 and FAT, where SPL boots directly into Linux without
 450           starting U-Boot first. Enabling this option will make env_get()
 451           and env_set() available in SPL.
 452
 453 config SPL_SAVEENV
 454         bool "Support save environment"
 455         depends on SPL_ENV_SUPPORT
 456         select SPL_MMC_WRITE if ENV_IS_IN_MMC
 457         help
 458           Enable save environment support in SPL after setenv. By default
 459           the saveenv option is not provided in SPL, but some boards need
 460           this support in 'Falcon' boot, where SPL need to boot from
 461           different images based on environment variable set by OS. For
 462           example OS may set "reboot_image" environment variable to
 463           "recovery" inorder to boot recovery image by SPL. The SPL read
 464           "reboot_image" and act accordingly and change the reboot_image
 465           to default mode using setenv and save the environment.
 466
 467 config SPL_ETH_SUPPORT
 468         bool "Support Ethernet"
 469         depends on SPL_ENV_SUPPORT
 470         help
 471           Enable access to the network subsystem and associated Ethernet
 472           drivers in SPL. This permits SPL to load U-Boot over an Ethernet
 473           link rather than from an on-board peripheral. Environment support
 474           is required since the network stack uses a number of environment
 475           variables. See also SPL_NET_SUPPORT.
 476
 477 config SPL_FS_EXT4
 478         bool "Support EXT filesystems"
 479         help
 480           Enable support for EXT2/3/4 filesystems with SPL. This permits
 481           U-Boot (or Linux in Falcon mode) to be loaded from an EXT
 482           filesystem from within SPL. Support for the underlying block
 483           device (e.g. MMC or USB) must be enabled separately.
 484
 485 config SPL_FS_FAT
 486         bool "Support FAT filesystems"
 487         select FS_FAT
 488         help
 489           Enable support for FAT and VFAT filesystems with SPL. This
 490           permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
 491           filesystem from within SPL. Support for the underlying block
 492           device (e.g. MMC or USB) must be enabled separately.
 493
 494 config SPL_FAT_WRITE
 495         bool "Support write for FAT filesystems"
 496         help
 497           Enable write support for FAT and VFAT filesystems with SPL.
 498           Support for the underlying block device (e.g. MMC or USB) must be
 499           enabled separately.
 500
 501 config SPL_FPGA_SUPPORT
 502         bool "Support FPGAs"
 503         help
 504           Enable support for FPGAs in SPL. Field-programmable Gate Arrays
 505           provide software-configurable hardware which is typically used to
 506           implement peripherals (such as UARTs, LCD displays, MMC) or
 507           accelerate custom processing functions, such as image processing
 508           or machine learning. Sometimes it is useful to program the FPGA
 509           as early as possible during boot, and this option can enable that
 510           within SPL.
 511
 512 config SPL_GPIO_SUPPORT
 513         bool "Support GPIO in SPL"
 514         help
 515           Enable support for GPIOs (General-purpose Input/Output) in SPL.
 516           GPIOs allow U-Boot to read the state of an input line (high or
 517           low) and set the state of an output line. This can be used to
 518           drive LEDs, control power to various system parts and read user
 519           input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
 520           for example. Enable this option to build the drivers in
 521           drivers/gpio as part of an SPL build.
 522
 523 config SPL_I2C_SUPPORT
 524         bool "Support I2C"
 525         help
 526           Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
 527           I2C works with a clock and data line which can be driven by a
 528           one or more masters or slaves. It is a fairly complex bus but is
 529           widely used as it only needs two lines for communication. Speeds of
 530           400kbps are typical but up to 3.4Mbps is supported by some
 531           hardware. I2C can be useful in SPL to configure power management
 532           ICs (PMICs) before raising the CPU clock speed, for example.
 533           Enable this option to build the drivers in drivers/i2c as part of
 534           an SPL build.
 535
 536 config SPL_LIBCOMMON_SUPPORT
 537         bool "Support common libraries"
 538         help
 539           Enable support for common U-Boot libraries within SPL. These
 540           libraries include common code to deal with U-Boot images,
 541           environment and USB, for example. This option is enabled on many
 542           boards. Enable this option to build the code in common/ as part of
 543           an SPL build.
 544
 545 config SPL_LIBDISK_SUPPORT
 546         bool "Support disk partitions"
 547         select PARTITIONS
 548         help
 549           Enable support for disk partitions within SPL. 'Disk' is something
 550           of a misnomer as it includes non-spinning media such as flash (as
 551           used in MMC and USB sticks). Partitions provide a way for a disk
 552           to be split up into separate regions, with a partition table placed
 553           at the start or end which describes the location and size of each
 554           'partition'. These partitions are typically uses as individual block
 555           devices, typically with an EXT2 or FAT filesystem in each. This
 556           option enables whatever partition support has been enabled in
 557           U-Boot to also be used in SPL. It brings in the code in disk/.
 558
 559 config SPL_LIBGENERIC_SUPPORT
 560         bool "Support generic libraries"
 561         help
 562           Enable support for generic U-Boot libraries within SPL. These
 563           libraries include generic code to deal with device tree, hashing,
 564           printf(), compression and the like. This option is enabled on many
 565           boards. Enable this option to build the code in lib/ as part of an
 566           SPL build.
 567
 568 config SPL_DM_MAILBOX
 569         bool "Support Mailbox"
 570         help
 571           Enable support for Mailbox within SPL. This enable the inter
 572           processor communication protocols tobe used within SPL. Enable
 573           this option to build the drivers in drivers/mailbox as part of
 574           SPL build.
 575
 576 config SPL_MMC_SUPPORT
 577         bool "Support MMC"
 578         depends on MMC
 579         select HAVE_BLOCK_DEVICE
 580         help
 581           Enable support for MMC (Multimedia Card) within SPL. This enables
 582           the MMC protocol implementation and allows any enabled drivers to
 583           be used within SPL. MMC can be used with or without disk partition
 584           support depending on the application (SPL_LIBDISK_SUPPORT). Enable
 585           this option to build the drivers in drivers/mmc as part of an SPL
 586           build.
 587
 588 config SPL_MMC_TINY
 589         bool "Tiny MMC framework in SPL"
 590         depends on SPL_MMC_SUPPORT
 591         default n
 592         help
 593           Enable MMC framework tinification support. This option is useful if
 594           if your SPL is extremely size constrained. Heed the warning, enable
 595           this option if and only if you know exactly what you are doing, if
 596           you are reading this help text, you most likely have no idea :-)
 597
 598           The MMC framework is reduced to bare minimum to be useful. No malloc
 599           support is needed for the MMC framework operation with this option
 600           enabled. The framework supports exactly one MMC device and exactly
 601           one MMC driver. The MMC driver can be adjusted to avoid any malloc
 602           operations too, which can remove the need for malloc support in SPL
 603           and thus further reduce footprint.
 604
 605 config SPL_MMC_WRITE
 606         bool "MMC/SD/SDIO card support for write operations in SPL"
 607         depends on SPL_MMC_SUPPORT
 608         default n
 609         help
 610           Enable write access to MMC and SD Cards in SPL
 611
 612
 613 config SPL_MPC8XXX_INIT_DDR_SUPPORT
 614         bool "Support MPC8XXX DDR init"
 615         help
 616           Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
 617           random-access memory) on the MPC8XXX family within SPL. This
 618           allows DRAM to be set up before loading U-Boot into that DRAM,
 619           where it can run.
 620
 621 config SPL_MTD_SUPPORT
 622         bool "Support MTD drivers"
 623         help
 624           Enable support for MTD (Memory Technology Device) within SPL. MTD
 625           provides a block interface over raw NAND and can also be used with
 626           SPI flash. This allows SPL to load U-Boot from supported MTD
 627           devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
 628           to enable specific MTD drivers.
 629
 630 config SPL_MUSB_NEW_SUPPORT
 631         bool "Support new Mentor Graphics USB"
 632         help
 633           Enable support for Mentor Graphics USB in SPL. This is a new
 634           driver used by some boards. Enable this option to build
 635           the drivers in drivers/usb/musb-new as part of an SPL build. The
 636           old drivers are in drivers/usb/musb.
 637
 638 config SPL_NAND_SUPPORT
 639         bool "Support NAND flash"
 640         help
 641           Enable support for NAND (Negative AND) flash in SPL. NAND flash
 642           can be used to allow SPL to load U-Boot from supported devices.
 643           This enables the drivers in drivers/mtd/nand/raw as part of an SPL
 644           build.
 645
 646 config SPL_UBI
 647         bool "Support UBI"
 648         help
 649           Enable support for loading payloads from UBI. See
 650           README.ubispl for more info.
 651
 652 if SPL_UBI
 653 config SPL_UBI_LOAD_BY_VOLNAME
 654         bool "Support loading volumes by name"
 655         help
 656           This enables support for loading UBI volumes by name. When this
 657           is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
 658           configure the volume name from which to load U-Boot.
 659
 660 config SPL_UBI_MAX_VOL_LEBS
 661         int "Maximum number of LEBs per volume"
 662         depends on SPL_UBI
 663         help
 664           The maximum number of logical eraseblocks which a static volume
 665           to load can contain. Used for sizing the scan data structure.
 666
 667 config SPL_UBI_MAX_PEB_SIZE
 668         int "Maximum PEB size"
 669         depends on SPL_UBI
 670         help
 671           The maximum physical erase block size.
 672
 673 config SPL_UBI_MAX_PEBS
 674         int "Maximum number of PEBs"
 675         depends on SPL_UBI
 676         help
 677           The maximum physical erase block size. If not overridden by
 678           board code, this value will be used as the actual number of PEBs.
 679
 680 config SPL_UBI_PEB_OFFSET
 681         int "Offset to first UBI PEB"
 682         depends on SPL_UBI
 683         help
 684           The offset in number of PEBs from the start of flash to the first
 685           PEB part of the UBI image.
 686
 687 config SPL_UBI_VID_OFFSET
 688         int "Offset to VID header"
 689         depends on SPL_UBI
 690
 691 config SPL_UBI_LEB_START
 692         int "Offset to LEB in PEB"
 693         depends on SPL_UBI
 694         help
 695           The offset in bytes to the LEB within a PEB.
 696
 697 config SPL_UBI_INFO_ADDR
 698         hex "Address to place UBI scan info"
 699         depends on SPL_UBI
 700         help
 701           Address for ubispl to place the scan info. Read README.ubispl to
 702           determine the required size
 703
 704 config SPL_UBI_VOL_IDS
 705         int "Maximum volume id"
 706         depends on SPL_UBI
 707         help
 708           The maximum volume id which can be loaded. Used for sizing the
 709           scan data structure.
 710
 711 config SPL_UBI_LOAD_MONITOR_ID
 712         int "id of U-Boot volume"
 713         depends on SPL_UBI
 714         help
 715           The UBI volume id from which to load U-Boot
 716
 717 config SPL_UBI_LOAD_MONITOR_VOLNAME
 718         string "volume name of U-Boot volume"
 719         depends on SPL_UBI_LOAD_BY_VOLNAME
 720         help
 721           The UBI volume name from which to load U-Boot
 722
 723 config SPL_UBI_LOAD_KERNEL_ID
 724         int "id of kernel volume"
 725         depends on SPL_OS_BOOT && SPL_UBI
 726         help
 727           The UBI volume id from which to load the kernel
 728
 729 config SPL_UBI_LOAD_ARGS_ID
 730         int "id of kernel args volume"
 731         depends on SPL_OS_BOOT && SPL_UBI
 732         help
 733           The UBI volume id from which to load the device tree
 734
 735 config UBI_SPL_SILENCE_MSG
 736         bool "silence UBI SPL messages"
 737         default n
 738         help
 739           Disable messages from UBI SPL. This leaves warnings
 740           and errors enabled.
 741
 742 endif   # if SPL_UBI
 743
 744 config SPL_NET_SUPPORT
 745         bool "Support networking"
 746         help
 747           Enable support for network devices (such as Ethernet) in SPL.
 748           This permits SPL to load U-Boot over a network link rather than
 749           from an on-board peripheral. Environment support is required since
 750           the network stack uses a number of environment variables. See also
 751           SPL_ETH_SUPPORT.
 752
 753 if SPL_NET_SUPPORT
 754 config SPL_NET_VCI_STRING
 755         string "BOOTP Vendor Class Identifier string sent by SPL"
 756         help
 757           As defined by RFC 2132 the vendor class identifier field can be
 758           sent by the client to identify the vendor type and configuration
 759           of a client.  This is often used in practice to allow for the DHCP
 760           server to specify different files to load depending on if the ROM,
 761           SPL or U-Boot itself makes the request
 762 endif   # if SPL_NET_SUPPORT
 763
 764 config SPL_NO_CPU_SUPPORT
 765         bool "Drop CPU code in SPL"
 766         help
 767           This is specific to the ARM926EJ-S CPU. It disables the standard
 768           start.S start-up code, presumably so that a replacement can be
 769           used on that CPU. You should not enable it unless you know what
 770           you are doing.
 771
 772 config SPL_NOR_SUPPORT
 773         bool "Support NOR flash"
 774         help
 775           Enable support for loading U-Boot from memory-mapped NOR (Negative
 776           OR) flash in SPL. NOR flash is slow to write but fast to read, and
 777           a memory-mapped device makes it very easy to access. Loading from
 778           NOR is typically achieved with just a memcpy().
 779
 780 config SPL_XIP_SUPPORT
 781         bool "Support XIP"
 782         depends on SPL
 783         help
 784           Enable support for execute in place of U-Boot or kernel image. There
 785           is no need to copy image from flash to ram if flash supports execute
 786           in place. Its very useful in systems having enough flash but not
 787           enough ram to load the image.
 788
 789 config SPL_ONENAND_SUPPORT
 790         bool "Support OneNAND flash"
 791         help
 792           Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
 793           a type of NAND flash and therefore can be used to allow SPL to
 794           load U-Boot from supported devices. This enables the drivers in
 795           drivers/mtd/onenand as part of an SPL build.
 796
 797 config SPL_OS_BOOT
 798         bool "Activate Falcon Mode"
 799         depends on !TI_SECURE_DEVICE
 800         default n
 801         help
 802           Enable booting directly to an OS from SPL.
 803           for more info read doc/README.falcon
 804
 805 if SPL_OS_BOOT
 806 config SYS_OS_BASE
 807         hex "addr, where OS is found"
 808         depends on SPL_NOR_SUPPORT
 809         help
 810           Specify the address, where the OS image is found, which
 811           gets booted.
 812
 813 endif # SPL_OS_BOOT
 814
 815 config SPL_PAYLOAD
 816         string "SPL payload"
 817         default "tpl/u-boot-with-tpl.bin" if TPL
 818         default "u-boot.bin"
 819         help
 820           Payload for SPL boot. For backward compatibility, default to
 821           u-boot.bin, i.e. RAW image without any header. In case of
 822           TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
 823           use u-boot.img.
 824
 825 config SPL_PCI
 826         bool "Support PCI drivers"
 827         help
 828           Enable support for PCI in SPL. For platforms that need PCI to boot,
 829           or must perform some init using PCI in SPL, this provides the
 830           necessary driver support. This enables the drivers in drivers/pci
 831           as part of an SPL build.
 832
 833 config SPL_PCH_SUPPORT
 834         bool "Support PCH drivers"
 835         help
 836           Enable support for PCH (Platform Controller Hub) devices in SPL.
 837           These are used to set up GPIOs and the SPI peripheral early in
 838           boot. This enables the drivers in drivers/pch as part of an SPL
 839           build.
 840
 841 config SPL_POST_MEM_SUPPORT
 842         bool "Support POST drivers"
 843         help
 844           Enable support for POST (Power-on Self Test) in SPL. POST is a
 845           procedure that checks that the hardware (CPU or board) appears to
 846           be functionally correctly. It is a sanity check that can be
 847           performed before booting. This enables the drivers in post/drivers
 848           as part of an SPL build.
 849
 850 config SPL_DM_RESET
 851         bool "Support reset drivers"
 852         depends on SPL
 853         help
 854           Enable support for reset control in SPL.
 855           That can be useful in SPL to handle IP reset in driver, as in U-Boot,
 856           by using the generic reset API provided by driver model.
 857           This enables the drivers in drivers/reset as part of an SPL build.
 858
 859 config SPL_POWER_SUPPORT
 860         bool "Support power drivers"
 861         help
 862           Enable support for power control in SPL. This includes support
 863           for PMICs (Power-management Integrated Circuits) and some of the
 864           features provided by PMICs. In particular, voltage regulators can
 865           be used to enable/disable power and vary its voltage. That can be
 866           useful in SPL to turn on boot peripherals and adjust CPU voltage
 867           so that the clock speed can be increased. This enables the drivers
 868           in drivers/power, drivers/power/pmic and drivers/power/regulator
 869           as part of an SPL build.
 870
 871 config SPL_POWER_DOMAIN
 872         bool "Support power domain drivers"
 873         help
 874           Enable support for power domain control in SPL. Many SoCs allow
 875           power to be applied to or removed from portions of the SoC (power
 876           domains). This may be used to save power. This API provides the
 877           means to control such power management hardware. This enables
 878           the drivers in drivers/power/domain as part of a SPL build.
 879
 880 config SPL_RAM_SUPPORT
 881         bool "Support booting from RAM"
 882         default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
 883         help
 884           Enable booting of an image in RAM. The image can be preloaded or
 885           it can be loaded by SPL directly into RAM (e.g. using USB).
 886
 887 config SPL_RAM_DEVICE
 888         bool "Support booting from preloaded image in RAM"
 889         depends on SPL_RAM_SUPPORT
 890         default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
 891         help
 892           Enable booting of an image already loaded in RAM. The image has to
 893           be already in memory when SPL takes over, e.g. loaded by the boot
 894           ROM.
 895
 896 config SPL_REMOTEPROC
 897         bool "Support REMOTEPROCS"
 898         help
 899           Enable support for REMOTEPROCs in SPL. This permits to load
 900           a remote processor firmware in SPL.
 901
 902 config SPL_RTC_SUPPORT
 903         bool "Support RTC drivers"
 904         help
 905           Enable RTC (Real-time Clock) support in SPL. This includes support
 906           for reading and setting the time. Some RTC devices also have some
 907           non-volatile (battery-backed) memory which is accessible if
 908           needed. This enables the drivers in drivers/rtc as part of an SPL
 909           build.
 910
 911 config SPL_SATA_SUPPORT
 912         bool "Support loading from SATA"
 913         help
 914           Enable support for SATA (Serial AT attachment) in SPL. This allows
 915           use of SATA devices such as hard drives and flash drivers for
 916           loading U-Boot. SATA is used in higher-end embedded systems and
 917           can provide higher performance than MMC , at somewhat higher
 918           expense and power consumption. This enables loading from SATA
 919           using a configured device.
 920
 921 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
 922         bool "SATA raw mode: by sector"
 923         depends on SPL_SATA_SUPPORT
 924         help
 925           Use sector number for specifying U-Boot location on SATA disk in
 926           raw mode.
 927
 928 config SPL_SATA_RAW_U_BOOT_SECTOR
 929         hex "Sector on the SATA disk to load U-Boot from"
 930         depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
 931         help
 932           Sector on the SATA disk to load U-Boot from, when the SATA disk is being
 933           used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
 934
 935 config SPL_SERIAL_SUPPORT
 936         bool "Support serial"
 937         select SPL_PRINTF
 938         select SPL_STRTO
 939         help
 940           Enable support for serial in SPL. This allows use of a serial UART
 941           for displaying messages while SPL is running. It also brings in
 942           printf() and panic() functions. This should normally be enabled
 943           unless there are space reasons not to. Even then, consider
 944           enabling USE_TINY_PRINTF which is a small printf() version.
 945
 946 config SPL_SPI_FLASH_SUPPORT
 947         bool "Support SPI flash drivers"
 948         help
 949           Enable support for using SPI flash in SPL, and loading U-Boot from
 950           SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
 951           the SPI bus that is used to connect it to a system. It is a simple
 952           but fast bidirectional 4-wire bus (clock, chip select and two data
 953           lines). This enables the drivers in drivers/mtd/spi as part of an
 954           SPL build. This normally requires SPL_SPI_SUPPORT.
 955
 956 if SPL_SPI_FLASH_SUPPORT
 957
 958 config SPL_SPI_FLASH_TINY
 959         bool "Enable low footprint SPL SPI Flash support"
 960         depends on !SPI_FLASH_BAR
 961         default y if SPI_FLASH
 962         help
 963          Enable lightweight SPL SPI Flash support that supports just reading
 964          data/images from flash. No support to write/erase flash. Enable
 965          this if you have SPL size limitations and don't need full
 966          fledged SPI flash support.
 967
 968 config SPL_SPI_FLASH_SFDP_SUPPORT
 969         bool "SFDP table parsing support for SPI NOR flashes"
 970         depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
 971         help
 972          Enable support for parsing and auto discovery of parameters for
 973          SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
 974          tables as per JESD216 standard in SPL.
 975
 976 config SPL_SPI_LOAD
 977         bool "Support loading from SPI flash"
 978         help
 979           Enable support for loading next stage, U-Boot or otherwise, from
 980           SPI NOR in U-Boot SPL.
 981
 982 endif # SPL_SPI_FLASH_SUPPORT
 983
 984 config SPL_SPI_SUPPORT
 985         bool "Support SPI drivers"
 986         help
 987           Enable support for using SPI in SPL. This is used for connecting
 988           to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
 989           more details on that. The SPI driver provides the transport for
 990           data between the SPI flash and the CPU. This option can be used to
 991           enable SPI drivers that are needed for other purposes also, such
 992           as a SPI PMIC.
 993
 994 config SPL_THERMAL
 995         bool "Driver support for thermal devices"
 996         help
 997           Enable support for temperature-sensing devices. Some SoCs have on-chip
 998           temperature sensors to permit warnings, speed throttling or even
 999           automatic power-off when the temperature gets too high or low. Other
1000           devices may be discrete but connected on a suitable bus.
1001
1002 config SPL_USB_HOST_SUPPORT
1003         bool "Support USB host drivers"
1004         select HAVE_BLOCK_DEVICE
1005         help
1006           Enable access to USB (Universal Serial Bus) host devices so that
1007           SPL can load U-Boot from a connected USB peripheral, such as a USB
1008           flash stick. While USB takes a little longer to start up than most
1009           buses, it is very flexible since many different types of storage
1010           device can be attached. This option enables the drivers in
1011           drivers/usb/host as part of an SPL build.
1012
1013 config SPL_USB_STORAGE
1014         bool "Support loading from USB"
1015         depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1016         help
1017           Enable support for USB devices in SPL. This allows use of USB
1018           devices such as hard drives and flash drivers for loading U-Boot.
1019           The actual drivers are enabled separately using the normal U-Boot
1020           config options. This enables loading from USB using a configured
1021           device.
1022
1023 config SPL_USB_GADGET
1024         bool "Suppport USB Gadget drivers"
1025         help
1026           Enable USB Gadget API which allows to enable USB device functions
1027           in SPL.
1028
1029 if SPL_USB_GADGET
1030
1031 config SPL_USB_ETHER
1032         bool "Support USB Ethernet drivers"
1033         help
1034           Enable access to the USB network subsystem and associated
1035           drivers in SPL. This permits SPL to load U-Boot over a
1036           USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1037           than from an onboard peripheral. Environment support is required
1038           since the network stack uses a number of environment variables.
1039           See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1040
1041 config SPL_DFU
1042         bool "Support DFU (Device Firmware Upgrade)"
1043         select SPL_HASH_SUPPORT
1044         select SPL_DFU_NO_RESET
1045         depends on SPL_RAM_SUPPORT
1046         help
1047           This feature enables the DFU (Device Firmware Upgrade) in SPL with
1048           RAM memory device support. The ROM code will load and execute
1049           the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1050           selected device partition from host-pc using dfu-utils.
1051           This feature is useful to flash the binaries to factory or bare-metal
1052           boards using USB interface.
1053
1054 choice
1055         bool "DFU device selection"
1056         depends on SPL_DFU
1057
1058 config SPL_DFU_RAM
1059         bool "RAM device"
1060         depends on SPL_DFU && SPL_RAM_SUPPORT
1061         help
1062          select RAM/DDR memory device for loading binary images
1063          (u-boot/kernel) to the selected device partition using
1064          DFU and execute the u-boot/kernel from RAM.
1065
1066 endchoice
1067
1068 config SPL_USB_SDP_SUPPORT
1069         bool "Support SDP (Serial Download Protocol)"
1070         help
1071           Enable Serial Download Protocol (SDP) device support in SPL. This
1072           allows to download images into memory and execute (jump to) them
1073           using the same protocol as implemented by the i.MX family's boot ROM.
1074 endif
1075
1076 config SPL_WATCHDOG_SUPPORT
1077         bool "Support watchdog drivers"
1078         imply SPL_WDT if !HW_WATCHDOG
1079         help
1080           Enable support for watchdog drivers in SPL. A watchdog is
1081           typically a hardware peripheral which can reset the system when it
1082           detects no activity for a while (such as a software crash). This
1083           enables the drivers in drivers/watchdog as part of an SPL build.
1084
1085 config SPL_YMODEM_SUPPORT
1086         bool "Support loading using Ymodem"
1087         depends on SPL_SERIAL_SUPPORT
1088         help
1089           While loading from serial is slow it can be a useful backup when
1090           there is no other option. The Ymodem protocol provides a reliable
1091           means of transmitting U-Boot over a serial line for using in SPL,
1092           with a checksum to ensure correctness.
1093
1094 config SPL_ATF
1095         bool "Support ARM Trusted Firmware"
1096         depends on ARM64
1097         help
1098           ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1099           is loaded by SPL (which is considered as BL2 in ATF terminology).
1100           More detail at: https://github.com/ARM-software/arm-trusted-firmware
1101
1102 config SPL_ATF_NO_PLATFORM_PARAM
1103         bool "Pass no platform parameter"
1104         depends on SPL_ATF
1105         help
1106           While we expect to call a pointer to a valid FDT (or NULL)
1107           as the platform parameter to an ATF, some ATF versions are
1108           not U-Boot aware and have an insufficiently robust parameter
1109           validation to gracefully reject a FDT being passed.
1110
1111           If this option is enabled, the spl_atf os-type handler will
1112           always pass NULL for the platform parameter.
1113
1114           If your ATF is affected, say Y.
1115
1116 config SPL_AM33XX_ENABLE_RTC32K_OSC
1117         bool "Enable the RTC32K OSC on AM33xx based platforms"
1118         default y if AM33XX
1119         help
1120           Enable access to the AM33xx RTC and select the external 32kHz clock
1121           source.
1122
1123 config SPL_OPTEE
1124         bool "Support OP-TEE Trusted OS"
1125         depends on ARM
1126         help
1127           OP-TEE is an open source Trusted OS  which is loaded by SPL.
1128           More detail at: https://github.com/OP-TEE/optee_os
1129
1130 config TPL
1131         bool
1132         depends on SUPPORT_TPL
1133         prompt "Enable TPL"
1134         help
1135           If you want to build TPL as well as the normal image and SPL, say Y.
1136
1137 if TPL
1138
1139 config TPL_HANDOFF
1140         bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1141         depends on HANDOFF
1142         default y
1143         help
1144           This option enables TPL to write handoff information. This can be
1145           used to pass information like the size of SDRAM from TPL to U-Boot
1146           proper. The information is also available to SPL if it is useful
1147           there.
1148
1149 config TPL_BOARD_INIT
1150         bool "Call board-specific initialization in TPL"
1151         help
1152           If this option is enabled, U-Boot will call the function
1153           spl_board_init() from board_init_r(). This function should be
1154           provided by the board.
1155
1156 config TPL_LDSCRIPT
1157         string "Linker script for the TPL stage"
1158         depends on TPL
1159         default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1160         default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1161         help
1162           The TPL stage will usually require a different linker-script
1163           (as it runs from a different memory region) than the regular
1164           U-Boot stage.  Set this to the path of the linker-script to
1165           be used for TPL.
1166
1167           May be left empty to trigger the Makefile infrastructure to
1168           fall back to the linker-script used for the SPL stage.
1169
1170 config TPL_NEEDS_SEPARATE_TEXT_BASE
1171         bool "TPL needs a separate text-base"
1172         default n
1173         depends on TPL
1174         help
1175           Enable, if the TPL stage should not inherit its text-base
1176           from the SPL stage.  When enabled, a base address for the
1177           .text sections of the TPL stage has to be set below.
1178
1179 config TPL_NEEDS_SEPARATE_STACK
1180         bool "TPL needs a separate initial stack-pointer"
1181         default n
1182         depends on TPL
1183         help
1184           Enable, if the TPL stage should not inherit its initial
1185           stack-pointer from the settings for the SPL stage.
1186
1187 config TPL_TEXT_BASE
1188         hex "Base address for the .text section of the TPL stage"
1189         depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1190         help
1191           The base address for the .text section of the TPL stage.
1192
1193 config TPL_MAX_SIZE
1194         int "Maximum size (in bytes) for the TPL stage"
1195         default 0
1196         depends on TPL
1197         help
1198           The maximum size (in bytes) of the TPL stage.
1199
1200 config TPL_STACK
1201         hex "Address of the initial stack-pointer for the TPL stage"
1202         depends on TPL_NEEDS_SEPARATE_STACK
1203         help
1204           The address of the initial stack-pointer for the TPL stage.
1205           Usually this will be the (aligned) top-of-stack.
1206
1207 config TPL_BOOTROM_SUPPORT
1208         bool "Support returning to the BOOTROM (from TPL)"
1209         help
1210           Some platforms (e.g. the Rockchip RK3368) provide support in their
1211           ROM for loading the next boot-stage after performing basic setup
1212           from the TPL stage.
1213
1214           Enable this option, to return to the BOOTROM through the
1215           BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1216           boot device list, if not implemented for a given board)
1217
1218 config TPL_DRIVERS_MISC_SUPPORT
1219         bool "Support misc drivers in TPL"
1220         help
1221           Enable miscellaneous drivers in TPL. These drivers perform various
1222           tasks that don't fall nicely into other categories, Enable this
1223           option to build the drivers in drivers/misc as part of an TPL
1224           build, for those that support building in TPL (not all drivers do).
1225
1226 config TPL_ENV_SUPPORT
1227         bool "Support an environment"
1228         help
1229           Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1230
1231 config TPL_GPIO_SUPPORT
1232         bool "Support GPIO in TPL"
1233         help
1234           Enable support for GPIOs (General-purpose Input/Output) in TPL.
1235           GPIOs allow U-Boot to read the state of an input line (high or
1236           low) and set the state of an output line. This can be used to
1237           drive LEDs, control power to various system parts and read user
1238           input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1239           for example. Enable this option to build the drivers in
1240           drivers/gpio as part of an TPL build.
1241
1242 config TPL_I2C_SUPPORT
1243         bool "Support I2C"
1244         help
1245           Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1246           details.
1247
1248 config TPL_LIBCOMMON_SUPPORT
1249         bool "Support common libraries"
1250         help
1251           Enable support for common U-Boot libraries within TPL. See
1252           SPL_LIBCOMMON_SUPPORT for details.
1253
1254 config TPL_LIBGENERIC_SUPPORT
1255         bool "Support generic libraries"
1256         help
1257           Enable support for generic U-Boot libraries within TPL. See
1258           SPL_LIBGENERIC_SUPPORT for details.
1259
1260 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1261         bool "Support MPC8XXX DDR init"
1262         help
1263           Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1264           SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1265
1266 config TPL_MMC_SUPPORT
1267         bool "Support MMC"
1268         depends on MMC
1269         help
1270           Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1271
1272 config TPL_NAND_SUPPORT
1273         bool "Support NAND flash"
1274         help
1275           Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1276
1277 config TPL_PCI
1278         bool "Support PCI drivers"
1279         help
1280           Enable support for PCI in TPL. For platforms that need PCI to boot,
1281           or must perform some init using PCI in SPL, this provides the
1282           necessary driver support. This enables the drivers in drivers/pci
1283           as part of a TPL build.
1284
1285 config TPL_PCH_SUPPORT
1286         bool "Support PCH drivers"
1287         help
1288           Enable support for PCH (Platform Controller Hub) devices in TPL.
1289           These are used to set up GPIOs and the SPI peripheral early in
1290           boot. This enables the drivers in drivers/pch as part of a TPL
1291           build.
1292
1293 config TPL_RAM_SUPPORT
1294         bool "Support booting from RAM"
1295         help
1296           Enable booting of an image in RAM. The image can be preloaded or
1297           it can be loaded by TPL directly into RAM (e.g. using USB).
1298
1299 config TPL_RAM_DEVICE
1300         bool "Support booting from preloaded image in RAM"
1301         depends on TPL_RAM_SUPPORT
1302         help
1303           Enable booting of an image already loaded in RAM. The image has to
1304           be already in memory when TPL takes over, e.g. loaded by the boot
1305           ROM.
1306
1307 config TPL_RTC_SUPPORT
1308         bool "Support RTC drivers"
1309         help
1310           Enable RTC (Real-time Clock) support in TPL. This includes support
1311           for reading and setting the time. Some RTC devices also have some
1312           non-volatile (battery-backed) memory which is accessible if
1313           needed. This enables the drivers in drivers/rtc as part of an TPL
1314           build.
1315
1316 config TPL_SERIAL_SUPPORT
1317         bool "Support serial"
1318         select TPL_PRINTF
1319         select TPL_STRTO
1320         help
1321           Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1322           details.
1323
1324 config TPL_SPI_FLASH_SUPPORT
1325         bool "Support SPI flash drivers"
1326         help
1327           Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1328           for details.
1329
1330 config TPL_SPI_LOAD
1331         bool "Support loading from SPI flash"
1332         depends on TPL_SPI_FLASH_SUPPORT
1333         help
1334           Enable support for loading next stage, U-Boot or otherwise, from
1335           SPI NOR in U-Boot TPL.
1336
1337 config TPL_SPI_SUPPORT
1338         bool "Support SPI drivers"
1339         help
1340           Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1341           details.
1342
1343 config TPL_YMODEM_SUPPORT
1344         bool "Support loading using Ymodem"
1345         depends on TPL_SERIAL_SUPPORT
1346         help
1347           While loading from serial is slow it can be a useful backup when
1348           there is no other option. The Ymodem protocol provides a reliable
1349           means of transmitting U-Boot over a serial line for using in TPL,
1350           with a checksum to ensure correctness.
1351
1352 endif # TPL
1353
1354 config SPL_AT91_MCK_BYPASS
1355         bool "Use external clock signal as a source of main clock for AT91 platforms"
1356         depends on ARCH_AT91
1357         default n
1358         help
1359           Use external 8 to 24 Mhz clock signal as source of main clock instead
1360           of an external crystal oscillator.
1361           This option disables the internal driving on the XOUT pin.
1362           The external source has to provide a stable clock on the XIN pin.
1363           If this option is disabled, the SoC expects a crystal oscillator
1364           that needs driving on both XIN and XOUT lines.
1365
1366 endif # SPL
1367 endmenu