On Fri, Nov 21, 2014 at 03:43:54PM -0800, Stephen Boyd wrote: > On 11/21/2014 03:27 PM, Mark Brown wrote:
> > 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. ... > 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?
signature.asc
Description: Digital signature
