On Wed, Mar 30, 2016 at 09:36:50AM -0700, Mark Brown wrote: > On Wed, Mar 30, 2016 at 09:58:12AM +0100, Charles Keepax wrote: > > On Tue, Mar 29, 2016 at 02:22:24PM -0700, Mark Brown wrote: > > > > Is this not just a normal CODEC connected to a back end on a DPCM > > > system? What are a "dynamic DAI" and "static DAI"? Your changelog is > > > very unclear, I really can't tell from your changelog what this is > > > aiming to do or how it proposes to do it. > > > The issue is basically if you have a path with a DPCM DAI at the > > front, but then a regular CODEC to CODEC DAI link later in the > > path. Say for example a CODEC attached to a CPU that uses DPCM > > but then the path goes through a CODEC to CODEC link to a speaker > > AMP after the CODEC. > > Doesn't this mean that the appropriate fix is to terminate the DPCM > routing at the first back end DAI so we're not trying to DPCM outside > the SoC? I think (not 100% certain) you can have multiple backends connected to a single front end, which makes it hard to know when to stop or even if it is assured that all the backends will be before any other spurious DAIs in the widget list. Thanks, Charles _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
