[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176070026206.36020.13915370894346909307.b4-ty@kernel.org>
Date: Fri, 17 Oct 2025 12:24:22 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org,
Dario Binacchi <dario.binacchi@...rulasolutions.com>
Cc: linux-amarula@...rulasolutions.com, Frank Li <Frank.Li@....com>,
Sascha Hauer <s.hauer@...gutronix.de>, Shawn Guo <shawnguo@...nel.org>,
Michael Trimarchi <michael@...rulasolutions.com>,
Fabio Estevam <festevam@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Liam Girdwood <lgirdwood@...il.com>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Takashi Iwai <tiwai@...e.com>, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-sound@...r.kernel.org
Subject: Re: (subset) [RESEND PATCH 1/3] ASoC: mxs-saif: support usage with
simple-audio-card
On Wed, 24 Sep 2025 15:07:44 +0200, Dario Binacchi wrote:
> Add support for enabling MCLK output when using the simple-audio-card
> driver. In the sound/soc/mxs/mxs-sgtl5000.c use case, that driver
> handles MCLK enable/disable by calling mxs_saif_get_mclk() and
> mxs_saif_put_mclk() at probe/remove. This does not happen when the
> simple-audio-card driver is used. Extend the mxs-saif driver to enable
> MCLK output in that scenario.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: mxs-saif: support usage with simple-audio-card
commit: 1e570e77392f43a3cdab2849d1f81535f8a033e2
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
Powered by blists - more mailing lists