xref: /openbmc/u-boot/common/spl/Kconfig (revision e7ab6dfc)
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_EXT_SUPPORT
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_FAT_SUPPORT
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_FPGA_SUPPORT
408	bool "Support FPGAs"
409	help
410	  Enable support for FPGAs in SPL. Field-programmable Gate Arrays
411	  provide software-configurable hardware which is typically used to
412	  implement peripherals (such as UARTs, LCD displays, MMC) or
413	  accelerate custom processing functions, such as image processing
414	  or machine learning. Sometimes it is useful to program the FPGA
415	  as early as possible during boot, and this option can enable that
416	  within SPL.
417
418config SPL_GPIO_SUPPORT
419	bool "Support GPIO in SPL"
420	help
421	  Enable support for GPIOs (General-purpose Input/Output) in SPL.
422	  GPIOs allow U-Boot to read the state of an input line (high or
423	  low) and set the state of an output line. This can be used to
424	  drive LEDs, control power to various system parts and read user
425	  input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
426	  for example. Enable this option to build the drivers in
427	  drivers/gpio as part of an SPL build.
428
429config SPL_I2C_SUPPORT
430	bool "Support I2C"
431	help
432	  Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
433	  I2C works with a clock and data line which can be driven by a
434	  one or more masters or slaves. It is a fairly complex bus but is
435	  widely used as it only needs two lines for communication. Speeds of
436	  400kbps are typical but up to 3.4Mbps is supported by some
437	  hardware. I2C can be useful in SPL to configure power management
438	  ICs (PMICs) before raising the CPU clock speed, for example.
439	  Enable this option to build the drivers in drivers/i2c as part of
440	  an SPL build.
441
442config SPL_LIBCOMMON_SUPPORT
443	bool "Support common libraries"
444	help
445	  Enable support for common U-Boot libraries within SPL. These
446	  libraries include common code to deal with U-Boot images,
447	  environment and USB, for example. This option is enabled on many
448	  boards. Enable this option to build the code in common/ as part of
449	  an SPL build.
450
451config SPL_LIBDISK_SUPPORT
452	bool "Support disk partitions"
453	select PARTITIONS
454	help
455	  Enable support for disk partitions within SPL. 'Disk' is something
456	  of a misnomer as it includes non-spinning media such as flash (as
457	  used in MMC and USB sticks). Partitions provide a way for a disk
458	  to be split up into separate regions, with a partition table placed
459	  at the start or end which describes the location and size of each
460	  'partition'. These partitions are typically uses as individual block
461	  devices, typically with an EXT2 or FAT filesystem in each. This
462	  option enables whatever partition support has been enabled in
463	  U-Boot to also be used in SPL. It brings in the code in disk/.
464
465config SPL_LIBGENERIC_SUPPORT
466	bool "Support generic libraries"
467	help
468	  Enable support for generic U-Boot libraries within SPL. These
469	  libraries include generic code to deal with device tree, hashing,
470	  printf(), compression and the like. This option is enabled on many
471	  boards. Enable this option to build the code in lib/ as part of an
472	  SPL build.
473
474config SPL_DM_MAILBOX
475	bool "Support Mailbox"
476	help
477	  Enable support for Mailbox within SPL. This enable the inter
478	  processor communication protocols tobe used within SPL. Enable
479	  this option to build the drivers in drivers/mailbox as part of
480	  SPL build.
481
482config SPL_MMC_SUPPORT
483	bool "Support MMC"
484	depends on MMC
485	select HAVE_BLOCK_DEVICE
486	help
487	  Enable support for MMC (Multimedia Card) within SPL. This enables
488	  the MMC protocol implementation and allows any enabled drivers to
489	  be used within SPL. MMC can be used with or without disk partition
490	  support depending on the application (SPL_LIBDISK_SUPPORT). Enable
491	  this option to build the drivers in drivers/mmc as part of an SPL
492	  build.
493
494config SPL_MMC_WRITE
495	bool "MMC/SD/SDIO card support for write operations in SPL"
496	depends on SPL_MMC_SUPPORT
497	default n
498	help
499	  Enable write access to MMC and SD Cards in SPL
500
501
502config SPL_MPC8XXX_INIT_DDR_SUPPORT
503	bool "Support MPC8XXX DDR init"
504	help
505	  Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
506	  random-access memory) on the MPC8XXX family within SPL. This
507	  allows DRAM to be set up before loading U-Boot into that DRAM,
508	  where it can run.
509
510config SPL_MTD_SUPPORT
511	bool "Support MTD drivers"
512	help
513	  Enable support for MTD (Memory Technology Device) within SPL. MTD
514	  provides a block interface over raw NAND and can also be used with
515	  SPI flash. This allows SPL to load U-Boot from supported MTD
516	  devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
517	  to enable specific MTD drivers.
518
519config SPL_MUSB_NEW_SUPPORT
520	bool "Support new Mentor Graphics USB"
521	help
522	  Enable support for Mentor Graphics USB in SPL. This is a new
523	  driver used by some boards. Enable this option to build
524	  the drivers in drivers/usb/musb-new as part of an SPL build. The
525	  old drivers are in drivers/usb/musb.
526
527config SPL_NAND_SUPPORT
528	bool "Support NAND flash"
529	help
530	  Enable support for NAND (Negative AND) flash in SPL. NAND flash
531	  can be used to allow SPL to load U-Boot from supported devices.
532	  This enables the drivers in drivers/mtd/nand/raw as part of an SPL
533	  build.
534
535config SPL_NET_SUPPORT
536	bool "Support networking"
537	help
538	  Enable support for network devices (such as Ethernet) in SPL.
539	  This permits SPL to load U-Boot over a network link rather than
540	  from an on-board peripheral. Environment support is required since
541	  the network stack uses a number of environment variables. See also
542	  SPL_ETH_SUPPORT.
543
544if SPL_NET_SUPPORT
545config SPL_NET_VCI_STRING
546	string "BOOTP Vendor Class Identifier string sent by SPL"
547	help
548	  As defined by RFC 2132 the vendor class identifier field can be
549	  sent by the client to identify the vendor type and configuration
550	  of a client.  This is often used in practice to allow for the DHCP
551	  server to specify different files to load depending on if the ROM,
552	  SPL or U-Boot itself makes the request
553endif   # if SPL_NET_SUPPORT
554
555config SPL_NO_CPU_SUPPORT
556	bool "Drop CPU code in SPL"
557	help
558	  This is specific to the ARM926EJ-S CPU. It disables the standard
559	  start.S start-up code, presumably so that a replacement can be
560	  used on that CPU. You should not enable it unless you know what
561	  you are doing.
562
563config SPL_NOR_SUPPORT
564	bool "Support NOR flash"
565	help
566	  Enable support for loading U-Boot from memory-mapped NOR (Negative
567	  OR) flash in SPL. NOR flash is slow to write but fast to read, and
568	  a memory-mapped device makes it very easy to access. Loading from
569	  NOR is typically achieved with just a memcpy().
570
571config SPL_XIP_SUPPORT
572	bool "Support XIP"
573	depends on SPL
574	help
575	  Enable support for execute in place of U-Boot or kernel image. There
576	  is no need to copy image from flash to ram if flash supports execute
577	  in place. Its very useful in systems having enough flash but not
578	  enough ram to load the image.
579
580config SPL_ONENAND_SUPPORT
581	bool "Support OneNAND flash"
582	help
583	  Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
584	  a type of NAND flash and therefore can be used to allow SPL to
585	  load U-Boot from supported devices. This enables the drivers in
586	  drivers/mtd/onenand as part of an SPL build.
587
588config SPL_OS_BOOT
589	bool "Activate Falcon Mode"
590	depends on !TI_SECURE_DEVICE
591	default n
592	help
593	  Enable booting directly to an OS from SPL.
594	  for more info read doc/README.falcon
595
596if SPL_OS_BOOT
597config SYS_OS_BASE
598	hex "addr, where OS is found"
599	depends on SPL_NOR_SUPPORT
600	help
601	  Specify the address, where the OS image is found, which
602	  gets booted.
603
604endif # SPL_OS_BOOT
605
606config SPL_PAYLOAD
607	string "SPL payload"
608	default "tpl/u-boot-with-tpl.bin" if TPL
609	default "u-boot.bin"
610	help
611	  Payload for SPL boot. For backward compability, default to
612	  u-boot.bin, i.e. RAW image without any header. In case of
613	  TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
614	  use u-boot.img.
615
616config SPL_PCI
617	bool "Support PCI drivers"
618	help
619	  Enable support for PCI in SPL. For platforms that need PCI to boot,
620	  or must perform some init using PCI in SPL, this provides the
621	  necessary driver support. This enables the drivers in drivers/pci
622	  as part of an SPL build.
623
624config SPL_PCH_SUPPORT
625	bool "Support PCH drivers"
626	help
627	  Enable support for PCH (Platform Controller Hub) devices in SPL.
628	  These are used to set up GPIOs and the SPI peripheral early in
629	  boot. This enables the drivers in drivers/pch as part of an SPL
630	  build.
631
632config SPL_POST_MEM_SUPPORT
633	bool "Support POST drivers"
634	help
635	  Enable support for POST (Power-on Self Test) in SPL. POST is a
636	  procedure that checks that the hardware (CPU or board) appears to
637	  be functionally correctly. It is a sanity check that can be
638	  performed before booting. This enables the drivers in post/drivers
639	  as part of an SPL build.
640
641config SPL_DM_RESET
642	bool "Support reset drivers"
643	depends on SPL
644	help
645	  Enable support for reset control in SPL.
646	  That can be useful in SPL to handle IP reset in driver, as in U-Boot,
647	  by using the generic reset API provided by driver model.
648	  This enables the drivers in drivers/reset as part of an SPL build.
649
650config SPL_POWER_SUPPORT
651	bool "Support power drivers"
652	help
653	  Enable support for power control in SPL. This includes support
654	  for PMICs (Power-management Integrated Circuits) and some of the
655	  features provided by PMICs. In particular, voltage regulators can
656	  be used to enable/disable power and vary its voltage. That can be
657	  useful in SPL to turn on boot peripherals and adjust CPU voltage
658	  so that the clock speed can be increased. This enables the drivers
659	  in drivers/power, drivers/power/pmic and drivers/power/regulator
660	  as part of an SPL build.
661
662config SPL_POWER_DOMAIN
663	bool "Support power domain drivers"
664	help
665	  Enable support for power domain control in SPL. Many SoCs allow
666	  power to be applied to or removed from portions of the SoC (power
667	  domains). This may be used to save power. This API provides the
668	  means to control such power management hardware. This enables
669	  the drivers in drivers/power/domain as part of a SPL build.
670
671config SPL_RAM_SUPPORT
672	bool "Support booting from RAM"
673	default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
674	help
675	  Enable booting of an image in RAM. The image can be preloaded or
676	  it can be loaded by SPL directly into RAM (e.g. using USB).
677
678config SPL_RAM_DEVICE
679	bool "Support booting from preloaded image in RAM"
680	depends on SPL_RAM_SUPPORT
681	default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
682	help
683	  Enable booting of an image already loaded in RAM. The image has to
684	  be already in memory when SPL takes over, e.g. loaded by the boot
685	  ROM.
686
687config SPL_REMOTEPROC
688	bool "Support REMOTEPROCS"
689	help
690	  Enable support for REMOTEPROCs in SPL. This permits to load
691	  a remote processor firmware in SPL.
692
693config SPL_RTC_SUPPORT
694	bool "Support RTC drivers"
695	help
696	  Enable RTC (Real-time Clock) support in SPL. This includes support
697	  for reading and setting the time. Some RTC devices also have some
698	  non-volatile (battery-backed) memory which is accessible if
699	  needed. This enables the drivers in drivers/rtc as part of an SPL
700	  build.
701
702config SPL_SATA_SUPPORT
703	bool "Support loading from SATA"
704	help
705	  Enable support for SATA (Serial AT attachment) in SPL. This allows
706	  use of SATA devices such as hard drives and flash drivers for
707	  loading U-Boot. SATA is used in higher-end embedded systems and
708	  can provide higher performance than MMC , at somewhat higher
709	  expense and power consumption. This enables loading from SATA
710	  using a configured device.
711
712config SPL_SERIAL_SUPPORT
713	bool "Support serial"
714	select SPL_PRINTF
715	select SPL_STRTO
716	help
717	  Enable support for serial in SPL. This allows use of a serial UART
718	  for displaying messages while SPL is running. It also brings in
719	  printf() and panic() functions. This should normally be enabled
720	  unless there are space reasons not to. Even then, consider
721	  enabling USE_TINY_PRINTF which is a small printf() version.
722
723config SPL_SPI_FLASH_SUPPORT
724	bool "Support SPI flash drivers"
725	help
726	  Enable support for using SPI flash in SPL, and loading U-Boot from
727	  SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
728	  the SPI bus that is used to connect it to a system. It is a simple
729	  but fast bidirectional 4-wire bus (clock, chip select and two data
730	  lines). This enables the drivers in drivers/mtd/spi as part of an
731	  SPL build. This normally requires SPL_SPI_SUPPORT.
732
733config SPL_SPI_LOAD
734	bool "Support loading from SPI flash"
735	depends on SPL_SPI_FLASH_SUPPORT
736	help
737	  Enable support for loading next stage, U-Boot or otherwise, from
738	  SPI NOR in U-Boot SPL.
739
740config SPL_SPI_SUPPORT
741	bool "Support SPI drivers"
742	help
743	  Enable support for using SPI in SPL. This is used for connecting
744	  to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
745	  more details on that. The SPI driver provides the transport for
746	  data between the SPI flash and the CPU. This option can be used to
747	  enable SPI drivers that are needed for other purposes also, such
748	  as a SPI PMIC.
749
750config SPL_THERMAL
751	bool "Driver support for thermal devices"
752	help
753	  Enable support for temperature-sensing devices. Some SoCs have on-chip
754	  temperature sensors to permit warnings, speed throttling or even
755	  automatic power-off when the temperature gets too high or low. Other
756	  devices may be discrete but connected on a suitable bus.
757
758config SPL_USB_HOST_SUPPORT
759	bool "Support USB host drivers"
760	select HAVE_BLOCK_DEVICE
761	help
762	  Enable access to USB (Universal Serial Bus) host devices so that
763	  SPL can load U-Boot from a connected USB peripheral, such as a USB
764	  flash stick. While USB takes a little longer to start up than most
765	  buses, it is very flexible since many different types of storage
766	  device can be attached. This option enables the drivers in
767	  drivers/usb/host as part of an SPL build.
768
769config SPL_USB_SUPPORT
770	bool "Support loading from USB"
771	depends on SPL_USB_HOST_SUPPORT
772	help
773	  Enable support for USB devices in SPL. This allows use of USB
774	  devices such as hard drives and flash drivers for loading U-Boot.
775	  The actual drivers are enabled separately using the normal U-Boot
776	  config options. This enables loading from USB using a configured
777	  device.
778
779config SPL_USB_GADGET
780	bool "Suppport USB Gadget drivers"
781	help
782	  Enable USB Gadget API which allows to enable USB device functions
783	  in SPL.
784
785if SPL_USB_GADGET
786
787config SPL_USB_ETHER
788	bool "Support USB Ethernet drivers"
789	help
790	  Enable access to the USB network subsystem and associated
791	  drivers in SPL. This permits SPL to load U-Boot over a
792	  USB-connected Ethernet link (such as a USB Ethernet dongle) rather
793	  than from an onboard peripheral. Environment support is required
794	  since the network stack uses a number of environment variables.
795	  See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
796
797config SPL_DFU_SUPPORT
798	bool "Support DFU (Device Firmware Upgrade)"
799	select SPL_HASH_SUPPORT
800	select SPL_DFU_NO_RESET
801	depends on SPL_RAM_SUPPORT
802	help
803	  This feature enables the DFU (Device Firmware Upgrade) in SPL with
804	  RAM memory device support. The ROM code will load and execute
805	  the SPL built with dfu. The user can load binaries (u-boot/kernel) to
806	  selected device partition from host-pc using dfu-utils.
807	  This feature is useful to flash the binaries to factory or bare-metal
808	  boards using USB interface.
809
810choice
811	bool "DFU device selection"
812	depends on SPL_DFU_SUPPORT
813
814config SPL_DFU_RAM
815	bool "RAM device"
816	depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
817	help
818	 select RAM/DDR memory device for loading binary images
819	 (u-boot/kernel) to the selected device partition using
820	 DFU and execute the u-boot/kernel from RAM.
821
822endchoice
823
824config SPL_USB_SDP_SUPPORT
825	bool "Support SDP (Serial Download Protocol)"
826	help
827	  Enable Serial Download Protocol (SDP) device support in SPL. This
828	  allows to download images into memory and execute (jump to) them
829	  using the same protocol as implemented by the i.MX family's boot ROM.
830endif
831
832config SPL_WATCHDOG_SUPPORT
833	bool "Support watchdog drivers"
834	help
835	  Enable support for watchdog drivers in SPL. A watchdog is
836	  typically a hardware peripheral which can reset the system when it
837	  detects no activity for a while (such as a software crash). This
838	  enables the drivers in drivers/watchdog as part of an SPL build.
839
840config SPL_YMODEM_SUPPORT
841	bool "Support loading using Ymodem"
842	depends on SPL_SERIAL_SUPPORT
843	help
844	  While loading from serial is slow it can be a useful backup when
845	  there is no other option. The Ymodem protocol provides a reliable
846	  means of transmitting U-Boot over a serial line for using in SPL,
847	  with a checksum to ensure correctness.
848
849config SPL_ATF
850	bool "Support ARM Trusted Firmware"
851	depends on ARM64
852	help
853	  ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
854	  is loaded by SPL (which is considered as BL2 in ATF terminology).
855	  More detail at: https://github.com/ARM-software/arm-trusted-firmware
856
857config SPL_ATF_NO_PLATFORM_PARAM
858        bool "Pass no platform parameter"
859	depends on SPL_ATF
860	help
861	  While we expect to call a pointer to a valid FDT (or NULL)
862	  as the platform parameter to an ATF, some ATF versions are
863	  not U-Boot aware and have an insufficiently robust parameter
864	  validation to gracefully reject a FDT being passed.
865
866	  If this option is enabled, the spl_atf os-type handler will
867	  always pass NULL for the platform parameter.
868
869	  If your ATF is affected, say Y.
870
871config SPL_AM33XX_ENABLE_RTC32K_OSC
872	bool "Enable the RTC32K OSC on AM33xx based platforms"
873	default y if AM33XX
874	help
875	  Enable access to the AM33xx RTC and select the external 32kHz clock
876	  source.
877
878config SPL_OPTEE
879	bool "Support OP-TEE Trusted OS"
880	depends on ARM
881	help
882	  OP-TEE is an open source Trusted OS  which is loaded by SPL.
883	  More detail at: https://github.com/OP-TEE/optee_os
884
885config TPL
886	bool
887	depends on SUPPORT_TPL
888	prompt "Enable TPL"
889	help
890	  If you want to build TPL as well as the normal image and SPL, say Y.
891
892if TPL
893
894config TPL_HANDOFF
895	bool "Pass hand-off information from TPL to SPL and U-Boot proper"
896	depends on HANDOFF
897	default y
898	help
899	  This option enables TPL to write handoff information. This can be
900	  used to pass information like the size of SDRAM from TPL to U-Boot
901	  proper. The information is also available to SPL if it is useful
902	  there.
903
904config TPL_BOARD_INIT
905	bool "Call board-specific initialization in TPL"
906	help
907	  If this option is enabled, U-Boot will call the function
908	  spl_board_init() from board_init_r(). This function should be
909	  provided by the board.
910
911config TPL_LDSCRIPT
912        string "Linker script for the TPL stage"
913	depends on TPL
914	help
915	  The TPL stage will usually require a different linker-script
916	  (as it runs from a different memory region) than the regular
917	  U-Boot stage.  Set this to the path of the linker-script to
918	  be used for TPL.
919
920	  May be left empty to trigger the Makefile infrastructure to
921	  fall back to the linker-script used for the SPL stage.
922
923config TPL_NEEDS_SEPARATE_TEXT_BASE
924        bool "TPL needs a separate text-base"
925	default n
926	depends on TPL
927	help
928	  Enable, if the TPL stage should not inherit its text-base
929	  from the SPL stage.  When enabled, a base address for the
930	  .text sections of the TPL stage has to be set below.
931
932config TPL_NEEDS_SEPARATE_STACK
933        bool "TPL needs a separate initial stack-pointer"
934	default n
935	depends on TPL
936	help
937	  Enable, if the TPL stage should not inherit its initial
938	  stack-pointer from the settings for the SPL stage.
939
940config TPL_TEXT_BASE
941        hex "Base address for the .text section of the TPL stage"
942	depends on TPL_NEEDS_SEPARATE_TEXT_BASE
943	help
944	  The base address for the .text section of the TPL stage.
945
946config TPL_MAX_SIZE
947        int "Maximum size (in bytes) for the TPL stage"
948	default 0
949	depends on TPL
950	help
951	  The maximum size (in bytes) of the TPL stage.
952
953config TPL_STACK
954        hex "Address of the initial stack-pointer for the TPL stage"
955	depends on TPL_NEEDS_SEPARATE_STACK
956	help
957	  The address of the initial stack-pointer for the TPL stage.
958	  Usually this will be the (aligned) top-of-stack.
959
960config TPL_BOOTROM_SUPPORT
961        bool "Support returning to the BOOTROM (from TPL)"
962	help
963	  Some platforms (e.g. the Rockchip RK3368) provide support in their
964	  ROM for loading the next boot-stage after performing basic setup
965	  from the TPL stage.
966
967	  Enable this option, to return to the BOOTROM through the
968	  BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
969	  boot device list, if not implemented for a given board)
970
971config TPL_DRIVERS_MISC_SUPPORT
972	bool "Support misc drivers in TPL"
973	help
974	  Enable miscellaneous drivers in TPL. These drivers perform various
975	  tasks that don't fall nicely into other categories, Enable this
976	  option to build the drivers in drivers/misc as part of an TPL
977	  build, for those that support building in TPL (not all drivers do).
978
979config TPL_ENV_SUPPORT
980	bool "Support an environment"
981	help
982	  Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
983
984config TPL_GPIO_SUPPORT
985	bool "Support GPIO in TPL"
986	help
987	  Enable support for GPIOs (General-purpose Input/Output) in TPL.
988	  GPIOs allow U-Boot to read the state of an input line (high or
989	  low) and set the state of an output line. This can be used to
990	  drive LEDs, control power to various system parts and read user
991	  input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
992	  for example. Enable this option to build the drivers in
993	  drivers/gpio as part of an TPL build.
994
995config TPL_I2C_SUPPORT
996	bool "Support I2C"
997	help
998	  Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
999	  details.
1000
1001config TPL_LIBCOMMON_SUPPORT
1002	bool "Support common libraries"
1003	help
1004	  Enable support for common U-Boot libraries within TPL. See
1005	  SPL_LIBCOMMON_SUPPORT for details.
1006
1007config TPL_LIBGENERIC_SUPPORT
1008	bool "Support generic libraries"
1009	help
1010	  Enable support for generic U-Boot libraries within TPL. See
1011	  SPL_LIBGENERIC_SUPPORT for details.
1012
1013config TPL_MPC8XXX_INIT_DDR_SUPPORT
1014	bool "Support MPC8XXX DDR init"
1015	help
1016	  Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1017	  SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1018
1019config TPL_MMC_SUPPORT
1020	bool "Support MMC"
1021	depends on MMC
1022	help
1023	  Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1024
1025config TPL_NAND_SUPPORT
1026	bool "Support NAND flash"
1027	help
1028	  Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1029
1030config TPL_PCI
1031	bool "Support PCI drivers"
1032	help
1033	  Enable support for PCI in TPL. For platforms that need PCI to boot,
1034	  or must perform some init using PCI in SPL, this provides the
1035	  necessary driver support. This enables the drivers in drivers/pci
1036	  as part of a TPL build.
1037
1038config TPL_PCH_SUPPORT
1039	bool "Support PCH drivers"
1040	help
1041	  Enable support for PCH (Platform Controller Hub) devices in TPL.
1042	  These are used to set up GPIOs and the SPI peripheral early in
1043	  boot. This enables the drivers in drivers/pch as part of a TPL
1044	  build.
1045
1046config TPL_RAM_SUPPORT
1047	bool "Support booting from RAM"
1048	help
1049	  Enable booting of an image in RAM. The image can be preloaded or
1050	  it can be loaded by TPL directly into RAM (e.g. using USB).
1051
1052config TPL_RAM_DEVICE
1053	bool "Support booting from preloaded image in RAM"
1054	depends on TPL_RAM_SUPPORT
1055	help
1056	  Enable booting of an image already loaded in RAM. The image has to
1057	  be already in memory when TPL takes over, e.g. loaded by the boot
1058	  ROM.
1059
1060config TPL_RTC_SUPPORT
1061	bool "Support RTC drivers"
1062	help
1063	  Enable RTC (Real-time Clock) support in TPL. This includes support
1064	  for reading and setting the time. Some RTC devices also have some
1065	  non-volatile (battery-backed) memory which is accessible if
1066	  needed. This enables the drivers in drivers/rtc as part of an TPL
1067	  build.
1068
1069config TPL_SERIAL_SUPPORT
1070	bool "Support serial"
1071	select TPL_PRINTF
1072	select TPL_STRTO
1073	help
1074	  Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1075	  details.
1076
1077config TPL_SPI_FLASH_SUPPORT
1078	bool "Support SPI flash drivers"
1079	help
1080	  Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1081	  for details.
1082
1083config TPL_SPI_LOAD
1084	bool "Support loading from SPI flash"
1085	depends on TPL_SPI_FLASH_SUPPORT
1086	help
1087	  Enable support for loading next stage, U-Boot or otherwise, from
1088	  SPI NOR in U-Boot TPL.
1089
1090config TPL_SPI_SUPPORT
1091	bool "Support SPI drivers"
1092	help
1093	  Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1094	  details.
1095
1096config TPL_YMODEM_SUPPORT
1097	bool "Support loading using Ymodem"
1098	depends on TPL_SERIAL_SUPPORT
1099	help
1100	  While loading from serial is slow it can be a useful backup when
1101	  there is no other option. The Ymodem protocol provides a reliable
1102	  means of transmitting U-Boot over a serial line for using in TPL,
1103	  with a checksum to ensure correctness.
1104
1105endif # TPL
1106
1107endif # SPL
1108endmenu
1109