From: Andrew Lunn <andrew@lunn.ch>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, "Jakub Kicinski" <kuba@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Herve Codina" <herve.codina@bootlin.com>,
"Florian Fainelli" <f.fainelli@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,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>,
"Frank Wunderlich" <frank.wunderlich@linux.dev>
Subject: Re: [PATCH net-next v10 5/9] net: phy: Represent PHY-less SFP modules with phy_port
Date: Thu, 14 May 2026 15:49:59 +0200 [thread overview]
Message-ID: <233de63c-f4a4-44cc-bb88-eb10d298b9b0@lunn.ch> (raw)
In-Reply-To: <20260513130521.1064094-6-maxime.chevallier@bootlin.com>
On Wed, May 13, 2026 at 03:05:16PM +0200, Maxime Chevallier wrote:
> Now that the SFP bus infrastructure notifies when PHY-less modules are
> connected, we can create a phy_port to represent it. Instead of letting
> the SFP subsystem handle that, the Bus' upstream is in charge of
> maintaining that phy_port and register it to the topology, as the
> upstream (in this case a phy device) is directly interacting with the
> underlying net_device.
>
> Add a phy_caps helper to get the achievable modes on this module based
> on what the phy_port representing the bus supports.
>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2026-05-14 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 13:05 [PATCH net-next v10 0/9] net: phy_port: SFP modules representation and phy_port listing Maxime Chevallier
2026-05-13 13:05 ` [PATCH net-next v10 1/9] net: phy: phy_link_topology: Add a helper for opportunistic alloc Maxime Chevallier
2026-05-13 13:05 ` [PATCH net-next v10 2/9] net: phy: phy_link_topology: Track ports in phy_link_topology Maxime Chevallier
2026-05-13 13:05 ` [PATCH net-next v10 3/9] net: phylink: Register a phy_port for MAC-driven SFP cages Maxime Chevallier
2026-05-14 13:43 ` Andrew Lunn
2026-05-13 13:05 ` [PATCH net-next v10 4/9] net: phy: Create SFP phy_port before registering upstream Maxime Chevallier
2026-05-14 13:46 ` Andrew Lunn
2026-05-13 13:05 ` [PATCH net-next v10 5/9] net: phy: Represent PHY-less SFP modules with phy_port Maxime Chevallier
2026-05-14 13:49 ` Andrew Lunn [this message]
2026-05-13 13:05 ` [PATCH net-next v10 6/9] net: phy: phy_port: Store information about a MII port's vacant state Maxime Chevallier
2026-05-14 13:58 ` Andrew Lunn
2026-05-13 13:05 ` [PATCH net-next v10 7/9] net: phy: phy_link_topology: Add a helper to retrieve ports Maxime Chevallier
2026-05-14 13:59 ` Andrew Lunn
2026-05-13 13:05 ` [PATCH net-next v10 8/9] netlink: specs: Add ethernet port listing with ethtool Maxime Chevallier
2026-05-14 14:05 ` Andrew Lunn
2026-05-13 13:05 ` [PATCH net-next v10 9/9] net: ethtool: Introduce ethtool command to list ports Maxime Chevallier
2026-05-14 14:07 ` Andrew Lunn
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=233de63c-f4a4-44cc-bb88-eb10d298b9b0@lunn.ch \
--to=andrew@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=frank.wunderlich@linux.dev \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@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