Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
30 lines
887 B
Plaintext
30 lines
887 B
Plaintext
config ARCH_SUPPORTS_FIRMWARE
|
|
bool
|
|
|
|
config ARCH_SUPPORTS_TRUSTED_FOUNDATIONS
|
|
bool
|
|
select ARCH_SUPPORTS_FIRMWARE
|
|
|
|
menu "Firmware options"
|
|
depends on ARCH_SUPPORTS_FIRMWARE
|
|
|
|
config TRUSTED_FOUNDATIONS
|
|
bool "Trusted Foundations secure monitor support"
|
|
depends on ARCH_SUPPORTS_TRUSTED_FOUNDATIONS
|
|
default y
|
|
help
|
|
Some devices (including most Tegra-based consumer devices on the
|
|
market) are booted with the Trusted Foundations secure monitor
|
|
active, requiring some core operations to be performed by the secure
|
|
monitor instead of the kernel.
|
|
|
|
This option allows the kernel to invoke the secure monitor whenever
|
|
required on devices using Trusted Foundations. See
|
|
arch/arm/include/asm/trusted_foundations.h or the
|
|
tlm,trusted-foundations device tree binding documentation for details
|
|
on how to use it.
|
|
|
|
Say n if you don't know what this is about.
|
|
|
|
endmenu
|