Re: [PATCH 0/6] ASoC: Fix controls that write another control's bits

[Mark Brown]

On Thu, 08 Oct 2026 22:09:46 +0900, HyeongJun An wrote:
> ASoC: Fix controls that write another control's bits
> 
> In the es8316 thread Mark suggested checking at registration time for
> controls whose register fields overlap [1]. Before adding such a check,
> I wanted to see what it would find in the tree today.
> 
> A script expanded the control tables of every ASoC driver built by
> allmodconfig and looked for two controls in one table whose register
> fields overlap. It found 80 pairs in 33 drivers. Most are real bugs.
> The rest are deliberate, where two names drive the same field, such as
> the AC and DRC mode thresholds in sta32x.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3

Thanks!

[1/6] ASoC: cs42l56: Put the Limiter Cushion control on the limiter register
      https://git.kernel.org/broonie/misc/c/203436d2aeb7
[2/6] ASoC: cs42l52: Fix the NG Type Switch bit
      https://git.kernel.org/broonie/misc/c/8b08b98796d2
[3/6] ASoC: pcm3168a: Fix the DAC zero flag polarity bit
      https://git.kernel.org/broonie/misc/c/b26edc925c1c
[4/6] ASoC: max98371: Fix the Speaker DHT Min Volume bits
      https://git.kernel.org/broonie/misc/c/f7934340c56a
[5/6] ASoC: wm8978: Fix the 128x oversampling switch bits
      https://git.kernel.org/broonie/misc/c/d0567ca9a2fa
[6/6] ASoC: nau8822: Fix the 128x oversampling switch bits
      https://git.kernel.org/broonie/misc/c/4db45fc1da3d

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark