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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180626115526.GC1779@sirena.org.uk>
Date:   Tue, 26 Jun 2018 12:55:26 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Jerome Brunet <jbrunet@...libre.com>
Cc:     jiada_wang@...tor.com, lgirdwood@...il.com, perex@...ex.cz,
        tiwai@...e.com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org
Subject: Re: [alsa-devel] [PATCH 1/1] ASoC: soc-pcm: DPCM cares BE channel
 constraint

On Tue, Jun 26, 2018 at 12:18:38PM +0200, Jerome Brunet wrote:
> On Wed, 2018-06-20 at 18:25 +0900, jiada_wang@...tor.com wrote:

> > +	/* DPCM used FE & BE merged channel */
> > +	unsigned int dpcm_merged_chan:1;

> Jiada, Mark,

> Do you think we could extend this flag to let the link choose whether the merge
> should be performed on the codec dais (as done here) or on the backend cpu dais
> ?

> I have more less the same need as Jiada but since my card uses multicodec links,
> merging on the codec dais does not work for me.

> Like in soc_pcm_init_runtime_hw(), we can't enforce channels min/max based on
> the codec when there is multiple codecs on the link.

Ugh, probably that'd work.  The ideal thing would be to remove DPCM but
we're stuck with it for the time being :(

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ