41ba11229a
Currently, arch/arm64 requires coreboot to run on EL3 due to EL3 register access. This might be an issue when, for example, one boots into TF-A first and drops into EL2 for coreboot afterwards. This patch aims at making arch/arm64 more versatile by removing the current EL3 constraint and allowing arm64 coreboot to run on EL1, EL2 and EL3. The strategy here, is to add a Kconfig option (ARM64_CURRENT_EL) which lets us specify coreboot's EL upon entry. Based on that, we access the appropriate ELx registers. So, for example, when running coreboot on EL1, we would not access vbar_el3 or vbar_el2 but instead vbar_el1. This way, we don't generate faults when accessing higher-EL registers. Currently only tested on the qemu-aarch64 target. Exceptions were tested by enabling FATAL_ASSERTS. Signed-off-by: David Milosevic <David.Milosevic@9elements.com> Change-Id: Iae1c57f0846c8d0585384f7e54102a837e701e7e Reviewed-on: https://review.coreboot.org/c/coreboot/+/74798 Reviewed-by: Werner Zeh <werner.zeh@siemens.com> Reviewed-by: ron minnich <rminnich@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Julius Werner <jwerner@chromium.org>
78 lines
1.9 KiB
Plaintext
78 lines
1.9 KiB
Plaintext
## SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
config ARCH_ARM64
|
|
bool
|
|
|
|
config ARCH_BOOTBLOCK_ARM64
|
|
bool
|
|
select ARCH_ARM64
|
|
|
|
config ARCH_VERSTAGE_ARM64
|
|
bool
|
|
select ARCH_ARM64
|
|
|
|
config ARCH_ROMSTAGE_ARM64
|
|
bool
|
|
select ARCH_ARM64
|
|
|
|
config ARCH_RAMSTAGE_ARM64
|
|
bool
|
|
select ARCH_ARM64
|
|
|
|
source "src/arch/arm64/armv8/Kconfig"
|
|
|
|
if ARCH_ARM64
|
|
|
|
config ARM64_CURRENT_EL
|
|
int
|
|
default 3
|
|
range 1 3
|
|
help
|
|
The exception level on which coreboot is started. Accepted
|
|
values are: 1 (EL1), 2 (EL2) and 3 (EL3). This option can be
|
|
used to restrict access to available control registers in case
|
|
prior firmware already dropped to a lower exception level. By default,
|
|
coreboot is the first firmware that runs on the system and should thus
|
|
always run on EL3. This option is only provided for edge-case platforms
|
|
that require running a different firmware before coreboot which drops
|
|
to a lower exception level.
|
|
|
|
config ARM64_USE_ARCH_TIMER
|
|
bool
|
|
default n
|
|
|
|
config ARM64_USE_ARM_TRUSTED_FIRMWARE
|
|
bool
|
|
default n
|
|
depends on ARCH_RAMSTAGE_ARM64 && ARM64_CURRENT_EL = 3
|
|
|
|
config ARM64_BL31_EXTERNAL_FILE
|
|
string "Path to external BL31.ELF (leave empty to build from source)"
|
|
depends on ARM64_USE_ARM_TRUSTED_FIRMWARE
|
|
help
|
|
The blob to use instead of building the Arm Trusted Firmware
|
|
from tree. It is discouraged as compatibility with out-of-tree
|
|
blobs may break anytime.
|
|
|
|
config ARM64_USE_SECURE_OS
|
|
bool
|
|
default n
|
|
depends on ARM64_USE_ARM_TRUSTED_FIRMWARE
|
|
|
|
config ARM64_SECURE_OS_FILE
|
|
string "Secure OS binary file"
|
|
depends on ARM64_USE_SECURE_OS
|
|
help
|
|
Secure OS binary file.
|
|
|
|
config ARM64_A53_ERRATUM_843419
|
|
bool
|
|
default n
|
|
help
|
|
Some early Cortex-A53 revisions had a hardware bug that results in
|
|
incorrect address calculations in rare cases. This option enables a
|
|
linker workaround to avoid those cases if your toolchain supports it.
|
|
Should be selected automatically by SoCs that are affected.
|
|
|
|
endif # if ARCH_ARM64
|