Re: [PATCH 0/6] ASoC: meson: axg fixes and clean-up

From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
	 Jerome Brunet <jbrunet@baylibre.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	 linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 0/6] ASoC: meson: axg fixes and clean-up
Date: Mon, 26 Feb 2024 19:28:23 +0000	[thread overview]
Message-ID: <170897570345.121037.4947854271427341182.b4-ty@kernel.org> (raw)
In-Reply-To: <20240223175116.2005407-1-jbrunet@baylibre.com>

On Fri, 23 Feb 2024 18:51:06 +0100, Jerome Brunet wrote:
> This are various fixes and clean up gathered while working on Amlogic audio
> support. These help better handle higher and unusual clock configuration
> for TDM, SPDIF or PDM.
> 
> Jerome Brunet (6):
>   ASoC: meson: axg-tdm-interface: fix mclk setup without mclk-fs
>   ASoC: meson: axg-tdm-interface: add frame rate constraint
>   ASoC: meson: axg-tdm-interface: update error format error traces
>   ASoC: meson: axg-spdifin: use max width for rate detection
>   ASoC: meson: axg-fifo: take continuous rates
>   ASoC: meson: axg-fifo: use FIELD helpers
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: meson: axg-tdm-interface: fix mclk setup without mclk-fs
      commit: e3741a8d28a1137f8b19ae6f3d6e3be69a454a0a
[2/6] ASoC: meson: axg-tdm-interface: add frame rate constraint
      commit: 59c6a3a43b221cc2a211181b1298e43b2c2df782
[3/6] ASoC: meson: axg-tdm-interface: update error format error traces
      commit: 48bbec092e4cf2fe1d3f81a889ec176e83aee695
[4/6] ASoC: meson: axg-spdifin: use max width for rate detection
      commit: a2417b6c0f9c3cc914c88face9abd6e9b9d76c00
[5/6] ASoC: meson: axg-fifo: take continuous rates
      commit: 8b410b3c46128f1eee78f1182731b84d9d2e79ef
[6/6] ASoC: meson: axg-fifo: use FIELD helpers
      (no commit info)

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