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