Re: [PATCH v3 0/7] ASoC: codecs: aw88261: fixes and cleanup

[Mark Brown <broonie@kernel.org>]

On Fri, 29 May 2026 17:05:07 -0300, Val Packett wrote:
> ASoC: codecs: aw88261: fixes and cleanup
> 
> The Awinic smart speaker/amp drivers were merged in a very
> "downstream-brained" state, where configuration was only really
> determined by the binary "firmware" (register list) file instead
> of properly participating in the ASoC system. Let's start
> untangling this mess. This series makes aw88261 actually usable
> on devices like fairphone-fp5, motorola-dubai and xiaomi-pipa.
> 
> [...]

Applied to

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

Thanks!

[1/7] ASoC: codecs: aw88261: support changing sample rate and bit width
      https://git.kernel.org/broonie/sound/c/1b92b0673d5e
[2/7] ASoC: codecs: aw88261: add TDM support
      https://git.kernel.org/broonie/sound/c/33f917e18f39
[3/7] ASoC: codecs: aw88261: reduce log spam
      https://git.kernel.org/broonie/sound/c/d90c361af215
[4/7] ASoC: codecs: aw88261: remove fade in/out on start/stop
      https://git.kernel.org/broonie/sound/c/edf01bc1c698
[5/7] ASoC: codecs: aw88261: remove async start
      https://git.kernel.org/broonie/sound/c/caea99ac809d
[6/7] ASoC: codecs: aw88261: fix incorrect masks for boost regs
      https://git.kernel.org/broonie/sound/c/79c053a1ff9d
[7/7] ASoC: codecs: aw88261: make volume control usable
      https://git.kernel.org/broonie/sound/c/9b2929eed4d2

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