On 5/14/2012 1:34 AM, Mark Brown wrote:
On Sun, May 13, 2012 at 11:30:29PM -0700, Patrick Lai wrote:
that as system attempts to enter suspend while DAILINK X is active, snd_soc_suspend() calls snd_soc_dapm_stream_event( SND_SOC_DAPM_STREAM_SUSPEND) on inactive DAILINK Y since DAILINK Y ignore flag is not set. Consequently, CODEC widgets get powered off even though they should remain powered for DAILINK X.
This sounds like expected behaviour, if the widgets aren't marked as ignoring suspend then they will be suspended.
As CODEC is getting more complicated and more widgets would be defined, I don't think it's scalable to mark ignore suspend per widget.
- Should soc-core check if CODEC DAI is active beside checking
ignore_suspend flag before calling snd_soc_dapm_stream_event()? I checked latest soc-core.c from kernel 3.4 RC7. The logic is the same as 3.0
No, the whole point here is to suspend. If we did that we'd never suspend any active streams.
If so, what is purpose of ignore_suspend? My problem is that active stream which has ignore_suspend flag set ends up suspended because an inactive stream without ignore_suspend flag set happens to be using same CODEC but different digital audio interface. I don't think it's the right behavior. DAPM should maintain widget usage reference. Only If all CODEC DAIs that are using given widget are going to suspend should DAPM go ahead power off the widget.
Thanks Patrick