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