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