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
19config 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
28config 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
37config 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
46config 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
55config 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
65config SPL_SYS_STACK_F_CHECK_BYTE
66 hex
67 default 0xaa
68 help
69 Constant used to check the stack
70
71config 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
84menu "PowerPC SPL Boot options"
85 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
86
87config SPL_NAND_BOOT
88 bool "Load SPL from NAND flash"
89
90config SPL_MMC_BOOT
91 bool "Load SPL from SD Card / eMMC"
92
93config SPL_SPI_BOOT
94 bool "Load SPL from SPI flash"
95
96config 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
102endmenu
103
104config 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
114if SPL
115
116config 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
126config 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
135config 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
145config 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
152config 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
163config 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
172config 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
181config 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
189config 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
199config 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
208config 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
218config 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
228config 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
236config 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
246config 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
255config 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
263config 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
272config 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
282config 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
290config 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
301config 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
317config 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
322config 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
330config 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
338config 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
345config 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
355config 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
367config 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
379config 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
393config 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
409config 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
418config 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
426config 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
436config TPL_HASH_SUPPORT
437 bool "Support hashing drivers in TPL"
438 depends on TPL
439 select SHA1
440 select SHA256
441 help
442 Enable hashing drivers in SPL. These drivers can be used to
443 accelerate secure boot processing in secure applications. Enable
444 this option to build system-specific drivers for hash acceleration
445 as part of an SPL build.
446
447config SPL_DMA_SUPPORT
448 bool "Support DMA drivers"
449 help
450 Enable DMA (direct-memory-access) drivers in SPL. These drivers
451 can be used to handle memory-to-peripheral data transfer without
452 the CPU moving the data. Enable this option to build the drivers
453 in drivers/dma as part of an SPL build.
454
455config SPL_DRIVERS_MISC_SUPPORT
456 bool "Support misc drivers"
457 help
458 Enable miscellaneous drivers in SPL. These drivers perform various
459 tasks that don't fall nicely into other categories, Enable this
460 option to build the drivers in drivers/misc as part of an SPL
461 build, for those that support building in SPL (not all drivers do).
462
463config SPL_ENV_SUPPORT
464 bool "Support an environment"
465 help
466 Enable environment support in SPL. The U-Boot environment provides
467 a number of settings (essentially name/value pairs) which can
468 control many aspects of U-Boot's operation. Normally this is not
469 needed in SPL as it has a much simpler task with less
470 configuration. But some boards use this to support 'Falcon' boot
471 on EXT2 and FAT, where SPL boots directly into Linux without
472 starting U-Boot first. Enabling this option will make env_get()
473 and env_set() available in SPL.
474
475config SPL_SAVEENV
476 bool "Support save environment"
477 depends on SPL_ENV_SUPPORT
478 select SPL_MMC_WRITE if ENV_IS_IN_MMC
479 help
480 Enable save environment support in SPL after setenv. By default
481 the saveenv option is not provided in SPL, but some boards need
482 this support in 'Falcon' boot, where SPL need to boot from
483 different images based on environment variable set by OS. For
484 example OS may set "reboot_image" environment variable to
485 "recovery" inorder to boot recovery image by SPL. The SPL read
486 "reboot_image" and act accordingly and change the reboot_image
487 to default mode using setenv and save the environment.
488
489config SPL_ETH_SUPPORT
490 bool "Support Ethernet"
491 depends on SPL_ENV_SUPPORT
492 help
493 Enable access to the network subsystem and associated Ethernet
494 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
495 link rather than from an on-board peripheral. Environment support
496 is required since the network stack uses a number of environment
497 variables. See also SPL_NET_SUPPORT.
498
499config SPL_FS_EXT4
500 bool "Support EXT filesystems"
501 help
502 Enable support for EXT2/3/4 filesystems with SPL. This permits
503 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
504 filesystem from within SPL. Support for the underlying block
505 device (e.g. MMC or USB) must be enabled separately.
506
507config SPL_FS_FAT
508 bool "Support FAT filesystems"
509 select FS_FAT
510 help
511 Enable support for FAT and VFAT filesystems with SPL. This
512 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
513 filesystem from within SPL. Support for the underlying block
514 device (e.g. MMC or USB) must be enabled separately.
515
516config SPL_FAT_WRITE
517 bool "Support write for FAT filesystems"
518 help
519 Enable write support for FAT and VFAT filesystems with SPL.
520 Support for the underlying block device (e.g. MMC or USB) must be
521 enabled separately.
522
523config SPL_FPGA_SUPPORT
524 bool "Support FPGAs"
525 help
526 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
527 provide software-configurable hardware which is typically used to
528 implement peripherals (such as UARTs, LCD displays, MMC) or
529 accelerate custom processing functions, such as image processing
530 or machine learning. Sometimes it is useful to program the FPGA
531 as early as possible during boot, and this option can enable that
532 within SPL.
533
534config SPL_GPIO_SUPPORT
535 bool "Support GPIO in SPL"
536 help
537 Enable support for GPIOs (General-purpose Input/Output) in SPL.
538 GPIOs allow U-Boot to read the state of an input line (high or
539 low) and set the state of an output line. This can be used to
540 drive LEDs, control power to various system parts and read user
541 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
542 for example. Enable this option to build the drivers in
543 drivers/gpio as part of an SPL build.
544
545config SPL_I2C_SUPPORT
546 bool "Support I2C"
547 help
548 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
549 I2C works with a clock and data line which can be driven by a
550 one or more masters or slaves. It is a fairly complex bus but is
551 widely used as it only needs two lines for communication. Speeds of
552 400kbps are typical but up to 3.4Mbps is supported by some
553 hardware. I2C can be useful in SPL to configure power management
554 ICs (PMICs) before raising the CPU clock speed, for example.
555 Enable this option to build the drivers in drivers/i2c as part of
556 an SPL build.
557
558config SPL_LIBCOMMON_SUPPORT
559 bool "Support common libraries"
560 help
561 Enable support for common U-Boot libraries within SPL. These
562 libraries include common code to deal with U-Boot images,
563 environment and USB, for example. This option is enabled on many
564 boards. Enable this option to build the code in common/ as part of
565 an SPL build.
566
567config SPL_LIBDISK_SUPPORT
568 bool "Support disk partitions"
569 select PARTITIONS
570 help
571 Enable support for disk partitions within SPL. 'Disk' is something
572 of a misnomer as it includes non-spinning media such as flash (as
573 used in MMC and USB sticks). Partitions provide a way for a disk
574 to be split up into separate regions, with a partition table placed
575 at the start or end which describes the location and size of each
576 'partition'. These partitions are typically uses as individual block
577 devices, typically with an EXT2 or FAT filesystem in each. This
578 option enables whatever partition support has been enabled in
579 U-Boot to also be used in SPL. It brings in the code in disk/.
580
581config SPL_LIBGENERIC_SUPPORT
582 bool "Support generic libraries"
583 help
584 Enable support for generic U-Boot libraries within SPL. These
585 libraries include generic code to deal with device tree, hashing,
586 printf(), compression and the like. This option is enabled on many
587 boards. Enable this option to build the code in lib/ as part of an
588 SPL build.
589
590config SPL_DM_MAILBOX
591 bool "Support Mailbox"
592 help
593 Enable support for Mailbox within SPL. This enable the inter
594 processor communication protocols tobe used within SPL. Enable
595 this option to build the drivers in drivers/mailbox as part of
596 SPL build.
597
598config SPL_MMC_SUPPORT
599 bool "Support MMC"
600 depends on MMC
601 select HAVE_BLOCK_DEVICE
602 help
603 Enable support for MMC (Multimedia Card) within SPL. This enables
604 the MMC protocol implementation and allows any enabled drivers to
605 be used within SPL. MMC can be used with or without disk partition
606 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
607 this option to build the drivers in drivers/mmc as part of an SPL
608 build.
609
610config SPL_MMC_TINY
611 bool "Tiny MMC framework in SPL"
612 depends on SPL_MMC_SUPPORT
613 default n
614 help
615 Enable MMC framework tinification support. This option is useful if
616 if your SPL is extremely size constrained. Heed the warning, enable
617 this option if and only if you know exactly what you are doing, if
618 you are reading this help text, you most likely have no idea :-)
619
620 The MMC framework is reduced to bare minimum to be useful. No malloc
621 support is needed for the MMC framework operation with this option
622 enabled. The framework supports exactly one MMC device and exactly
623 one MMC driver. The MMC driver can be adjusted to avoid any malloc
624 operations too, which can remove the need for malloc support in SPL
625 and thus further reduce footprint.
626
627config SPL_MMC_WRITE
628 bool "MMC/SD/SDIO card support for write operations in SPL"
629 depends on SPL_MMC_SUPPORT
630 default n
631 help
632 Enable write access to MMC and SD Cards in SPL
633
634
635config SPL_MPC8XXX_INIT_DDR_SUPPORT
636 bool "Support MPC8XXX DDR init"
637 help
638 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
639 random-access memory) on the MPC8XXX family within SPL. This
640 allows DRAM to be set up before loading U-Boot into that DRAM,
641 where it can run.
642
643config SPL_MTD_SUPPORT
644 bool "Support MTD drivers"
645 help
646 Enable support for MTD (Memory Technology Device) within SPL. MTD
647 provides a block interface over raw NAND and can also be used with
648 SPI flash. This allows SPL to load U-Boot from supported MTD
649 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
650 to enable specific MTD drivers.
651
652config SPL_MUSB_NEW_SUPPORT
653 bool "Support new Mentor Graphics USB"
654 help
655 Enable support for Mentor Graphics USB in SPL. This is a new
656 driver used by some boards. Enable this option to build
657 the drivers in drivers/usb/musb-new as part of an SPL build. The
658 old drivers are in drivers/usb/musb.
659
660config SPL_NAND_SUPPORT
661 bool "Support NAND flash"
662 help
663 Enable support for NAND (Negative AND) flash in SPL. NAND flash
664 can be used to allow SPL to load U-Boot from supported devices.
665 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
666 build.
667
668config SPL_UBI
669 bool "Support UBI"
670 help
671 Enable support for loading payloads from UBI. See
672 README.ubispl for more info.
673
674if SPL_UBI
675config SPL_UBI_LOAD_BY_VOLNAME
676 bool "Support loading volumes by name"
677 help
678 This enables support for loading UBI volumes by name. When this
679 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
680 configure the volume name from which to load U-Boot.
681
682config SPL_UBI_MAX_VOL_LEBS
683 int "Maximum number of LEBs per volume"
684 depends on SPL_UBI
685 help
686 The maximum number of logical eraseblocks which a static volume
687 to load can contain. Used for sizing the scan data structure.
688
689config SPL_UBI_MAX_PEB_SIZE
690 int "Maximum PEB size"
691 depends on SPL_UBI
692 help
693 The maximum physical erase block size.
694
695config SPL_UBI_MAX_PEBS
696 int "Maximum number of PEBs"
697 depends on SPL_UBI
698 help
699 The maximum physical erase block size. If not overridden by
700 board code, this value will be used as the actual number of PEBs.
701
702config SPL_UBI_PEB_OFFSET
703 int "Offset to first UBI PEB"
704 depends on SPL_UBI
705 help
706 The offset in number of PEBs from the start of flash to the first
707 PEB part of the UBI image.
708
709config SPL_UBI_VID_OFFSET
710 int "Offset to VID header"
711 depends on SPL_UBI
712
713config SPL_UBI_LEB_START
714 int "Offset to LEB in PEB"
715 depends on SPL_UBI
716 help
717 The offset in bytes to the LEB within a PEB.
718
719config SPL_UBI_INFO_ADDR
720 hex "Address to place UBI scan info"
721 depends on SPL_UBI
722 help
723 Address for ubispl to place the scan info. Read README.ubispl to
724 determine the required size
725
726config SPL_UBI_VOL_IDS
727 int "Maximum volume id"
728 depends on SPL_UBI
729 help
730 The maximum volume id which can be loaded. Used for sizing the
731 scan data structure.
732
733config SPL_UBI_LOAD_MONITOR_ID
734 int "id of U-Boot volume"
735 depends on SPL_UBI
736 help
737 The UBI volume id from which to load U-Boot
738
739config SPL_UBI_LOAD_MONITOR_VOLNAME
740 string "volume name of U-Boot volume"
741 depends on SPL_UBI_LOAD_BY_VOLNAME
742 help
743 The UBI volume name from which to load U-Boot
744
745config SPL_UBI_LOAD_KERNEL_ID
746 int "id of kernel volume"
747 depends on SPL_OS_BOOT && SPL_UBI
748 help
749 The UBI volume id from which to load the kernel
750
751config SPL_UBI_LOAD_ARGS_ID
752 int "id of kernel args volume"
753 depends on SPL_OS_BOOT && SPL_UBI
754 help
755 The UBI volume id from which to load the device tree
756
757config UBI_SPL_SILENCE_MSG
758 bool "silence UBI SPL messages"
759 default n
760 help
761 Disable messages from UBI SPL. This leaves warnings
762 and errors enabled.
763
764endif
765
766config SPL_NET_SUPPORT
767 bool "Support networking"
768 help
769 Enable support for network devices (such as Ethernet) in SPL.
770 This permits SPL to load U-Boot over a network link rather than
771 from an on-board peripheral. Environment support is required since
772 the network stack uses a number of environment variables. See also
773 SPL_ETH_SUPPORT.
774
775if SPL_NET_SUPPORT
776config SPL_NET_VCI_STRING
777 string "BOOTP Vendor Class Identifier string sent by SPL"
778 help
779 As defined by RFC 2132 the vendor class identifier field can be
780 sent by the client to identify the vendor type and configuration
781 of a client. This is often used in practice to allow for the DHCP
782 server to specify different files to load depending on if the ROM,
783 SPL or U-Boot itself makes the request
784endif
785
786config SPL_NO_CPU_SUPPORT
787 bool "Drop CPU code in SPL"
788 help
789 This is specific to the ARM926EJ-S CPU. It disables the standard
790 start.S start-up code, presumably so that a replacement can be
791 used on that CPU. You should not enable it unless you know what
792 you are doing.
793
794config SPL_NOR_SUPPORT
795 bool "Support NOR flash"
796 help
797 Enable support for loading U-Boot from memory-mapped NOR (Negative
798 OR) flash in SPL. NOR flash is slow to write but fast to read, and
799 a memory-mapped device makes it very easy to access. Loading from
800 NOR is typically achieved with just a memcpy().
801
802config SPL_XIP_SUPPORT
803 bool "Support XIP"
804 depends on SPL
805 help
806 Enable support for execute in place of U-Boot or kernel image. There
807 is no need to copy image from flash to ram if flash supports execute
808 in place. Its very useful in systems having enough flash but not
809 enough ram to load the image.
810
811config SPL_ONENAND_SUPPORT
812 bool "Support OneNAND flash"
813 help
814 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
815 a type of NAND flash and therefore can be used to allow SPL to
816 load U-Boot from supported devices. This enables the drivers in
817 drivers/mtd/onenand as part of an SPL build.
818
819config SPL_OS_BOOT
820 bool "Activate Falcon Mode"
821 depends on !TI_SECURE_DEVICE
822 default n
823 help
824 Enable booting directly to an OS from SPL.
825 for more info read doc/README.falcon
826
827if SPL_OS_BOOT
828config SYS_OS_BASE
829 hex "addr, where OS is found"
830 depends on SPL_NOR_SUPPORT
831 help
832 Specify the address, where the OS image is found, which
833 gets booted.
834
835endif
836
837config SPL_PAYLOAD
838 string "SPL payload"
839 default "tpl/u-boot-with-tpl.bin" if TPL
840 default "u-boot.bin"
841 help
842 Payload for SPL boot. For backward compatibility, default to
843 u-boot.bin, i.e. RAW image without any header. In case of
844 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
845 use u-boot.img.
846
847config SPL_PCI
848 bool "Support PCI drivers"
849 help
850 Enable support for PCI in SPL. For platforms that need PCI to boot,
851 or must perform some init using PCI in SPL, this provides the
852 necessary driver support. This enables the drivers in drivers/pci
853 as part of an SPL build.
854
855config SPL_PCH_SUPPORT
856 bool "Support PCH drivers"
857 help
858 Enable support for PCH (Platform Controller Hub) devices in SPL.
859 These are used to set up GPIOs and the SPI peripheral early in
860 boot. This enables the drivers in drivers/pch as part of an SPL
861 build.
862
863config SPL_POST_MEM_SUPPORT
864 bool "Support POST drivers"
865 help
866 Enable support for POST (Power-on Self Test) in SPL. POST is a
867 procedure that checks that the hardware (CPU or board) appears to
868 be functionally correctly. It is a sanity check that can be
869 performed before booting. This enables the drivers in post/drivers
870 as part of an SPL build.
871
872config SPL_DM_RESET
873 bool "Support reset drivers"
874 depends on SPL
875 help
876 Enable support for reset control in SPL.
877 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
878 by using the generic reset API provided by driver model.
879 This enables the drivers in drivers/reset as part of an SPL build.
880
881config SPL_POWER_SUPPORT
882 bool "Support power drivers"
883 help
884 Enable support for power control in SPL. This includes support
885 for PMICs (Power-management Integrated Circuits) and some of the
886 features provided by PMICs. In particular, voltage regulators can
887 be used to enable/disable power and vary its voltage. That can be
888 useful in SPL to turn on boot peripherals and adjust CPU voltage
889 so that the clock speed can be increased. This enables the drivers
890 in drivers/power, drivers/power/pmic and drivers/power/regulator
891 as part of an SPL build.
892
893config SPL_POWER_DOMAIN
894 bool "Support power domain drivers"
895 help
896 Enable support for power domain control in SPL. Many SoCs allow
897 power to be applied to or removed from portions of the SoC (power
898 domains). This may be used to save power. This API provides the
899 means to control such power management hardware. This enables
900 the drivers in drivers/power/domain as part of a SPL build.
901
902config SPL_RAM_SUPPORT
903 bool "Support booting from RAM"
904 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
905 help
906 Enable booting of an image in RAM. The image can be preloaded or
907 it can be loaded by SPL directly into RAM (e.g. using USB).
908
909config SPL_RAM_DEVICE
910 bool "Support booting from preloaded image in RAM"
911 depends on SPL_RAM_SUPPORT
912 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
913 help
914 Enable booting of an image already loaded in RAM. The image has to
915 be already in memory when SPL takes over, e.g. loaded by the boot
916 ROM.
917
918config SPL_REMOTEPROC
919 bool "Support REMOTEPROCS"
920 help
921 Enable support for REMOTEPROCs in SPL. This permits to load
922 a remote processor firmware in SPL.
923
924config SPL_RTC_SUPPORT
925 bool "Support RTC drivers"
926 help
927 Enable RTC (Real-time Clock) support in SPL. This includes support
928 for reading and setting the time. Some RTC devices also have some
929 non-volatile (battery-backed) memory which is accessible if
930 needed. This enables the drivers in drivers/rtc as part of an SPL
931 build.
932
933config SPL_SATA_SUPPORT
934 bool "Support loading from SATA"
935 help
936 Enable support for SATA (Serial AT attachment) in SPL. This allows
937 use of SATA devices such as hard drives and flash drivers for
938 loading U-Boot. SATA is used in higher-end embedded systems and
939 can provide higher performance than MMC , at somewhat higher
940 expense and power consumption. This enables loading from SATA
941 using a configured device.
942
943config SPL_SATA_RAW_U_BOOT_USE_SECTOR
944 bool "SATA raw mode: by sector"
945 depends on SPL_SATA_SUPPORT
946 help
947 Use sector number for specifying U-Boot location on SATA disk in
948 raw mode.
949
950config SPL_SATA_RAW_U_BOOT_SECTOR
951 hex "Sector on the SATA disk to load U-Boot from"
952 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
953 help
954 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
955 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
956
957config SPL_SERIAL_SUPPORT
958 bool "Support serial"
959 select SPL_PRINTF
960 select SPL_STRTO
961 help
962 Enable support for serial in SPL. This allows use of a serial UART
963 for displaying messages while SPL is running. It also brings in
964 printf() and panic() functions. This should normally be enabled
965 unless there are space reasons not to. Even then, consider
966 enabling USE_TINY_PRINTF which is a small printf() version.
967
968config SPL_SPI_FLASH_SUPPORT
969 bool "Support SPI flash drivers"
970 help
971 Enable support for using SPI flash in SPL, and loading U-Boot from
972 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
973 the SPI bus that is used to connect it to a system. It is a simple
974 but fast bidirectional 4-wire bus (clock, chip select and two data
975 lines). This enables the drivers in drivers/mtd/spi as part of an
976 SPL build. This normally requires SPL_SPI_SUPPORT.
977
978if SPL_SPI_FLASH_SUPPORT
979
980config SPL_SPI_FLASH_TINY
981 bool "Enable low footprint SPL SPI Flash support"
982 depends on !SPI_FLASH_BAR
983 default y if SPI_FLASH
984 help
985 Enable lightweight SPL SPI Flash support that supports just reading
986 data/images from flash. No support to write/erase flash. Enable
987 this if you have SPL size limitations and don't need full
988 fledged SPI flash support.
989
990config SPL_SPI_FLASH_SFDP_SUPPORT
991 bool "SFDP table parsing support for SPI NOR flashes"
992 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
993 help
994 Enable support for parsing and auto discovery of parameters for
995 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
996 tables as per JESD216 standard in SPL.
997
998config SPL_SPI_LOAD
999 bool "Support loading from SPI flash"
1000 help
1001 Enable support for loading next stage, U-Boot or otherwise, from
1002 SPI NOR in U-Boot SPL.
1003
1004endif
1005
1006config SYS_SPI_U_BOOT_OFFS
1007 hex "address of u-boot payload in SPI flash"
1008 default 0x0
1009 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1010 help
1011 Address within SPI-Flash from where the u-boot payload is fetched
1012 from.
1013
1014config SPL_SPI_SUPPORT
1015 bool "Support SPI drivers"
1016 help
1017 Enable support for using SPI in SPL. This is used for connecting
1018 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1019 more details on that. The SPI driver provides the transport for
1020 data between the SPI flash and the CPU. This option can be used to
1021 enable SPI drivers that are needed for other purposes also, such
1022 as a SPI PMIC.
1023
1024config SPL_THERMAL
1025 bool "Driver support for thermal devices"
1026 help
1027 Enable support for temperature-sensing devices. Some SoCs have on-chip
1028 temperature sensors to permit warnings, speed throttling or even
1029 automatic power-off when the temperature gets too high or low. Other
1030 devices may be discrete but connected on a suitable bus.
1031
1032config SPL_USB_HOST_SUPPORT
1033 bool "Support USB host drivers"
1034 select HAVE_BLOCK_DEVICE
1035 help
1036 Enable access to USB (Universal Serial Bus) host devices so that
1037 SPL can load U-Boot from a connected USB peripheral, such as a USB
1038 flash stick. While USB takes a little longer to start up than most
1039 buses, it is very flexible since many different types of storage
1040 device can be attached. This option enables the drivers in
1041 drivers/usb/host as part of an SPL build.
1042
1043config SPL_USB_STORAGE
1044 bool "Support loading from USB"
1045 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1046 help
1047 Enable support for USB devices in SPL. This allows use of USB
1048 devices such as hard drives and flash drivers for loading U-Boot.
1049 The actual drivers are enabled separately using the normal U-Boot
1050 config options. This enables loading from USB using a configured
1051 device.
1052
1053config SPL_USB_GADGET
1054 bool "Suppport USB Gadget drivers"
1055 help
1056 Enable USB Gadget API which allows to enable USB device functions
1057 in SPL.
1058
1059if SPL_USB_GADGET
1060
1061config SPL_USB_ETHER
1062 bool "Support USB Ethernet drivers"
1063 help
1064 Enable access to the USB network subsystem and associated
1065 drivers in SPL. This permits SPL to load U-Boot over a
1066 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1067 than from an onboard peripheral. Environment support is required
1068 since the network stack uses a number of environment variables.
1069 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1070
1071config SPL_DFU
1072 bool "Support DFU (Device Firmware Upgrade)"
1073 select SPL_HASH_SUPPORT
1074 select SPL_DFU_NO_RESET
1075 depends on SPL_RAM_SUPPORT
1076 help
1077 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1078 RAM memory device support. The ROM code will load and execute
1079 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1080 selected device partition from host-pc using dfu-utils.
1081 This feature is useful to flash the binaries to factory or bare-metal
1082 boards using USB interface.
1083
1084choice
1085 bool "DFU device selection"
1086 depends on SPL_DFU
1087
1088config SPL_DFU_RAM
1089 bool "RAM device"
1090 depends on SPL_DFU && SPL_RAM_SUPPORT
1091 help
1092 select RAM/DDR memory device for loading binary images
1093 (u-boot/kernel) to the selected device partition using
1094 DFU and execute the u-boot/kernel from RAM.
1095
1096endchoice
1097
1098config SPL_USB_SDP_SUPPORT
1099 bool "Support SDP (Serial Download Protocol)"
1100 help
1101 Enable Serial Download Protocol (SDP) device support in SPL. This
1102 allows to download images into memory and execute (jump to) them
1103 using the same protocol as implemented by the i.MX family's boot ROM.
1104endif
1105
1106config SPL_WATCHDOG_SUPPORT
1107 bool "Support watchdog drivers"
1108 imply SPL_WDT if !HW_WATCHDOG
1109 help
1110 Enable support for watchdog drivers in SPL. A watchdog is
1111 typically a hardware peripheral which can reset the system when it
1112 detects no activity for a while (such as a software crash). This
1113 enables the drivers in drivers/watchdog as part of an SPL build.
1114
1115config SPL_YMODEM_SUPPORT
1116 bool "Support loading using Ymodem"
1117 depends on SPL_SERIAL_SUPPORT
1118 help
1119 While loading from serial is slow it can be a useful backup when
1120 there is no other option. The Ymodem protocol provides a reliable
1121 means of transmitting U-Boot over a serial line for using in SPL,
1122 with a checksum to ensure correctness.
1123
1124config SPL_ATF
1125 bool "Support ARM Trusted Firmware"
1126 depends on ARM64
1127 help
1128 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1129 is loaded by SPL (which is considered as BL2 in ATF terminology).
1130 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1131
1132config SPL_ATF_NO_PLATFORM_PARAM
1133 bool "Pass no platform parameter"
1134 depends on SPL_ATF
1135 help
1136 While we expect to call a pointer to a valid FDT (or NULL)
1137 as the platform parameter to an ATF, some ATF versions are
1138 not U-Boot aware and have an insufficiently robust parameter
1139 validation to gracefully reject a FDT being passed.
1140
1141 If this option is enabled, the spl_atf os-type handler will
1142 always pass NULL for the platform parameter.
1143
1144 If your ATF is affected, say Y.
1145
1146config SPL_AM33XX_ENABLE_RTC32K_OSC
1147 bool "Enable the RTC32K OSC on AM33xx based platforms"
1148 default y if AM33XX
1149 help
1150 Enable access to the AM33xx RTC and select the external 32kHz clock
1151 source.
1152
1153config SPL_OPTEE
1154 bool "Support OP-TEE Trusted OS"
1155 depends on ARM
1156 help
1157 OP-TEE is an open source Trusted OS which is loaded by SPL.
1158 More detail at: https://github.com/OP-TEE/optee_os
1159
1160config SPL_OPENSBI
1161 bool "Support RISC-V OpenSBI"
1162 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1163 help
1164 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1165 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1166 firmware. It is loaded and started by U-Boot SPL.
1167
1168 More details are available at https://github.com/riscv/opensbi and
1169 https://github.com/riscv/riscv-sbi-doc
1170
1171config SPL_OPENSBI_LOAD_ADDR
1172 hex "OpenSBI load address"
1173 depends on SPL_OPENSBI
1174 help
1175 Load address of the OpenSBI binary.
1176
1177config TPL
1178 bool
1179 depends on SUPPORT_TPL
1180 prompt "Enable TPL"
1181 help
1182 If you want to build TPL as well as the normal image and SPL, say Y.
1183
1184if TPL
1185
1186config TPL_HANDOFF
1187 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1188 depends on HANDOFF
1189 default y
1190 help
1191 This option enables TPL to write handoff information. This can be
1192 used to pass information like the size of SDRAM from TPL to U-Boot
1193 proper. The information is also available to SPL if it is useful
1194 there.
1195
1196config TPL_BOARD_INIT
1197 bool "Call board-specific initialization in TPL"
1198 help
1199 If this option is enabled, U-Boot will call the function
1200 spl_board_init() from board_init_r(). This function should be
1201 provided by the board.
1202
1203config TPL_LDSCRIPT
1204 string "Linker script for the TPL stage"
1205 depends on TPL
1206 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1207 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1208 help
1209 The TPL stage will usually require a different linker-script
1210 (as it runs from a different memory region) than the regular
1211 U-Boot stage. Set this to the path of the linker-script to
1212 be used for TPL.
1213
1214 May be left empty to trigger the Makefile infrastructure to
1215 fall back to the linker-script used for the SPL stage.
1216
1217config TPL_NEEDS_SEPARATE_TEXT_BASE
1218 bool "TPL needs a separate text-base"
1219 default n
1220 depends on TPL
1221 help
1222 Enable, if the TPL stage should not inherit its text-base
1223 from the SPL stage. When enabled, a base address for the
1224 .text sections of the TPL stage has to be set below.
1225
1226config TPL_NEEDS_SEPARATE_STACK
1227 bool "TPL needs a separate initial stack-pointer"
1228 default n
1229 depends on TPL
1230 help
1231 Enable, if the TPL stage should not inherit its initial
1232 stack-pointer from the settings for the SPL stage.
1233
1234config TPL_TEXT_BASE
1235 hex "Base address for the .text section of the TPL stage"
1236 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1237 help
1238 The base address for the .text section of the TPL stage.
1239
1240config TPL_MAX_SIZE
1241 int "Maximum size (in bytes) for the TPL stage"
1242 default 0
1243 depends on TPL
1244 help
1245 The maximum size (in bytes) of the TPL stage.
1246
1247config TPL_STACK
1248 hex "Address of the initial stack-pointer for the TPL stage"
1249 depends on TPL_NEEDS_SEPARATE_STACK
1250 help
1251 The address of the initial stack-pointer for the TPL stage.
1252 Usually this will be the (aligned) top-of-stack.
1253
1254config TPL_BOOTROM_SUPPORT
1255 bool "Support returning to the BOOTROM (from TPL)"
1256 help
1257 Some platforms (e.g. the Rockchip RK3368) provide support in their
1258 ROM for loading the next boot-stage after performing basic setup
1259 from the TPL stage.
1260
1261 Enable this option, to return to the BOOTROM through the
1262 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1263 boot device list, if not implemented for a given board)
1264
1265config TPL_DRIVERS_MISC_SUPPORT
1266 bool "Support misc drivers in TPL"
1267 help
1268 Enable miscellaneous drivers in TPL. These drivers perform various
1269 tasks that don't fall nicely into other categories, Enable this
1270 option to build the drivers in drivers/misc as part of an TPL
1271 build, for those that support building in TPL (not all drivers do).
1272
1273config TPL_ENV_SUPPORT
1274 bool "Support an environment"
1275 help
1276 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1277
1278config TPL_GPIO_SUPPORT
1279 bool "Support GPIO in TPL"
1280 help
1281 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1282 GPIOs allow U-Boot to read the state of an input line (high or
1283 low) and set the state of an output line. This can be used to
1284 drive LEDs, control power to various system parts and read user
1285 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1286 for example. Enable this option to build the drivers in
1287 drivers/gpio as part of an TPL build.
1288
1289config TPL_I2C_SUPPORT
1290 bool "Support I2C"
1291 help
1292 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1293 details.
1294
1295config TPL_LIBCOMMON_SUPPORT
1296 bool "Support common libraries"
1297 help
1298 Enable support for common U-Boot libraries within TPL. See
1299 SPL_LIBCOMMON_SUPPORT for details.
1300
1301config TPL_LIBGENERIC_SUPPORT
1302 bool "Support generic libraries"
1303 help
1304 Enable support for generic U-Boot libraries within TPL. See
1305 SPL_LIBGENERIC_SUPPORT for details.
1306
1307config TPL_MPC8XXX_INIT_DDR_SUPPORT
1308 bool "Support MPC8XXX DDR init"
1309 help
1310 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1311 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1312
1313config TPL_MMC_SUPPORT
1314 bool "Support MMC"
1315 depends on MMC
1316 help
1317 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1318
1319config TPL_NAND_SUPPORT
1320 bool "Support NAND flash"
1321 help
1322 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1323
1324config TPL_PCI
1325 bool "Support PCI drivers"
1326 help
1327 Enable support for PCI in TPL. For platforms that need PCI to boot,
1328 or must perform some init using PCI in SPL, this provides the
1329 necessary driver support. This enables the drivers in drivers/pci
1330 as part of a TPL build.
1331
1332config TPL_PCH_SUPPORT
1333 bool "Support PCH drivers"
1334 help
1335 Enable support for PCH (Platform Controller Hub) devices in TPL.
1336 These are used to set up GPIOs and the SPI peripheral early in
1337 boot. This enables the drivers in drivers/pch as part of a TPL
1338 build.
1339
1340config TPL_RAM_SUPPORT
1341 bool "Support booting from RAM"
1342 help
1343 Enable booting of an image in RAM. The image can be preloaded or
1344 it can be loaded by TPL directly into RAM (e.g. using USB).
1345
1346config TPL_RAM_DEVICE
1347 bool "Support booting from preloaded image in RAM"
1348 depends on TPL_RAM_SUPPORT
1349 help
1350 Enable booting of an image already loaded in RAM. The image has to
1351 be already in memory when TPL takes over, e.g. loaded by the boot
1352 ROM.
1353
1354config TPL_RTC_SUPPORT
1355 bool "Support RTC drivers"
1356 help
1357 Enable RTC (Real-time Clock) support in TPL. This includes support
1358 for reading and setting the time. Some RTC devices also have some
1359 non-volatile (battery-backed) memory which is accessible if
1360 needed. This enables the drivers in drivers/rtc as part of an TPL
1361 build.
1362
1363config TPL_SERIAL_SUPPORT
1364 bool "Support serial"
1365 select TPL_PRINTF
1366 select TPL_STRTO
1367 help
1368 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1369 details.
1370
1371config TPL_SPI_FLASH_SUPPORT
1372 bool "Support SPI flash drivers"
1373 help
1374 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1375 for details.
1376
1377config TPL_SPI_LOAD
1378 bool "Support loading from SPI flash"
1379 depends on TPL_SPI_FLASH_SUPPORT
1380 help
1381 Enable support for loading next stage, U-Boot or otherwise, from
1382 SPI NOR in U-Boot TPL.
1383
1384config TPL_SPI_SUPPORT
1385 bool "Support SPI drivers"
1386 help
1387 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1388 details.
1389
1390config TPL_YMODEM_SUPPORT
1391 bool "Support loading using Ymodem"
1392 depends on TPL_SERIAL_SUPPORT
1393 help
1394 While loading from serial is slow it can be a useful backup when
1395 there is no other option. The Ymodem protocol provides a reliable
1396 means of transmitting U-Boot over a serial line for using in TPL,
1397 with a checksum to ensure correctness.
1398
1399endif
1400
1401config SPL_AT91_MCK_BYPASS
1402 bool "Use external clock signal as a source of main clock for AT91 platforms"
1403 depends on ARCH_AT91
1404 default n
1405 help
1406 Use external 8 to 24 Mhz clock signal as source of main clock instead
1407 of an external crystal oscillator.
1408 This option disables the internal driving on the XOUT pin.
1409 The external source has to provide a stable clock on the XIN pin.
1410 If this option is disabled, the SoC expects a crystal oscillator
1411 that needs driving on both XIN and XOUT lines.
1412
1413endif
1414endmenu
1415
