xref: /openbmc/u-boot/Kconfig (revision e3f44f5c)
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 LOCALVERSION
18	string "Local version - append to U-Boot release"
19	help
20	  Append an extra string to the end of your U-Boot version.
21	  This will show up in your boot log, for example.
22	  The string you set here will be appended after the contents of
23	  any files with a filename matching localversion* in your
24	  object and source tree, in that order.  Your total string can
25	  be a maximum of 64 characters.
26
27config LOCALVERSION_AUTO
28	bool "Automatically append version information to the version string"
29	default y
30	help
31	  This will try to automatically determine if the current tree is a
32	  release tree by looking for Git tags that belong to the current
33	  top of tree revision.
34
35	  A string of the format -gxxxxxxxx will be added to the localversion
36	  if a Git-based tree is found.  The string generated by this will be
37	  appended after any matching localversion* files, and after the value
38	  set in CONFIG_LOCALVERSION.
39
40	  (The actual string used here is the first eight characters produced
41	  by running the command:
42
43	    $ git rev-parse --verify HEAD
44
45	  which is done within the script "scripts/setlocalversion".)
46
47config CC_OPTIMIZE_FOR_SIZE
48	bool "Optimize for size"
49	default y
50	help
51	  Enabling this option will pass "-Os" instead of "-O2" to gcc
52	  resulting in a smaller U-Boot image.
53
54	  This option is enabled by default for U-Boot.
55
56config DISTRO_DEFAULTS
57	bool "Select defaults suitable for booting general purpose Linux distributions"
58	default y if ARCH_SUNXI || TEGRA
59	default y if ARCH_LS2080A
60	default y if ARCH_MESON
61	default y if ARCH_ROCKCHIP
62	default n
63	select CMD_BOOTZ if ARM && !ARM64
64	select CMD_BOOTI if ARM64
65	select CMD_DHCP
66	select CMD_PXE
67	select CMD_EXT2
68	select CMD_EXT4
69	select CMD_FAT
70	select CMD_FS_GENERIC
71	select CMD_MII
72	select CMD_PING
73	select CMD_PART
74	select HUSH_PARSER
75	help
76	  Select this to enable various options and commands which are suitable
77	  for building u-boot for booting general purpose Linux distributions.
78
79config SYS_MALLOC_F
80	bool "Enable malloc() pool before relocation"
81	default y if DM
82	help
83	  Before relocation, memory is very limited on many platforms. Still,
84	  we can provide a small malloc() pool if needed. Driver model in
85	  particular needs this to operate, so that it can allocate the
86	  initial serial device and any others that are needed.
87
88config SYS_MALLOC_F_LEN
89	hex "Size of malloc() pool before relocation"
90	depends on SYS_MALLOC_F
91	default 0x400
92	help
93	  Before relocation, memory is very limited on many platforms. Still,
94	  we can provide a small malloc() pool if needed. Driver model in
95	  particular needs this to operate, so that it can allocate the
96	  initial serial device and any others that are needed.
97
98config SPL_SYS_MALLOC_F_LEN
99        hex "Size of malloc() pool in spl before relocation"
100        depends on SYS_MALLOC_F
101        default SYS_MALLOC_F_LEN
102        help
103          Before relocation, memory is very limited on many platforms. Still,
104          we can provide a small malloc() pool if needed. Driver model in
105          particular needs this to operate, so that it can allocate the
106          initial serial device and any others that are needed.
107
108menuconfig EXPERT
109	bool "Configure standard U-Boot features (expert users)"
110	default y
111	help
112	  This option allows certain base U-Boot options and settings
113	  to be disabled or tweaked. This is for specialized
114	  environments which can tolerate a "non-standard" U-Boot.
115	  Use this only if you really know what you are doing.
116
117if EXPERT
118	config SYS_MALLOC_CLEAR_ON_INIT
119	bool "Init with zeros the memory reserved for malloc (slow)"
120	default y
121	help
122	  This setting is enabled by default. The reserved malloc
123	  memory is initialized with zeros, so first malloc calls
124	  will return the pointer to the zeroed memory. But this
125	  slows the boot time.
126
127	  It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
128	  value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
129	  Then the boot time can be significantly reduced.
130	  Warning:
131	  When disabling this, please check if malloc calls, maybe
132	  should be replaced by calloc - if one expects zeroed memory.
133
134config TOOLS_DEBUG
135	bool "Enable debug information for tools"
136	help
137	  Enable generation of debug information for tools such as mkimage.
138	  This can be used for debugging purposes. With debug information
139	  it is possible to set breakpoints on particular lines, single-step
140	  debug through the source code, etc.
141
142endif # EXPERT
143
144config PHYS_64BIT
145	bool "64bit physical address support"
146	help
147	  Say Y here to support 64bit physical memory address.
148	  This can be used not only for 64bit SoCs, but also for
149	  large physical address extention on 32bit SoCs.
150
151endmenu		# General setup
152
153menu "Boot images"
154
155config FIT
156	bool "Support Flattened Image Tree"
157	select MD5
158	select SHA1
159	help
160	  This option allows you to boot the new uImage structure,
161	  Flattened Image Tree.  FIT is formally a FDT, which can include
162	  images of various types (kernel, FDT blob, ramdisk, etc.)
163	  in a single blob.  To boot this new uImage structure,
164	  pass the address of the blob to the "bootm" command.
165	  FIT is very flexible, supporting compression, multiple images,
166	  multiple configurations, verification through hashing and also
167	  verified boot (secure boot using RSA).
168
169if FIT
170
171config FIT_ENABLE_SHA256_SUPPORT
172	bool "Support SHA256 checksum of FIT image contents"
173	select SHA256
174	default y
175	help
176	  Enable this to support SHA256 checksum of FIT image contents. A
177	  SHA256 checksum is a 256-bit (32-byte) hash value used to check that
178	  the image contents have not been corrupted. SHA256 is recommended
179	  for use in secure applications since (as at 2016) there is no known
180	  feasible attack that could produce a 'collision' with differing
181	  input data. Use this for the highest security. Note that only the
182	  SHA256 variant is supported: SHA512 and others are not currently
183	  supported in U-Boot.
184
185config FIT_SIGNATURE
186	bool "Enable signature verification of FIT uImages"
187	depends on DM
188	select RSA
189	help
190	  This option enables signature verification of FIT uImages,
191	  using a hash signed and verified using RSA. If
192	  CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
193	  hashing is available using hardware, then the RSA library will use
194	  it. See doc/uImage.FIT/signature.txt for more details.
195
196	  WARNING: When relying on signed FIT images with a required signature
197	  check the legacy image format is disabled by default, so that
198	  unsigned images cannot be loaded. If a board needs the legacy image
199	  format support in this case, enable it using
200	  CONFIG_IMAGE_FORMAT_LEGACY.
201
202config FIT_VERBOSE
203	bool "Show verbose messages when FIT images fail"
204	help
205	  Generally a system will have valid FIT images so debug messages
206	  are a waste of code space. If you are debugging your images then
207	  you can enable this option to get more verbose information about
208	  failures.
209
210config FIT_BEST_MATCH
211	bool "Select the best match for the kernel device tree"
212	help
213	  When no configuration is explicitly selected, default to the
214	  one whose fdt's compatibility field best matches that of
215	  U-Boot itself. A match is considered "best" if it matches the
216	  most specific compatibility entry of U-Boot's fdt's root node.
217	  The order of entries in the configuration's fdt is ignored.
218
219config FIT_IMAGE_POST_PROCESS
220	bool "Enable post-processing of FIT artifacts after loading by U-Boot"
221	depends on TI_SECURE_DEVICE
222	help
223	  Allows doing any sort of manipulation to blobs after they got extracted
224	  from FIT images like stripping off headers or modifying the size of the
225	  blob, verification, authentication, decryption etc. in a platform or
226	  board specific way. In order to use this feature a platform or board-
227	  specific implementation of board_fit_image_post_process() must be
228	  provided. Also, anything done during this post-processing step would
229	  need to be comprehended in how the images were prepared before being
230	  injected into the FIT creation (i.e. the blobs would have been pre-
231	  processed before being added to the FIT image).
232
233if SPL
234
235config SPL_FIT
236	bool "Support Flattened Image Tree within SPL"
237	depends on SPL
238	select SPL_OF_LIBFDT
239
240config SPL_FIT_SIGNATURE
241	bool "Enable signature verification of FIT firmware within SPL"
242	depends on SPL_DM
243	select SPL_FIT
244	select SPL_RSA
245
246config SPL_LOAD_FIT
247	bool "Enable SPL loading U-Boot as a FIT"
248	select SPL_FIT
249	help
250	  Normally with the SPL framework a legacy image is generated as part
251	  of the build. This contains U-Boot along with information as to
252	  where it should be loaded. This option instead enables generation
253	  of a FIT (Flat Image Tree) which provides more flexibility. In
254	  particular it can handle selecting from multiple device tree
255	  and passing the correct one to U-Boot.
256
257config SPL_FIT_IMAGE_POST_PROCESS
258	bool "Enable post-processing of FIT artifacts after loading by the SPL"
259	depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
260	help
261	  Allows doing any sort of manipulation to blobs after they got extracted
262	  from the U-Boot FIT image like stripping off headers or modifying the
263	  size of the blob, verification, authentication, decryption etc. in a
264	  platform or board specific way. In order to use this feature a platform
265	  or board-specific implementation of board_fit_image_post_process() must
266	  be provided. Also, anything done during this post-processing step would
267	  need to be comprehended in how the images were prepared before being
268	  injected into the FIT creation (i.e. the blobs would have been pre-
269	  processed before being added to the FIT image).
270
271config SPL_FIT_SOURCE
272	string ".its source file for U-Boot FIT image"
273	depends on SPL_FIT
274	help
275	  Specifies a (platform specific) FIT source file to generate the
276	  U-Boot FIT image. This could specify further image to load and/or
277	  execute.
278
279config SPL_FIT_GENERATOR
280	string ".its file generator script for U-Boot FIT image"
281	depends on SPL_FIT
282	default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
283	help
284	  Specifies a (platform specific) script file to generate the FIT
285	  source file used to build the U-Boot FIT image file. This gets
286	  passed a list of supported device tree file stub names to
287	  include in the generated image.
288
289endif # SPL
290
291endif # FIT
292
293config OF_BOARD_SETUP
294	bool "Set up board-specific details in device tree before boot"
295	depends on OF_LIBFDT
296	help
297	  This causes U-Boot to call ft_board_setup() before booting into
298	  the Operating System. This function can set up various
299	  board-specific information in the device tree for use by the OS.
300	  The device tree is then passed to the OS.
301
302config OF_SYSTEM_SETUP
303	bool "Set up system-specific details in device tree before boot"
304	depends on OF_LIBFDT
305	help
306	  This causes U-Boot to call ft_system_setup() before booting into
307	  the Operating System. This function can set up various
308	  system-specific information in the device tree for use by the OS.
309	  The device tree is then passed to the OS.
310
311config OF_STDOUT_VIA_ALIAS
312	bool "Update the device-tree stdout alias from U-Boot"
313	depends on OF_LIBFDT
314	help
315	  This uses U-Boot's serial alias from the aliases node to update
316	  the device tree passed to the OS. The "linux,stdout-path" property
317	  in the chosen node is set to point to the correct serial node.
318	  This option currently references CONFIG_CONS_INDEX, which is
319	  incorrect when used with device tree as this option does not
320	  exist / should not be used.
321
322config SYS_EXTRA_OPTIONS
323	string "Extra Options (DEPRECATED)"
324	help
325	  The old configuration infrastructure (= mkconfig + boards.cfg)
326	  provided the extra options field. If you have something like
327	  "HAS_BAR,BAZ=64", the optional options
328	    #define CONFIG_HAS
329	    #define CONFIG_BAZ	64
330	  will be defined in include/config.h.
331	  This option was prepared for the smooth migration from the old
332	  configuration to Kconfig. Since this option will be removed sometime,
333	  new boards should not use this option.
334
335config SYS_TEXT_BASE
336	depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
337		(M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
338		ARCH_ZYNQ || ARCH_KEYSTONE
339	depends on !EFI_APP
340	hex "Text Base"
341	help
342	  TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
343
344
345config SYS_CLK_FREQ
346	depends on ARC || ARCH_SUNXI
347	int "CPU clock frequency"
348	help
349	  TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
350
351config ARCH_FIXUP_FDT_MEMORY
352	bool "Enable arch_fixup_memory_banks() call"
353	default y
354	help
355	  Enable FDT memory map syncup before OS boot. This feature can be
356	  used for booting OS with different memory setup where the part of
357	  the memory location should be used for different purpose.
358
359endmenu		# Boot images
360
361source "api/Kconfig"
362
363source "common/Kconfig"
364
365source "cmd/Kconfig"
366
367source "disk/Kconfig"
368
369source "dts/Kconfig"
370
371source "net/Kconfig"
372
373source "drivers/Kconfig"
374
375source "fs/Kconfig"
376
377source "lib/Kconfig"
378
379source "test/Kconfig"
380
381source "scripts/Kconfig"
382