linux-kernel - Re: [RFC PATCH] ASoC: pcm_dmaengine: Add support for BE DAIs

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20201214171928.GB4880@sirena.org.uk>
Date:   Mon, 14 Dec 2020 17:19:28 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Codrin.Ciubotariu@...rochip.com
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        lgirdwood@...il.com, tiwai@...e.com, perex@...ex.cz,
        lars@...afoo.de
Subject: Re: [RFC PATCH] ASoC: pcm_dmaengine: Add support for BE DAIs

On Fri, Dec 11, 2020 at 06:00:55PM +0000, Codrin.Ciubotariu@...rochip.com wrote:

> Also, I noticed that the HW constraints added by a DAI driver (a codec 
> for example) are added to PCM's runtime->hw_constraints, even if the DAI 
> driver is part of a BE. Shouldn't these constraints be applied only to 
> BE and eventually merge them to FE (struct snd_pcm_hardware) if 
> dai_link->dpcm_merged_* are set?

Probably, not sure why it's done like that.

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