[PATCH v4 0/2] Add Renesas RZ/G3L RSPI support

Biju posted 2 patches 5 days, 10 hours ago
.../bindings/spi/renesas,rzv2h-rspi.yaml      | 29 +++++++++++++++++++
drivers/spi/spi-rzv2h-rspi.c                  |  8 +++++
2 files changed, 37 insertions(+)
[PATCH v4 0/2] Add Renesas RZ/G3L RSPI support
Posted by Biju 5 days, 10 hours ago
From: Biju Das <biju.das.jz@bp.renesas.com>

This patch series adds binding and driver support for RSPI IP found on the
RZ/G3L SoC. The RSPI is compatible with RZ/V2H RSPI, but has 2 clocks
compared to 3 on RZ/V2H.

v3->v4:
 * Added a blank line before the dmas property in bindings.
 * Collected tags for binding patch.
v2->v3:
 * Added ordered DMA names for the dma-names property.
 * Dropped the tag from bindings as there is a change related to dma-names
   property.
v1->v2:
 * Rebased to next
 * Collected tags

Biju Das (2):
  dt-bindings: spi: renesas,rzv2h-rspi: Document RZ/G3L SoC
  spi: rzv2h-rspi: Add support for RZ/G3L (R9A08G046)

 .../bindings/spi/renesas,rzv2h-rspi.yaml      | 29 +++++++++++++++++++
 drivers/spi/spi-rzv2h-rspi.c                  |  8 +++++
 2 files changed, 37 insertions(+)

-- 
2.43.0
Re: [PATCH v4 0/2] Add Renesas RZ/G3L RSPI support
Posted by Mark Brown 5 days, 4 hours ago
On Wed, 08 Apr 2026 09:54:13 +0100, Biju wrote:
> Add Renesas RZ/G3L RSPI support
> 
> From: Biju Das <biju.das.jz@bp.renesas.com>
> 
> This patch series adds binding and driver support for RSPI IP found on the
> RZ/G3L SoC. The RSPI is compatible with RZ/V2H RSPI, but has 2 clocks
> compared to 3 on RZ/V2H.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.1

Thanks!

[1/2] dt-bindings: spi: renesas,rzv2h-rspi: Document RZ/G3L SoC
      https://git.kernel.org/broonie/spi/c/5277c291968d
[2/2] spi: rzv2h-rspi: Add support for RZ/G3L (R9A08G046)
      https://git.kernel.org/broonie/spi/c/9be114351647

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