Kconfig 20 KB

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