diff options
| author | Grzegorz Jaszczyk <jaz@semihalf.com> | 2018-11-14 18:47:35 +0100 |
|---|---|---|
| committer | Konstantin Porotchkin <kostap@marvell.com> | 2018-12-04 14:09:44 +0200 |
| commit | 9cb6751d5988fe62d10b809469d4f6ec082730c6 (patch) | |
| tree | c33a80a5c335ab192fae44ba3408962d845fb0f1 /drivers/marvell/comphy/phy-comphy-cp110.c | |
| parent | 0529106c4bb7e6e14247b3cca98b7c12009b42f0 (diff) | |
| download | platform_external_arm-trusted-firmware-9cb6751d5988fe62d10b809469d4f6ec082730c6.tar.gz platform_external_arm-trusted-firmware-9cb6751d5988fe62d10b809469d4f6ec082730c6.tar.bz2 platform_external_arm-trusted-firmware-9cb6751d5988fe62d10b809469d4f6ec082730c6.zip | |
plat: marvell: a3700: do not power off cpu due to errata ref #13
Do not power off the CPU1 since there is no way to wake it up
(wake-up is causing CPU0 reset as well duo to HW bug). Quote from errata
Ref #13 [In power saving mode, both cores must be powered off]:
"When Core 0 is on and Core 1 is in power-off state, a Core 1
wake-up resets Core 0 as well and puts Core 0 back to ROM".
To overcome described HW bug instead of powering the CPU off, let it
reach WFI instruction, which is invoked by generic psci_do_cpu_off
function after platform handler finishes. This will put the core in low
power state and give a chance to wake it up.
Before this change, after running secondary kernel via kexec, only one
core was up, now both cores are up.
Change-Id: I87f144867550728055d9b8a2edb84a14539acab7
Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
Reviewed-by: Kostya Porotchkin <kostap@marvell.com>
Diffstat (limited to 'drivers/marvell/comphy/phy-comphy-cp110.c')
0 files changed, 0 insertions, 0 deletions