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