On Wed, May 05, 2010 at 03:20:40PM -0400, Alan Stern wrote: > One the face of it, a runtime-PM solution would dictate that the > codec's driver ought to turn off the codec whenever the driver thinks > it isn't being used. Ergo, if the driver didn't know when a call was > in progress, it would use runtime PM to turn off the codec during a > call. Well, part of the problem is that right now most of our beliefs about imposed constraints tend to be based on what userspace is doing - "Don't power down the audio codec when userspace has it open", for instance. But that goes away with opportunistic suspend. In most cases you don't want the audio codec to stay awake just because userspace was using it to make bouncing cow noises, especially if you've just frozen userspace. So the problem becomes more complicated than it would otherwise be. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
