xref: /rk3399_rockchip-uboot/Kconfig (revision 008ec9b4bc06f98dd7efdc7d2f44eb066be036e6)
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	help
213	  This option enables signature verification of FIT uImages,
214	  using a hash signed and verified using RSA. If
215	  CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
216	  hashing is available using hardware, then the RSA library will use
217	  it. See doc/uImage.FIT/signature.txt for more details.
218
219	  WARNING: When relying on signed FIT images with a required signature
220	  check the legacy image format is disabled by default, so that
221	  unsigned images cannot be loaded. If a board needs the legacy image
222	  format support in this case, enable it using
223	  CONFIG_IMAGE_FORMAT_LEGACY.
224
225config FIT_VERBOSE
226	bool "Show verbose messages when FIT images fail"
227	help
228	  Generally a system will have valid FIT images so debug messages
229	  are a waste of code space. If you are debugging your images then
230	  you can enable this option to get more verbose information about
231	  failures.
232
233config FIT_BEST_MATCH
234	bool "Select the best match for the kernel device tree"
235	help
236	  When no configuration is explicitly selected, default to the
237	  one whose fdt's compatibility field best matches that of
238	  U-Boot itself. A match is considered "best" if it matches the
239	  most specific compatibility entry of U-Boot's fdt's root node.
240	  The order of entries in the configuration's fdt is ignored.
241
242config FIT_IMAGE_POST_PROCESS
243	bool "Enable post-processing of FIT artifacts after loading by U-Boot"
244	depends on TI_SECURE_DEVICE
245	help
246	  Allows doing any sort of manipulation to blobs after they got extracted
247	  from FIT images like stripping off headers or modifying the size of the
248	  blob, verification, authentication, decryption etc. in a platform or
249	  board specific way. In order to use this feature a platform or board-
250	  specific implementation of board_fit_image_post_process() must be
251	  provided. Also, anything done during this post-processing step would
252	  need to be comprehended in how the images were prepared before being
253	  injected into the FIT creation (i.e. the blobs would have been pre-
254	  processed before being added to the FIT image).
255
256config FIT_HW_CRYPTO
257	bool "Enable hardware crypto for FIT image checksum and rsa verify"
258	depends on DM_CRYPTO
259	help
260	  Enable hardware crypto for FIT image checksum and rsa verify.
261
262if SPL
263
264config SPL_FIT
265	bool "Support Flattened Image Tree within SPL"
266	depends on SPL
267	select SPL_OF_LIBFDT
268
269config SPL_FIT_SIGNATURE
270	bool "Enable signature verification of FIT firmware within SPL"
271	depends on SPL_DM
272	select SPL_FIT
273	select SPL_RSA
274
275config SPL_LOAD_FIT
276	bool "Enable SPL loading U-Boot as a FIT"
277	select SPL_FIT
278	help
279	  Normally with the SPL framework a legacy image is generated as part
280	  of the build. This contains U-Boot along with information as to
281	  where it should be loaded. This option instead enables generation
282	  of a FIT (Flat Image Tree) which provides more flexibility. In
283	  particular it can handle selecting from multiple device tree
284	  and passing the correct one to U-Boot.
285
286config SPL_FIT_IMAGE_POST_PROCESS
287	bool "Enable post-processing of FIT artifacts after loading by the SPL"
288	depends on SPL_LOAD_FIT
289	help
290	  Allows doing any sort of manipulation to blobs after they got extracted
291	  from the U-Boot FIT image like stripping off headers or modifying the
292	  size of the blob, verification, authentication, decryption etc. in a
293	  platform or board specific way. In order to use this feature a platform
294	  or board-specific implementation of board_fit_image_post_process() must
295	  be provided. Also, anything done during this post-processing step would
296	  need to be comprehended in how the images were prepared before being
297	  injected into the FIT creation (i.e. the blobs would have been pre-
298	  processed before being added to the FIT image).
299
300config SPL_FIT_SOURCE
301	string ".its source file for U-Boot FIT image"
302	depends on SPL_FIT
303	help
304	  Specifies a (platform specific) FIT source file to generate the
305	  U-Boot FIT image. This could specify further image to load and/or
306	  execute.
307
308config SPL_FIT_GENERATOR
309	string ".its file generator script for U-Boot FIT image"
310	depends on SPL_FIT
311	default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
312	help
313	  Specifies a (platform specific) script file to generate the FIT
314	  source file used to build the U-Boot FIT image file. This gets
315	  passed a list of supported device tree file stub names to
316	  include in the generated image.
317
318config SPL_FIT_HW_CRYPTO
319	bool "Enable SPL hardware crypto for FIT image checksum and rsa verify"
320	depends on SPL_DM_CRYPTO
321	help
322	  Enable SPL hardware crypto for FIT image checksum and rsa verify.
323
324endif # SPL
325
326endif # FIT
327
328config OF_BOARD_SETUP
329	bool "Set up board-specific details in device tree before boot"
330	depends on OF_LIBFDT
331	help
332	  This causes U-Boot to call ft_board_setup() before booting into
333	  the Operating System. This function can set up various
334	  board-specific information in the device tree for use by the OS.
335	  The device tree is then passed to the OS.
336
337config OF_SYSTEM_SETUP
338	bool "Set up system-specific details in device tree before boot"
339	depends on OF_LIBFDT
340	help
341	  This causes U-Boot to call ft_system_setup() before booting into
342	  the Operating System. This function can set up various
343	  system-specific information in the device tree for use by the OS.
344	  The device tree is then passed to the OS.
345
346config OF_STDOUT_VIA_ALIAS
347	bool "Update the device-tree stdout alias from U-Boot"
348	depends on OF_LIBFDT
349	help
350	  This uses U-Boot's serial alias from the aliases node to update
351	  the device tree passed to the OS. The "linux,stdout-path" property
352	  in the chosen node is set to point to the correct serial node.
353	  This option currently references CONFIG_CONS_INDEX, which is
354	  incorrect when used with device tree as this option does not
355	  exist / should not be used.
356
357config SYS_EXTRA_OPTIONS
358	string "Extra Options (DEPRECATED)"
359	help
360	  The old configuration infrastructure (= mkconfig + boards.cfg)
361	  provided the extra options field. If you have something like
362	  "HAS_BAR,BAZ=64", the optional options
363	    #define CONFIG_HAS
364	    #define CONFIG_BAZ	64
365	  will be defined in include/config.h.
366	  This option was prepared for the smooth migration from the old
367	  configuration to Kconfig. Since this option will be removed sometime,
368	  new boards should not use this option.
369
370config SYS_TEXT_BASE
371	depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
372		(M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
373		ARCH_ZYNQ || ARCH_KEYSTONE || ARCH_OMAP2PLUS
374	depends on !EFI_APP
375	hex "Text Base"
376	help
377	  TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
378
379	default 0x80800000 if ARCH_OMAP2PLUS
380
381
382config SYS_CLK_FREQ
383	depends on ARC || ARCH_SUNXI
384	int "CPU clock frequency"
385	help
386	  TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
387
388config ARCH_FIXUP_FDT_MEMORY
389	bool "Enable arch_fixup_memory_banks() call"
390	default y
391	help
392	  Enable FDT memory map syncup before OS boot. This feature can be
393	  used for booting OS with different memory setup where the part of
394	  the memory location should be used for different purpose.
395
396endmenu		# Boot images
397
398source "api/Kconfig"
399
400source "common/Kconfig"
401
402source "cmd/Kconfig"
403
404source "disk/Kconfig"
405
406source "dts/Kconfig"
407
408source "env/Kconfig"
409
410source "net/Kconfig"
411
412source "drivers/Kconfig"
413
414source "fs/Kconfig"
415
416source "lib/Kconfig"
417
418source "test/Kconfig"
419