linux-kernel - Re: [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210416163131.GI5560@sirena.org.uk>
Date:   Fri, 16 Apr 2021 17:31:31 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Codrin.Ciubotariu@...rochip.com
Cc:     perex@...ex.cz, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, gustavoars@...nel.org,
        mirq-linux@...e.qmqm.pl, tiwai@...e.com, lgirdwood@...il.com
Subject: Re: [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones

On Fri, Apr 16, 2021 at 04:03:05PM +0000, Codrin.Ciubotariu@...rochip.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 :/

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)