[RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones

[Codrin.Ciubotariu at microchip.com]

On 15.04.2021 19:17, Mark Brown wrote:
> On Wed, Apr 14, 2021 at 02:58:10PM +0000, Codrin.Ciubotariu at microchip.com wrote:
> 
>> How about using a different API for ASoC only, since that's the place of
>> DPCM. Only drivers that do not involve DSPs would have to to be changed
>> to call the new snd_pcm_hw_rule_add() variant.
>> Another solution would be to have a different snd_soc_pcm_runtime for BE
>> interfaces (with a new hw_constraints member of course). What do you think?
> 
> I'm really not convinced we want to continue to pile stuff on top of
> DPCM, it is just fundamentally not up to modelling what modern systems
> are able to do - it's already making things more fragile than they
> should be and more special cases seems like it's going to end up making
> that worse.  That said I've not seen the code but...
> 

Are there any plans for refactoring DPCM? any ideas ongoing? I also have 
some changes for PCM dmaengine, in the same 'style', similar to what I 
sent some time ago...
I can adjust to different ideas, if there are any, but, for a start, can 
anyone confirm that the problem I am trying to fix is real?

Best regards,
Codrin