Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513
  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 extention 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. endmenu # General setup
  196. menu "Boot images"
  197. config ANDROID_BOOT_IMAGE
  198. bool "Enable support for Android Boot Images"
  199. default y if FASTBOOT
  200. help
  201. This enables support for booting images which use the Android
  202. image format header.
  203. config FIT
  204. bool "Support Flattened Image Tree"
  205. select MD5
  206. select SHA1
  207. help
  208. This option allows you to boot the new uImage structure,
  209. Flattened Image Tree. FIT is formally a FDT, which can include
  210. images of various types (kernel, FDT blob, ramdisk, etc.)
  211. in a single blob. To boot this new uImage structure,
  212. pass the address of the blob to the "bootm" command.
  213. FIT is very flexible, supporting compression, multiple images,
  214. multiple configurations, verification through hashing and also
  215. verified boot (secure boot using RSA).
  216. if FIT
  217. config FIT_ENABLE_SHA256_SUPPORT
  218. bool "Support SHA256 checksum of FIT image contents"
  219. default y
  220. select SHA256
  221. help
  222. Enable this to support SHA256 checksum of FIT image contents. A
  223. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  224. the image contents have not been corrupted. SHA256 is recommended
  225. for use in secure applications since (as at 2016) there is no known
  226. feasible attack that could produce a 'collision' with differing
  227. input data. Use this for the highest security. Note that only the
  228. SHA256 variant is supported: SHA512 and others are not currently
  229. supported in U-Boot.
  230. config FIT_SIGNATURE
  231. bool "Enable signature verification of FIT uImages"
  232. depends on DM
  233. select HASH
  234. select RSA
  235. help
  236. This option enables signature verification of FIT uImages,
  237. using a hash signed and verified using RSA. If
  238. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  239. hashing is available using hardware, then the RSA library will use
  240. it. See doc/uImage.FIT/signature.txt for more details.
  241. WARNING: When relying on signed FIT images with a required signature
  242. check the legacy image format is disabled by default, so that
  243. unsigned images cannot be loaded. If a board needs the legacy image
  244. format support in this case, enable it using
  245. CONFIG_IMAGE_FORMAT_LEGACY.
  246. config FIT_SIGNATURE_MAX_SIZE
  247. hex "Max size of signed FIT structures"
  248. depends on FIT_SIGNATURE
  249. default 0x10000000
  250. help
  251. This option sets a max size in bytes for verified FIT uImages.
  252. A sane value of 256MB protects corrupted DTB structures from overlapping
  253. device memory. Assure this size does not extend past expected storage
  254. space.
  255. config FIT_ENABLE_RSASSA_PSS_SUPPORT
  256. bool "Support rsassa-pss signature scheme of FIT image contents"
  257. depends on FIT_SIGNATURE
  258. default n
  259. help
  260. Enable this to support the pss padding algorithm as described
  261. in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  262. config FIT_VERBOSE
  263. bool "Show verbose messages when FIT images fail"
  264. help
  265. Generally a system will have valid FIT images so debug messages
  266. are a waste of code space. If you are debugging your images then
  267. you can enable this option to get more verbose information about
  268. failures.
  269. config FIT_BEST_MATCH
  270. bool "Select the best match for the kernel device tree"
  271. help
  272. When no configuration is explicitly selected, default to the
  273. one whose fdt's compatibility field best matches that of
  274. U-Boot itself. A match is considered "best" if it matches the
  275. most specific compatibility entry of U-Boot's fdt's root node.
  276. The order of entries in the configuration's fdt is ignored.
  277. config FIT_IMAGE_POST_PROCESS
  278. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  279. depends on TI_SECURE_DEVICE
  280. help
  281. Allows doing any sort of manipulation to blobs after they got extracted
  282. from FIT images like stripping off headers or modifying the size of the
  283. blob, verification, authentication, decryption etc. in a platform or
  284. board specific way. In order to use this feature a platform or board-
  285. specific implementation of board_fit_image_post_process() must be
  286. provided. Also, anything done during this post-processing step would
  287. need to be comprehended in how the images were prepared before being
  288. injected into the FIT creation (i.e. the blobs would have been pre-
  289. processed before being added to the FIT image).
  290. if SPL
  291. config SPL_FIT
  292. bool "Support Flattened Image Tree within SPL"
  293. depends on SPL
  294. select SPL_OF_LIBFDT
  295. config SPL_FIT_PRINT
  296. bool "Support FIT printing within SPL"
  297. depends on SPL_FIT
  298. help
  299. Support printing the content of the fitImage in a verbose manner in SPL.
  300. config SPL_FIT_SIGNATURE
  301. bool "Enable signature verification of FIT firmware within SPL"
  302. depends on SPL_DM
  303. select SPL_FIT
  304. select SPL_RSA
  305. config SPL_LOAD_FIT
  306. bool "Enable SPL loading U-Boot as a FIT"
  307. select SPL_FIT
  308. help
  309. Normally with the SPL framework a legacy image is generated as part
  310. of the build. This contains U-Boot along with information as to
  311. where it should be loaded. This option instead enables generation
  312. of a FIT (Flat Image Tree) which provides more flexibility. In
  313. particular it can handle selecting from multiple device tree
  314. and passing the correct one to U-Boot.
  315. config SPL_LOAD_FIT_FULL
  316. bool "Enable SPL loading U-Boot as a FIT"
  317. select SPL_FIT
  318. help
  319. Normally with the SPL framework a legacy image is generated as part
  320. of the build. This contains U-Boot along with information as to
  321. where it should be loaded. This option instead enables generation
  322. of a FIT (Flat Image Tree) which provides more flexibility. In
  323. particular it can handle selecting from multiple device tree
  324. and passing the correct one to U-Boot.
  325. config SPL_FIT_IMAGE_POST_PROCESS
  326. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  327. depends on SPL_LOAD_FIT
  328. help
  329. Allows doing any sort of manipulation to blobs after they got extracted
  330. from the U-Boot FIT image like stripping off headers or modifying the
  331. size of the blob, verification, authentication, decryption etc. in a
  332. platform or board specific way. In order to use this feature a platform
  333. or board-specific implementation of board_fit_image_post_process() must
  334. be provided. Also, anything done during this post-processing step would
  335. need to be comprehended in how the images were prepared before being
  336. injected into the FIT creation (i.e. the blobs would have been pre-
  337. processed before being added to the FIT image).
  338. config SPL_FIT_SOURCE
  339. string ".its source file for U-Boot FIT image"
  340. depends on SPL_FIT
  341. help
  342. Specifies a (platform specific) FIT source file to generate the
  343. U-Boot FIT image. This could specify further image to load and/or
  344. execute.
  345. config SPL_FIT_GENERATOR
  346. string ".its file generator script for U-Boot FIT image"
  347. depends on SPL_FIT
  348. default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
  349. help
  350. Specifies a (platform specific) script file to generate the FIT
  351. source file used to build the U-Boot FIT image file. This gets
  352. passed a list of supported device tree file stub names to
  353. include in the generated image.
  354. endif # SPL
  355. endif # FIT
  356. config IMAGE_FORMAT_LEGACY
  357. bool "Enable support for the legacy image format"
  358. default y if !FIT_SIGNATURE
  359. help
  360. This option enables the legacy image format. It is enabled by
  361. default for backward compatibility, unless FIT_SIGNATURE is
  362. set where it is disabled so that unsigned images cannot be
  363. loaded. If a board needs the legacy image format support in this
  364. case, enable it here.
  365. config OF_BOARD_SETUP
  366. bool "Set up board-specific details in device tree before boot"
  367. depends on OF_LIBFDT
  368. help
  369. This causes U-Boot to call ft_board_setup() before booting into
  370. the Operating System. This function can set up various
  371. board-specific information in the device tree for use by the OS.
  372. The device tree is then passed to the OS.
  373. config OF_SYSTEM_SETUP
  374. bool "Set up system-specific details in device tree before boot"
  375. depends on OF_LIBFDT
  376. help
  377. This causes U-Boot to call ft_system_setup() before booting into
  378. the Operating System. This function can set up various
  379. system-specific information in the device tree for use by the OS.
  380. The device tree is then passed to the OS.
  381. config OF_STDOUT_VIA_ALIAS
  382. bool "Update the device-tree stdout alias from U-Boot"
  383. depends on OF_LIBFDT
  384. help
  385. This uses U-Boot's serial alias from the aliases node to update
  386. the device tree passed to the OS. The "linux,stdout-path" property
  387. in the chosen node is set to point to the correct serial node.
  388. This option currently references CONFIG_CONS_INDEX, which is
  389. incorrect when used with device tree as this option does not
  390. exist / should not be used.
  391. config SYS_EXTRA_OPTIONS
  392. string "Extra Options (DEPRECATED)"
  393. help
  394. The old configuration infrastructure (= mkconfig + boards.cfg)
  395. provided the extra options field. If you have something like
  396. "HAS_BAR,BAZ=64", the optional options
  397. #define CONFIG_HAS
  398. #define CONFIG_BAZ 64
  399. will be defined in include/config.h.
  400. This option was prepared for the smooth migration from the old
  401. configuration to Kconfig. Since this option will be removed sometime,
  402. new boards should not use this option.
  403. config SYS_TEXT_BASE
  404. depends on !NIOS2 && !XTENSA
  405. depends on !EFI_APP
  406. default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
  407. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  408. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  409. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  410. hex "Text Base"
  411. help
  412. The address in memory that U-Boot will be running from, initially.
  413. config SYS_CLK_FREQ
  414. depends on ARC || ARCH_SUNXI
  415. int "CPU clock frequency"
  416. help
  417. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  418. config ARCH_FIXUP_FDT_MEMORY
  419. bool "Enable arch_fixup_memory_banks() call"
  420. default y
  421. help
  422. Enable FDT memory map syncup before OS boot. This feature can be
  423. used for booting OS with different memory setup where the part of
  424. the memory location should be used for different purpose.
  425. endmenu # Boot images
  426. source "api/Kconfig"
  427. source "common/Kconfig"
  428. source "cmd/Kconfig"
  429. source "disk/Kconfig"
  430. source "dts/Kconfig"
  431. source "env/Kconfig"
  432. source "net/Kconfig"
  433. source "drivers/Kconfig"
  434. source "fs/Kconfig"
  435. source "lib/Kconfig"
  436. source "test/Kconfig"