From: "Rob Herring (Arm)" <robh@kernel.org>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: "Biju Das" <biju.das.jz@bp.renesas.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Paolo Abeni" <pabeni@redhat.com>,
"Clément Léger" <clement.leger@bootlin.com>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Russell King" <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Fabrizio Castro" <fabrizio.castro.jz@renesas.com>,
linux-renesas-soc@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Magnus Damm" <magnus.damm@gmail.com>
Subject: Re: [PATCH net-next v3 1/9] dt-bindings: net: pcs: renesas,rzn1-miic: Add RZ/T2H and RZ/N2H support
Date: Sun, 14 Sep 2025 19:25:00 -0500 [thread overview]
Message-ID: <175789589955.2309369.4610960260845760288.robh@kernel.org> (raw)
In-Reply-To: <20250910204132.319975-2-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Wed, 10 Sep 2025 21:41:22 +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Add device tree binding support for RZ/T2H and RZ/N2H SoCs to the
> existing RZ/N1 MIIC converter binding. These SoCs share similar MIIC
> functionality but have architectural differences that require schema
> updates.
>
> Add new compatible strings "renesas,r9a09g077-miic" for RZ/T2H and
> "renesas,r9a09g087-miic" for RZ/N2H, with the latter falling back to
> the RZ/T2H variant. The new SoCs require reset support with two reset
> lines for converter register reset and converter reset, which are not
> present on RZ/N1.
>
> Update port configurations to accommodate the different architectures.
> RZ/N1 supports 5 ports numbered 1-5 with complex input mappings
> covering indices 0-13, while RZ/T2H and RZ/N2H support 4 ports
> numbered 0-3 with simplified input mappings covering indices 0-8.
> Extend the switch port configuration property to support value 0 for
> the new SoCs.
>
> Add a new dt-bindings header file with media interface connection
> matrix constants that map GMAC, ESC, and ETHSW ports to numeric
> identifiers for use with RZ/T2H and RZ/N2H device trees.
>
> Update DT schema validation to ensure proper port numbering and input
> mappings per SoC variant.
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> v2->v3:
> - Added Tested-by tag.
>
> v1->v2:
> - Dropped regx in title and description.
> - As done for other IPs used T2H compatible as a fallback for N2H.
> - Renamed pcs-rzt2h-miic.h -> renesas,r9a09g077-pcs-miic.h
> - Added matrix table in the new header file.
> - Corrected the resets check for RZ/N1.
> - Updated the commit message.
> ---
> .../bindings/net/pcs/renesas,rzn1-miic.yaml | 177 +++++++++++++-----
> .../net/renesas,r9a09g077-pcs-miic.h | 36 ++++
> 2 files changed, 165 insertions(+), 48 deletions(-)
> create mode 100644 include/dt-bindings/net/renesas,r9a09g077-pcs-miic.h
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-09-15 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 20:41 [PATCH net-next v3 0/9] Add PCS support for Renesas RZ/{T2H,N2H} SoCs Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 1/9] dt-bindings: net: pcs: renesas,rzn1-miic: Add RZ/T2H and RZ/N2H support Prabhakar
2025-09-15 0:25 ` Rob Herring (Arm) [this message]
2025-09-10 20:41 ` [PATCH net-next v3 2/9] net: pcs: rzn1-miic: Drop trailing comma from of_device_id table Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 3/9] net: pcs: rzn1-miic: Add missing include files Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 4/9] net: pcs: rzn1-miic: Move configuration data to SoC-specific struct Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 5/9] net: pcs: rzn1-miic: move port range handling into SoC data Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 6/9] net: pcs: rzn1-miic: Make switch mode mask SoC-specific Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 7/9] net: pcs: rzn1-miic: Add support to handle resets Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 8/9] net: pcs: rzn1-miic: Add per-SoC control for MIIC register unlock/lock Prabhakar
2025-09-10 20:41 ` [PATCH net-next v3 9/9] net: pcs: rzn1-miic: Add RZ/T2H MIIC support Prabhakar
2025-09-16 0:50 ` [PATCH net-next v3 0/9] Add PCS support for Renesas RZ/{T2H,N2H} SoCs patchwork-bot+netdevbpf
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=175789589955.2309369.4610960260845760288.robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=biju.das.jz@bp.renesas.com \
--cc=clement.leger@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®