summaryrefslogtreecommitdiffstats
path: root/drivers/soc
diff options
context:
space:
mode:
authorOleksandr Tyshchenko2019-05-29 18:05:00 +0200
committerSimon Horman2019-05-31 11:38:01 +0200
commit51a0daf64dee78dacaecc7bec3d36e0b2f49c7a1 (patch)
tree943770cd24632375da24fe8bc9ef2c5d702a2a02 /drivers/soc
parentLinux 5.2-rc1 (diff)
downloadkernel-qcow2-linux-51a0daf64dee78dacaecc7bec3d36e0b2f49c7a1.tar.gz
kernel-qcow2-linux-51a0daf64dee78dacaecc7bec3d36e0b2f49c7a1.tar.xz
kernel-qcow2-linux-51a0daf64dee78dacaecc7bec3d36e0b2f49c7a1.zip
ARM: mach-shmobile: Don't init CNTVOFF/counter if PSCI is available
If PSCI is available then most likely we are running on PSCI-enabled U-Boot which, we assume, has already taken care of resetting CNTVOFF and updating counter module before switching to non-secure mode and we don't need to. As the psci_smp_available() helper always returns false if CONFIG_SMP is disabled, it can't be used safely as an indicator of PSCI usage. For that reason, we check for the mandatory PSCI operation to be available. Please note, an extra check to prevent secure_cntvoff_init() from being called for secondary CPUs in headsmp-apmu.S is not needed, as SMP code for APMU based system is not executed if PSCI is in use. Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'drivers/soc')
0 files changed, 0 insertions, 0 deletions