[alsa-devel] [PATCH 01/13] ASoC: topology: Able to create BE DAIs

[Mark Brown]

On Fri, Aug 19, 2016 at 06:12:35PM +0800, mengdong.lin at linux.intel.com wrote:

> Topology will check with ASoC if a BE DAI already exists by checking
> its name. If the BE DAI doesn't exist, topology will create a new one
> and the dai_load ops will be called for device specific init.

This doesn't explain in what situation we'd want to dynamically create a
back end, or why we're representing DPCM so directly in the topology -
we really need more words about what the use case is and why this makes
sense.  The expectation would be that back ends refer to physical
objects that exist in the system so it's not clear why we'd be loading
them from topologies (and that even where this makes sense there
wouldn't be any misuse by other users).  This is a bit of a theme here,
the series is adding a bunch of stuff but not explaining why.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20160823/3576bef0/attachment-0001.sig>