From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>,
davem@davemloft.net, 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>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
"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>,
"Pietro Ameruoso" <p.ameruoso@live.it>,
"Aleksei Sviridkin" <f@lex.la>
Subject: Re: [PATCH net-next v18 06/10] net: phy: phy_port: Store information about a port's upstream
Date: Mon, 28 Sep 2026 11:43:17 +0200 [thread overview]
Message-ID: <04e6c889-b312-4351-a2b6-4540e9576408@kernel.org> (raw)
In-Reply-To: <20260927133619.955236-7-maxime.chevallier@bootlin.com>
Le 27/09/2026 à 15:36, Maxime Chevallier a écrit :
> MII phy_ports are not meant to be connected directly to a link partner.
> They are meant to feed into some media converter devices that will
> expose an MDI phy_port, so far we only support SFP modules for that.
>
> In the case an MDI phy_port is backed by an MII port (e.g. a SFP
> module's port, backed by the SFP cage port), let's keep track of the
> port id of the MII port backing it.
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> Tested-by: Aleksei Sviridkin <f@lex.la>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
> ---
> drivers/net/phy/phy_device.c | 29 +++++++++++++++++++++++++++--
> drivers/net/phy/phylink.c | 5 +++++
> include/linux/phy.h | 4 ++++
> include/linux/phy_port.h | 3 +++
> 4 files changed, 39 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
> index ab9631b161bc..2bb4abd0d392 100644
> --- a/drivers/net/phy/phy_device.c
> +++ b/drivers/net/phy/phy_device.c
> @@ -1403,6 +1403,7 @@ static int phy_sfp_connect_phy(void *upstream, struct phy_device *phy)
> int ret;
>
> phydev->has_sfp_mod_phy = true;
> + phy_set_upstream_port(phy, phydev->sfp_cage_port);
>
> /* If we aren't attached to a netdev, we can't add the SFP PHY to its
> * topology.
> @@ -1436,6 +1437,8 @@ static void phy_sfp_disconnect_phy(void *upstream, struct phy_device *phy)
>
> if (dev)
> phy_link_topo_del_phy(dev, phy);
> +
> + phy_set_upstream_port(phy, NULL);
> }
>
> /**
> @@ -1571,6 +1574,8 @@ static int phy_add_sfp_mod_port(struct phy_device *phydev)
> */
> phydev->mod_port = port;
>
> + port->upstream_port = phydev->sfp_cage_port;
> +
> return 0;
> }
>
> @@ -1726,6 +1731,8 @@ static int phy_sfp_probe(struct phy_device *phydev)
> }
> }
>
> + phydev->sfp_cage_port = port;
> +
> ret = sfp_bus_add_upstream(bus, phydev, &sfp_phydev_ops);
> if (ret)
> goto out_port;
> @@ -1735,14 +1742,13 @@ static int phy_sfp_probe(struct phy_device *phydev)
> */
> sfp_bus_put(bus);
>
> - phydev->sfp_cage_port = port;
> -
> return ret;
>
> out_port:
> if (port) {
> phy_del_port(phydev, port);
> phy_port_destroy(port);
> + phydev->sfp_cage_port = NULL;
> }
> out_sfp:
> sfp_bus_put(bus);
> @@ -3687,6 +3693,25 @@ struct phy_port *phy_get_sfp_port(struct phy_device *phydev)
> }
> EXPORT_SYMBOL_GPL(phy_get_sfp_port);
>
> +/**
> + * phy_set_upstream_port() - Sets the phy_port controlling the MII this PHY is
> + * attached to.
> + * @phydev: pointer to the PHY device we set the upstream of.
> + * @port: The phy_port upstream of this PHY, can be NULL.
> + */
> +void phy_set_upstream_port(struct phy_device *phydev, struct phy_port *port)
> +{
> + struct phy_port *local_port;
> +
> + ASSERT_RTNL();
> +
> + phydev->upstream_port = port;
> +
> + phy_for_each_port(phydev, local_port)
> + local_port->upstream_port = port;
> +}
> +EXPORT_SYMBOL_GPL(phy_set_upstream_port);
> +
> /**
> * fwnode_mdio_find_device - Given a fwnode, find the mdio_device
> * @fwnode: pointer to the mdio_device's fwnode
> diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
> index db05d2dda429..2583e913cff6 100644
> --- a/drivers/net/phy/phylink.c
> +++ b/drivers/net/phy/phylink.c
> @@ -4047,6 +4047,8 @@ static int phylink_add_sfp_mod_port(struct phylink *pl)
> }
> }
>
> + port->upstream_port = pl->sfp_cage_port;
> +
> pl->mod_port = port;
>
> return 0;
> @@ -4150,6 +4152,8 @@ static int phylink_sfp_connect_phy(void *upstream, struct phy_device *phy)
> phy_interface_and(phy->host_interfaces, phylink_sfp_interfaces,
> pl->config->supported_interfaces);
>
> + phy_set_upstream_port(phy, pl->sfp_cage_port);
> +
> /* Do the initial configuration */
> return phylink_sfp_config_phy(pl, phy);
> }
> @@ -4158,6 +4162,7 @@ static void phylink_sfp_disconnect_phy(void *upstream,
> struct phy_device *phydev)
> {
> phylink_disconnect_phy(upstream);
> + phy_set_upstream_port(phydev, NULL);
> }
>
> static const struct sfp_upstream_ops sfp_phylink_ops = {
> diff --git a/include/linux/phy.h b/include/linux/phy.h
> index dbd6ed5864f2..1fb87d12367b 100644
> --- a/include/linux/phy.h
> +++ b/include/linux/phy.h
> @@ -615,6 +615,7 @@ struct phy_oatc14_sqi_capability {
> * @sfp_bus: SFP bus attached to this PHY's fiber port
> * @sfp_cage_port: The phy_port connected to the downstream SFP cage
> * @mod_port: phy_port representing the SFP module, if it is phy-less
> + * @upstream_port: phy_port this PHY's MII attaches to, if any
> * @attached_dev: The attached enet driver's device instance ptr
> * @adjust_link: Callback for the enet controller to respond to changes: in the
> * link state.
> @@ -809,6 +810,7 @@ struct phy_device {
> struct sfp_bus *sfp_bus;
> struct phy_port *sfp_cage_port;
> struct phy_port *mod_port;
> + struct phy_port *upstream_port;
> struct phylink *phylink;
> struct net_device *attached_dev;
> struct mii_timestamper *mii_ts;
> @@ -2493,6 +2495,8 @@ int __phy_hwtstamp_set(struct phy_device *phydev,
>
> struct phy_port *phy_get_sfp_port(struct phy_device *phydev);
>
> +void phy_set_upstream_port(struct phy_device *phydev, struct phy_port *port);
> +
> /**
> * phy_module_driver() - Helper macro for registering PHY drivers
> * @__phy_drivers: array of PHY drivers to register
> diff --git a/include/linux/phy_port.h b/include/linux/phy_port.h
> index 4e2a3fdd2f2e..8f45c031cbc1 100644
> --- a/include/linux/phy_port.h
> +++ b/include/linux/phy_port.h
> @@ -40,6 +40,8 @@ struct phy_port_ops {
> * @head: Used by the port's parent to list ports
> * @parent_type: The type of device this port is directly connected to
> * @phy: If the parent is PHY_PORT_PHYDEV, the PHY controlling that port
> + * @upstream_port: Indicates the MII port that feeds this port, if any,
> + * e.g. the SFP cage port for a SFP module port.
> * @ops: Callback ops implemented by the port controller
> * @pairs: The number of pairs this port has, 0 if not applicable
> * @mediums: Bitmask of the physical mediums this port provides access to
> @@ -59,6 +61,7 @@ struct phy_port {
> union {
> struct phy_device *phy;
> };
> + struct phy_port *upstream_port;
>
> const struct phy_port_ops *ops;
>
next prev parent reply other threads:[~2026-09-28 9:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 13:36 [PATCH net-next v18 00/10] net: phy_port: SFP modules representation and phy_port listing Maxime Chevallier
2026-09-27 13:36 ` [PATCH net-next v18 01/10] net: phy: phy_link_topology: Add a helper for opportunistic alloc Maxime Chevallier
2026-09-28 9:36 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 02/10] net: phy: phy_link_topology: Track ports in phy_link_topology Maxime Chevallier
2026-09-28 9:37 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 03/10] net: phylink: Register a phy_port for MAC-driven SFP cages Maxime Chevallier
2026-09-28 9:38 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 04/10] net: phy: Create SFP phy_port before registering upstream Maxime Chevallier
2026-09-28 9:40 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 05/10] net: phy: Represent PHY-less SFP modules with phy_port Maxime Chevallier
2026-09-28 9:42 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 06/10] net: phy: phy_port: Store information about a port's upstream Maxime Chevallier
2026-09-28 9:43 ` Christophe Leroy (CS GROUP) [this message]
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 07/10] net: phy: phy_link_topology: Add a helper to retrieve ports Maxime Chevallier
2026-09-28 9:43 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 08/10] netlink: specs: Add ethernet port listing with ethtool Maxime Chevallier
2026-09-28 9:47 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 09/10] net: ethtool: Introduce ethtool command to list ports Maxime Chevallier
2026-09-28 9:48 ` Christophe Leroy (CS GROUP)
2026-09-29 0:38 ` netdev-bot+sashiko
2026-09-27 13:36 ` [PATCH net-next v18 10/10] Documentation: networking: Update the phy_port infrastructure description Maxime Chevallier
2026-09-28 10:07 ` Christophe Leroy (CS GROUP)
2026-09-28 17:31 ` [PATCH net-next v18 00/10] net: phy_port: SFP modules representation and phy_port listing Christophe Leroy (CS GROUP)
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=04e6c889-b312-4351-a2b6-4540e9576408@kernel.org \
--to=chleroy@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=f@lex.la \
--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=p.ameruoso@live.it \
--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®