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