RFC cpuidle/powernv: Interface to handle idle-stop versioning
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | Interface for an idle-stop dependency structurearch/ arch/ arch/ +1 more | +37 | 2 replies | |
| 2/3 | Demonstration of handling an idle-stop quirk versionarch/ arch/ arch/ | +25 | 0 replies | |
| 3/3 | Introduce capability for firmware-enabled-stoparch/ arch/ | +10 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/3] cpuidle/powernv: Interface to handle idle-stop versioning
A design patch series illuminates the idea of handling different versions of idle-stop, the properties they support and the quirks that need to be handled before entering or after exiting stop.
It also adds a functionality to identify firmware-enabled-stop and set the according bits to encapsulate the support and corresponding handling
Corresponding RFC skiboot patch: https://lists.ozlabs.org/pipermail/skiboot/2020-March/016552.html
Pratik Rajesh Sampat (3):
Interface for an idle-stop dependency structure Demonstration of handling an idle-stop quirk version Introduce capability for firmware-enabled-stop
arch/powerpc/include/asm/processor.h | 19 +++++++++++++++++ arch/powerpc/kernel/dt_cpu_ftrs.c | 30 +++++++++++++++++++++++++++ arch/powerpc/platforms/powernv/idle.c | 25 ++++++++++++++++++---- drivers/cpuidle/cpuidle-powernv.c | 3 ++- 4 files changed, 72 insertions(+), 5 deletions(-)
Signature · 1 line
2.24.1