Kconfig 31 KB

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