Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: linux-arm-msm@vger.kernel.org,
	"Russell King" <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	"Oleksij Rempel" <o.rempel@pengutronix.de>,
	"Antoine Tenart" <atenart@kernel.org>,
	"Marek Behún" <kabel@kernel.org>,
	"Köry Maincent" <kory.maincent@bootlin.com>,
	"Herve Codina" <herve.codina@bootlin.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	mwojtas@chromium.org, devicetree@vger.kernel.org,
	"Romain Gantois" <romain.gantois@bootlin.com>,
	"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	linux-kernel@vger.kernel.org, "Paolo Abeni" <pabeni@redhat.com>,
	"Nicolò Veronese" <nicveronese@gmail.com>,
	thomas.petazzoni@bootlin.com, "Andrew Lunn" <andrew@lunn.ch>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Eric Dumazet" <edumazet@google.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Daniel Golle" <daniel@makrotopia.org>,
	"Tariq Toukan" <tariqt@nvidia.com>,
	"Simon Horman" <horms@kernel.org>,
	"Vladimir Oltean" <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net-next v22 01/14] dt-bindings: net: Introduce the ethernet-connector description
Date: Tue, 13 Jan 2026 08:46:14 -0600	[thread overview]
Message-ID: <176831557374.3740779.1775436338458125748.robh@kernel.org> (raw)
In-Reply-To: <20260108080041.553250-2-maxime.chevallier@bootlin.com>


On Thu, 08 Jan 2026 09:00:26 +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      | 56 +++++++++++++++++++
>  .../devicetree/bindings/net/ethernet-phy.yaml | 18 ++++++
>  MAINTAINERS                                   |  1 +
>  3 files changed, 75 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/net/ethernet-connector.yaml
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2026-01-13 14:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  8:00 [PATCH net-next v22 00/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 01/14] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2026-01-13 14:46   ` Rob Herring (Arm) [this message]
2026-01-08  8:00 ` [PATCH net-next v22 02/14] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2026-01-08 16:53   ` Andrew Lunn
2026-01-08  8:00 ` [PATCH net-next v22 03/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2026-01-08 16:59   ` Andrew Lunn
2026-01-08  8:00 ` [PATCH net-next v22 04/14] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 05/14] dt-bindings: net: dp83822: Deprecate ti,fiber-mode Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 06/14] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 07/14] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 08/14] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 09/14] net: phy: marvell: " Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 10/14] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 11/14] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 12/14] net: phy: qca807x: " Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 13/14] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2026-01-08  8:00 ` [PATCH net-next v22 14/14] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
2026-01-14  3:00 ` [PATCH net-next v22 00/14] net: phy: Introduce PHY ports representation 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=176831557374.3740779.1775436338458125748.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=tariqt@nvidia.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