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