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