On Thu, 21 Mar 2013, Rajagopal Venkat wrote: > Allow device devfreq to be suspend/resume automatically with > runtime pm suspend/resume. The devfreq drivers should be least > cared when to suspend/resume the devfreq. > > pm_runtime_suspend(dev) will first suspend device devfreq(if available) > before device is suspended from runtime pm core. > > pm_runtime_resume(dev) will resume device devfreq(if available) after > device is resumed from runtime pm core.
Aren't these backward? The device continues to need its clocks and frequency settings until _after_ it has been suspended. Similarly, it needs them to be available _before_ it resumes. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
