On Tue, Aug 27, 2013 at 06:05:34PM -0700, Russ Dill wrote: > On Tue, Aug 27, 2013 at 3:44 PM, Kevin Hilman <khilman@xxxxxxxxxx> wrote: > > The framework already has a concept of suspend voltage, suspend mode > > etc. Maybe it needs some generalizing so low-level platform code could > > query the framework for the sequence so it can be done late in platform > > idle/suspend paths. Especially for regmap drivers, this seems feasible. > Yes, my main hesitation for going down this path is possible lack of > support for such an interface upstream. Someone is going to have to walk me through the context for me to fully understand what this is all about - what's the problem? Generally for suspend if the sequencing is being done by the processor it's been handled by the drivers for the components in question. For sequencing beyond that you're into hardware features which aren't all that regular sadly and often aren't controllable either. It sounds like this is the latter case but the thing that manages some of the late power down stages does so using a firmware we can rewrite?
Attachment:
signature.asc
Description: Digital signature
