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