[RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones
Mark Brown
broonie at kernel.org
Fri Apr 16 18:31:31 CEST 2021
On Fri, Apr 16, 2021 at 04:03:05PM +0000, Codrin.Ciubotariu at microchip.com wrote:
> Thank you for the links! So basically the machine driver disappears and
> all the components will be visible in user-space.
Not entirely - you still need something to say how they're wired
together but it'll be a *lot* simpler for anything that currently used
DPCM.
> If there is a list with the 'steps' or tasks to achieve this? I can try
> to pitch in.
Not really written down that I can think of. I think the next steps
that I can think of right now are unfortunately bigger and harder ones,
mainly working out a way to represent digital configuration as a graph
that can be attached to/run in parallel with DAPM other people might
have some better ideas though. Sorry, I appreciate that this isn't
super helpful :/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20210416/6d41388e/attachment-0001.sig>
More information about the Alsa-devel
mailing list