Kconfig 18 KB

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