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