From: "Rob Herring (Arm)" <robh@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: "Romain Gantois" <romain.gantois@bootlin.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Nicolò Veronese" <nicveronese@gmail.com>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>,
davem@davemloft.net, linux-arm-msm@vger.kernel.org,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
netdev@vger.kernel.org,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Russell King" <linux@armlinux.org.uk>,
devicetree@vger.kernel.org, "Simon Horman" <horms@kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Eric Dumazet" <edumazet@google.com>,
"Marek Behún" <kabel@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Herve Codina" <herve.codina@bootlin.com>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, mwojtas@chromium.org,
"Antoine Tenart" <atenart@kernel.org>,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
"Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>
Subject: Re: [PATCH net-next v16 01/15] dt-bindings: net: Introduce the ethernet-connector description
Date: Tue, 18 Nov 2025 08:50:26 -0600 [thread overview]
Message-ID: <176347742560.3223087.13861755734926034941.robh@kernel.org> (raw)
In-Reply-To: <20251113081418.180557-2-maxime.chevallier@bootlin.com>
On Thu, 13 Nov 2025 09:14:03 +0100, Maxime Chevallier wrote:
> The ability to describe the physical ports of Ethernet devices is useful
> to describe multi-port devices, as well as to remove any ambiguity with
> regard to the nature of the port.
>
> Moreover, describing ports allows for a better description of features
> that are tied to connectors, such as PoE through the PSE-PD devices.
>
> Introduce a binding to allow describing the ports, for now with 2
> attributes :
>
> - The number of pairs, which is a quite generic property that allows
> differentating between multiple similar technologies such as BaseT1
> and "regular" BaseT (which usually means BaseT4).
>
> - The media that can be used on that port, such as BaseT for Twisted
> Copper, BaseC for coax copper, BaseS/L for Fiber, BaseK for backplane
> ethernet, etc. This allows defining the nature of the port, and
> therefore avoids the need for vendor-specific properties such as
> "micrel,fiber-mode" or "ti,fiber-mode".
>
> The port description lives in its own file, as it is intended in the
> future to allow describing the ports for phy-less devices.
>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> ---
> .../bindings/net/ethernet-connector.yaml | 57 +++++++++++++++++++
> .../devicetree/bindings/net/ethernet-phy.yaml | 18 ++++++
> MAINTAINERS | 1 +
> 3 files changed, 76 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/ethernet-connector.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-11-18 14:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 8:14 [PATCH net-next v16 00/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 01/15] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2025-11-13 13:11 ` Andrew Lunn
2025-11-15 12:52 ` Christophe Leroy
2025-11-18 14:50 ` Rob Herring (Arm) [this message]
2025-11-13 8:14 ` [PATCH net-next v16 02/15] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-11-15 12:52 ` Christophe Leroy
2025-11-19 3:15 ` Jakub Kicinski
2025-11-19 13:29 ` Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 03/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-13 13:13 ` Andrew Lunn
2025-11-15 12:53 ` Christophe Leroy
2025-11-19 3:15 ` Jakub Kicinski
2025-11-19 13:30 ` Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 04/15] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 05/15] dt-bindings: net: dp83822: Deprecate ti,fiber-mode Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 06/15] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-11-15 12:53 ` Christophe Leroy
2025-11-13 8:14 ` [PATCH net-next v16 07/15] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 08/15] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 09/15] net: phy: marvell: " Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 10/15] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-11-15 12:53 ` Christophe Leroy
2025-11-13 8:14 ` [PATCH net-next v16 11/15] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 12/15] net: phy: qca807x: " Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 13/15] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 14/15] net: phy: dp83822: Add SFP support through the phy_port interface Maxime Chevallier
2025-11-13 8:14 ` [PATCH net-next v16 15/15] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
2025-11-19 3:17 ` Jakub Kicinski
2025-11-19 13:31 ` Maxime Chevallier
2025-11-15 12:55 ` [PATCH net-next v16 00/15] net: phy: Introduce PHY ports representation Christophe Leroy
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=176347742560.3223087.13861755734926034941.robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=mwojtas@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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®