[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176373522063.27158.18194207753711685036.b4-ty@kernel.org>
Date: Fri, 21 Nov 2025 14:27:00 +0000
From: Mark Brown <broonie@...nel.org>
To: Biju Das <biju.das.jz@...renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Biju <biju.das.au@...il.com>
Cc: linux-sound@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org, Geert Uytterhoeven <geert+renesas@...der.be>
Subject: Re: [PATCH v3 0/2] RZ/G2L SSI full duplex fixes
On Fri, 14 Nov 2025 07:37:04 +0000, Biju wrote:
> The first patch in this series fixes audio channel swap issue because of
> half duplex to full duplex switching during the streaming that involves
> FIFO reset which drops the word leading to audio channel swap issue. The
> second patch fixes sample width value in the hw_params_cache::sample_width
>
> v2->v3:
> * Reduced the indentation by restructuring the tests in rz_ssi_start().
> * Retained the tag as change is trivial.
> v1->v2:
> * Split the fixes patches separate.
> * Improved code logic in rz_ssi_start() by using else if
> * Collected tags from Morimoto-san
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: renesas: rz-ssi: Fix channel swap issue in full duplex mode
commit: 52a525011cb8e293799a085436f026f2958403f9
[2/2] ASoC: renesas: rz-ssi: Fix rz_ssi_priv::hw_params_cache::sample_width
commit: 2bae7beda19f3b2dc6ab2062c94df19c27923712
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