xref: /OK3568_Linux_fs/u-boot/Kconfig (revision 4882a59341e53eb6f0b4789bf948001014eff981)
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#
6mainmenu "U-Boot $UBOOTVERSION Configuration"
7
8config UBOOTVERSION
9	string
10	option env="UBOOTVERSION"
11
12# Allow defaults in arch-specific code to override any given here
13source "arch/Kconfig"
14
15menu "General setup"
16
17config BROKEN
18	bool
19	help
20	  This option cannot be enabled. It is used as dependency
21	  for broken and incomplete features.
22
23config LOCALVERSION
24	string "Local version - append to U-Boot release"
25	help
26	  Append an extra string to the end of your U-Boot version.
27	  This will show up in your boot log, for example.
28	  The string you set here will be appended after the contents of
29	  any files with a filename matching localversion* in your
30	  object and source tree, in that order.  Your total string can
31	  be a maximum of 64 characters.
32
33config LOCALVERSION_AUTO
34	bool "Automatically append version information to the version string"
35	default y
36	help
37	  This will try to automatically determine if the current tree is a
38	  release tree by looking for Git tags that belong to the current
39	  top of tree revision.
40
41	  A string of the format -gxxxxxxxx will be added to the localversion
42	  if a Git-based tree is found.  The string generated by this will be
43	  appended after any matching localversion* files, and after the value
44	  set in CONFIG_LOCALVERSION.
45
46	  (The actual string used here is the first eight characters produced
47	  by running the command:
48
49	    $ git rev-parse --verify HEAD
50
51	  which is done within the script "scripts/setlocalversion".)
52
53config CC_OPTIMIZE_FOR_SIZE
54	bool "Optimize for size"
55	default y
56	help
57	  Enabling this option will pass "-Os" instead of "-O2" to gcc
58	  resulting in a smaller U-Boot image.
59
60	  This option is enabled by default for U-Boot.
61
62config DISTRO_DEFAULTS
63	bool "Select defaults suitable for booting general purpose Linux distributions"
64	default y if ARCH_SUNXI || TEGRA
65	default y if ARCH_LS2080A
66	default y if ARCH_MESON
67	default y if ARCH_ROCKCHIP
68	default n
69	select CMD_BOOTZ if ARM && !ARM64
70	select CMD_BOOTI if ARM64
71	select CMD_DHCP
72	imply CMD_PXE
73	select CMD_EXT2
74	select CMD_EXT4
75	select CMD_FAT
76	select CMD_FS_GENERIC
77	imply CMD_MII
78	select CMD_PING
79	select CMD_PART
80	select HUSH_PARSER
81	help
82	  Select this to enable various options and commands which are suitable
83	  for building u-boot for booting general purpose Linux distributions.
84
85config SYS_MALLOC_F
86	bool "Enable malloc() pool before relocation"
87	default y if DM
88	help
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.
93
94config SYS_MALLOC_F_LEN
95	hex "Size of malloc() pool before relocation"
96	depends on SYS_MALLOC_F
97	default 0x400
98	help
99	  Before relocation, memory is very limited on many platforms. Still,
100	  we can provide a small malloc() pool if needed. Driver model in
101	  particular needs this to operate, so that it can allocate the
102	  initial serial device and any others that are needed.
103
104config SPL_SYS_MALLOC_F_LEN
105        hex "Size of malloc() pool in SPL before relocation"
106        depends on SYS_MALLOC_F
107        default SYS_MALLOC_F_LEN
108        help
109          Before relocation, memory is very limited on many platforms. Still,
110          we can provide a small malloc() pool if needed. Driver model in
111          particular needs this to operate, so that it can allocate the
112          initial serial device and any others that are needed.
113
114config TPL_SYS_MALLOC_F_LEN
115        hex "Size of malloc() pool in TPL before relocation"
116        depends on SYS_MALLOC_F
117        default SYS_MALLOC_F_LEN
118        help
119          Before relocation, memory is very limited on many platforms. Still,
120          we can provide a small malloc() pool if needed. Driver model in
121          particular needs this to operate, so that it can allocate the
122          initial serial device and any others that are needed.
123
124menuconfig EXPERT
125	bool "Configure standard U-Boot features (expert users)"
126	default y
127	help
128	  This option allows certain base U-Boot options and settings
129	  to be disabled or tweaked. This is for specialized
130	  environments which can tolerate a "non-standard" U-Boot.
131	  Use this only if you really know what you are doing.
132
133if EXPERT
134	config SYS_MALLOC_CLEAR_ON_INIT
135	bool "Init with zeros the memory reserved for malloc (slow)"
136	default y if !ARCH_ROCKCHIP
137	help
138	  This setting is enabled by default. The reserved malloc
139	  memory is initialized with zeros, so first malloc calls
140	  will return the pointer to the zeroed memory. But this
141	  slows the boot time.
142
143	  It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
144	  value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
145	  Then the boot time can be significantly reduced.
146	  Warning:
147	  When disabling this, please check if malloc calls, maybe
148	  should be replaced by calloc - if one expects zeroed memory.
149
150config TOOLS_DEBUG
151	bool "Enable debug information for tools"
152	help
153	  Enable generation of debug information for tools such as mkimage.
154	  This can be used for debugging purposes. With debug information
155	  it is possible to set breakpoints on particular lines, single-step
156	  debug through the source code, etc.
157
158endif # EXPERT
159
160config PHYS_64BIT
161	bool "64bit physical address support"
162	help
163	  Say Y here to support 64bit physical memory address.
164	  This can be used not only for 64bit SoCs, but also for
165	  large physical address extention on 32bit SoCs.
166
167endmenu		# General setup
168
169menu "Boot images"
170
171config ANDROID_BOOT_IMAGE
172	bool "Enable support for Android Boot Images"
173	default y if FASTBOOT
174	help
175	  This enables support for booting images which use the Android
176	  image format header.
177
178config FIT
179	bool "Support Flattened Image Tree"
180	help
181	  This option allows you to boot the new uImage structure,
182	  Flattened Image Tree.  FIT is formally a FDT, which can include
183	  images of various types (kernel, FDT blob, ramdisk, etc.)
184	  in a single blob.  To boot this new uImage structure,
185	  pass the address of the blob to the "bootm" command.
186	  FIT is very flexible, supporting compression, multiple images,
187	  multiple configurations, verification through hashing and also
188	  verified boot (secure boot using RSA).
189
190if FIT
191
192config FIT_ENABLE_SHA256_SUPPORT
193	bool "Support SHA256 checksum of FIT image contents"
194	select SHA256 if !DM_CRYPTO
195	default y
196	help
197	  Enable this to support SHA256 checksum of FIT image contents. A
198	  SHA256 checksum is a 256-bit (32-byte) hash value used to check that
199	  the image contents have not been corrupted. SHA256 is recommended
200	  for use in secure applications since (as at 2016) there is no known
201	  feasible attack that could produce a 'collision' with differing
202	  input data. Use this for the highest security. Note that only the
203	  SHA256 variant is supported: SHA512 and others are not currently
204	  supported in U-Boot.
205
206config FIT_ENABLE_RSA4096_SUPPORT
207	bool "Support RSA4096 verification of FIT image contents"
208	select RSA_SOFTWARE_EXP if !DM_CRYPTO
209	default n
210	help
211	  Enable this to support RSA4096 checksum of FIT image contents. A
212	  RSA4096 is a 4096-bit (512-byte) key used to check that
213	  check if the content comes from an encryption party. RSA4096 is one
214	  of algorithms recommended for use in secure applications since (as at 2016)
215	  there is no known feasible attack that could produce a 'collision' with differing
216	  input data. Use this for the higher security than RSA2048 in default.
217
218config FIT_SIGNATURE
219	bool "Enable signature verification of FIT uImages"
220	depends on DM
221	select RSA
222	select CONSOLE_DISABLE_CLI
223	help
224	  This option enables signature verification of FIT uImages,
225	  using a hash signed and verified using RSA. If
226	  CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
227	  hashing is available using hardware, then the RSA library will use
228	  it. See doc/uImage.FIT/signature.txt for more details.
229
230	  WARNING: When relying on signed FIT images with a required signature
231	  check the legacy image format is disabled by default, so that
232	  unsigned images cannot be loaded. If a board needs the legacy image
233	  format support in this case, enable it using
234	  CONFIG_IMAGE_FORMAT_LEGACY.
235
236config FIT_ROLLBACK_PROTECT
237	bool "Enable rollback-index protection for FIT image"
238	depends on FIT_SIGNATURE
239	help
240	  Enable rollback-index protection for FIT image
241
242config FIT_ENABLE_RSASSA_PSS_SUPPORT
243	bool "Support rsassa-pss signature scheme of FIT image contents"
244	depends on FIT_SIGNATURE
245	default y
246	help
247	  Enable this to support the pss padding algorithm as described
248	  in the rfc8017 (https://tools.ietf.org/html/rfc8017).
249
250config FIT_VERBOSE
251	bool "Show verbose messages when FIT images fail"
252	help
253	  Generally a system will have valid FIT images so debug messages
254	  are a waste of code space. If you are debugging your images then
255	  you can enable this option to get more verbose information about
256	  failures.
257
258config FIT_BEST_MATCH
259	bool "Select the best match for the kernel device tree"
260	help
261	  When no configuration is explicitly selected, default to the
262	  one whose fdt's compatibility field best matches that of
263	  U-Boot itself. A match is considered "best" if it matches the
264	  most specific compatibility entry of U-Boot's fdt's root node.
265	  The order of entries in the configuration's fdt is ignored.
266
267config FIT_IMAGE_POST_PROCESS
268	bool "Enable post-processing of FIT artifacts after loading by U-Boot"
269	help
270	  Allows doing any sort of manipulation to blobs after they got extracted
271	  from FIT images like stripping off headers or modifying the size of the
272	  blob, verification, authentication, decryption etc. in a platform or
273	  board specific way. In order to use this feature a platform or board-
274	  specific implementation of board_fit_image_post_process() must be
275	  provided. Also, anything done during this post-processing step would
276	  need to be comprehended in how the images were prepared before being
277	  injected into the FIT creation (i.e. the blobs would have been pre-
278	  processed before being added to the FIT image).
279
280config FIT_HW_CRYPTO
281	bool "Enable hardware crypto for FIT image checksum and rsa verify"
282	depends on DM_CRYPTO
283	help
284	  Enable hardware crypto for FIT image checksum and rsa verify.
285
286config FIT_PRINT
287	bool "Enable fit image structure and data print"
288	default y
289	help
290	  Say y here if you want to enable fit image structure and data
291	  print.
292
293config FIT_OMIT_UBOOT
294	bool "Omit u-boot-nodtb.bin and u-boot.dtb when output uboot.itb"
295
296if SPL
297
298config SPL_FIT
299	bool "Support Flattened Image Tree within SPL"
300	depends on SPL
301	select SPL_OF_LIBFDT
302
303config SPL_FIT_SIGNATURE
304	bool "Enable signature verification of FIT firmware within SPL"
305	depends on SPL_DM
306	select SPL_FIT
307	select SPL_RSA
308
309config SPL_FIT_ROLLBACK_PROTECT
310	bool "Enable SPL rollback-index protection for FIT image"
311	depends on SPL_FIT_SIGNATURE
312	help
313	  Enable SPL rollback-index protection for FIT image
314
315config SPL_LOAD_FIT
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
326config SPL_FIT_IMAGE_POST_PROCESS
327	bool "Enable post-processing of FIT artifacts after loading by the SPL"
328	depends on SPL_LOAD_FIT
329	help
330	  Allows doing any sort of manipulation to blobs after they got extracted
331	  from the U-Boot FIT image like stripping off headers or modifying the
332	  size of the blob, verification, authentication, decryption etc. in a
333	  platform or board specific way. In order to use this feature a platform
334	  or board-specific implementation of board_fit_image_post_process() must
335	  be provided. Also, anything done during this post-processing step would
336	  need to be comprehended in how the images were prepared before being
337	  injected into the FIT creation (i.e. the blobs would have been pre-
338	  processed before being added to the FIT image).
339
340config SPL_FIT_HW_CRYPTO
341	bool "Enable SPL hardware crypto for FIT image checksum and rsa verify"
342	depends on SPL_DM_CRYPTO
343	help
344	  Enable SPL hardware crypto for FIT image checksum and rsa verify.
345
346config SPL_SYS_DCACHE_OFF
347	bool "Disable SPL dcache"
348	default y
349	help
350	  Disable SPL dcache. Please make sure CONFIG_SPL_SYS_MALLOC_F_LEN
351	  is large enough to malloc TLB and bd_t buffer while enabling dcache.
352
353config SPL_FIT_PRINT
354	bool "Enable fit image structure and data print in SPL"
355	default n
356	help
357	  Say y here if you want to enable fit image structure and data
358	  print in SPL.
359
360endif # SPL
361
362config SPL_FIT_SOURCE
363	string ".its source file for U-Boot FIT image"
364	depends on SPL_FIT || FIT
365	help
366	  Specifies a (platform specific) FIT source file to generate the
367	  U-Boot FIT image. This could specify further image to load and/or
368	  execute.
369
370config SPL_FIT_GENERATOR
371	string ".its file generator script for U-Boot FIT image"
372	depends on SPL_FIT || FIT
373	default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
374	help
375	  Specifies a (platform specific) script file to generate the FIT
376	  source file used to build the U-Boot FIT image file. This gets
377	  passed a list of supported device tree file stub names to
378	  include in the generated image.
379
380config SPL_FIT_IMAGE_KB
381	int "SPL FIT image size in KiB"
382	depends on SPL_FIT || FIT
383	default 2048
384	help
385	  SPL FIT image size in KiB, default 2048KB = 1024KB(u-boot) + 1024KB(tee/atf + others).
386
387config SPL_FIT_IMAGE_MULTIPLE
388	int "SPL FIT image multiple number"
389	depends on SPL_FIT || FIT
390	default 2
391	help
392	  SPL FIT image multiple number.
393
394endif # FIT
395
396config OF_BOARD_SETUP
397	bool "Set up board-specific details in device tree before boot"
398	depends on OF_LIBFDT
399	help
400	  This causes U-Boot to call ft_board_setup() before booting into
401	  the Operating System. This function can set up various
402	  board-specific information in the device tree for use by the OS.
403	  The device tree is then passed to the OS.
404
405config OF_SYSTEM_SETUP
406	bool "Set up system-specific details in device tree before boot"
407	depends on OF_LIBFDT
408	help
409	  This causes U-Boot to call ft_system_setup() before booting into
410	  the Operating System. This function can set up various
411	  system-specific information in the device tree for use by the OS.
412	  The device tree is then passed to the OS.
413
414config OF_STDOUT_VIA_ALIAS
415	bool "Update the device-tree stdout alias from U-Boot"
416	depends on OF_LIBFDT
417	help
418	  This uses U-Boot's serial alias from the aliases node to update
419	  the device tree passed to the OS. The "linux,stdout-path" property
420	  in the chosen node is set to point to the correct serial node.
421	  This option currently references CONFIG_CONS_INDEX, which is
422	  incorrect when used with device tree as this option does not
423	  exist / should not be used.
424
425config SYS_EXTRA_OPTIONS
426	string "Extra Options (DEPRECATED)"
427	help
428	  The old configuration infrastructure (= mkconfig + boards.cfg)
429	  provided the extra options field. If you have something like
430	  "HAS_BAR,BAZ=64", the optional options
431	    #define CONFIG_HAS
432	    #define CONFIG_BAZ	64
433	  will be defined in include/config.h.
434	  This option was prepared for the smooth migration from the old
435	  configuration to Kconfig. Since this option will be removed sometime,
436	  new boards should not use this option.
437
438config SYS_TEXT_BASE
439	depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
440		(M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
441		ARCH_ZYNQ || ARCH_KEYSTONE || ARCH_OMAP2PLUS
442	depends on !EFI_APP
443	hex "Text Base"
444	help
445	  TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
446
447	default 0x80800000 if ARCH_OMAP2PLUS
448
449
450config SYS_CLK_FREQ
451	depends on ARC || ARCH_SUNXI
452	int "CPU clock frequency"
453	help
454	  TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
455
456config ARCH_FIXUP_FDT_MEMORY
457	bool "Enable arch_fixup_memory_banks() call"
458	default y
459	help
460	  Enable FDT memory map syncup before OS boot. This feature can be
461	  used for booting OS with different memory setup where the part of
462	  the memory location should be used for different purpose.
463
464endmenu		# Boot images
465
466source "api/Kconfig"
467
468source "common/Kconfig"
469
470source "cmd/Kconfig"
471
472source "disk/Kconfig"
473
474source "dts/Kconfig"
475
476source "env/Kconfig"
477
478source "net/Kconfig"
479
480source "drivers/Kconfig"
481
482source "fs/Kconfig"
483
484source "lib/Kconfig"
485
486source "test/Kconfig"
487