Messages in this thread | | | Date | Tue, 10 Aug 2004 22:50:06 +0200 | From | Pavel Machek <> | Subject | Re: [RFC] Fix Device Power Management States |
| |
Hi!
> Hmm, some of these proposals seem to relate to stuff OTHER than the > device power management states. While I suspect it might be a very > handy thing to add methods to quiesce drivers (drivers have to have > that anyway) the semantics need to be properly nailed down.
Okay, what about:
* switch system state to suspend_state_t (initialy u32)
* pass system state down to the drivers
* create helpers to convert from system state to PCI state (etc)
* create some well-known suspend_state_t's (like suspend_state_t prepare_for_powerdown = 3). Drivers may either compare state passed to them with one of well-known states, or call a helper
This should solve current mess. If we'll want to do runtime power managment (etc), we can change suspend_state_t into structure / whatever, but we will not break all the drivers this time. (=> this approach does not solve runtime suspend, but will probably make it easier).
I'd like to do this in 2.6.9 timeframe... Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |