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