xref: /openbmc/u-boot/common/spl/Kconfig (revision 0f44d33536a50ef65259c322fa2d4a058585caf9)
1 menu "SPL / TPL"
2 
3 config SUPPORT_SPL
4 	bool
5 
6 config SUPPORT_TPL
7 	bool
8 
9 config SPL_DFU_NO_RESET
10 	bool
11 
12 config 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 
19 config 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 
28 if SPL
29 
30 config 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 
39 config 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 
46 config 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 
57 config 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 
66 config 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 
74 config 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 
83 config 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 
92 config 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 
102 config 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 
110 config 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 
120 config 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 
129 config 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 
136 config 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 
144 config 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 
154 config 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 
170 config 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 
175 config 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 
183 config 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 
191 config 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 
198 config 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 
208 config 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 
220 config 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 
232 config 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 
246 config 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 
261 config 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 
270 config 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 
278 config 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 
288 config 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 
296 config 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 
304 config 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 
316 config 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 
330 config 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 
340 config 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 
348 config 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 
357 config 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 
368 config 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 
379 config 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 
392 config 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 
401 config 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 
414 config 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 
423 config 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 
434 config 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 
442 config 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 
450 config 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 
459 config 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 
467 config 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 
475 config 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 
484 if SPL_NET_SUPPORT
485 config 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
493 endif   # if SPL_NET_SUPPORT
494 
495 config 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 
503 config 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 
511 config 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 
520 config 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 
528 config 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 
536 if SPL_OS_BOOT
537 config 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 
544 endif # SPL_OS_BOOT
545 
546 config 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 
554 config 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 
562 config 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 
571 config SPL_POWER_SUPPORT
572 	bool "Support power drivers"
573 	help
574 	  Enable support for power control in SPL. This includes support
575 	  for PMICs (Power-management Integrated Circuits) and some of the
576 	  features provided by PMICs. In particular, voltage regulators can
577 	  be used to enable/disable power and vary its voltage. That can be
578 	  useful in SPL to turn on boot peripherals and adjust CPU voltage
579 	  so that the clock speed can be increased. This enables the drivers
580 	  in drivers/power, drivers/power/pmic and drivers/power/regulator
581 	  as part of an SPL build.
582 
583 config SPL_RAM_SUPPORT
584 	bool "Support booting from RAM"
585 	default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
586 	help
587 	  Enable booting of an image in RAM. The image can be preloaded or
588 	  it can be loaded by SPL directly into RAM (e.g. using USB).
589 
590 config SPL_RAM_DEVICE
591 	bool "Support booting from preloaded image in RAM"
592 	depends on SPL_RAM_SUPPORT
593 	default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
594 	help
595 	  Enable booting of an image already loaded in RAM. The image has to
596 	  be already in memory when SPL takes over, e.g. loaded by the boot
597 	  ROM.
598 
599 config SPL_RTC_SUPPORT
600 	bool "Support RTC drivers"
601 	help
602 	  Enable RTC (Real-time Clock) support in SPL. This includes support
603 	  for reading and setting the time. Some RTC devices also have some
604 	  non-volatile (battery-backed) memory which is accessible if
605 	  needed. This enables the drivers in drivers/rtc as part of an SPL
606 	  build.
607 
608 config SPL_SATA_SUPPORT
609 	bool "Support loading from SATA"
610 	help
611 	  Enable support for SATA (Serial AT attachment) in SPL. This allows
612 	  use of SATA devices such as hard drives and flash drivers for
613 	  loading U-Boot. SATA is used in higher-end embedded systems and
614 	  can provide higher performance than MMC , at somewhat higher
615 	  expense and power consumption. This enables loading from SATA
616 	  using a configured device.
617 
618 config SPL_SERIAL_SUPPORT
619 	bool "Support serial"
620 	help
621 	  Enable support for serial in SPL. This allows use of a serial UART
622 	  for displaying messages while SPL is running. It also brings in
623 	  printf() and panic() functions. This should normally be enabled
624 	  unless there are space reasons not to. Even then, consider
625 	  enabling USE_TINY_PRINTF which is a small printf() version.
626 
627 config SPL_SPI_FLASH_SUPPORT
628 	bool "Support SPI flash drivers"
629 	help
630 	  Enable support for using SPI flash in SPL, and loading U-Boot from
631 	  SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
632 	  the SPI bus that is used to connect it to a system. It is a simple
633 	  but fast bidirectional 4-wire bus (clock, chip select and two data
634 	  lines). This enables the drivers in drivers/mtd/spi as part of an
635 	  SPL build. This normally requires SPL_SPI_SUPPORT.
636 
637 config SPL_SPI_SUPPORT
638 	bool "Support SPI drivers"
639 	help
640 	  Enable support for using SPI in SPL. This is used for connecting
641 	  to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
642 	  more details on that. The SPI driver provides the transport for
643 	  data between the SPI flash and the CPU. This option can be used to
644 	  enable SPI drivers that are needed for other purposes also, such
645 	  as a SPI PMIC.
646 
647 config SPL_THERMAL
648 	bool "Driver support for thermal devices"
649 	help
650 	  Enable support for temperature-sensing devices. Some SoCs have on-chip
651 	  temperature sensors to permit warnings, speed throttling or even
652 	  automatic power-off when the temperature gets too high or low. Other
653 	  devices may be discrete but connected on a suitable bus.
654 
655 config SPL_USB_HOST_SUPPORT
656 	bool "Support USB host drivers"
657 	help
658 	  Enable access to USB (Universal Serial Bus) host devices so that
659 	  SPL can load U-Boot from a connected USB peripheral, such as a USB
660 	  flash stick. While USB takes a little longer to start up than most
661 	  buses, it is very flexible since many different types of storage
662 	  device can be attached. This option enables the drivers in
663 	  drivers/usb/host as part of an SPL build.
664 
665 config SPL_USB_SUPPORT
666 	bool "Support loading from USB"
667 	depends on SPL_USB_HOST_SUPPORT
668 	help
669 	  Enable support for USB devices in SPL. This allows use of USB
670 	  devices such as hard drives and flash drivers for loading U-Boot.
671 	  The actual drivers are enabled separately using the normal U-Boot
672 	  config options. This enables loading from USB using a configured
673 	  device.
674 
675 config SPL_USB_GADGET_SUPPORT
676 	bool "Suppport USB Gadget drivers"
677 	help
678 	  Enable USB Gadget API which allows to enable USB device functions
679 	  in SPL.
680 
681 if SPL_USB_GADGET_SUPPORT
682 
683 config SPL_USBETH_SUPPORT
684 	bool "Support USB Ethernet drivers"
685 	help
686 	  Enable access to the USB network subsystem and associated
687 	  drivers in SPL. This permits SPL to load U-Boot over a
688 	  USB-connected Ethernet link (such as a USB Ethernet dongle) rather
689 	  than from an onboard peripheral. Environment support is required
690 	  since the network stack uses a number of environment variables.
691 	  See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
692 
693 config SPL_DFU_SUPPORT
694 	bool "Support DFU (Device Firmware Upgarde)"
695 	select SPL_HASH_SUPPORT
696 	select SPL_DFU_NO_RESET
697 	depends on SPL_RAM_SUPPORT
698 	help
699 	  This feature enables the DFU (Device Firmware Upgarde) in SPL with
700 	  RAM memory device support. The ROM code will load and execute
701 	  the SPL built with dfu. The user can load binaries (u-boot/kernel) to
702 	  selected device partition from host-pc using dfu-utils.
703 	  This feature is useful to flash the binaries to factory or bare-metal
704 	  boards using USB interface.
705 
706 choice
707 	bool "DFU device selection"
708 	depends on SPL_DFU_SUPPORT
709 
710 config SPL_DFU_RAM
711 	bool "RAM device"
712 	depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
713 	help
714 	 select RAM/DDR memory device for loading binary images
715 	 (u-boot/kernel) to the selected device partition using
716 	 DFU and execute the u-boot/kernel from RAM.
717 
718 endchoice
719 
720 config SPL_USB_SDP_SUPPORT
721 	bool "Support SDP (Serial Download Protocol)"
722 	help
723 	  Enable Serial Download Protocol (SDP) device support in SPL. This
724 	  allows to download images into memory and execute (jump to) them
725 	  using the same protocol as implemented by the i.MX family's boot ROM.
726 endif
727 
728 config SPL_WATCHDOG_SUPPORT
729 	bool "Support watchdog drivers"
730 	help
731 	  Enable support for watchdog drivers in SPL. A watchdog is
732 	  typically a hardware peripheral which can reset the system when it
733 	  detects no activity for a while (such as a software crash). This
734 	  enables the drivers in drivers/watchdog as part of an SPL build.
735 
736 config SPL_YMODEM_SUPPORT
737 	bool "Support loading using Ymodem"
738 	help
739 	  While loading from serial is slow it can be a useful backup when
740 	  there is no other option. The Ymodem protocol provides a reliable
741 	  means of transmitting U-Boot over a serial line for using in SPL,
742 	  with a checksum to ensure correctness.
743 
744 config SPL_ATF
745 	bool "Support ARM Trusted Firmware"
746 	depends on ARM64
747 	help
748 	  ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
749 	  is loaded by SPL (which is considered as BL2 in ATF terminology).
750 	  More detail at: https://github.com/ARM-software/arm-trusted-firmware
751 
752 config SPL_ATF_NO_PLATFORM_PARAM
753         bool "Pass no platform parameter"
754 	depends on SPL_ATF
755 	help
756 	  While we expect to call a pointer to a valid FDT (or NULL)
757 	  as the platform parameter to an ATF, some ATF versions are
758 	  not U-Boot aware and have an insufficiently robust parameter
759 	  validation to gracefully reject a FDT being passed.
760 
761 	  If this option is enabled, the spl_atf os-type handler will
762 	  always pass NULL for the platform parameter.
763 
764 	  If your ATF is affected, say Y.
765 
766 config TPL
767 	bool
768 	depends on SUPPORT_TPL
769 	prompt "Enable TPL"
770 	help
771 	  If you want to build TPL as well as the normal image and SPL, say Y.
772 
773 if TPL
774 
775 config TPL_BOARD_INIT
776 	bool "Call board-specific initialization in TPL"
777 	help
778 	  If this option is enabled, U-Boot will call the function
779 	  spl_board_init() from board_init_r(). This function should be
780 	  provided by the board.
781 
782 config TPL_LDSCRIPT
783         string "Linker script for the TPL stage"
784 	depends on TPL
785 	help
786 	  The TPL stage will usually require a different linker-script
787 	  (as it runs from a different memory region) than the regular
788 	  U-Boot stage.  Set this to the path of the linker-script to
789 	  be used for TPL.
790 
791 	  May be left empty to trigger the Makefile infrastructure to
792 	  fall back to the linker-script used for the SPL stage.
793 
794 config TPL_NEEDS_SEPARATE_TEXT_BASE
795         bool "TPL needs a separate text-base"
796 	default n
797 	depends on TPL
798 	help
799 	  Enable, if the TPL stage should not inherit its text-base
800 	  from the SPL stage.  When enabled, a base address for the
801 	  .text sections of the TPL stage has to be set below.
802 
803 config TPL_NEEDS_SEPARATE_STACK
804         bool "TPL needs a separate initial stack-pointer"
805 	default n
806 	depends on TPL
807 	help
808 	  Enable, if the TPL stage should not inherit its initial
809 	  stack-pointer from the settings for the SPL stage.
810 
811 config TPL_TEXT_BASE
812         hex "Base address for the .text section of the TPL stage"
813 	depends on TPL_NEEDS_SEPARATE_TEXT_BASE
814 	help
815 	  The base address for the .text section of the TPL stage.
816 
817 config TPL_MAX_SIZE
818         int "Maximum size (in bytes) for the TPL stage"
819 	default 0
820 	depends on TPL
821 	help
822 	  The maximum size (in bytes) of the TPL stage.
823 
824 config TPL_STACK
825         hex "Address of the initial stack-pointer for the TPL stage"
826 	depends on TPL_NEEDS_SEPARATE_STACK
827 	help
828 	  The address of the initial stack-pointer for the TPL stage.
829 	  Usually this will be the (aligned) top-of-stack.
830 
831 config TPL_BOOTROM_SUPPORT
832         bool "Support returning to the BOOTROM (from TPL)"
833 	help
834 	  Some platforms (e.g. the Rockchip RK3368) provide support in their
835 	  ROM for loading the next boot-stage after performing basic setup
836 	  from the TPL stage.
837 
838 	  Enable this option, to return to the BOOTROM through the
839 	  BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
840 	  boot device list, if not implemented for a given board)
841 
842 config TPL_DRIVERS_MISC_SUPPORT
843 	bool "Support misc drivers in TPL"
844 	help
845 	  Enable miscellaneous drivers in TPL. These drivers perform various
846 	  tasks that don't fall nicely into other categories, Enable this
847 	  option to build the drivers in drivers/misc as part of an TPL
848 	  build, for those that support building in TPL (not all drivers do).
849 
850 config TPL_ENV_SUPPORT
851 	bool "Support an environment"
852 	help
853 	  Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
854 
855 config TPL_I2C_SUPPORT
856 	bool "Support I2C"
857 	help
858 	  Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
859 	  details.
860 
861 config TPL_LIBCOMMON_SUPPORT
862 	bool "Support common libraries"
863 	help
864 	  Enable support for common U-Boot libraries within TPL. See
865 	  SPL_LIBCOMMON_SUPPORT for details.
866 
867 config TPL_LIBGENERIC_SUPPORT
868 	bool "Support generic libraries"
869 	help
870 	  Enable support for generic U-Boot libraries within TPL. See
871 	  SPL_LIBGENERIC_SUPPORT for details.
872 
873 config TPL_MPC8XXX_INIT_DDR_SUPPORT
874 	bool "Support MPC8XXX DDR init"
875 	help
876 	  Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
877 	  SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
878 
879 config TPL_MMC_SUPPORT
880 	bool "Support MMC"
881 	depends on MMC
882 	help
883 	  Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
884 
885 config TPL_NAND_SUPPORT
886 	bool "Support NAND flash"
887 	help
888 	  Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
889 
890 config TPL_SERIAL_SUPPORT
891 	bool "Support serial"
892 	help
893 	  Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
894 	  details.
895 
896 config TPL_SPI_FLASH_SUPPORT
897 	bool "Support SPI flash drivers"
898 	help
899 	  Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
900 	  for details.
901 
902 config TPL_SPI_SUPPORT
903 	bool "Support SPI drivers"
904 	help
905 	  Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
906 	  details.
907 
908 endif # TPL
909 
910 endif # SPL
911 endmenu
912