diff options
author | Heinrich Schuchardt <xypron.glpk@gmx.de> | 2018-10-18 12:29:40 +0200 |
---|---|---|
committer | Alexander Graf <agraf@suse.de> | 2018-12-02 21:59:37 +0100 |
commit | 81ea00838c682da06637bcf208549095181df337 (patch) | |
tree | 34fae16c5c4252c09835e63f605e4be9614a24e7 /arch/arm/cpu/u-boot-spl.lds | |
parent | eb3bc8bb177e8b19464529826acad5ec0d0edb61 (diff) | |
download | u-boot-81ea00838c682da06637bcf208549095181df337.zip u-boot-81ea00838c682da06637bcf208549095181df337.tar.gz u-boot-81ea00838c682da06637bcf208549095181df337.tar.bz2 |
efi_loader: PSCI reset and shutdown
When an operating system started via bootefi tries to reset or power off
this is done by calling the EFI runtime ResetSystem(). On most ARMv8 system
the actual reset relies on PSCI. Depending on whether the PSCI firmware
resides the hypervisor (EL2) or in the secure monitor (EL3) either an HVC
or an SMC command has to be issued.
The current implementation always uses SMC. This results in crashes on
systems where the PSCI firmware is implemented in the hypervisor, e.g.
qemu-arm64_defconfig.
The logic to decide which call is needed based on the device tree is
already implemented in the PSCI firmware driver. During the EFI runtime
the device driver model is not available. But we can minimize code
duplication by merging the EFI runtime reset and poweroff code with
the PSCI firmware driver.
As the same HVC/SMC problem is also evident for the ARMv8 do_poweroff
and reset_misc routines let's move them into the same code module.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
Tested-by: Sumit Garg <sumit.garg@linaro.org>
Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'arch/arm/cpu/u-boot-spl.lds')
0 files changed, 0 insertions, 0 deletions