RFC Qualcomm RPM sleep states
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/2] Qualcomm RPM sleep states
Quoted 16 lines · Stephen Boyd
Quoted 3 lines · Mark Brown
I'm afraid the above is making very little sense to me. What is "voting" and how is it different to "enabling", "notification" or "flushing"?
The regulators are shared between multiple "masters" in the SoC. So the CPUs that are running linux only "vote" on attributes of regulators and then another processor that isn't running linux (called RPM) aggregates the request from Linux along with other "masters" like wifi, modem, etc. and then changes something for that regulator like voltage, enable/disable, etc. We also have some hardware next to our CPUs that notifies the RPM when we transition into or out of idle/suspend (it's called an SPM). This is the notification part. Flushing has to do with batching up multiple RPM sleep set requests and sending them before we enter idle/suspend.
...
Quoted 1 line
Hopefully it's clear now. If not I can clarify further.
A bit, but I'm afraid I'm still at a loss as to what the problems and
debate are here. Why is this more complex than the Linux part of the
system just saying what it wants at any given time? It sounds like that
has some sort of performance issue?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141124/0f9234ad/attachment.sig>