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