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