Re: comments on irc log

[Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

Hi!

> > I have this crazy idea that we could have a single "new" enter_state(), and keep
> > suspend/resume for system state transitions.
> > 
> > Basically, my idea there is that enter_state() is the actual low level driver
> > state change function. It is called when userland picks a state in sysfs, or
> > we could deal with the various bus state dependencies if we want etc...
> > 
> > We could keep suspend/resume separate for the system-wide suspend, and have
> > them implement the policy of converting a system wide suspend/resume into the
> > appropriate enter_state() for the driver.
> > 
> > "Old" or "Simple" drivers would just suspend/resume and not implement
> > enter_state, more complex/subtle drivers would do the above.
> > 
> > I haven't quite thought out the implications, it's just an idea that came to mind
> > as I was reading the log...
> 
> This sounds like a reasonable thing to do.  We do need distinct ways to
> tell drivers "Go to this system state" and "Go to this bus/device state".  
> Whether they are implemented by 1, 2, or 3 different callbacks doesn't
> really matter (except that we might want to minimize the number of 
> function pointers stored in the driver structures).

Actually you want to re-use existing suspend-to-ram code in drivers as
much as possible.

								Pavel

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]