From: Rob Herring <robh@kernel.org>
To: John Madieu <john.madieu.xa@bp.renesas.com>
Cc: prabhakar.mahadev-lad.rj@bp.renesas.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, krzk+dt@kernel.org, conor+dt@kernel.org,
geert+renesas@glider.be, biju.das.jz@bp.renesas.com,
claudiu.beznea@tuxon.dev, linux@armlinux.org.uk,
magnus.damm@gmail.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] dt-bindings: net: renesas-gbeth: Add port-id property
Date: Tue, 9 Dec 2025 14:34:06 -0600 [thread overview]
Message-ID: <20251209203406.GA1038446-robh@kernel.org> (raw)
In-Reply-To: <20251204164028.7321-3-john.madieu.xa@bp.renesas.com>
On Thu, Dec 04, 2025 at 05:40:27PM +0100, John Madieu wrote:
> Add optional port-id property to identify ethernet ports on RZ/V2H
> SoCs. The hardware doesn't provide unique identification registers
> for multiple ethernet instances, so this property allows explicit
> port identification from the device tree.
>
> Signed-off-by: John Madieu <john.madieu.xa@bp.renesas.com>
> ---
> .../bindings/net/renesas,rzv2h-gbeth.yaml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/renesas,rzv2h-gbeth.yaml b/Documentation/devicetree/bindings/net/renesas,rzv2h-gbeth.yaml
> index bd53ab300f500..bb59c6a925d3f 100644
> --- a/Documentation/devicetree/bindings/net/renesas,rzv2h-gbeth.yaml
> +++ b/Documentation/devicetree/bindings/net/renesas,rzv2h-gbeth.yaml
> @@ -117,6 +117,23 @@ properties:
> - description: AXI power-on system reset
> - description: AHB reset
>
> + renesas,port-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Optional unique port identifier for this ethernet interface.
> + Used for physical port identification (phys_port_id, phys_port_name).
> + If not specified, the ethernet alias index is used as fallback.
We already have a common way with aliases, why do we want a vendor
specific way?
> + minimum: 0
> + maximum: 255
> +
> + renesas,port-name:
> + $ref: /schemas/types.yaml#/definitions/string
> + description:
> + Optional custom name for the physical port. Used by
> + ndo_get_phys_port_name() for interface naming.
> + If not specified, "p<N>" format is used where N is the port-id
> + or ethernet alias index.
Other vendors don't want to name their ports?
Maybe 'label' should be used here (for both parts? Generally, the value
of label shouldn't be an ABI though. So if for example, software needs
to find the 'mgmt' port then we should find another way to define that.
Rob
next prev parent reply other threads:[~2025-12-09 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 16:40 [PATCH net-next 0/3] net: stmmac: add physical port identification support John Madieu
2025-12-04 16:40 ` [PATCH net-next 1/3] " John Madieu
2025-12-04 16:40 ` [PATCH net-next 2/3] dt-bindings: net: renesas-gbeth: Add port-id property John Madieu
2025-12-09 20:34 ` Rob Herring [this message]
2025-12-04 16:40 ` [PATCH net-next 3/3] net: stmmac: dwmac-renesas-gbeth: add physical port identification John Madieu
2025-12-04 16:55 ` [PATCH net-next 0/3] net: stmmac: add physical port identification support Krzysztof Kozlowski
2025-12-04 17:02 ` John Madieu
2025-12-04 17:09 ` Russell King (Oracle)
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 16:37 John Madieu
2025-12-04 16:37 ` [PATCH net-next 2/3] dt-bindings: net: renesas-gbeth: Add port-id property John Madieu
2025-12-04 16:31 [PATCH net-next 0/3] net: stmmac: add physical port identification support John Madieu
2025-12-04 16:31 ` [PATCH net-next 2/3] dt-bindings: net: renesas-gbeth: Add port-id property John Madieu
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=20251209203406.GA1038446-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=john.madieu.xa@bp.renesas.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.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;
as well as URLs for NNTP newsgroup(s).