From: Pavel Machek <pavel@denx.de>
To: ovidiu.panait.rb@renesas.com
Cc: cip-dev@lists.cip-project.org, nobuhiro.iwamatsu.x90@mail.toshiba
Subject: Re: [cip-dev] [PATCH 6.1.y-cip 06/12] dt-bindings: serial: renesas: Document RZ/V2N SCIF
Date: Thu, 4 Dec 2025 11:45:16 +0100 [thread overview]
Message-ID: <aTFmPKKMoErVHwg3@duo.ucw.cz> (raw)
In-Reply-To: <20251203153757.32977-7-ovidiu.panait.rb@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Hi!
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> commit 5eb2d4b3e9a19f08e0ccbb81e0fbfa61de229345 upstream.
>
> Document SCIF bindings for the Renesas RZ/V2N (a.k.a R9A09G056) SoC.
> The SCIF interface in Renesas RZ/V2N is identical to the one available
> in RZ/V2H(P), so `renesas,scif-r9a09g057` will be used as a fallback,
> allowing reuse of the existing driver without modifications.
I'd expect some kind of generic fallback, not reusing id from other
hardware.
Best regards,
Pavel
> +++ b/Documentation/devicetree/bindings/serial/renesas,scif.yaml
> @@ -83,6 +83,7 @@ properties:
> - items:
> - enum:
> - renesas,scif-r9a09g047 # RZ/G3E
> + - renesas,scif-r9a09g056 # RZ/V2N
> - const: renesas,scif-r9a09g057 # RZ/V2H fallback
>
> reg:
--
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-12-04 10:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 15:37 [PATCH 6.1.y-cip 00/12] Add initial support for RZ/V2N EVK Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 01/12] dt-bindings: soc: renesas: Move renesas.yaml from arm to soc Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 02/12] dt-bindings: soc: renesas: Document Renesas RZ/V2N SoC variants and EVK Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 03/12] soc: renesas: Add config option for RZ/V2N (R9A09G056) SoC Ovidiu Panait
2025-12-04 10:41 ` [cip-dev] " Pavel Machek
2025-12-03 15:37 ` [PATCH 6.1.y-cip 04/12] dt-bindings: soc: renesas: Document SYS for RZ/V2N SoC Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 05/12] soc: renesas: rz-sysc: Add SoC identification " Ovidiu Panait
2025-12-04 10:43 ` [cip-dev] " Pavel Machek
2025-12-03 15:37 ` [PATCH 6.1.y-cip 06/12] dt-bindings: serial: renesas: Document RZ/V2N SCIF Ovidiu Panait
2025-12-04 10:45 ` Pavel Machek [this message]
2025-12-03 15:37 ` [PATCH 6.1.y-cip 07/12] dt-bindings: mmc: renesas,sdhi: Document RZ/V2N support Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 08/12] dt-bindings: clock: renesas: Document RZ/V2N SoC CPG Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 09/12] clk: renesas: rzv2h: Add support for RZ/V2N SoC Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 10/12] arm64: dts: renesas: Add initial SoC DTSI for RZ/V2N Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 11/12] arm64: dts: renesas: Add initial device tree for RZ/V2N EVK Ovidiu Panait
2025-12-03 15:37 ` [PATCH 6.1.y-cip 12/12] arm64: dts: renesas: Add CN15 eMMC and SD overlays for RZ/V2H and RZ/V2N EVKs Ovidiu Panait
2025-12-04 11:04 ` [cip-dev] [PATCH 6.1.y-cip 00/12] Add initial support for RZ/V2N EVK Pavel Machek
2025-12-05 11:33 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aTFmPKKMoErVHwg3@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=ovidiu.panait.rb@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox