-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(armv8/psci): Handle unexpected psci behavior #179
Conversation
@DavidMCerdeira Shouldn't we address other calls to |
This is a good point |
Please make sure we are also inline with the PSCI in this respect. |
14d8cc1
to
2f33b23
Compare
a981972
to
93d03a6
Compare
93d03a6
to
7fa7b46
Compare
We've observed that some platforms behave unexpectedly when performing power down. In these cases, after powerdown, the CPU cores are not awaken by interrupts as expected by Bao. This commit solve this, by adding the ability to skip the powerdown firmware call, instead relying on the fallback mechanism of using standby. Signed-off-by: David Cerdeira <[email protected]>
7fa7b46
to
aeeaa2c
Compare
aeeaa2c
to
d5ec70b
Compare
The development target zcu104/zcu102 and Ultra96 does not wake up on interrupts after emiting PSCI standby calls to TF-A. We should understand why. To circunvent this, we allow platforms to declare standby is not supported and fallback to wfi. Signed-off-by: David Cerdeira <[email protected]>
d5ec70b
to
43c4321
Compare
We've observed that some platforms behave unexpectedly when performing power down, and others when performing standby. In these cases, the CPU cores are not awaken by interrupts as expected. These commit solve this, by adding the ability to skip the respective firmware call, instead relying on the fallback mechanism of using wfi.