Kconfig - OpenGrok cross reference for /OK3568_Linux_fs/u-boot/common/spl/Kconfig

35 	default "arch/$(ARCH)/cpu/u-boot-spl.lds"
38 	  The SPL stage will usually require a different linker-script
40 	  U-Boot stage.	 Set this to the path of the linker-script to
44 	bool "Call board-specific initialization in SPL"
46 	  If this option is enabled, U-Boot will call the function
54 	  ROM for loading the next boot-stage after performing basic setup
58 	  BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
85 	  usage as the *_simple malloc functions do not re-use free-ed mem.
94 	  usage as the *_simple malloc functions do not re-use free-ed mem.
103 	  location for the SPL stack. U-Boot SPL switches to this after
133 	bool "Display a board-specific message in SPL"
135 	  If this option is enabled, U-Boot will call the function
137 	  banner ("U-Boot SPL ..."). This function should be provided by
171 	  Use sector number for specifying U-Boot location on MMC/SD in
175 	hex "Address on the MMC to load U-Boot from"
187 	  Address on the MMC to load U-Boot from, when the MMC is being used
194 	  Use a partition for loading U-Boot when using MMC/SD in raw mode.
197 	hex "Partition to use to load U-Boot from"
201 	  Partition on the MMC to load U-Boot from when the MMC is being
208 	  Use partition type for specifying U-Boot partition on MMC/SD in
209 	  raw mode. U-Boot will be loaded from the first partition of this
213 	string "Partition Name on the MMC to load U-Boot from"
217           Partition Name on the MMC to load U-Boot from, when the MMC is being
221 	hex "Partition Type on the MMC to load U-Boot from"
224 	  Partition Type on the MMC to load U-Boot from, when the MMC is being
237 	  32-bit checksum value that can be used to verify images. This is
247 	  checksum is a 128-bit hash value used to check that the image
249 	  secure as it is possible (with a brute-force attack) to adjust the
260 	  checksum is a 160-bit (20-byte) hash value used to check that the
263 	  due to the expanding computing power avaiable to brute-force
272 	  checksum is a 256-bit (32-byte) hash value used to check that the
278 	  supported in U-Boot.
290 	  first image to be treated as having a U-Boot style calling
320 	  this option to build system-specific drivers for hash acceleration
326 	  Enable DMA (direct-memory-access) drivers in SPL. These drivers
327 	  can be used to handle memory-to-peripheral data transfer without
342 	  Enable environment support in SPL. The U-Boot environment provides
344 	  control many aspects of U-Boot's operation. Normally this is not
348 	  starting U-Boot first. Enabling this option will make env_get()
370 	  drivers in SPL. This permits SPL to load U-Boot over an Ethernet
371 	  link rather than from an on-board peripheral. Environment support
379 	  U-Boot (or Linux in Falcon mode) to be loaded from an EXT
388 	  permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
395 	  Enable support for FPGAs in SPL. Field-programmable Gate Arrays
396 	  provide software-configurable hardware which is typically used to
406 	  Enable support for GPIOs (General-purpose Input/Output) in SPL.
407 	  GPIOs allow U-Boot to read the state of an input line (high or
410 	  input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
417 	  Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
418 	  I2C works with a clock and data line which can be driven by a
430 	  Enable support for common U-Boot libraries within SPL. These
431 	  libraries include common code to deal with U-Boot images,
440 	  of a misnomer as it includes non-spinning media such as flash (as
447 	  U-Boot to also be used in SPL. It brings in the code in disk/.
452 	  Enable support for generic U-Boot libraries within SPL. These
480 	  Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
481 	  random-access memory) on the MPC8XXX family within SPL. This
482 	  allows DRAM to be set up before loading U-Boot into that DRAM,
490 	  SPI flash. This allows SPL to load U-Boot from supported MTD
495 	hex "Location in MTD block to read U-Boot from"
500 	  u-boot should be loaded from.
514 	  the drivers in drivers/usb/musb-new as part of an SPL build. The
521 	  can be used to allow SPL to load U-Boot from supported devices.
529 	  This permits SPL to load U-Boot over a network link rather than
530 	  from an on-board peripheral. Environment support is required since
542 	  SPL or U-Boot itself makes the request
548 	  This is specific to the ARM926EJ-S CPU. It disables the standard
549 	  start.S start-up code, presumably so that a replacement can be
556 	  Enable support for loading U-Boot from memory-mapped NOR (Negative
558 	  a memory-mapped device makes it very easy to access. Loading from
565 	  Enable support for execute in place of U-Boot or kernel image. There
575 	  load U-Boot from supported devices. This enables the drivers in
621 	  Enable support for POST (Power-on Self Test) in SPL. POST is a
631 	  for PMICs (Power-management Integrated Circuits) and some of the
665 	  Enable RTC (Real-time Clock) support in SPL. This includes support
667 	  non-volatile (battery-backed) memory which is accessible if
676 	  loading U-Boot. SATA is used in higher-end embedded systems and
693 	  Enable support for using SPI flash in SPL, and loading U-Boot from
696 	  but fast bidirectional 4-wire bus (clock, chip select and two data
710 	hex "Location in RKNAND block to read U-Boot from"
715 	  u-boot should be loaded from.
739 	  Enable support for loading next stage, U-Boot or otherwise, from
740 	  SPI NOR in U-Boot SPL.
748 	  to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
758 	  SPL can load U-Boot from a connected USB peripheral, such as a USB
769 	  devices such as hard drives and flash drivers for loading U-Boot.
770 	  The actual drivers are enabled separately using the normal U-Boot
786 	  drivers in SPL. This permits SPL to load U-Boot over a
787 	  USB-connected Ethernet link (such as a USB Ethernet dongle) rather
800 	  the SPL built with dfu. The user can load binaries (u-boot/kernel) to
801 	  selected device partition from host-pc using dfu-utils.
802 	  This feature is useful to flash the binaries to factory or bare-metal
814 	 (u-boot/kernel) to the selected device partition using
815 	 DFU and execute the u-boot/kernel from RAM.
840 	  means of transmitting U-Boot over a serial line for using in SPL,
849 	  More detail at: https://github.com/ARM-software/arm-trusted-firmware
852 	bool "Support OP-TEE Trusted OS"
855 	  OP-TEE is an open source Trusted OS  which is loaded by SPL.
856 	  More detail at: https://github.com/OP-TEE/optee_os
864 	  not U-Boot aware and have an insufficiently robust parameter
867 	  If this option is enabled, the spl_atf os-type handler will
879 	bool "Support OP-TEE Trusted OS"
882 	  OP-TEE is an open source Trusted OS  which is loaded by SPL.
883 	  More detail at: https://github.com/OP-TEE/optee_os
897 	  for trust and U-Boot images.
999 	bool "Call board-specific initialization in TPL"
1001 	  If this option is enabled, U-Boot will call the function
1009 	  The TPL stage will usually require a different linker-script
1011 	  U-Boot stage.  Set this to the path of the linker-script to
1015 	  fall back to the linker-script used for the SPL stage.
1018         bool "TPL needs a separate text-base"
1022 	  Enable, if the TPL stage should not inherit its text-base
1027         bool "TPL needs a separate initial stack-pointer"
1032 	  stack-pointer from the settings for the SPL stage.
1048         hex "Address of the initial stack-pointer for the TPL stage"
1051 	  The address of the initial stack-pointer for the TPL stage.
1052 	  Usually this will be the (aligned) top-of-stack.
1058 	  ROM for loading the next boot-stage after performing basic setup
1062 	  BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1087 	  Enable support for common U-Boot libraries within TPL. See
1093 	  Enable support for generic U-Boot libraries within TPL. See
1104 	  Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See