Kconfig 36 KB

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