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.
6 mainmenu "U-Boot $UBOOTVERSION Configuration"
10 option env="UBOOTVERSION"
12 # Allow defaults in arch-specific code to override any given here
18 string "Local version - append to U-Boot release"
20 Append an extra string to the end of your U-Boot version.
21 This will show up in your boot log, for example.
22 The string you set here will be appended after the contents of
23 any files with a filename matching localversion* in your
24 object and source tree, in that order. Your total string can
25 be a maximum of 64 characters.
27 config LOCALVERSION_AUTO
28 bool "Automatically append version information to the version string"
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
35 A string of the format -gxxxxxxxx will be added to the localversion
36 if a Git-based tree is found. The string generated by this will be
37 appended after any matching localversion* files, and after the value
38 set in CONFIG_LOCALVERSION.
40 (The actual string used here is the first eight characters produced
41 by running the command:
43 $ git rev-parse --verify HEAD
45 which is done within the script "scripts/setlocalversion".)
47 config CC_OPTIMIZE_FOR_SIZE
48 bool "Optimize for size"
51 Enabling this option will pass "-Os" instead of "-O2" to gcc
52 resulting in a smaller U-Boot image.
54 This option is enabled by default for U-Boot.
56 config DISTRO_DEFAULTS
57 bool "Select defaults suitable for booting general purpose Linux distributions"
58 default y if ARCH_SUNXI
61 select CMD_BOOTI if ARM64
71 Select this to enable various options and commands which are suitable
72 for building u-boot for booting general purpose Linux distributions.
75 bool "Enable malloc() pool before relocation"
78 Before relocation, memory is very limited on many platforms. Still,
79 we can provide a small malloc() pool if needed. Driver model in
80 particular needs this to operate, so that it can allocate the
81 initial serial device and any others that are needed.
83 config SYS_MALLOC_F_LEN
84 hex "Size of malloc() pool before relocation"
85 depends on SYS_MALLOC_F
88 Before relocation, memory is very limited on many platforms. Still,
89 we can provide a small malloc() pool if needed. Driver model in
90 particular needs this to operate, so that it can allocate the
91 initial serial device and any others that are needed.
94 bool "Configure standard U-Boot features (expert users)"
97 This option allows certain base U-Boot options and settings
98 to be disabled or tweaked. This is for specialized
99 environments which can tolerate a "non-standard" U-Boot.
100 Use this only if you really know what you are doing.
103 config SYS_MALLOC_CLEAR_ON_INIT
104 bool "Init with zeros the memory reserved for malloc (slow)"
107 This setting is enabled by default. The reserved malloc
108 memory is initialized with zeros, so first malloc calls
109 will return the pointer to the zeroed memory. But this
112 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
113 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
114 Then the boot time can be significantly reduced.
116 When disabling this, please check if malloc calls, maybe
117 should be replaced by calloc - if one expects zeroed memory.
120 bool "Enable debug information for tools"
122 Enable generation of debug information for tools such as mkimage.
123 This can be used for debugging purposes. With debug information
124 it is possible to set breakpoints on particular lines, single-step
125 debug through the source code, etc.
130 bool "64bit physical address support"
132 Say Y here to support 64bit physical memory address.
133 This can be used not only for 64bit SoCs, but also for
134 large physical address extention on 32bit SoCs.
136 endmenu # General setup
148 depends on SUPPORT_SPL
151 If you want to build SPL as well as the normal image, say Y.
153 config SPL_SYS_MALLOC_SIMPLE
156 prompt "Only use malloc_simple functions in the SPL"
158 Say Y here to only use the *_simple malloc functions from
159 malloc_simple.c, rather then using the versions from dlmalloc.c;
160 this will make the SPL binary smaller at the cost of more heap
161 usage as the *_simple malloc functions do not re-use free-ed mem.
165 bool "Enable SDRAM location for SPL stack"
167 SPL starts off execution in SRAM and thus typically has only a small
168 stack available. Since SPL sets up DRAM while in its board_init_f()
169 function, it is possible for the stack to move there before
170 board_init_r() is reached. This option enables a special SDRAM
171 location for the SPL stack. U-Boot SPL switches to this after
172 board_init_f() completes, and before board_init_r() starts.
174 config SPL_STACK_R_ADDR
175 depends on SPL_STACK_R
176 hex "SDRAM location for SPL stack"
178 Specify the address in SDRAM for the SPL stack. This will be set up
179 before board_init_r() is called.
181 config SPL_STACK_R_MALLOC_SIMPLE_LEN
182 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
183 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
186 Specify the amount of the stack to use as memory pool for
187 malloc_simple after switching the stack to DRAM. This may be set
188 to give board_init_r() a larger heap then the initial heap in
189 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
191 config SPL_SEPARATE_BSS
193 bool "BSS section is in a different memory region from text"
195 Some platforms need a large BSS region in SPL and can provide this
196 because RAM is already set up. In this case BSS can be moved to RAM.
197 This option should then be enabled so that the correct device tree
198 location is used. Normally we put the device tree at the end of BSS
199 but with this option enabled, it goes at _image_binary_end.
203 depends on SPL && SUPPORT_TPL
206 If you want to build TPL as well as the normal image and SPL, say Y.
209 bool "Support Flattened Image Tree"
211 This option allows to boot the new uImage structrure,
212 Flattened Image Tree. FIT is formally a FDT, which can include
213 images of various types (kernel, FDT blob, ramdisk, etc.)
214 in a single blob. To boot this new uImage structure,
215 pass the address of the blob to the "bootm" command.
216 FIT is very flexible, supporting compression, multiple images,
217 multiple configurations, verification through hashing and also
218 verified boot (secure boot using RSA). This option enables that
222 bool "Support Flattened Image Tree within SPL"
227 bool "Display verbose messages on FIT boot"
231 bool "Enable signature verification of FIT uImages"
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 then RSA library will use
240 it. See doc/uImage.FIT/signature.txt for more details.
242 WARNING: When relying on signed FIT images with a required signature
243 check the legacy image format is disabled by default, so that
244 unsigned images cannot be loaded. If a board needs the legacy image
245 format support in this case, enable it using
246 CONFIG_IMAGE_FORMAT_LEGACY.
248 config SPL_FIT_SIGNATURE
249 bool "Enable signature verification of FIT firmware within SPL"
254 config FIT_BEST_MATCH
255 bool "Select the best match for the kernel device tree"
258 When no configuration is explicitly selected, default to the
259 one whose fdt's compatibility field best matches that of
260 U-Boot itself. A match is considered "best" if it matches the
261 most specific compatibility entry of U-Boot's fdt's root node.
262 The order of entries in the configuration's fdt is ignored.
265 bool "Show verbose messages when FIT images fails"
268 Generally a system will have valid FIT images so debug messages
269 are a waste of code space. If you are debugging your images then
270 you can enable this option to get more verbose information about
273 config OF_BOARD_SETUP
274 bool "Set up board-specific details in device tree before boot"
277 This causes U-Boot to call ft_board_setup() before booting into
278 the Operating System. This function can set up various
279 board-specific information in the device tree for use by the OS.
280 The device tree is then passed to the OS.
282 config OF_SYSTEM_SETUP
283 bool "Set up system-specific details in device tree before boot"
286 This causes U-Boot to call ft_system_setup() before booting into
287 the Operating System. This function can set up various
288 system-specific information in the device tree for use by the OS.
289 The device tree is then passed to the OS.
291 config OF_STDOUT_VIA_ALIAS
292 bool "Update the device-tree stdout alias from U-Boot"
295 This uses U-Boot's serial alias from the aliases node to update
296 the device tree passed to the OS. The "linux,stdout-path" property
297 in the chosen node is set to point to the correct serial node.
298 This option currently references CONFIG_CONS_INDEX, which is
299 incorrect when used with device tree as this option does not
300 exist / should not be used.
302 config SYS_EXTRA_OPTIONS
303 string "Extra Options (DEPRECATED)"
305 The old configuration infrastructure (= mkconfig + boards.cfg)
306 provided the extra options field. If you have something like
307 "HAS_BAR,BAZ=64", the optional options
309 #define CONFIG_BAZ 64
310 will be defined in include/config.h.
311 This option was prepared for the smooth migration from the old
312 configuration to Kconfig. Since this option will be removed sometime,
313 new boards should not use this option.
316 depends on SPARC || ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
317 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS
321 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
324 bool "Enable SPL loading U-Boot as a FIT"
327 Normally with the SPL framework a legacy image is generated as part
328 of the build. This contains U-Boot along with information as to
329 where it should be loaded. This option instead enables generation
330 of a FIT (Flat Image Tree) which provides more flexibility. In
331 particular it can handle selecting from multiple device tree
332 and passing the correct one to U-Boot.
334 config SPL_FIT_IMAGE_POST_PROCESS
335 bool "Enable post-processing of FIT artifacts after loading by the SPL"
336 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
338 Allows doing any sort of manipulation to blobs after they got extracted
339 from the U-Boot FIT image like stripping off headers or modifying the
340 size of the blob, verification, authentication, decryption etc. in a
341 platform or board specific way. In order to use this feature a platform
342 or board-specific implementation of board_fit_image_post_process() must
343 be provided. Also, anything done during this post-processing step would
344 need to be comprehended in how the images were prepared before being
345 injected into the FIT creation (i.e. the blobs would have been pre-
346 processed before being added to the FIT image).
348 config FIT_IMAGE_POST_PROCESS
349 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
350 depends on FIT && TI_SECURE_DEVICE
352 Allows doing any sort of manipulation to blobs after they got extracted
353 from FIT images like stripping off headers or modifying the size of the
354 blob, verification, authentication, decryption etc. in a platform or
355 board specific way. In order to use this feature a platform or board-
356 specific implementation of board_fit_image_post_process() must be
357 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).
363 depends on ARC || ARCH_SUNXI
364 int "CPU clock frequency"
366 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
368 config ARCH_FIXUP_FDT
369 bool "Enable arch_fixup_fdt() call"
370 depends on ARM || MIPS
373 Enable FDT memory map syncup before OS boot. This feature can be
374 used for booting OS with different memory setup where the part of
375 the memory location should be used for different purpose.
377 endmenu # Boot images
379 source "common/Kconfig"
387 source "drivers/Kconfig"
393 source "test/Kconfig"