Re: [PATCH 00/10] ASoC: Intel: avs: Mute and multi-channel controls support

[Mark Brown <broonie@xxxxxxxxxx>]

On Mon, 17 Feb 2025 11:21:05 +0100, Cezary Rojewski wrote:
> Note: the patchset DOES provide functional changes to the ASoC
> framework.
> 
> Current kcontrols loaded with ASoC topology allow for mono or stereo
> configuration only. To expand this and provide support to up to 8
> channels, first address the limitations found within the ASoC core and
> then update the user (avs-driver) so that it can utilize these new
> functionality. The 8 channels max stems from SND_SOC_TPLG_MAX_CHAN
> constant which is part of UAPI - asoc.h.
> 
> [...]

Applied to

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

Thanks!

[01/10] ASoC: topology: Create kcontrols based on their type
        commit: 758beab0252912395efb79f34095c5ae7e3e58b1
[02/10] ASoC: topology: Save num_channels value for mixer controls
        commit: 81eb3a2bd273b84fa9808e6b13b533f9c55e16eb
[03/10] ASoC: Intel: avs: Make PEAKVOL configurable from topology
        commit: 28feec15fa285e561c626b3490bc5a10f5d177c8
[04/10] ASoC: Intel: avs: Add volume control for GAIN module
        commit: 4c43a930e3e165ca6890147a309508ccb6768faf
[05/10] ASoC: Intel: avs: Update VOLUME and add MUTE IPCs
        commit: 10188a25c9b5944c0a912482011b484b7c2e22d4
[06/10] ASoC: Intel: avs: New volume control operations
        commit: c321a4d705a31a50d7580516422aaa5b853e7602
[07/10] ASoC: Intel: avs: Move to the new control operations
        commit: 4c32ebcc8650ce506632a32136993c85537fb01a
[08/10] ASoC: Intel: avs: Add support for mute for PEAKVOL and GAIN
        commit: a4217a03686989c4a79530fe54fa17576aff7330
[09/10] ASoC: Intel: avs: Honor the invert flag for mixer controls
        commit: 76e013152891a69dfe68a28706a51a7df9ed4c42
[10/10] ASoC: Intel: avs: Support multi-channel PEAKVOL instantiation
        commit: a9409fcb979eaff401837b955b234ca1ee05fdbd

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