diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2017-04-14 02:10:24 (GMT) |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2017-04-18 14:29:19 (GMT) |
commit | 573a3811edc89c2ea3bf4fd077e3673b863b9a0d (patch) | |
tree | 8704ecc42d27c29d7aaef07c2f3942a67d8df476 /drivers/sysreset/Makefile | |
parent | c54bcf6805cc6762cb998751b8e005f39ee1dad1 (diff) | |
download | u-boot-573a3811edc89c2ea3bf4fd077e3673b863b9a0d.tar.xz |
sysreset: psci: support system reset in a generic way with PSCI
If the system is running PSCI firmware, the System Reset function
(func ID: 0x80000009) is supposed to be handled by PSCI, that is,
the SoC/board specific reset implementation should be moved to PSCI.
U-Boot should call the PSCI service according to the arm-smccc
manner.
The arm-smccc is supported on ARMv7 or later. Especially, ARMv8
generation SoCs are likely to run ARM Trusted Firmware BL31. In
this case, U-Boot is a non-secure world boot loader, so it should
not be able to reset the system directly.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'drivers/sysreset/Makefile')
-rw-r--r-- | drivers/sysreset/Makefile | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/sysreset/Makefile b/drivers/sysreset/Makefile index 49b8bb6..7bb8406 100644 --- a/drivers/sysreset/Makefile +++ b/drivers/sysreset/Makefile @@ -5,6 +5,7 @@ # obj-$(CONFIG_SYSRESET) += sysreset-uclass.o +obj-$(CONFIG_SYSRESET_PSCI) += sysreset_psci.o ifndef CONFIG_SPL_BUILD obj-$(CONFIG_ROCKCHIP_RK3036) += sysreset_rk3036.o |