On 16.07.2013 19:47, Mark Brown wrote:
On Tue, Jul 16, 2013 at 07:07:33PM +0200, Daniel Mack wrote:
On 16.07.2013 18:57, Mark Brown wrote:
No, no feature here. Off the top of my head I'd suggest soc-pcm plus a virtual DAI for the second link.
That would still require userspace to open and configure both subdevices, right?
Shouldn't.
How so? As each link exposes its own PCM subdevice, how would codec of link #1 get a hw_params call if an application just opens PCM subdevice #0 for playback? This is the case I want to address.
Half the point of soc-pcm is to decouple the streams seen by the application layer from the DAIs that the driver sees so I'd expect us to be able to map a single application layer/memory stream onto multiple CODEC DAIs. One front end connected to two back ends.
You're talking about DPCM, right? Unfortunately, there is no active user of this in mainline, and no documentation either. I'll try and find out how this is supposed to work first ...
Maybe Liam has some explanation ready?
By naive approach atm would be to just add .codec_names, .codec_dai_names and .codec_of_node to snd_soc_dai_link, and make their use mutually exclusive to the existing ones. That way, we don't need to touch any existing user.
May as well bite the bullet and do the refactoring, it should be automatable. There's also the fun of handling what happens when you want to stream from one CODEC to another but I think that's second stage...
Looking deeper into this, I'm not sure whether each of those codec instances inside one snd_soc_dai_link should have it own runtime, of if they should rather share one. The latter isn't straight-forward, as current users simply access the codec from their callbacks as rtd->codec_dai. However, open-coding routines to access the correct codec from these callbacks is not nice at all either. Hmm.
Let's see if DPCM can help here.
Daniel