[PATCH v2] spi: dt-bindings: renesas,rzv2h-rspi: Document RZ/V2N SoC support

Prabhakar posted 1 patch 5 days, 8 hours ago
Documentation/devicetree/bindings/spi/renesas,rzv2h-rspi.yaml | 3 +++
1 file changed, 3 insertions(+)
[PATCH v2] spi: dt-bindings: renesas,rzv2h-rspi: Document RZ/V2N SoC support
Posted by Prabhakar 5 days, 8 hours ago
From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>

Document the RSPI controller on the Renesas RZ/V2N SoC. The block is
compatible with the RSPI implementation found on the RZ/V2H(P) family.

Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
v1-v2:
- Added the item after enum for RZ/V2H and RZ/T2H as suggested by Geert.
- Updated the commit header to match with the subsystem naming conventions.
- Added Reviewed-by and Acked-by tags.
---
 Documentation/devicetree/bindings/spi/renesas,rzv2h-rspi.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/spi/renesas,rzv2h-rspi.yaml b/Documentation/devicetree/bindings/spi/renesas,rzv2h-rspi.yaml
index be62fd0841aa..0253c04c28cb 100644
--- a/Documentation/devicetree/bindings/spi/renesas,rzv2h-rspi.yaml
+++ b/Documentation/devicetree/bindings/spi/renesas,rzv2h-rspi.yaml
@@ -15,6 +15,9 @@ properties:
       - enum:
           - renesas,r9a09g057-rspi # RZ/V2H(P)
           - renesas,r9a09g077-rspi # RZ/T2H
+      - items:
+          - const: renesas,r9a09g056-rspi # RZ/V2N
+          - const: renesas,r9a09g057-rspi
       - items:
           - const: renesas,r9a09g087-rspi # RZ/N2H
           - const: renesas,r9a09g077-rspi # RZ/T2H
-- 
2.52.0
Re: [PATCH v2] spi: dt-bindings: renesas,rzv2h-rspi: Document RZ/V2N SoC support
Posted by Mark Brown 4 days, 10 hours ago
On Wed, 26 Nov 2025 13:16:19 +0000, Prabhakar wrote:
> Document the RSPI controller on the Renesas RZ/V2N SoC. The block is
> compatible with the RSPI implementation found on the RZ/V2H(P) family.
> 
> 

Applied to

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

Thanks!

[1/1] spi: dt-bindings: renesas,rzv2h-rspi: Document RZ/V2N SoC support
      commit: 043cc033451530f81d7fe791dcc29874f6a147fd

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
Re: [PATCH v2] spi: dt-bindings: renesas,rzv2h-rspi: Document RZ/V2N SoC support
Posted by Mark Brown 5 days, 2 hours ago
On Wed, 26 Nov 2025 13:16:19 +0000, Prabhakar wrote:
> Document the RSPI controller on the Renesas RZ/V2N SoC. The block is
> compatible with the RSPI implementation found on the RZ/V2H(P) family.
> 
> 

Applied to

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

Thanks!

[1/1] spi: dt-bindings: renesas,rzv2h-rspi: Document RZ/V2N SoC support
      commit: 043cc033451530f81d7fe791dcc29874f6a147fd

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