linux-kernel - Re: [PATCH AUTOSEL 6.11 109/244] ASoC: soc-pcm: Indicate warning if dpcm_playback/capture were used for availability limition

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: <ZvP-YQuXTyGDfb8x@finisterre.sirena.org.uk>
Date: Wed, 25 Sep 2024 14:13:21 +0200
From: Mark Brown <broonie@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
	Jerome Brunet <jbrunet@...libre.com>, lgirdwood@...il.com,
	perex@...ex.cz, tiwai@...e.com, linux-sound@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.11 109/244] ASoC: soc-pcm: Indicate warning if
 dpcm_playback/capture were used for availability limition

On Wed, Sep 25, 2024 at 07:25:30AM -0400, Sasha Levin wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
> 
> [ Upstream commit fd69dfe6789f4ed46d1fdb52e223cff83946d997 ]
> 
> I have been wondering why DPCM needs special flag (= dpcm_playback/capture)
> to use it. Below is the history why it was added to ASoC.

...

> Because of these history, this dpcm_xxx is unneeded flag today. But because
> we have been used it for 10 years since (B), it may have been used
> differently. For example some DAI available both playback/capture, but it
> set dpcm_playback flag only, in this case dpcm_xxx flag is used as
> availability limitation. We can use playback_only flag instead in this
> case, but it is very difficult to find such DAI today.
> 
> Let's add grace time to remove dpcm_playback/capture flag.
> 
> This patch don't use dpcm_xxx flag anymore, and indicates warning to use
> xxx_only flag if both playback/capture were available but using only
> one of dpcm_xxx flag, and not using xxx_only flag.

This is a cleanup/refactoring preparation patch, I can see no reason why
it would be considered for stable.

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