Hi,
On Jan 19 2016 12:08, Kuninori Morimoto wrote:
Userspace can get to know the XRUN state by calling some APIs. Then,
it can recover PCM substream by executing SNDRV_PCM_IOCTL_PREPARE
ioctl.
I think we can use snd_pcm_stop_xrun() for this purpose.
Right. But beware of locking by this function. Unlike snd_pcm_stop()
this function takes the stream lock by itself.
Thanks !
I see. I will investigate it.
The 'lock' is what I mentioned in former message to you:
Can I stop sound from driver as system error ?
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-December/102010.html
Yes, I had asked same question to ML, I'm sorry about that.
And, can I confirm about your concern ?
I guess you are worrying about dead-lock by stop xrun, but is that correct ?
Recent SoC tends to accumurate much IPs with variety functionalities.
If your SoC, R-Car, has such IPs and snd-soc-rcar utilize it, I can
assume that snd-soc-rcar require to wait for some events after operating
to the IPs. Or snd-soc-rcar require to manage race conditions between
many PCM substreams.
In this case, current structure of snd-soc-rcar may cause problems (at
least, in the end of last year), because it pushes many operations into
'struct snd_pcm_ops.trigger'. This callback is executed in both of
process context and interrupt context and drivers should not wait for
events or should not manage race conditions.
This is my concern about it.
Regards
Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
