Kconfig 21 KB

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