From: Rob Herring <robh@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
thomas.petazzoni@bootlin.com, "Andrew Lunn" <andrew@lunn.ch>,
"Jakub Kicinski" <kuba@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Herve Codina" <herve.codina@bootlin.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Marek Behún" <kabel@kernel.org>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Nicolò Veronese" <nicveronese@gmail.com>,
"Simon Horman" <horms@kernel.org>,
mwojtas@chromium.org, "Antoine Tenart" <atenart@kernel.org>,
devicetree@vger.kernel.org, "Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>
Subject: Re: [PATCH net-next v7 01/15] dt-bindings: net: Introduce the ethernet-connector description
Date: Tue, 8 Jul 2025 10:57:33 -0500 [thread overview]
Message-ID: <20250708155733.GA481837-robh@kernel.org> (raw)
In-Reply-To: <20250630143315.250879-2-maxime.chevallier@bootlin.com>
On Mon, Jun 30, 2025 at 04:33:00PM +0200, 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 lanes, 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 | 47 +++++++++++++++++++
> .../devicetree/bindings/net/ethernet-phy.yaml | 18 +++++++
> MAINTAINERS | 1 +
> 3 files changed, 66 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/ethernet-connector.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/ethernet-connector.yaml b/Documentation/devicetree/bindings/net/ethernet-connector.yaml
> new file mode 100644
> index 000000000000..2aa28e6c1523
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/ethernet-connector.yaml
> @@ -0,0 +1,47 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/ethernet-connector.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Generic Ethernet Connector
> +
> +maintainers:
> + - Maxime Chevallier <maxime.chevallier@bootlin.com>
> +
> +description:
> + An Ethernet Connectr represents the output of a network component such as
typo
> + a PHY, an Ethernet controller with no PHY, or an SFP module.
> +
> +properties:
> +
> + lanes:
> + description:
> + Defines the number of lanes on the port, that is the number of physical
> + channels used to convey the data with the link partner.
> + $ref: /schemas/types.yaml#/definitions/uint32
maximum?
Or I'd guess this is power of 2 values?
> +
> + media:
> + description:
> + The mediums, as defined in 802.3, that can be used on the port.
> + items:
> + enum:
> + - BaseT
> + - BaseK
> + - BaseS
> + - BaseC
> + - BaseL
> + - BaseD
> + - BaseE
> + - BaseF
> + - BaseV
> + - BaseMLD
> + - BaseX
This can be multiple values? But then how does one know what is actually
attached?
> +
> +required:
> + - lanes
> + - media
> +
> +additionalProperties: true
> +
> +...
> diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> index 71e2cd32580f..6bf670beb66f 100644
> --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> @@ -277,6 +277,17 @@ properties:
>
> additionalProperties: false
>
> + mdi:
> + type: object
> +
> + patternProperties:
> + '^connector-[a-f0-9]+$':
> + $ref: /schemas/net/ethernet-connector.yaml#
> +
> + unevaluatedProperties: false
> +
> + additionalProperties: false
> +
> required:
> - reg
>
> @@ -313,5 +324,12 @@ examples:
> default-state = "keep";
> };
> };
> +
> + mdi {
> + connector-0 {
> + lanes = <2>;
> + media = "BaseT";
> + };
> + };
> };
> };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index bb9df569a3ff..20806cfc1003 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8946,6 +8946,7 @@ R: Russell King <linux@armlinux.org.uk>
> L: netdev@vger.kernel.org
> S: Maintained
> F: Documentation/ABI/testing/sysfs-class-net-phydev
> +F: Documentation/devicetree/bindings/net/ethernet-connector.yaml
> F: Documentation/devicetree/bindings/net/ethernet-phy.yaml
> F: Documentation/devicetree/bindings/net/mdio*
> F: Documentation/devicetree/bindings/net/qca,ar803x.yaml
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-07-08 16:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 14:32 [PATCH net-next v7 00/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 01/15] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2025-07-08 15:57 ` Rob Herring [this message]
2025-07-09 6:36 ` Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 02/15] net: ethtool: common: Indicate that BaseT works on up to 4 lanes Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 03/15] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 04/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-07-01 13:02 ` Simon Horman
2025-07-01 13:06 ` Maxime Chevallier
2025-07-14 19:08 ` Dan Carpenter
2025-06-30 14:33 ` [PATCH net-next v7 05/15] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 06/15] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 07/15] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 08/15] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 09/15] net: phy: marvell: " Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 10/15] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 11/15] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 12/15] net: phy: qca807x: " Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 13/15] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 14/15] net: phy: dp83822: Add SFP support through the phy_port interface Maxime Chevallier
2025-06-30 14:33 ` [PATCH net-next v7 15/15] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
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=20250708155733.GA481837-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.