On Wed, May 5, 2010 at 4:40 PM, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Wed, May 05, 2010 at 01:56:07PM -0700, Brian Swetland wrote: ... >> taken on MSM, regardless of suspend state. I don't view suspend as >> something that stops audio playback in progress. Sort of similar to >> how the modem doesn't power off down when the system is in suspend, >> etc. > > This really does depend heavily on system design and the intended > function of the suspend on the part of the initiator. In many systems > suspend will remove sufficient power to stop audio running even if it > were desired, and there's the idea with existing manually initiated > suspends that the system should stop what it's doing and go into a low > power, low responsiveness state. Some systems will initiate a suspend > with active audio paths (especially those to or from the AP) which they > expect to be stopped. > You can support both in the same driver in some cases (without a switch). If the hardware cannot wake the system when it needs more audio buffers, then the driver needs to block suspend while audio is playing. Since suspend blockers only block opportunistic suspend, the driver can also implement suspend to stop audio playback and it will only be called for forced suspend. -- Arve Hjønnevåg _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
