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
60 select CMD_BOOTZ if ARM && !ARM64
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
86 default 0x2000 if SPL_DM && SPL_OF_CONTROL
89 Before relocation, memory is very limited on many platforms. Still,
90 we can provide a small malloc() pool if needed. Driver model in
91 particular needs this to operate, so that it can allocate the
92 initial serial device and any others that are needed.
95 bool "Configure standard U-Boot features (expert users)"
98 This option allows certain base U-Boot options and settings
99 to be disabled or tweaked. This is for specialized
100 environments which can tolerate a "non-standard" U-Boot.
101 Use this only if you really know what you are doing.
104 config SYS_MALLOC_CLEAR_ON_INIT
105 bool "Init with zeros the memory reserved for malloc (slow)"
108 This setting is enabled by default. The reserved malloc
109 memory is initialized with zeros, so first malloc calls
110 will return the pointer to the zeroed memory. But this
113 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
114 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
115 Then the boot time can be significantly reduced.
117 When disabling this, please check if malloc calls, maybe
118 should be replaced by calloc - if one expects zeroed memory.
121 bool "Enable debug information for tools"
123 Enable generation of debug information for tools such as mkimage.
124 This can be used for debugging purposes. With debug information
125 it is possible to set breakpoints on particular lines, single-step
126 debug through the source code, etc.
131 bool "64bit physical address support"
133 Say Y here to support 64bit physical memory address.
134 This can be used not only for 64bit SoCs, but also for
135 large physical address extention on 32bit SoCs.
137 endmenu # General setup
149 depends on SUPPORT_SPL
152 If you want to build SPL as well as the normal image, say Y.
154 config SPL_SYS_MALLOC_SIMPLE
157 prompt "Only use malloc_simple functions in the SPL"
159 Say Y here to only use the *_simple malloc functions from
160 malloc_simple.c, rather then using the versions from dlmalloc.c;
161 this will make the SPL binary smaller at the cost of more heap
162 usage as the *_simple malloc functions do not re-use free-ed mem.
166 bool "Enable SDRAM location for SPL stack"
168 SPL starts off execution in SRAM and thus typically has only a small
169 stack available. Since SPL sets up DRAM while in its board_init_f()
170 function, it is possible for the stack to move there before
171 board_init_r() is reached. This option enables a special SDRAM
172 location for the SPL stack. U-Boot SPL switches to this after
173 board_init_f() completes, and before board_init_r() starts.
175 config SPL_STACK_R_ADDR
176 depends on SPL_STACK_R
177 hex "SDRAM location for SPL stack"
179 Specify the address in SDRAM for the SPL stack. This will be set up
180 before board_init_r() is called.
182 config SPL_STACK_R_MALLOC_SIMPLE_LEN
183 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
184 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
187 Specify the amount of the stack to use as memory pool for
188 malloc_simple after switching the stack to DRAM. This may be set
189 to give board_init_r() a larger heap then the initial heap in
190 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
192 config SPL_SEPARATE_BSS
194 bool "BSS section is in a different memory region from text"
196 Some platforms need a large BSS region in SPL and can provide this
197 because RAM is already set up. In this case BSS can be moved to RAM.
198 This option should then be enabled so that the correct device tree
199 location is used. Normally we put the device tree at the end of BSS
200 but with this option enabled, it goes at _image_binary_end.
204 depends on SPL && SUPPORT_TPL
207 If you want to build TPL as well as the normal image and SPL, say Y.
210 bool "Support Flattened Image Tree"
212 This option allows to boot the new uImage structrure,
213 Flattened Image Tree. FIT is formally a FDT, which can include
214 images of various types (kernel, FDT blob, ramdisk, etc.)
215 in a single blob. To boot this new uImage structure,
216 pass the address of the blob to the "bootm" command.
217 FIT is very flexible, supporting compression, multiple images,
218 multiple configurations, verification through hashing and also
219 verified boot (secure boot using RSA). This option enables that
223 bool "Support Flattened Image Tree within SPL"
228 bool "Display verbose messages on FIT boot"
232 bool "Enable signature verification of FIT uImages"
237 This option enables signature verification of FIT uImages,
238 using a hash signed and verified using RSA. If
239 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
240 hashing is available using hardware, then then RSA library will use
241 it. See doc/uImage.FIT/signature.txt for more details.
243 WARNING: When relying on signed FIT images with a required signature
244 check the legacy image format is disabled by default, so that
245 unsigned images cannot be loaded. If a board needs the legacy image
246 format support in this case, enable it using
247 CONFIG_IMAGE_FORMAT_LEGACY.
249 config SPL_FIT_SIGNATURE
250 bool "Enable signature verification of FIT firmware within SPL"
255 config FIT_BEST_MATCH
256 bool "Select the best match for the kernel device tree"
259 When no configuration is explicitly selected, default to the
260 one whose fdt's compatibility field best matches that of
261 U-Boot itself. A match is considered "best" if it matches the
262 most specific compatibility entry of U-Boot's fdt's root node.
263 The order of entries in the configuration's fdt is ignored.
266 bool "Show verbose messages when FIT images fails"
269 Generally a system will have valid FIT images so debug messages
270 are a waste of code space. If you are debugging your images then
271 you can enable this option to get more verbose information about
274 config OF_BOARD_SETUP
275 bool "Set up board-specific details in device tree before boot"
278 This causes U-Boot to call ft_board_setup() before booting into
279 the Operating System. This function can set up various
280 board-specific information in the device tree for use by the OS.
281 The device tree is then passed to the OS.
283 config OF_SYSTEM_SETUP
284 bool "Set up system-specific details in device tree before boot"
287 This causes U-Boot to call ft_system_setup() before booting into
288 the Operating System. This function can set up various
289 system-specific information in the device tree for use by the OS.
290 The device tree is then passed to the OS.
292 config OF_STDOUT_VIA_ALIAS
293 bool "Update the device-tree stdout alias from U-Boot"
296 This uses U-Boot's serial alias from the aliases node to update
297 the device tree passed to the OS. The "linux,stdout-path" property
298 in the chosen node is set to point to the correct serial node.
299 This option currently references CONFIG_CONS_INDEX, which is
300 incorrect when used with device tree as this option does not
301 exist / should not be used.
303 config SYS_EXTRA_OPTIONS
304 string "Extra Options (DEPRECATED)"
306 The old configuration infrastructure (= mkconfig + boards.cfg)
307 provided the extra options field. If you have something like
308 "HAS_BAR,BAZ=64", the optional options
310 #define CONFIG_BAZ 64
311 will be defined in include/config.h.
312 This option was prepared for the smooth migration from the old
313 configuration to Kconfig. Since this option will be removed sometime,
314 new boards should not use this option.
317 depends on SPARC || ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
318 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS
322 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
325 bool "Enable SPL loading U-Boot as a FIT"
328 Normally with the SPL framework a legacy image is generated as part
329 of the build. This contains U-Boot along with information as to
330 where it should be loaded. This option instead enables generation
331 of a FIT (Flat Image Tree) which provides more flexibility. In
332 particular it can handle selecting from multiple device tree
333 and passing the correct one to U-Boot.
335 config SPL_FIT_IMAGE_POST_PROCESS
336 bool "Enable post-processing of FIT artifacts after loading by the SPL"
337 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
339 Allows doing any sort of manipulation to blobs after they got extracted
340 from the U-Boot FIT image like stripping off headers or modifying the
341 size of the blob, verification, authentication, decryption etc. in a
342 platform or board specific way. In order to use this feature a platform
343 or board-specific implementation of board_fit_image_post_process() must
344 be provided. Also, anything done during this post-processing step would
345 need to be comprehended in how the images were prepared before being
346 injected into the FIT creation (i.e. the blobs would have been pre-
347 processed before being added to the FIT image).
349 config FIT_IMAGE_POST_PROCESS
350 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
351 depends on FIT && TI_SECURE_DEVICE
353 Allows doing any sort of manipulation to blobs after they got extracted
354 from FIT images like stripping off headers or modifying the size of the
355 blob, verification, authentication, decryption etc. in a platform or
356 board specific way. In order to use this feature a platform or board-
357 specific implementation of board_fit_image_post_process() must be
358 provided. Also, anything done during this post-processing step would
359 need to be comprehended in how the images were prepared before being
360 injected into the FIT creation (i.e. the blobs would have been pre-
361 processed before being added to the FIT image).
364 depends on ARC || ARCH_SUNXI
365 int "CPU clock frequency"
367 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
369 config ARCH_FIXUP_FDT
370 bool "Enable arch_fixup_fdt() call"
371 depends on ARM || MIPS
374 Enable FDT memory map syncup before OS boot. This feature can be
375 used for booting OS with different memory setup where the part of
376 the memory location should be used for different purpose.
378 endmenu # Boot images
380 source "common/Kconfig"
388 source "drivers/Kconfig"
394 source "test/Kconfig"