Kconfig 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see the file Documentation/kbuild/kconfig-language.txt in the
  4. # Linux kernel source tree.
  5. #
  6. mainmenu "U-Boot $UBOOTVERSION Configuration"
  7. config UBOOTVERSION
  8. string
  9. option env="UBOOTVERSION"
  10. # Allow defaults in arch-specific code to override any given here
  11. source "arch/Kconfig"
  12. menu "General setup"
  13. config BROKEN
  14. bool
  15. help
  16. This option cannot be enabled. It is used as dependency
  17. for broken and incomplete features.
  18. config DEPRECATED
  19. bool
  20. help
  21. This option cannot be enabled. It it used as a dependency for
  22. code that relies on deprecated features that will be removed and
  23. the conversion deadline has passed.
  24. config LOCALVERSION
  25. string "Local version - append to U-Boot release"
  26. help
  27. Append an extra string to the end of your U-Boot version.
  28. This will show up in your boot log, for example.
  29. The string you set here will be appended after the contents of
  30. any files with a filename matching localversion* in your
  31. object and source tree, in that order. Your total string can
  32. be a maximum of 64 characters.
  33. config LOCALVERSION_AUTO
  34. bool "Automatically append version information to the version string"
  35. default y
  36. help
  37. This will try to automatically determine if the current tree is a
  38. release tree by looking for Git tags that belong to the current
  39. top of tree revision.
  40. A string of the format -gxxxxxxxx will be added to the localversion
  41. if a Git-based tree is found. The string generated by this will be
  42. appended after any matching localversion* files, and after the value
  43. set in CONFIG_LOCALVERSION.
  44. (The actual string used here is the first eight characters produced
  45. by running the command:
  46. $ git rev-parse --verify HEAD
  47. which is done within the script "scripts/setlocalversion".)
  48. config CC_OPTIMIZE_FOR_SIZE
  49. bool "Optimize for size"
  50. default y
  51. help
  52. Enabling this option will pass "-Os" instead of "-O2" to gcc
  53. resulting in a smaller U-Boot image.
  54. This option is enabled by default for U-Boot.
  55. config CC_COVERAGE
  56. bool "Enable code coverage analysis"
  57. depends on SANDBOX
  58. help
  59. Enabling this option will pass "--coverage" to gcc to compile
  60. and link code instrumented for coverage analysis.
  61. config DISTRO_DEFAULTS
  62. bool "Select defaults suitable for booting general purpose Linux distributions"
  63. select AUTO_COMPLETE
  64. select CMDLINE_EDITING
  65. select CMD_BOOTI if ARM64
  66. select CMD_BOOTZ if ARM && !ARM64
  67. select CMD_DHCP if CMD_NET
  68. select CMD_ENV_EXISTS
  69. select CMD_EXT2
  70. select CMD_EXT4
  71. select CMD_FAT
  72. select CMD_FS_GENERIC
  73. select CMD_PART if PARTITIONS
  74. select CMD_PING if CMD_NET
  75. select CMD_PXE if NET
  76. select ENV_VARS_UBOOT_CONFIG
  77. select HUSH_PARSER
  78. select SUPPORT_RAW_INITRD
  79. select SYS_LONGHELP
  80. imply CMD_MII if NET
  81. imply USB_STORAGE
  82. imply USE_BOOTCOMMAND
  83. help
  84. Select this to enable various options and commands which are suitable
  85. for building u-boot for booting general purpose Linux distributions.
  86. config ENV_VARS_UBOOT_CONFIG
  87. bool "Add arch, board, vendor and soc variables to default environment"
  88. help
  89. Define this in order to add variables describing the
  90. U-Boot build configuration to the default environment.
  91. These will be named arch, cpu, board, vendor, and soc.
  92. Enabling this option will cause the following to be defined:
  93. - CONFIG_SYS_ARCH
  94. - CONFIG_SYS_CPU
  95. - CONFIG_SYS_BOARD
  96. - CONFIG_SYS_VENDOR
  97. - CONFIG_SYS_SOC
  98. config NR_DRAM_BANKS
  99. int "Number of DRAM banks"
  100. default 4
  101. help
  102. This defines the number of DRAM banks.
  103. config SYS_BOOT_GET_CMDLINE
  104. bool "Enable kernel command line setup"
  105. help
  106. Enables allocating and saving kernel cmdline in space between
  107. "bootm_low" and "bootm_low" + BOOTMAPSZ.
  108. config SYS_BOOT_GET_KBD
  109. bool "Enable kernel board information setup"
  110. help
  111. Enables allocating and saving a kernel copy of the bd_info in
  112. space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
  113. config SYS_MALLOC_F
  114. bool "Enable malloc() pool before relocation"
  115. default y if DM
  116. help
  117. Before relocation, memory is very limited on many platforms. Still,
  118. we can provide a small malloc() pool if needed. Driver model in
  119. particular needs this to operate, so that it can allocate the
  120. initial serial device and any others that are needed.
  121. config SYS_MALLOC_F_LEN
  122. hex "Size of malloc() pool before relocation"
  123. depends on SYS_MALLOC_F
  124. default 0x1000 if AM33XX
  125. default 0x2800 if SANDBOX
  126. default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
  127. ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5)
  128. default 0x400
  129. help
  130. Before relocation, memory is very limited on many platforms. Still,
  131. we can provide a small malloc() pool if needed. Driver model in
  132. particular needs this to operate, so that it can allocate the
  133. initial serial device and any others that are needed.
  134. config SYS_MALLOC_LEN
  135. hex "Define memory for Dynamic allocation"
  136. depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP
  137. help
  138. This defines memory to be allocated for Dynamic allocation
  139. TODO: Use for other architectures
  140. config SPL_SYS_MALLOC_F_LEN
  141. hex "Size of malloc() pool in SPL before relocation"
  142. depends on SYS_MALLOC_F
  143. default 0x2800 if RCAR_GEN3
  144. default SYS_MALLOC_F_LEN
  145. help
  146. Before relocation, memory is very limited on many platforms. Still,
  147. we can provide a small malloc() pool if needed. Driver model in
  148. particular needs this to operate, so that it can allocate the
  149. initial serial device and any others that are needed.
  150. config TPL_SYS_MALLOC_F_LEN
  151. hex "Size of malloc() pool in TPL before relocation"
  152. depends on SYS_MALLOC_F
  153. default SYS_MALLOC_F_LEN
  154. help
  155. Before relocation, memory is very limited on many platforms. Still,
  156. we can provide a small malloc() pool if needed. Driver model in
  157. particular needs this to operate, so that it can allocate the
  158. initial serial device and any others that are needed.
  159. menuconfig EXPERT
  160. bool "Configure standard U-Boot features (expert users)"
  161. default y
  162. help
  163. This option allows certain base U-Boot options and settings
  164. to be disabled or tweaked. This is for specialized
  165. environments which can tolerate a "non-standard" U-Boot.
  166. Use this only if you really know what you are doing.
  167. if EXPERT
  168. config SYS_MALLOC_CLEAR_ON_INIT
  169. bool "Init with zeros the memory reserved for malloc (slow)"
  170. default y
  171. help
  172. This setting is enabled by default. The reserved malloc
  173. memory is initialized with zeros, so first malloc calls
  174. will return the pointer to the zeroed memory. But this
  175. slows the boot time.
  176. It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
  177. value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
  178. Then the boot time can be significantly reduced.
  179. Warning:
  180. When disabling this, please check if malloc calls, maybe
  181. should be replaced by calloc - if one expects zeroed memory.
  182. config TOOLS_DEBUG
  183. bool "Enable debug information for tools"
  184. help
  185. Enable generation of debug information for tools such as mkimage.
  186. This can be used for debugging purposes. With debug information
  187. it is possible to set breakpoints on particular lines, single-step
  188. debug through the source code, etc.
  189. endif # EXPERT
  190. config PHYS_64BIT
  191. bool "64bit physical address support"
  192. help
  193. Say Y here to support 64bit physical memory address.
  194. This can be used not only for 64bit SoCs, but also for
  195. large physical address extension on 32bit SoCs.
  196. config BUILD_ROM
  197. bool "Build U-Boot as BIOS replacement"
  198. depends on X86
  199. help
  200. This option allows to build a ROM version of U-Boot.
  201. The build process generally requires several binary blobs
  202. which are not shipped in the U-Boot source tree.
  203. Please, see doc/README.x86 for details.
  204. config SPL_IMAGE
  205. string "SPL image used in the combined SPL+U-Boot image"
  206. default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  207. default "spl/u-boot-spl.bin"
  208. help
  209. Select the SPL build target that shall be generated by the SPL
  210. build process (default spl/u-boot-spl.bin). This image will be
  211. used to generate a combined image with SPL and main U-Boot
  212. proper as one single image.
  213. config BUILD_TARGET
  214. string "Build target special images"
  215. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
  216. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
  217. default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
  218. default "u-boot-elf.srec" if RCAR_GEN3
  219. default "u-boot.itb" if SPL_LOAD_FIT && (ROCKCHIP_RK3399 || ARCH_SUNXI)
  220. default "u-boot.kwb" if KIRKWOOD
  221. default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  222. help
  223. Some SoCs need special image types (e.g. U-Boot binary
  224. with a special header) as build targets. By defining
  225. CONFIG_BUILD_TARGET in the SoC / board header, this
  226. special image will be automatically built upon calling
  227. make / buildman.
  228. config SYS_CUSTOM_LDSCRIPT
  229. bool "Use a custom location for the U-Boot linker script"
  230. help
  231. Normally when linking U-Boot we will look in the board directory,
  232. the CPU directory and finally the "cpu" directory of the architecture
  233. for the ile "u-boot.lds" and use that as our linker. However, in
  234. some cases we need to provide a different linker script. To do so,
  235. enable this option and then provide the location under
  236. CONFIG_SYS_LDSCRIPT.
  237. config SYS_LDSCRIPT
  238. depends on SYS_CUSTOM_LDSCRIPT
  239. string "Custom ldscript location"
  240. help
  241. Path within the source tree to the linker script to use for the
  242. main U-Boot binary.
  243. endmenu # General setup
  244. menu "Boot images"
  245. config ANDROID_BOOT_IMAGE
  246. bool "Enable support for Android Boot Images"
  247. default y if FASTBOOT
  248. help
  249. This enables support for booting images which use the Android
  250. image format header.
  251. config FIT
  252. bool "Support Flattened Image Tree"
  253. select MD5
  254. select SHA1
  255. help
  256. This option allows you to boot the new uImage structure,
  257. Flattened Image Tree. FIT is formally a FDT, which can include
  258. images of various types (kernel, FDT blob, ramdisk, etc.)
  259. in a single blob. To boot this new uImage structure,
  260. pass the address of the blob to the "bootm" command.
  261. FIT is very flexible, supporting compression, multiple images,
  262. multiple configurations, verification through hashing and also
  263. verified boot (secure boot using RSA).
  264. if FIT
  265. config FIT_EXTERNAL_OFFSET
  266. hex "FIT external data offset"
  267. default 0x0
  268. help
  269. This specifies a data offset in fit image.
  270. The offset is from data payload offset to the beginning of
  271. fit image header. When specifies a offset, specific data
  272. could be put in the hole between data payload and fit image
  273. header, such as CSF data on i.MX platform.
  274. config FIT_ENABLE_SHA256_SUPPORT
  275. bool "Support SHA256 checksum of FIT image contents"
  276. default y
  277. select SHA256
  278. help
  279. Enable this to support SHA256 checksum of FIT image contents. A
  280. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  281. the image contents have not been corrupted. SHA256 is recommended
  282. for use in secure applications since (as at 2016) there is no known
  283. feasible attack that could produce a 'collision' with differing
  284. input data. Use this for the highest security. Note that only the
  285. SHA256 variant is supported: SHA512 and others are not currently
  286. supported in U-Boot.
  287. config FIT_SIGNATURE
  288. bool "Enable signature verification of FIT uImages"
  289. depends on DM
  290. select HASH
  291. select RSA
  292. help
  293. This option enables signature verification of FIT uImages,
  294. using a hash signed and verified using RSA. If
  295. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  296. hashing is available using hardware, then the RSA library will use
  297. it. See doc/uImage.FIT/signature.txt for more details.
  298. WARNING: When relying on signed FIT images with a required signature
  299. check the legacy image format is disabled by default, so that
  300. unsigned images cannot be loaded. If a board needs the legacy image
  301. format support in this case, enable it using
  302. CONFIG_LEGACY_IMAGE_FORMAT.
  303. config FIT_SIGNATURE_MAX_SIZE
  304. hex "Max size of signed FIT structures"
  305. depends on FIT_SIGNATURE
  306. default 0x10000000
  307. help
  308. This option sets a max size in bytes for verified FIT uImages.
  309. A sane value of 256MB protects corrupted DTB structures from overlapping
  310. device memory. Assure this size does not extend past expected storage
  311. space.
  312. config FIT_ENABLE_RSASSA_PSS_SUPPORT
  313. bool "Support rsassa-pss signature scheme of FIT image contents"
  314. depends on FIT_SIGNATURE
  315. default n
  316. help
  317. Enable this to support the pss padding algorithm as described
  318. in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  319. config FIT_VERBOSE
  320. bool "Show verbose messages when FIT images fail"
  321. help
  322. Generally a system will have valid FIT images so debug messages
  323. are a waste of code space. If you are debugging your images then
  324. you can enable this option to get more verbose information about
  325. failures.
  326. config FIT_BEST_MATCH
  327. bool "Select the best match for the kernel device tree"
  328. help
  329. When no configuration is explicitly selected, default to the
  330. one whose fdt's compatibility field best matches that of
  331. U-Boot itself. A match is considered "best" if it matches the
  332. most specific compatibility entry of U-Boot's fdt's root node.
  333. The order of entries in the configuration's fdt is ignored.
  334. config FIT_IMAGE_POST_PROCESS
  335. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  336. depends on TI_SECURE_DEVICE
  337. help
  338. Allows doing any sort of manipulation to blobs after they got extracted
  339. from FIT images like stripping off headers or modifying the size of the
  340. blob, verification, authentication, decryption etc. in a platform or
  341. board specific way. In order to use this feature a platform or board-
  342. specific implementation of board_fit_image_post_process() must be
  343. provided. Also, anything done during this post-processing step would
  344. need to be comprehended in how the images were prepared before being
  345. injected into the FIT creation (i.e. the blobs would have been pre-
  346. processed before being added to the FIT image).
  347. if SPL
  348. config SPL_FIT
  349. bool "Support Flattened Image Tree within SPL"
  350. depends on SPL
  351. select SPL_OF_LIBFDT
  352. config SPL_FIT_PRINT
  353. bool "Support FIT printing within SPL"
  354. depends on SPL_FIT
  355. help
  356. Support printing the content of the fitImage in a verbose manner in SPL.
  357. config SPL_FIT_SIGNATURE
  358. bool "Enable signature verification of FIT firmware within SPL"
  359. depends on SPL_DM
  360. select SPL_FIT
  361. select SPL_RSA
  362. config SPL_LOAD_FIT
  363. bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
  364. select SPL_FIT
  365. help
  366. Normally with the SPL framework a legacy image is generated as part
  367. of the build. This contains U-Boot along with information as to
  368. where it should be loaded. This option instead enables generation
  369. of a FIT (Flat Image Tree) which provides more flexibility. In
  370. particular it can handle selecting from multiple device tree
  371. and passing the correct one to U-Boot.
  372. config SPL_LOAD_FIT_FULL
  373. bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
  374. select SPL_FIT
  375. help
  376. Normally with the SPL framework a legacy image is generated as part
  377. of the build. This contains U-Boot along with information as to
  378. where it should be loaded. This option instead enables generation
  379. of a FIT (Flat Image Tree) which provides more flexibility. In
  380. particular it can handle selecting from multiple device tree
  381. and passing the correct one to U-Boot.
  382. config SPL_FIT_IMAGE_POST_PROCESS
  383. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  384. depends on SPL_LOAD_FIT
  385. help
  386. Allows doing any sort of manipulation to blobs after they got extracted
  387. from the U-Boot FIT image like stripping off headers or modifying the
  388. size of the blob, verification, authentication, decryption etc. in a
  389. platform or board specific way. In order to use this feature a platform
  390. or board-specific implementation of board_fit_image_post_process() must
  391. be provided. Also, anything done during this post-processing step would
  392. need to be comprehended in how the images were prepared before being
  393. injected into the FIT creation (i.e. the blobs would have been pre-
  394. processed before being added to the FIT image).
  395. config SPL_FIT_SOURCE
  396. string ".its source file for U-Boot FIT image"
  397. depends on SPL_FIT
  398. help
  399. Specifies a (platform specific) FIT source file to generate the
  400. U-Boot FIT image. This could specify further image to load and/or
  401. execute.
  402. config SPL_FIT_GENERATOR
  403. string ".its file generator script for U-Boot FIT image"
  404. depends on SPL_FIT
  405. default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
  406. default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
  407. help
  408. Specifies a (platform specific) script file to generate the FIT
  409. source file used to build the U-Boot FIT image file. This gets
  410. passed a list of supported device tree file stub names to
  411. include in the generated image.
  412. endif # SPL
  413. endif # FIT
  414. config LEGACY_IMAGE_FORMAT
  415. bool "Enable support for the legacy image format"
  416. default y if !FIT_SIGNATURE
  417. help
  418. This option enables the legacy image format. It is enabled by
  419. default for backward compatibility, unless FIT_SIGNATURE is
  420. set where it is disabled so that unsigned images cannot be
  421. loaded. If a board needs the legacy image format support in this
  422. case, enable it here.
  423. config OF_BOARD_SETUP
  424. bool "Set up board-specific details in device tree before boot"
  425. depends on OF_LIBFDT
  426. help
  427. This causes U-Boot to call ft_board_setup() before booting into
  428. the Operating System. This function can set up various
  429. board-specific information in the device tree for use by the OS.
  430. The device tree is then passed to the OS.
  431. config OF_SYSTEM_SETUP
  432. bool "Set up system-specific details in device tree before boot"
  433. depends on OF_LIBFDT
  434. help
  435. This causes U-Boot to call ft_system_setup() before booting into
  436. the Operating System. This function can set up various
  437. system-specific information in the device tree for use by the OS.
  438. The device tree is then passed to the OS.
  439. config OF_STDOUT_VIA_ALIAS
  440. bool "Update the device-tree stdout alias from U-Boot"
  441. depends on OF_LIBFDT
  442. help
  443. This uses U-Boot's serial alias from the aliases node to update
  444. the device tree passed to the OS. The "linux,stdout-path" property
  445. in the chosen node is set to point to the correct serial node.
  446. This option currently references CONFIG_CONS_INDEX, which is
  447. incorrect when used with device tree as this option does not
  448. exist / should not be used.
  449. config SYS_EXTRA_OPTIONS
  450. string "Extra Options (DEPRECATED)"
  451. help
  452. The old configuration infrastructure (= mkconfig + boards.cfg)
  453. provided the extra options field. If you have something like
  454. "HAS_BAR,BAZ=64", the optional options
  455. #define CONFIG_HAS
  456. #define CONFIG_BAZ 64
  457. will be defined in include/config.h.
  458. This option was prepared for the smooth migration from the old
  459. configuration to Kconfig. Since this option will be removed sometime,
  460. new boards should not use this option.
  461. config SYS_TEXT_BASE
  462. depends on !NIOS2 && !XTENSA
  463. depends on !EFI_APP
  464. default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
  465. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  466. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  467. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  468. hex "Text Base"
  469. help
  470. The address in memory that U-Boot will be running from, initially.
  471. config SYS_CLK_FREQ
  472. depends on ARC || ARCH_SUNXI || MPC83xx
  473. int "CPU clock frequency"
  474. help
  475. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  476. config ARCH_FIXUP_FDT_MEMORY
  477. bool "Enable arch_fixup_memory_banks() call"
  478. default y
  479. help
  480. Enable FDT memory map syncup before OS boot. This feature can be
  481. used for booting OS with different memory setup where the part of
  482. the memory location should be used for different purpose.
  483. endmenu # Boot images
  484. source "api/Kconfig"
  485. source "common/Kconfig"
  486. source "cmd/Kconfig"
  487. source "disk/Kconfig"
  488. source "dts/Kconfig"
  489. source "env/Kconfig"
  490. source "net/Kconfig"
  491. source "drivers/Kconfig"
  492. source "fs/Kconfig"
  493. source "lib/Kconfig"
  494. source "test/Kconfig"