Kconfig 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353
  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 LOCALVERSION
  14. string "Local version - append to U-Boot release"
  15. help
  16. Append an extra string to the end of your U-Boot version.
  17. This will show up in your boot log, for example.
  18. The string you set here will be appended after the contents of
  19. any files with a filename matching localversion* in your
  20. object and source tree, in that order. Your total string can
  21. be a maximum of 64 characters.
  22. config LOCALVERSION_AUTO
  23. bool "Automatically append version information to the version string"
  24. default y
  25. help
  26. This will try to automatically determine if the current tree is a
  27. release tree by looking for Git tags that belong to the current
  28. top of tree revision.
  29. A string of the format -gxxxxxxxx will be added to the localversion
  30. if a Git-based tree is found. The string generated by this will be
  31. appended after any matching localversion* files, and after the value
  32. set in CONFIG_LOCALVERSION.
  33. (The actual string used here is the first eight characters produced
  34. by running the command:
  35. $ git rev-parse --verify HEAD
  36. which is done within the script "scripts/setlocalversion".)
  37. config CC_OPTIMIZE_FOR_SIZE
  38. bool "Optimize for size"
  39. default y
  40. help
  41. Enabling this option will pass "-Os" instead of "-O2" to gcc
  42. resulting in a smaller U-Boot image.
  43. This option is enabled by default for U-Boot.
  44. config DISTRO_DEFAULTS
  45. bool "Select defaults suitable for booting general purpose Linux distributions"
  46. default y if ARCH_SUNXI
  47. default y if ARCH_LS2080A
  48. default n
  49. select CMD_BOOTZ if ARM && !ARM64
  50. select CMD_BOOTI if ARM64
  51. select CMD_DHCP
  52. select CMD_EXT2
  53. select CMD_EXT4
  54. select CMD_FAT
  55. select CMD_FS_GENERIC
  56. select CMD_MII
  57. select CMD_PING
  58. select HUSH_PARSER
  59. help
  60. Select this to enable various options and commands which are suitable
  61. for building u-boot for booting general purpose Linux distributions.
  62. config SYS_MALLOC_F
  63. bool "Enable malloc() pool before relocation"
  64. default y if DM
  65. help
  66. Before relocation, memory is very limited on many platforms. Still,
  67. we can provide a small malloc() pool if needed. Driver model in
  68. particular needs this to operate, so that it can allocate the
  69. initial serial device and any others that are needed.
  70. config SYS_MALLOC_F_LEN
  71. hex "Size of malloc() pool before relocation"
  72. depends on SYS_MALLOC_F
  73. default 0x400
  74. help
  75. Before relocation, memory is very limited on many platforms. Still,
  76. we can provide a small malloc() pool if needed. Driver model in
  77. particular needs this to operate, so that it can allocate the
  78. initial serial device and any others that are needed.
  79. menuconfig EXPERT
  80. bool "Configure standard U-Boot features (expert users)"
  81. default y
  82. help
  83. This option allows certain base U-Boot options and settings
  84. to be disabled or tweaked. This is for specialized
  85. environments which can tolerate a "non-standard" U-Boot.
  86. Use this only if you really know what you are doing.
  87. if EXPERT
  88. config SYS_MALLOC_CLEAR_ON_INIT
  89. bool "Init with zeros the memory reserved for malloc (slow)"
  90. default y
  91. help
  92. This setting is enabled by default. The reserved malloc
  93. memory is initialized with zeros, so first malloc calls
  94. will return the pointer to the zeroed memory. But this
  95. slows the boot time.
  96. It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
  97. value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
  98. Then the boot time can be significantly reduced.
  99. Warning:
  100. When disabling this, please check if malloc calls, maybe
  101. should be replaced by calloc - if one expects zeroed memory.
  102. config TOOLS_DEBUG
  103. bool "Enable debug information for tools"
  104. help
  105. Enable generation of debug information for tools such as mkimage.
  106. This can be used for debugging purposes. With debug information
  107. it is possible to set breakpoints on particular lines, single-step
  108. debug through the source code, etc.
  109. endif
  110. config PHYS_64BIT
  111. bool "64bit physical address support"
  112. help
  113. Say Y here to support 64bit physical memory address.
  114. This can be used not only for 64bit SoCs, but also for
  115. large physical address extention on 32bit SoCs.
  116. endmenu # General setup
  117. menu "Boot images"
  118. config FIT
  119. bool "Support Flattened Image Tree"
  120. help
  121. This option allows to boot the new uImage structrure,
  122. Flattened Image Tree. FIT is formally a FDT, which can include
  123. images of various types (kernel, FDT blob, ramdisk, etc.)
  124. in a single blob. To boot this new uImage structure,
  125. pass the address of the blob to the "bootm" command.
  126. FIT is very flexible, supporting compression, multiple images,
  127. multiple configurations, verification through hashing and also
  128. verified boot (secure boot using RSA). This option enables that
  129. feature.
  130. config SPL_FIT
  131. bool "Support Flattened Image Tree within SPL"
  132. depends on FIT
  133. depends on SPL
  134. config FIT_VERBOSE
  135. bool "Display verbose messages on FIT boot"
  136. depends on FIT
  137. config FIT_SIGNATURE
  138. bool "Enable signature verification of FIT uImages"
  139. depends on FIT
  140. depends on DM
  141. select RSA
  142. help
  143. This option enables signature verification of FIT uImages,
  144. using a hash signed and verified using RSA. If
  145. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  146. hashing is available using hardware, then then RSA library will use
  147. it. See doc/uImage.FIT/signature.txt for more details.
  148. WARNING: When relying on signed FIT images with a required signature
  149. check the legacy image format is disabled by default, so that
  150. unsigned images cannot be loaded. If a board needs the legacy image
  151. format support in this case, enable it using
  152. CONFIG_IMAGE_FORMAT_LEGACY.
  153. config SPL_FIT_SIGNATURE
  154. bool "Enable signature verification of FIT firmware within SPL"
  155. depends on SPL_FIT
  156. depends on SPL_DM
  157. select SPL_RSA
  158. config FIT_BEST_MATCH
  159. bool "Select the best match for the kernel device tree"
  160. depends on FIT
  161. help
  162. When no configuration is explicitly selected, default to the
  163. one whose fdt's compatibility field best matches that of
  164. U-Boot itself. A match is considered "best" if it matches the
  165. most specific compatibility entry of U-Boot's fdt's root node.
  166. The order of entries in the configuration's fdt is ignored.
  167. config FIT_VERBOSE
  168. bool "Show verbose messages when FIT images fails"
  169. depends on FIT
  170. help
  171. Generally a system will have valid FIT images so debug messages
  172. are a waste of code space. If you are debugging your images then
  173. you can enable this option to get more verbose information about
  174. failures.
  175. config OF_BOARD_SETUP
  176. bool "Set up board-specific details in device tree before boot"
  177. depends on OF_LIBFDT
  178. help
  179. This causes U-Boot to call ft_board_setup() before booting into
  180. the Operating System. This function can set up various
  181. board-specific information in the device tree for use by the OS.
  182. The device tree is then passed to the OS.
  183. config OF_SYSTEM_SETUP
  184. bool "Set up system-specific details in device tree before boot"
  185. depends on OF_LIBFDT
  186. help
  187. This causes U-Boot to call ft_system_setup() before booting into
  188. the Operating System. This function can set up various
  189. system-specific information in the device tree for use by the OS.
  190. The device tree is then passed to the OS.
  191. config OF_STDOUT_VIA_ALIAS
  192. bool "Update the device-tree stdout alias from U-Boot"
  193. depends on OF_LIBFDT
  194. help
  195. This uses U-Boot's serial alias from the aliases node to update
  196. the device tree passed to the OS. The "linux,stdout-path" property
  197. in the chosen node is set to point to the correct serial node.
  198. This option currently references CONFIG_CONS_INDEX, which is
  199. incorrect when used with device tree as this option does not
  200. exist / should not be used.
  201. config SYS_EXTRA_OPTIONS
  202. string "Extra Options (DEPRECATED)"
  203. help
  204. The old configuration infrastructure (= mkconfig + boards.cfg)
  205. provided the extra options field. If you have something like
  206. "HAS_BAR,BAZ=64", the optional options
  207. #define CONFIG_HAS
  208. #define CONFIG_BAZ 64
  209. will be defined in include/config.h.
  210. This option was prepared for the smooth migration from the old
  211. configuration to Kconfig. Since this option will be removed sometime,
  212. new boards should not use this option.
  213. config SYS_TEXT_BASE
  214. depends on SPARC || ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
  215. (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS
  216. depends on !EFI_APP
  217. hex "Text Base"
  218. help
  219. TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
  220. config SPL_LOAD_FIT
  221. bool "Enable SPL loading U-Boot as a FIT"
  222. depends on FIT
  223. help
  224. Normally with the SPL framework a legacy image is generated as part
  225. of the build. This contains U-Boot along with information as to
  226. where it should be loaded. This option instead enables generation
  227. of a FIT (Flat Image Tree) which provides more flexibility. In
  228. particular it can handle selecting from multiple device tree
  229. and passing the correct one to U-Boot.
  230. config SPL_FIT_IMAGE_POST_PROCESS
  231. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  232. depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
  233. help
  234. Allows doing any sort of manipulation to blobs after they got extracted
  235. from the U-Boot FIT image like stripping off headers or modifying the
  236. size of the blob, verification, authentication, decryption etc. in a
  237. platform or board specific way. In order to use this feature a platform
  238. or board-specific implementation of board_fit_image_post_process() must
  239. be provided. Also, anything done during this post-processing step would
  240. need to be comprehended in how the images were prepared before being
  241. injected into the FIT creation (i.e. the blobs would have been pre-
  242. processed before being added to the FIT image).
  243. config FIT_IMAGE_POST_PROCESS
  244. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  245. depends on FIT && TI_SECURE_DEVICE
  246. help
  247. Allows doing any sort of manipulation to blobs after they got extracted
  248. from FIT images like stripping off headers or modifying the size of the
  249. blob, verification, authentication, decryption etc. in a platform or
  250. board specific way. In order to use this feature a platform or board-
  251. specific implementation of board_fit_image_post_process() must be
  252. provided. Also, anything done during this post-processing step would
  253. need to be comprehended in how the images were prepared before being
  254. injected into the FIT creation (i.e. the blobs would have been pre-
  255. processed before being added to the FIT image).
  256. config SPL_DFU_SUPPORT
  257. bool "Enable SPL with DFU to load binaries to memory device"
  258. depends on USB
  259. help
  260. Currently the SPL does not have capability to load the
  261. binaries or boot images to boot devices like ram,eMMC,SPI,etc.
  262. This feature enables the DFU (Device Firmware Upgarde) in SPL with
  263. RAM memory device support. The ROM code will load and execute
  264. the SPL built with dfu. The user can load binaries (u-boot/kernel) to
  265. selected device partition from host-pc using dfu-utils.
  266. This feature will be useful to flash the binaries to factory
  267. or bare-metal boards using USB interface.
  268. choice
  269. bool "DFU device selection"
  270. depends on SPL_DFU_SUPPORT
  271. config SPL_DFU_RAM
  272. bool "RAM device"
  273. depends on SPL_DFU_SUPPORT
  274. help
  275. select RAM/DDR memory device for loading binary images
  276. (u-boot/kernel) to the selected device partition using
  277. DFU and execute the u-boot/kernel from RAM.
  278. endchoice
  279. config SYS_CLK_FREQ
  280. depends on ARC || ARCH_SUNXI
  281. int "CPU clock frequency"
  282. help
  283. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  284. config ARCH_FIXUP_FDT
  285. bool "Enable arch_fixup_fdt() call"
  286. depends on ARM || MIPS
  287. default y
  288. help
  289. Enable FDT memory map syncup before OS boot. This feature can be
  290. used for booting OS with different memory setup where the part of
  291. the memory location should be used for different purpose.
  292. endmenu # Boot images
  293. source "common/Kconfig"
  294. source "cmd/Kconfig"
  295. source "dts/Kconfig"
  296. source "net/Kconfig"
  297. source "drivers/Kconfig"
  298. source "fs/Kconfig"
  299. source "lib/Kconfig"
  300. source "test/Kconfig"