Hi Mark, Coming back on this topic: We are trying to use the codec <-> codec approach to model our on-SoC DSP. So in our case it would be quite important that the full sequence of ops is called, so that we are not dependent on which ops the codec we use is relying on.
I am even thinking that it could be worth creating an internal PCM for the dai link that has the params field, and to call the standard soc functions (soc_pcm_open, ...) on it from the dai_link widget DAPM callback to start / stop the PCM.
Any feedback?
Thanks Regards Sebastien
-----Original Message----- From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com] Sent: Friday, October 26, 2012 7:02 PM To: Sebastien LEDUC Cc: alsa-devel@alsa-project.org; Liam Girdwood (lrg@ti.com) Subject: Re: question on snd_soc_dai_link_event
On Fri, Oct 26, 2012 at 01:58:54PM +0200, Sebastien LEDUC wrote:
Fix your mailer to word wrap within paragraphs, it makes your mails hard to read if you don't do this. I've reflowed for legibility.
I wonder why it does not call the full hw_params / prepare / trigger sequence on both dai drivers to start the 2 DAIs.
None of the drivers that use this actually have any of those calls so I didn't bother. Especially in the case of trigger it's unlikely that an off-SoC device without DMA would need this, though of course it could happen.