xref: /optee_os/mk/config.mk (revision c2e4eb43b7b7211345cd38ceceac97773bd78d2c)
1# Default configuration values for OP-TEE core (all platforms).
2#
3# Platform-specific overrides are in core/arch/arm32/plat-*/conf.mk.
4# Some subsystem-specific defaults are not here but rather in */sub.mk.
5#
6# Configuration values may be assigned from multiple sources.
7# From higher to lower priority:
8#
9#   1. Make arguments ('make CFG_FOO=bar...')
10#   2. The file specified by $(CFG_OPTEE_CONFIG) (if defined)
11#   3. The environment ('CFG_FOO=bar make...')
12#   4. The platform-specific configuration file: core/arch/arm32/plat-*/conf.mk
13#   5. This file
14#   6. Subsystem-specific makefiles (*/sub.mk)
15#
16# Actual values used during the build are output to $(out-dir)/conf.mk
17# (CFG_* variables only).
18
19# Cross-compiler prefix and suffix
20CROSS_COMPILE ?= arm-linux-gnueabihf-
21CROSS_COMPILE32 ?= $(CROSS_COMPILE)
22CROSS_COMPILE64 ?= aarch64-linux-gnu-
23COMPILER ?= gcc
24
25# For convenience
26ifdef CFLAGS
27CFLAGS32 ?= $(CFLAGS)
28CFLAGS64 ?= $(CFLAGS)
29endif
30
31# Compiler warning level.
32# Supported values: undefined, 1, 2 and 3. 3 gives more warnings.
33WARNS ?= 3
34
35# Path to the Python interpreter used by the build system.
36# This variable is set to the default python3 interpreter in the user's
37# path. But build environments that require more explicit control can
38# set the path to a specific interpreter through this variable.
39PYTHON3 ?= python3
40
41# Define DEBUG=1 to compile without optimization (forces -O0)
42# DEBUG=1
43
44# If y, enable debug features of the TEE core (assertions and lock checks
45# are enabled, panic and assert messages are more verbose, data and prefetch
46# aborts show a stack dump). When disabled, the NDEBUG directive is defined
47# so assertions are disabled.
48CFG_TEE_CORE_DEBUG ?= y
49
50# Log levels for the TEE core. Defines which core messages are displayed
51# on the secure console. Disabling core log (level set to 0) also disables
52# logs from the TAs.
53# 0: none
54# 1: error
55# 2: error + warning
56# 3: error + warning + debug
57# 4: error + warning + debug + flow
58CFG_TEE_CORE_LOG_LEVEL ?= 1
59
60# TA log level
61# If user-mode library libutils.a is built with CFG_TEE_TA_LOG_LEVEL=0,
62# TA tracing is disabled regardless of the value of CFG_TEE_TA_LOG_LEVEL
63# when the TA is built.
64CFG_TEE_TA_LOG_LEVEL ?= 1
65
66# TA enablement
67# When defined to "y", TA traces are output according to
68# CFG_TEE_TA_LOG_LEVEL. Otherwise, they are not output at all
69CFG_TEE_CORE_TA_TRACE ?= y
70
71# If y, enable the memory leak detection feature in the bget memory allocator.
72# When this feature is enabled, calling mdbg_check(1) will print a list of all
73# the currently allocated buffers and the location of the allocation (file and
74# line number).
75# Note: make sure the log level is high enough for the messages to show up on
76# the secure console! For instance:
77# - To debug user-mode (TA) allocations: build OP-TEE *and* the TA with:
78#   $ make CFG_TEE_TA_MALLOC_DEBUG=y CFG_TEE_TA_LOG_LEVEL=3
79# - To debug TEE core allocations: build OP-TEE with:
80#   $ make CFG_TEE_CORE_MALLOC_DEBUG=y CFG_TEE_CORE_LOG_LEVEL=3
81CFG_TEE_CORE_MALLOC_DEBUG ?= n
82CFG_TEE_TA_MALLOC_DEBUG ?= n
83# Prints an error message and dumps the stack on failed memory allocations
84# using malloc() and friends.
85CFG_CORE_DUMP_OOM ?= $(CFG_TEE_CORE_MALLOC_DEBUG)
86
87# Mask to select which messages are prefixed with long debugging information
88# (severity, core ID, thread ID, component name, function name, line number)
89# based on the message level. If BIT(level) is set, the long prefix is shown.
90# Otherwise a short prefix is used (severity and component name only).
91# Levels: 0=none 1=error 2=info 3=debug 4=flow
92CFG_MSG_LONG_PREFIX_MASK ?= 0x1a
93
94# PRNG configuration
95# If CFG_WITH_SOFTWARE_PRNG is enabled, crypto provider provided
96# software PRNG implementation is used.
97# Otherwise, you need to implement hw_get_random_byte() for your platform
98CFG_WITH_SOFTWARE_PRNG ?= y
99
100# Number of threads
101CFG_NUM_THREADS ?= 2
102
103# API implementation version
104CFG_TEE_API_VERSION ?= GPD-1.1-dev
105
106# Implementation description (implementation-dependent)
107CFG_TEE_IMPL_DESCR ?= OPTEE
108
109# Should OPTEE_SMC_CALL_GET_OS_REVISION return a build identifier to Normal
110# World?
111CFG_OS_REV_REPORTS_GIT_SHA1 ?= y
112
113# Trusted OS implementation version
114TEE_IMPL_VERSION ?= $(shell git describe --always --dirty=-dev 2>/dev/null || echo Unknown)
115ifeq ($(CFG_OS_REV_REPORTS_GIT_SHA1),y)
116TEE_IMPL_GIT_SHA1 := 0x$(shell git rev-parse --short=8 HEAD 2>/dev/null || echo 0)
117else
118TEE_IMPL_GIT_SHA1 := 0x0
119endif
120# The following values are not extracted from the "git describe" output because
121# we might be outside of a Git environment, or the tree may have been cloned
122# with limited depth not including any tag, so there is really no guarantee
123# that TEE_IMPL_VERSION contains the major and minor revision numbers.
124CFG_OPTEE_REVISION_MAJOR ?= 3
125CFG_OPTEE_REVISION_MINOR ?= 14
126
127# Trusted OS implementation manufacturer name
128CFG_TEE_MANUFACTURER ?= LINARO
129
130# Trusted firmware version
131CFG_TEE_FW_IMPL_VERSION ?= FW_IMPL_UNDEF
132
133# Trusted OS implementation manufacturer name
134CFG_TEE_FW_MANUFACTURER ?= FW_MAN_UNDEF
135
136# Rich Execution Environment (REE) file system support: normal world OS
137# provides the actual storage.
138# This is the default FS when enabled (i.e., the one used when
139# TEE_STORAGE_PRIVATE is passed to the trusted storage API)
140CFG_REE_FS ?= y
141
142# RPMB file system support
143CFG_RPMB_FS ?= n
144
145# Device identifier used when CFG_RPMB_FS = y.
146# The exact meaning of this value is platform-dependent. On Linux, the
147# tee-supplicant process will open /dev/mmcblk<id>rpmb
148CFG_RPMB_FS_DEV_ID ?= 0
149
150# This config variable determines the number of entries read in from RPMB at
151# once whenever a function traverses the RPMB FS. Increasing the default value
152# has the following consequences:
153# - More memory required on heap. A single FAT entry currently has a size of
154#   256 bytes.
155# - Potentially significant speed-ups for RPMB I/O. Depending on how many
156#   entries a function needs to traverse, the number of time-consuming RPMB
157#   read-in operations can be reduced.
158# Chosing a proper value is both platform- (available memory) and use-case-
159# dependent (potential number of FAT fs entries), so overwrite in platform
160# config files
161CFG_RPMB_FS_RD_ENTRIES ?= 8
162
163# Enables caching of FAT FS entries when set to a value greater than zero.
164# When enabled, the cache stores the first 'CFG_RPMB_FS_CACHE_ENTRIES' FAT FS
165# entries. The cache is populated when FAT FS entries are initially read in.
166# When traversing the FAT FS entries, we read from the cache instead of reading
167# in the entries from RPMB storage. Consequently, when a FAT FS entry is
168# written, the cache is updated. In scenarios where an estimate of the number
169# of FAT FS entries can be made, the cache may be specifically tailored to
170# store all entries. The caching can improve RPMB I/O at the cost
171# of additional memory.
172# Without caching, we temporarily require
173# CFG_RPMB_FS_RD_ENTRIES*sizeof(struct rpmb_fat_entry) bytes of heap memory
174# while traversing the FAT FS (e.g. in read_fat).
175# For example 8*256 bytes = 2kB while in read_fat.
176# With caching, we constantly require up to
177# CFG_RPMB_FS_CACHE_ENTRIES*sizeof(struct rpmb_fat_entry) bytes of heap memory
178# depending on how many elements are in the cache, and additional temporary
179# CFG_RPMB_FS_RD_ENTRIES*sizeof(struct rpmb_fat_entry) bytes of heap memory
180# in case the cache is too small to hold all elements when traversing.
181CFG_RPMB_FS_CACHE_ENTRIES ?= 0
182
183# Print RPMB data frames sent to and received from the RPMB device
184CFG_RPMB_FS_DEBUG_DATA ?= n
185
186# Clear RPMB content at cold boot
187CFG_RPMB_RESET_FAT ?= n
188
189# Use a hard coded RPMB key instead of deriving it from the platform HUK
190CFG_RPMB_TESTKEY ?= n
191
192# Enables RPMB key programming by the TEE, in case the RPMB partition has not
193# been configured yet.
194# !!! Security warning !!!
195# Do *NOT* enable this in product builds, as doing so would allow the TEE to
196# leak the RPMB key.
197# This option is useful in the following situations:
198# - Testing
199# - RPMB key provisioning in a controlled environment (factory setup)
200CFG_RPMB_WRITE_KEY ?= n
201
202# Signing key for OP-TEE TA's
203# When performing external HSM signing for TA's TA_SIGN_KEY can be set to dummy
204# key and then set TA_PUBLIC_KEY to match public key from the HSM.
205# TA_PUBLIC_KEY's public key will be embedded into OP-TEE OS.
206TA_SIGN_KEY ?= keys/default_ta.pem
207TA_PUBLIC_KEY ?= $(TA_SIGN_KEY)
208
209# Include lib/libutils/isoc in the build? Most platforms need this, but some
210# may not because they obtain the isoc functions from elsewhere
211CFG_LIBUTILS_WITH_ISOC ?= y
212
213# Enables floating point support for user TAs
214# ARM32: EABI defines both a soft-float ABI and a hard-float ABI,
215#	 hard-float is basically a super set of soft-float. Hard-float
216#	 requires all the support routines provided for soft-float, but the
217#	 compiler may choose to optimize to not use some of them and use
218#	 the floating-point registers instead.
219# ARM64: EABI doesn't define a soft-float ABI, everything is hard-float (or
220#	 nothing with ` -mgeneral-regs-only`)
221# With CFG_TA_FLOAT_SUPPORT enabled TA code is free use floating point types
222CFG_TA_FLOAT_SUPPORT ?= y
223
224# Stack unwinding: print a stack dump to the console on core or TA abort, or
225# when a TA panics.
226# If CFG_UNWIND is enabled, both the kernel and user mode call stacks can be
227# unwound (not paged TAs, however).
228# Note that 32-bit ARM code needs unwind tables for this to work, so enabling
229# this option will increase the size of the 32-bit TEE binary by a few KB.
230# Similarly, TAs have to be compiled with -funwind-tables (default when the
231# option is set) otherwise they can't be unwound.
232# Warning: since the unwind sequence for user-mode (TA) code is implemented in
233# the privileged layer of OP-TEE, enabling this feature will weaken the
234# user/kernel isolation. Therefore it should be disabled in release builds.
235ifeq ($(CFG_TEE_CORE_DEBUG),y)
236CFG_UNWIND ?= y
237endif
238
239# Enable support for dynamically loaded user TAs
240CFG_WITH_USER_TA ?= y
241
242# Choosing the architecture(s) of user-mode libraries (used by TAs)
243#
244# Platforms may define a list of supported architectures for user-mode code
245# by setting $(supported-ta-targets). Valid values are "ta_arm32", "ta_arm64",
246# "ta_arm32 ta_arm64" and "ta_arm64 ta_arm32".
247# $(supported-ta-targets) defaults to "ta_arm32" when the TEE core is 32-bits,
248# and "ta_arm32 ta_arm64" when it is 64-bits (that is, when CFG_ARM64_core=y).
249# The first entry in $(supported-ta-targets) has a special role, see
250# CFG_USER_TA_TARGET_<ta-name> below.
251#
252# CFG_USER_TA_TARGETS may be defined to restrict $(supported-ta-targets) or
253# change the order of the values.
254#
255# The list of TA architectures is ultimately stored in $(ta-targets).
256
257# CFG_USER_TA_TARGET_<ta-name> (for example, CFG_USER_TA_TARGET_avb), if
258# defined, selects the unique TA architecture mode for building the in-tree TA
259# <ta-name>. Can be either ta_arm32 or ta_arm64.
260# By default, in-tree TAs are built using the first architecture specified in
261# $(ta-targets).
262
263# Address Space Layout Randomization for user-mode Trusted Applications
264#
265# When this flag is enabled, the ELF loader will introduce a random offset
266# when mapping the application in user space. ASLR makes the exploitation of
267# memory corruption vulnerabilities more difficult.
268CFG_TA_ASLR ?= y
269
270# How much ASLR may shift the base address (in pages). The base address is
271# randomly shifted by an integer number of pages comprised between these two
272# values. Bigger ranges are more secure because they make the addresses harder
273# to guess at the expense of using more memory for the page tables.
274CFG_TA_ASLR_MIN_OFFSET_PAGES ?= 0
275CFG_TA_ASLR_MAX_OFFSET_PAGES ?= 128
276
277# Address Space Layout Randomization for TEE Core
278#
279# When this flag is enabled, the early init code will introduce a random
280# offset when mapping TEE Core. ASLR makes the exploitation of memory
281# corruption vulnerabilities more difficult.
282CFG_CORE_ASLR ?= y
283
284# Load user TAs from the REE filesystem via tee-supplicant
285CFG_REE_FS_TA ?= y
286
287# Pre-authentication of TA binaries loaded from the REE filesystem
288#
289# - If CFG_REE_FS_TA_BUFFERED=y: load TA binary into a temporary buffer in the
290#   "Secure DDR" pool, check the signature, then process the file only if it is
291#   valid.
292# - If disabled: hash the binaries as they are being processed and verify the
293#   signature as a last step.
294CFG_REE_FS_TA_BUFFERED ?= n
295$(eval $(call cfg-depends-all,CFG_REE_FS_TA_BUFFERED,CFG_REE_FS_TA))
296
297# When CFG_REE_FS=y and CFG_RPMB_FS=y:
298# Allow secure storage in the REE FS to be entirely deleted without causing
299# anti-rollback errors. That is, rm /data/tee/dirf.db or rm -rf /data/tee (or
300# whatever path is configured in tee-supplicant as CFG_TEE_FS_PARENT_PATH)
301# can be used to reset the secure storage to a clean, empty state.
302# Typically used for testing only since it weakens storage security.
303CFG_REE_FS_ALLOW_RESET ?= n
304
305# Support for loading user TAs from a special section in the TEE binary.
306# Such TAs are available even before tee-supplicant is available (hence their
307# name), but note that many services exported to TAs may need tee-supplicant,
308# so early use is limited to a subset of the TEE Internal Core API (crypto...)
309# To use this feature, set EARLY_TA_PATHS to the paths to one or more TA ELF
310# file(s). For example:
311#   $ make ... \
312#     EARLY_TA_PATHS="path/to/8aaaf200-2450-11e4-abe2-0002a5d5c51b.stripped.elf \
313#                     path/to/cb3e5ba0-adf1-11e0-998b-0002a5d5c51b.stripped.elf"
314# Typical build steps:
315#   $ make ta_dev_kit CFG_EARLY_TA=y # Create the dev kit (user mode libraries,
316#                                    # headers, makefiles), ready to build TAs.
317#                                    # CFG_EARLY_TA=y is optional, it prevents
318#                                    # later library recompilations.
319#   <build some TAs>
320#   $ make EARLY_TA_PATHS=<paths>    # Build OP-TEE and embbed the TA(s)
321#
322# Another option is CFG_IN_TREE_EARLY_TAS which is used to point at
323# in-tree TAs. CFG_IN_TREE_EARLY_TAS is formatted as:
324# <name-of-ta>/<uuid>
325# for instance avb/023f8f1a-292a-432b-8fc4-de8471358067
326ifneq ($(EARLY_TA_PATHS)$(CFG_IN_TREE_EARLY_TAS),)
327$(call force,CFG_EARLY_TA,y)
328else
329CFG_EARLY_TA ?= n
330endif
331
332ifeq ($(CFG_EARLY_TA),y)
333$(call force,CFG_EMBEDDED_TS,y)
334endif
335
336ifneq ($(SP_PATHS),)
337$(call force,CFG_EMBEDDED_TS,y)
338else
339CFG_SECURE_PARTITION ?= n
340endif
341
342ifeq ($(CFG_SECURE_PARTITION),y)
343$(call force,CFG_EMBEDDED_TS,y)
344endif
345
346ifeq ($(CFG_EMBEDDED_TS),y)
347$(call force,CFG_ZLIB,y)
348endif
349
350# By default the early TAs are compressed in the TEE binary, it is possible to
351# not compress them with CFG_EARLY_TA_COMPRESS=n
352CFG_EARLY_TA_COMPRESS ?= y
353
354# Enable paging, requires SRAM, can't be enabled by default
355CFG_WITH_PAGER ?= n
356
357# Use the pager for user TAs
358CFG_PAGED_USER_TA ?= $(CFG_WITH_PAGER)
359
360# If paging of user TAs, that is, R/W paging default to enable paging of
361# TAG and IV in order to reduce heap usage.
362CFG_CORE_PAGE_TAG_AND_IV ?= $(CFG_PAGED_USER_TA)
363
364# Runtime lock dependency checker: ensures that a proper locking hierarchy is
365# used in the TEE core when acquiring and releasing mutexes. Any violation will
366# cause a panic as soon as the invalid locking condition is detected. If
367# CFG_UNWIND and CFG_LOCKDEP_RECORD_STACK are both enabled, the algorithm
368# records the call stacks when locks are taken, and prints them when a
369# potential deadlock is found.
370# Expect a significant performance impact when enabling this.
371CFG_LOCKDEP ?= n
372CFG_LOCKDEP_RECORD_STACK ?= y
373
374# BestFit algorithm in bget reduces the fragmentation of the heap when running
375# with the pager enabled or lockdep
376CFG_CORE_BGET_BESTFIT ?= $(call cfg-one-enabled, CFG_WITH_PAGER CFG_LOCKDEP)
377
378# Enable support for detected undefined behavior in C
379# Uses a lot of memory, can't be enabled by default
380CFG_CORE_SANITIZE_UNDEFINED ?= n
381
382# Enable Kernel Address sanitizer, has a huge performance impact, uses a
383# lot of memory and need platform specific adaptations, can't be enabled by
384# default
385CFG_CORE_SANITIZE_KADDRESS ?= n
386
387# Add stack guards before/after stacks and periodically check them
388CFG_WITH_STACK_CANARIES ?= y
389
390# Use compiler instrumentation to troubleshoot stack overflows.
391# When enabled, most C functions check the stack pointer against the current
392# stack limits on entry and panic immediately if it is out of range.
393CFG_CORE_DEBUG_CHECK_STACKS ?= n
394
395# Use when the default stack allocations are not sufficient.
396CFG_STACK_THREAD_EXTRA ?= 0
397CFG_STACK_TMP_EXTRA ?= 0
398
399# Device Tree support
400#
401# When CFG_DT is enabled core embeds the FDT library (libfdt) allowing
402# device tree blob (DTB) parsing from the core.
403#
404# When CFG_DT is enabled, the TEE _start function expects to find
405# the address of a DTB in register X2/R2 provided by the early boot stage
406# or value 0 if boot stage provides no DTB.
407#
408# When CFG_EMBED_DTB is enabled, CFG_EMBED_DTB_SOURCE_FILE shall define the
409# relative path of a DTS file located in core/arch/$(ARCH)/dts.
410# The DTS file is compiled into a DTB file which content is embedded in a
411# read-only section of the core.
412ifneq ($(strip $(CFG_EMBED_DTB_SOURCE_FILE)),)
413CFG_EMBED_DTB ?= y
414endif
415ifeq ($(CFG_EMBED_DTB),y)
416$(call force,CFG_DT,y)
417endif
418CFG_EMBED_DTB ?= n
419CFG_DT ?= n
420
421# Maximum size of the Device Tree Blob, has to be large enough to allow
422# editing of the supplied DTB.
423CFG_DTB_MAX_SIZE ?= 0x10000
424
425# Device Tree Overlay support.
426# This define enables support for an OP-TEE provided DTB overlay.
427# One of two modes is supported in this case:
428# 1. Append OP-TEE nodes to an existing DTB overlay located at CFG_DT_ADDR or
429#    passed in arg2
430# 2. Generate a new DTB overlay at CFG_DT_ADDR
431# A subsequent boot stage must then merge the generated overlay DTB into a main
432# DTB using the standard fdt_overlay_apply() method.
433CFG_EXTERNAL_DTB_OVERLAY ?= n
434
435# All embedded tests are supposed to be disabled by default, this flag
436# is used to control the default value of all other embedded tests
437CFG_ENABLE_EMBEDDED_TESTS ?= n
438
439# Enable core self tests and related pseudo TAs
440CFG_TEE_CORE_EMBED_INTERNAL_TESTS ?= $(CFG_ENABLE_EMBEDDED_TESTS)
441
442# Compiles bget_main_test() to be called from a test TA
443CFG_TA_BGET_TEST ?= $(CFG_ENABLE_EMBEDDED_TESTS)
444
445# This option enables OP-TEE to respond to SMP boot request: the Rich OS
446# issues this to request OP-TEE to release secondaries cores out of reset,
447# with specific core number and non-secure entry address.
448CFG_BOOT_SECONDARY_REQUEST ?= n
449
450# Default heap size for Core, 64 kB
451CFG_CORE_HEAP_SIZE ?= 65536
452
453# Default size of nexus heap. 16 kB. Used only if CFG_VIRTUALIZATION
454# is enabled
455CFG_CORE_NEX_HEAP_SIZE ?= 16384
456
457# TA profiling.
458# When this option is enabled, OP-TEE can execute Trusted Applications
459# instrumented with GCC's -pg flag and will output profiling information
460# in gmon.out format to /tmp/gmon-<ta_uuid>.out (path is defined in
461# tee-supplicant)
462# Note: this does not work well with shared libraries at the moment for a
463# couple of reasons:
464# 1. The profiling code assumes a unique executable section in the TA VA space.
465# 2. The code used to detect at run time if the TA is intrumented assumes that
466# the TA is linked statically.
467CFG_TA_GPROF_SUPPORT ?= n
468
469# TA function tracing.
470# When this option is enabled, OP-TEE can execute Trusted Applications
471# instrumented with GCC's -pg flag and will output function tracing
472# information in ftrace.out format to /tmp/ftrace-<ta_uuid>.out (path is
473# defined in tee-supplicant)
474CFG_FTRACE_SUPPORT ?= n
475
476# How to make room when the function tracing buffer is full?
477# 'shift': shift the previously stored data by the amount needed in order
478#    to always keep the latest logs (slower, especially with big buffer sizes)
479# 'wrap': discard the previous data and start at the beginning of the buffer
480#    again (fast, but can result in a mostly empty buffer)
481# 'stop': stop logging new data
482CFG_FTRACE_BUF_WHEN_FULL ?= shift
483$(call cfg-check-value,FTRACE_BUF_WHEN_FULL,shift stop wrap)
484$(call force,_CFG_FTRACE_BUF_WHEN_FULL_$(CFG_FTRACE_BUF_WHEN_FULL),y)
485
486# Function tracing: unit to be used when displaying durations
487#  0: always display durations in microseconds
488# >0: if duration is greater or equal to the specified value (in microseconds),
489#     display it in milliseconds
490CFG_FTRACE_US_MS ?= 10000
491
492# Core syscall function tracing.
493# When this option is enabled, OP-TEE core is instrumented with GCC's
494# -pg flag and will output syscall function graph in user TA ftrace
495# buffer
496CFG_SYSCALL_FTRACE ?= n
497$(call cfg-depends-all,CFG_SYSCALL_FTRACE,CFG_FTRACE_SUPPORT)
498
499# Enable to compile user TA libraries with profiling (-pg).
500# Depends on CFG_TA_GPROF_SUPPORT or CFG_FTRACE_SUPPORT.
501CFG_ULIBS_MCOUNT ?= n
502# Profiling/tracing of syscall wrapper (utee_*)
503CFG_SYSCALL_WRAPPERS_MCOUNT ?= $(CFG_ULIBS_MCOUNT)
504
505ifeq (y,$(filter y,$(CFG_ULIBS_MCOUNT) $(CFG_SYSCALL_WRAPPERS_MCOUNT)))
506ifeq (,$(filter y,$(CFG_TA_GPROF_SUPPORT) $(CFG_FTRACE_SUPPORT)))
507$(error Cannot instrument user libraries if user mode profiling is disabled)
508endif
509endif
510
511# Build libutee, libutils, libmbedtls as shared libraries.
512# - Static libraries are still generated when this is enabled, but TAs will use
513# the shared libraries unless explicitly linked with the -static flag.
514# - Shared libraries are made of two files: for example, libutee is
515#   libutee.so and 527f1a47-b92c-4a74-95bd-72f19f4a6f74.ta. The '.so' file
516#   is a totally standard shared object, and should be used to link against.
517#   The '.ta' file is a signed version of the '.so' and should be installed
518#   in the same way as TAs so that they can be found at runtime.
519CFG_ULIBS_SHARED ?= n
520
521ifeq (yy,$(CFG_TA_GPROF_SUPPORT)$(CFG_ULIBS_SHARED))
522$(error CFG_TA_GPROF_SUPPORT and CFG_ULIBS_SHARED are currently incompatible)
523endif
524
525# CFG_GP_SOCKETS
526# Enable Global Platform Sockets support
527CFG_GP_SOCKETS ?= y
528
529# Enable Secure Data Path support in OP-TEE core (TA may be invoked with
530# invocation parameters referring to specific secure memories).
531CFG_SECURE_DATA_PATH ?= n
532
533# Enable storage for TAs in secure storage, depends on CFG_REE_FS=y
534# TA binaries are stored encrypted in the REE FS and are protected by
535# metadata in secure storage.
536CFG_SECSTOR_TA ?= $(call cfg-all-enabled,CFG_REE_FS CFG_WITH_USER_TA)
537$(eval $(call cfg-depends-all,CFG_SECSTOR_TA,CFG_REE_FS CFG_WITH_USER_TA))
538
539# Enable the pseudo TA that managages TA storage in secure storage
540CFG_SECSTOR_TA_MGMT_PTA ?= $(call cfg-all-enabled,CFG_SECSTOR_TA)
541$(eval $(call cfg-depends-all,CFG_SECSTOR_TA_MGMT_PTA,CFG_SECSTOR_TA))
542
543# Enable the pseudo TA for misc. auxilary services, extending existing
544# GlobalPlatform Core API (for example, re-seeding RNG entropy pool etc.)
545CFG_SYSTEM_PTA ?= y
546
547# Enable the pseudo TA for enumeration of TEE based devices for the normal
548# world OS.
549CFG_DEVICE_ENUM_PTA ?= y
550
551# Define the number of cores per cluster used in calculating core position.
552# The cluster number is shifted by this value and added to the core ID,
553# so its value represents log2(cores/cluster).
554# Default is 2**(2) = 4 cores per cluster.
555CFG_CORE_CLUSTER_SHIFT ?= 2
556
557# Define the number of threads per core used in calculating processing
558# element's position. The core number is shifted by this value and added to
559# the thread ID, so its value represents log2(threads/core).
560# Default is 2**(0) = 1 threads per core.
561CFG_CORE_THREAD_SHIFT ?= 0
562
563# Enable support for dynamic shared memory (shared memory anywhere in
564# non-secure memory).
565CFG_CORE_DYN_SHM ?= y
566
567# Enable support for reserved shared memory (shared memory in a carved out
568# memory area).
569CFG_CORE_RESERVED_SHM ?= y
570
571# Enables support for larger physical addresses, that is, it will define
572# paddr_t as a 64-bit type.
573CFG_CORE_LARGE_PHYS_ADDR ?= n
574
575# Define the maximum size, in bits, for big numbers in the Internal Core API
576# Arithmetical functions. This does *not* influence the key size that may be
577# manipulated through the Cryptographic API.
578# Set this to a lower value to reduce the TA memory footprint.
579CFG_TA_BIGNUM_MAX_BITS ?= 2048
580
581# Define the maximum size, in bits, for big numbers in the TEE core (privileged
582# layer).
583# This value is an upper limit for the key size in any cryptographic algorithm
584# implemented by the TEE core.
585# Set this to a lower value to reduce the memory footprint.
586CFG_CORE_BIGNUM_MAX_BITS ?= 4096
587
588# Not used since libmpa was removed. Force the values to catch build scripts
589# that would set = n.
590$(call force,CFG_TA_MBEDTLS_MPI,y)
591$(call force,CFG_TA_MBEDTLS,y)
592
593# Compile the TA library mbedTLS with self test functions, the functions
594# need to be called to test anything
595CFG_TA_MBEDTLS_SELF_TEST ?= y
596
597# By default use tomcrypt as the main crypto lib providing an implementation
598# for the API in <crypto/crypto.h>
599# CFG_CRYPTOLIB_NAME is used as libname and
600# CFG_CRYPTOLIB_DIR is used as libdir when compiling the library
601#
602# It's also possible to configure to use mbedtls instead of tomcrypt.
603# Then the variables should be assigned as "CFG_CRYPTOLIB_NAME=mbedtls" and
604# "CFG_CRYPTOLIB_DIR=lib/libmbedtls" respectively.
605CFG_CRYPTOLIB_NAME ?= tomcrypt
606CFG_CRYPTOLIB_DIR ?= core/lib/libtomcrypt
607
608# Not used since libmpa was removed. Force the value to catch build scripts
609# that would set = n.
610$(call force,CFG_CORE_MBEDTLS_MPI,y)
611
612# Enable virtualization support. OP-TEE will not work without compatible
613# hypervisor if this option is enabled.
614CFG_VIRTUALIZATION ?= n
615
616ifeq ($(CFG_VIRTUALIZATION),y)
617$(call force,CFG_CORE_RODATA_NOEXEC,y)
618$(call force,CFG_CORE_RWDATA_NOEXEC,y)
619
620# Default number of virtual guests
621CFG_VIRT_GUEST_COUNT ?= 2
622endif
623
624# Enables backwards compatible derivation of RPMB and SSK keys
625CFG_CORE_HUK_SUBKEY_COMPAT ?= y
626
627# Compress and encode conf.mk into the TEE core, and show the encoded string on
628# boot (with severity TRACE_INFO).
629CFG_SHOW_CONF_ON_BOOT ?= n
630
631# Enables support for passing a TPM Event Log stored in secure memory
632# to a TA, so a TPM Service could use it to extend any measurement
633# taken before the service was up and running.
634CFG_CORE_TPM_EVENT_LOG ?= n
635
636# When enabled, CFG_SCMI_MSG_DRIVERS embeds SCMI message drivers in the core.
637# Refer to the supported SCMI features embedded upon CFG_SCMI_MSG_*
638# CFG_SCMI_MSG_CLOCK embeds SCMI clock protocol support.
639# CFG_SCMI_MSG_RESET_DOMAIN embeds SCMI reset domain protocol support.
640# CFG_SCMI_MSG_SMT embeds SMT based message buffer of communication channel
641# CFG_SCMI_MSG_VOLTAGE_DOMAIN embeds SCMI voltage domain protocol support.
642CFG_SCMI_MSG_DRIVERS ?= n
643CFG_SCMI_MSG_CLOCK ?= n
644CFG_SCMI_MSG_RESET_DOMAIN ?= n
645CFG_SCMI_MSG_SMT ?= n
646CFG_SCMI_MSG_VOLTAGE_DOMAIN ?= n
647
648# Enable SCMI PTA interface for REE SCMI agents
649CFG_SCMI_PTA ?= n
650
651ifneq ($(CFG_STMM_PATH),)
652$(call force,CFG_WITH_STMM_SP,y)
653else
654CFG_WITH_STMM_SP ?= n
655endif
656ifeq ($(CFG_WITH_STMM_SP),y)
657$(call force,CFG_ZLIB,y)
658endif
659
660# When enabled checks that buffers passed to the GP Internal Core API
661# comply with the rules added as annotations as part of the definition of
662# the API. For example preventing buffers in non-secure shared memory when
663# not allowed.
664CFG_TA_STRICT_ANNOTATION_CHECKS ?= y
665
666# When enabled accepts the DES key sizes excluding parity bits as in
667# the GP Internal API Specification v1.0
668CFG_COMPAT_GP10_DES ?= y
669
670# Defines a limit for many levels TAs may call each others.
671CFG_CORE_MAX_SYSCALL_RECURSION ?= 4
672
673# Pseudo-TA to export hardware RNG output to Normal World
674# RNG characteristics are platform specific
675CFG_HWRNG_PTA ?= n
676ifeq ($(CFG_HWRNG_PTA),y)
677# Output rate of hw_get_random_bytes() in bytes per second, 0: not rate-limited
678CFG_HWRNG_RATE ?= 0
679# Quality/entropy of hw_get_random_bytes() per 1024 bits of output data, in bits
680ifeq (,$(CFG_HWRNG_QUALITY))
681$(error CFG_HWRNG_QUALITY not defined)
682endif
683endif
684