From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
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>,
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>,
"Rob Herring" <robh@kernel.org>,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>,
"Tariq Toukan" <tariqt@nvidia.com>
Subject: Re: [PATCH net-next v20 03/14] net: phy: Introduce PHY ports representation
Date: Fri, 28 Nov 2025 09:45:00 +0100 [thread overview]
Message-ID: <e18d4197-b06e-493a-a843-e195fbc46d6c@bootlin.com> (raw)
In-Reply-To: <aSiSxbE-XY_zxMBC@shell.armlinux.org.uk>
Hi Russell,
On 27/11/2025 19:04, Russell King (Oracle) wrote:
> On Thu, Nov 27, 2025 at 06:17:46PM +0100, Maxime Chevallier wrote:
>> Ethernet provides a wide variety of layer 1 protocols and standards for
>> data transmission. The front-facing ports of an interface have their own
>> complexity and configurability.
>>
>> Introduce a representation of these front-facing ports. The current code
>> is minimalistic and only support ports controlled by PHY devices, but
>> the plan is to extend that to SFP as well as raw Ethernet MACs that
>> don't use PHY devices.
>>
>> This minimal port representation allows describing the media and number
>> of pairs of a BaseT port. From that information, we can derive the
>> linkmodes usable on the port, which can be used to limit the
>> capabilities of an interface.
>>
>> For now, the port pairs and medium is derived from devicetree, defined
>> by the PHY driver, or populated with default values (as we assume that
>> all PHYs expose at least one port).
>>
>> The typical example is 100M ethernet. 100BaseT can work using only 2
>> pairs on a Cat 5 cables.
>
> Correction: 100BASE-TX. 100BASE-T, which covers the family of 100BASE-T
> media, includes 100BASE-T4 which is over all four pairs of the cable.
>
As Rob's bot made what appears at a first glance to be incorrect
comments, I'm not sure a resend is on the table yet. Do you want me to
send a v21 with the updated description ? I have the same question about
your comment on patch 2 :)
I'll gladly resend, but that'll be after the 24h cooldown.
Thanks a lot for taking a look a this,
Maxime
next prev parent reply other threads:[~2025-11-28 8:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 17:17 [PATCH net-next v20 00/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 01/14] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2025-11-27 18:16 ` Rob Herring (Arm)
2025-11-28 8:34 ` Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 02/14] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-11-27 18:02 ` Russell King (Oracle)
2025-11-27 17:17 ` [PATCH net-next v20 03/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-27 18:04 ` Russell King (Oracle)
2025-11-28 8:45 ` Maxime Chevallier [this message]
2025-11-27 17:17 ` [PATCH net-next v20 04/14] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 05/14] dt-bindings: net: dp83822: Deprecate ti,fiber-mode Maxime Chevallier
2025-11-27 18:16 ` Rob Herring (Arm)
2025-11-28 8:35 ` Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 06/14] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 07/14] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 08/14] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 09/14] net: phy: marvell: " Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 10/14] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 11/14] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 12/14] net: phy: qca807x: " Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 13/14] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 14/14] 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=e18d4197-b06e-493a-a843-e195fbc46d6c@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--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=mwojtas@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--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