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