xref: /openbmc/u-boot/Kconfig (revision fb1b7712)
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 CC_COVERAGE
63	bool "Enable code coverage analysis"
64	depends on SANDBOX
65	help
66	  Enabling this option will pass "--coverage" to gcc to compile
67	  and link code instrumented for coverage analysis.
68
69config DISTRO_DEFAULTS
70	bool "Select defaults suitable for booting general purpose Linux distributions"
71	select AUTO_COMPLETE
72	select CMDLINE_EDITING
73	select CMD_BOOTI if ARM64
74	select CMD_BOOTZ if ARM && !ARM64
75	select CMD_DHCP if CMD_NET
76	select CMD_ENV_EXISTS
77	select CMD_EXT2
78	select CMD_EXT4
79	select CMD_FAT
80	select CMD_FS_GENERIC
81	select CMD_PART if PARTITIONS
82	select CMD_PING if CMD_NET
83	select CMD_PXE if NET
84	select ENV_VARS_UBOOT_CONFIG
85	select HUSH_PARSER
86	select SUPPORT_RAW_INITRD
87	select SYS_LONGHELP
88	imply CMD_MII if NET
89	imply USB_STORAGE
90	imply USE_BOOTCOMMAND
91	help
92	  Select this to enable various options and commands which are suitable
93	  for building u-boot for booting general purpose Linux distributions.
94
95config ENV_VARS_UBOOT_CONFIG
96	bool "Add arch, board, vendor and soc variables to default environment"
97	help
98	  Define this in order to add variables describing the
99	  U-Boot build configuration to the default environment.
100	  These will be named arch, cpu, board, vendor, and soc.
101	  Enabling this option will cause the following to be defined:
102	  - CONFIG_SYS_ARCH
103	  - CONFIG_SYS_CPU
104	  - CONFIG_SYS_BOARD
105	  - CONFIG_SYS_VENDOR
106	  - CONFIG_SYS_SOC
107
108config NR_DRAM_BANKS
109	int "Number of DRAM banks"
110	default 4
111	help
112	  This defines the number of DRAM banks.
113
114config SYS_BOOT_GET_CMDLINE
115	bool "Enable kernel command line setup"
116	help
117	  Enables allocating and saving kernel cmdline in space between
118	  "bootm_low" and "bootm_low" + BOOTMAPSZ.
119
120config SYS_BOOT_GET_KBD
121	bool "Enable kernel board information setup"
122	help
123	  Enables allocating and saving a kernel copy of the bd_info in
124	  space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
125
126config SYS_MALLOC_F
127	bool "Enable malloc() pool before relocation"
128	default y if DM
129	help
130	  Before relocation, memory is very limited on many platforms. Still,
131	  we can provide a small malloc() pool if needed. Driver model in
132	  particular needs this to operate, so that it can allocate the
133	  initial serial device and any others that are needed.
134
135config SYS_MALLOC_F_LEN
136	hex "Size of malloc() pool before relocation"
137	depends on SYS_MALLOC_F
138	default 0x1000 if AM33XX
139	default 0x400
140	help
141	  Before relocation, memory is very limited on many platforms. Still,
142	  we can provide a small malloc() pool if needed. Driver model in
143	  particular needs this to operate, so that it can allocate the
144	  initial serial device and any others that are needed.
145
146config SYS_MALLOC_LEN
147	hex "Define memory for Dynamic allocation"
148	depends on ARCH_ZYNQ || ARCH_VERSAL
149	help
150	  This defines memory to be allocated for Dynamic allocation
151	  TODO: Use for other architectures
152
153config SPL_SYS_MALLOC_F_LEN
154	hex "Size of malloc() pool in SPL before relocation"
155	depends on SYS_MALLOC_F
156	default SYS_MALLOC_F_LEN
157	help
158	  Before relocation, memory is very limited on many platforms. Still,
159	  we can provide a small malloc() pool if needed. Driver model in
160	  particular needs this to operate, so that it can allocate the
161	  initial serial device and any others that are needed.
162
163config TPL_SYS_MALLOC_F_LEN
164	hex "Size of malloc() pool in TPL before relocation"
165	depends on SYS_MALLOC_F
166	default SYS_MALLOC_F_LEN
167	help
168	  Before relocation, memory is very limited on many platforms. Still,
169	  we can provide a small malloc() pool if needed. Driver model in
170	  particular needs this to operate, so that it can allocate the
171	  initial serial device and any others that are needed.
172
173menuconfig EXPERT
174	bool "Configure standard U-Boot features (expert users)"
175	default y
176	help
177	  This option allows certain base U-Boot options and settings
178	  to be disabled or tweaked. This is for specialized
179	  environments which can tolerate a "non-standard" U-Boot.
180	  Use this only if you really know what you are doing.
181
182if EXPERT
183	config SYS_MALLOC_CLEAR_ON_INIT
184	bool "Init with zeros the memory reserved for malloc (slow)"
185	default y
186	help
187	  This setting is enabled by default. The reserved malloc
188	  memory is initialized with zeros, so first malloc calls
189	  will return the pointer to the zeroed memory. But this
190	  slows the boot time.
191
192	  It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
193	  value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
194	  Then the boot time can be significantly reduced.
195	  Warning:
196	  When disabling this, please check if malloc calls, maybe
197	  should be replaced by calloc - if one expects zeroed memory.
198
199config TOOLS_DEBUG
200	bool "Enable debug information for tools"
201	help
202	  Enable generation of debug information for tools such as mkimage.
203	  This can be used for debugging purposes. With debug information
204	  it is possible to set breakpoints on particular lines, single-step
205	  debug through the source code, etc.
206
207endif # EXPERT
208
209config PHYS_64BIT
210	bool "64bit physical address support"
211	help
212	  Say Y here to support 64bit physical memory address.
213	  This can be used not only for 64bit SoCs, but also for
214	  large physical address extention on 32bit SoCs.
215
216config BUILD_ROM
217	bool "Build U-Boot as BIOS replacement"
218	depends on X86
219	help
220	  This option allows to build a ROM version of U-Boot.
221	  The build process generally requires several binary blobs
222	  which are not shipped in the U-Boot source tree.
223	  Please, see doc/README.x86 for details.
224
225endmenu		# General setup
226
227menu "Boot images"
228
229config ANDROID_BOOT_IMAGE
230	bool "Enable support for Android Boot Images"
231	default y if FASTBOOT
232	help
233	  This enables support for booting images which use the Android
234	  image format header.
235
236config FIT
237	bool "Support Flattened Image Tree"
238	select MD5
239	select SHA1
240	help
241	  This option allows you to boot the new uImage structure,
242	  Flattened Image Tree.  FIT is formally a FDT, which can include
243	  images of various types (kernel, FDT blob, ramdisk, etc.)
244	  in a single blob.  To boot this new uImage structure,
245	  pass the address of the blob to the "bootm" command.
246	  FIT is very flexible, supporting compression, multiple images,
247	  multiple configurations, verification through hashing and also
248	  verified boot (secure boot using RSA).
249
250if FIT
251
252config FIT_ENABLE_SHA256_SUPPORT
253	bool "Support SHA256 checksum of FIT image contents"
254	default y
255	select SHA256
256	help
257	  Enable this to support SHA256 checksum of FIT image contents. A
258	  SHA256 checksum is a 256-bit (32-byte) hash value used to check that
259	  the image contents have not been corrupted. SHA256 is recommended
260	  for use in secure applications since (as at 2016) there is no known
261	  feasible attack that could produce a 'collision' with differing
262	  input data. Use this for the highest security. Note that only the
263	  SHA256 variant is supported: SHA512 and others are not currently
264	  supported in U-Boot.
265
266config FIT_SIGNATURE
267	bool "Enable signature verification of FIT uImages"
268	depends on DM
269	select HASH
270	select RSA
271	help
272	  This option enables signature verification of FIT uImages,
273	  using a hash signed and verified using RSA. If
274	  CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
275	  hashing is available using hardware, then the RSA library will use
276	  it. See doc/uImage.FIT/signature.txt for more details.
277
278	  WARNING: When relying on signed FIT images with a required signature
279	  check the legacy image format is disabled by default, so that
280	  unsigned images cannot be loaded. If a board needs the legacy image
281	  format support in this case, enable it using
282	  CONFIG_IMAGE_FORMAT_LEGACY.
283
284config FIT_SIGNATURE_MAX_SIZE
285	hex "Max size of signed FIT structures"
286	depends on FIT_SIGNATURE
287	default 0x10000000
288	help
289	  This option sets a max size in bytes for verified FIT uImages.
290	  A sane value of 256MB protects corrupted DTB structures from overlapping
291	  device memory. Assure this size does not extend past expected storage
292	  space.
293
294config FIT_ENABLE_RSASSA_PSS_SUPPORT
295	bool "Support rsassa-pss signature scheme of FIT image contents"
296	depends on FIT_SIGNATURE
297	default n
298	help
299	  Enable this to support the pss padding algorithm as described
300	  in the rfc8017 (https://tools.ietf.org/html/rfc8017).
301
302config FIT_VERBOSE
303	bool "Show verbose messages when FIT images fail"
304	help
305	  Generally a system will have valid FIT images so debug messages
306	  are a waste of code space. If you are debugging your images then
307	  you can enable this option to get more verbose information about
308	  failures.
309
310config FIT_BEST_MATCH
311	bool "Select the best match for the kernel device tree"
312	help
313	  When no configuration is explicitly selected, default to the
314	  one whose fdt's compatibility field best matches that of
315	  U-Boot itself. A match is considered "best" if it matches the
316	  most specific compatibility entry of U-Boot's fdt's root node.
317	  The order of entries in the configuration's fdt is ignored.
318
319config FIT_IMAGE_POST_PROCESS
320	bool "Enable post-processing of FIT artifacts after loading by U-Boot"
321	depends on TI_SECURE_DEVICE
322	help
323	  Allows doing any sort of manipulation to blobs after they got extracted
324	  from FIT images like stripping off headers or modifying the size of the
325	  blob, verification, authentication, decryption etc. in a platform or
326	  board specific way. In order to use this feature a platform or board-
327	  specific implementation of board_fit_image_post_process() must be
328	  provided. Also, anything done during this post-processing step would
329	  need to be comprehended in how the images were prepared before being
330	  injected into the FIT creation (i.e. the blobs would have been pre-
331	  processed before being added to the FIT image).
332
333if SPL
334
335config SPL_FIT
336	bool "Support Flattened Image Tree within SPL"
337	depends on SPL
338	select SPL_OF_LIBFDT
339
340config SPL_FIT_PRINT
341	bool "Support FIT printing within SPL"
342	depends on SPL_FIT
343	help
344	  Support printing the content of the fitImage in a verbose manner in SPL.
345
346config SPL_FIT_SIGNATURE
347	bool "Enable signature verification of FIT firmware within SPL"
348	depends on SPL_DM
349	select SPL_FIT
350	select SPL_RSA
351
352config SPL_LOAD_FIT
353	bool "Enable SPL loading U-Boot as a FIT"
354	select SPL_FIT
355	help
356	  Normally with the SPL framework a legacy image is generated as part
357	  of the build. This contains U-Boot along with information as to
358	  where it should be loaded. This option instead enables generation
359	  of a FIT (Flat Image Tree) which provides more flexibility. In
360	  particular it can handle selecting from multiple device tree
361	  and passing the correct one to U-Boot.
362
363config SPL_LOAD_FIT_FULL
364	bool "Enable SPL loading U-Boot as a FIT"
365	select SPL_FIT
366	help
367	  Normally with the SPL framework a legacy image is generated as part
368	  of the build. This contains U-Boot along with information as to
369	  where it should be loaded. This option instead enables generation
370	  of a FIT (Flat Image Tree) which provides more flexibility. In
371	  particular it can handle selecting from multiple device tree
372	  and passing the correct one to U-Boot.
373
374config SPL_FIT_IMAGE_POST_PROCESS
375	bool "Enable post-processing of FIT artifacts after loading by the SPL"
376	depends on SPL_LOAD_FIT
377	help
378	  Allows doing any sort of manipulation to blobs after they got extracted
379	  from the U-Boot FIT image like stripping off headers or modifying the
380	  size of the blob, verification, authentication, decryption etc. in a
381	  platform or board specific way. In order to use this feature a platform
382	  or board-specific implementation of board_fit_image_post_process() must
383	  be provided. Also, anything done during this post-processing step would
384	  need to be comprehended in how the images were prepared before being
385	  injected into the FIT creation (i.e. the blobs would have been pre-
386	  processed before being added to the FIT image).
387
388config SPL_FIT_SOURCE
389	string ".its source file for U-Boot FIT image"
390	depends on SPL_FIT
391	help
392	  Specifies a (platform specific) FIT source file to generate the
393	  U-Boot FIT image. This could specify further image to load and/or
394	  execute.
395
396config SPL_FIT_GENERATOR
397	string ".its file generator script for U-Boot FIT image"
398	depends on SPL_FIT
399	default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
400	help
401	  Specifies a (platform specific) script file to generate the FIT
402	  source file used to build the U-Boot FIT image file. This gets
403	  passed a list of supported device tree file stub names to
404	  include in the generated image.
405
406endif # SPL
407
408endif # FIT
409
410config IMAGE_FORMAT_LEGACY
411	bool "Enable support for the legacy image format"
412	default y if !FIT_SIGNATURE
413	help
414	  This option enables the legacy image format. It is enabled by
415	  default for backward compatibility, unless FIT_SIGNATURE is
416	  set where it is disabled so that unsigned images cannot be
417	  loaded. If a board needs the legacy image format support in this
418	  case, enable it here.
419
420config OF_BOARD_SETUP
421	bool "Set up board-specific details in device tree before boot"
422	depends on OF_LIBFDT
423	help
424	  This causes U-Boot to call ft_board_setup() before booting into
425	  the Operating System. This function can set up various
426	  board-specific information in the device tree for use by the OS.
427	  The device tree is then passed to the OS.
428
429config OF_SYSTEM_SETUP
430	bool "Set up system-specific details in device tree before boot"
431	depends on OF_LIBFDT
432	help
433	  This causes U-Boot to call ft_system_setup() before booting into
434	  the Operating System. This function can set up various
435	  system-specific information in the device tree for use by the OS.
436	  The device tree is then passed to the OS.
437
438config OF_STDOUT_VIA_ALIAS
439	bool "Update the device-tree stdout alias from U-Boot"
440	depends on OF_LIBFDT
441	help
442	  This uses U-Boot's serial alias from the aliases node to update
443	  the device tree passed to the OS. The "linux,stdout-path" property
444	  in the chosen node is set to point to the correct serial node.
445	  This option currently references CONFIG_CONS_INDEX, which is
446	  incorrect when used with device tree as this option does not
447	  exist / should not be used.
448
449config SYS_EXTRA_OPTIONS
450	string "Extra Options (DEPRECATED)"
451	help
452	  The old configuration infrastructure (= mkconfig + boards.cfg)
453	  provided the extra options field. If you have something like
454	  "HAS_BAR,BAZ=64", the optional options
455	    #define CONFIG_HAS
456	    #define CONFIG_BAZ	64
457	  will be defined in include/config.h.
458	  This option was prepared for the smooth migration from the old
459	  configuration to Kconfig. Since this option will be removed sometime,
460	  new boards should not use this option.
461
462config SYS_TEXT_BASE
463	depends on !NIOS2 && !XTENSA
464	depends on !EFI_APP
465	default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
466	default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
467	default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
468	default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
469	hex "Text Base"
470	help
471	  The address in memory that U-Boot will be running from, initially.
472
473
474
475config SYS_CLK_FREQ
476	depends on ARC || ARCH_SUNXI
477	int "CPU clock frequency"
478	help
479	  TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
480
481config ARCH_FIXUP_FDT_MEMORY
482	bool "Enable arch_fixup_memory_banks() call"
483	default y
484	help
485	  Enable FDT memory map syncup before OS boot. This feature can be
486	  used for booting OS with different memory setup where the part of
487	  the memory location should be used for different purpose.
488
489endmenu		# Boot images
490
491source "api/Kconfig"
492
493source "common/Kconfig"
494
495source "cmd/Kconfig"
496
497source "disk/Kconfig"
498
499source "dts/Kconfig"
500
501source "env/Kconfig"
502
503source "net/Kconfig"
504
505source "drivers/Kconfig"
506
507source "fs/Kconfig"
508
509source "lib/Kconfig"
510
511source "test/Kconfig"
512