Re: [PATCH 0/6] ASoC: codecs: lpass-macros: switch regcache to REGCACHE_MAPLE
From: Mark Brown
Date: Tue Sep 08 2026 - 15:57:54 EST
On Tue, 08 Sep 2026 09:28:00 +0100, Srinivas Kandagatla wrote:
> ASoC: codecs: lpass-macros: switch regcache to REGCACHE_MAPLE
>
> Move all four LPASS codec macros (rx/tx/va/wsa) from REGCACHE_FLAT to
> REGCACHE_MAPLE, and fix a latent v2.5 Compander1 addressing bug that
> the flat cache had been absorbing.
>
> REGCACHE_FLAT hides missing-default reads by returning the zero-
> initialised cache slot instead of doing a bus read. The caller can't
> tell that value apart from a real hardware value, so any un-defaulted,
> readable, non-volatile register that gets read silently returns wrong
> data. Since commit e062bdfdd6ad ("regmap: warn users about
> uninitialized flat cache") regmap dev_warn_once()s the first such
> miss, but any subsequent miss stays silent.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.4
Thanks!
[1/6] ASoC: codecs: lpass-wsa-macro: use v2.5 Compander1 addresses on v2.5+
https://git.kernel.org/broonie/sound/c/233d36a96009
[2/6] ASoC: codecs: lpass-{rx,wsa}-macro: sort reg_defaults before regmap init
https://git.kernel.org/broonie/sound/c/246c785491bb
[3/6] ASoC: codecs: lpass-wsa-macro: switch cache to REGCACHE_MAPLE
https://git.kernel.org/broonie/sound/c/ce7164c89b5c
[4/6] ASoC: codecs: lpass-rx-macro: switch cache to REGCACHE_MAPLE
https://git.kernel.org/broonie/sound/c/384bd7cf4053
[5/6] ASoC: codecs: lpass-tx-macro: switch cache to REGCACHE_MAPLE
https://git.kernel.org/broonie/sound/c/8ed9306885eb
[6/6] ASoC: codecs: lpass-va-macro: switch cache to REGCACHE_MAPLE
https://git.kernel.org/broonie/sound/c/322a9e0850b4
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