Kconfig 34 KB

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