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