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