[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176580710142.161056.6367112117497563338.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:58:21 +0900
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 v2 0/5] Add {24,32}-bit sample width support for RZ/G2L
SSI
On Fri, 14 Nov 2025 07:58:47 +0000, Biju wrote:
> Add support for 24 and 32-bit sample format width for RZ/G2L SoCs. Apart
> from this, the patch series includes some code cleanups.
>
> This patch series depend upon [1]
> [1] https://lore.kernel.org/all/20251114073709.4376-1-biju.das.jz@bp.renesas.com/T/#t
>
> v1->v2:
> * Split the feature patches separate.
> * Updated rz_ssi_clk_setup() to make ssicr assignment in single line for
> 24-bit sample width.
> * Dropped checking {24,32}-bit sample width in rz_ssi_dma_slave_config() as
> it is taken care by restructuring the test for 16-bit sample width.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: renesas: rz-ssi: Use dev variable in probe()
commit: d6c160d5e86f4e7354dd6c3154b7cb562abc6c7d
[2/5] ASoC: renesas: rz-ssi: Remove trailing comma in the terminator entry
commit: a472f0b157832fc91c83179b1628d8f660c84c82
[3/5] ASoC: renesas: rz-ssi: Move DMA configuration
commit: b541cb0a27dfa7504a8008320502f869c75f8bfc
[4/5] ASoC: renesas: rz-ssi: Add support for 24 bits sample width
commit: 9e10709f831408d948be66bc8f6329fa37a3dc82
[5/5] ASoC: renesas: rz-ssi: Add support for 32 bits sample width
commit: 124f6155f3d97b0e33f178c10a5138a42c8fd207
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