Netdev List
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Zxyan Zhu <zxyan0222@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
	"Björn Töpel" <bjorn@kernel.org>
Subject: Re: [PATCH net-next] net: phylink: add phylink_pcs_loopback() method for PCS loopback support
Date: Fri, 24 Jul 2026 11:25:58 +0200	[thread overview]
Message-ID: <42606cde-cdef-420d-adf4-b28c353d564b@bootlin.com> (raw)
In-Reply-To: <20260724085224.3321663-1-zxyan0222@gmail.com>

Hi,

+Björn

On 7/24/26 10:52, Zxyan Zhu wrote:
> Add a pcs_loopback callback to struct phylink_pcs_ops to allow PCS
> devices to expose loopback capability. This is useful for MAC drivers
> running selftests on interfaces that use in-band signalling and have
> no external PHY device.
> 
> The phylink_pcs_loopback() helper calls the PCS ops callback if
> available, and returns -EOPNOTSUPP for PCS devices that do not
> support loopback.
> 
> In stmmac, use phylink_pcs_loopback() in stmmac_test_phy_loopback()
> and stmmac_selftest_run() when no phydev is present but a PCS with
> loopback support exists. This enables PHY loopback selftests on
> interfaces without an external PHY.

There have been talks about making a userspace API for loopback :

https://lore.kernel.org/netdev/20260325145022.2607545-4-bjorn@kernel.org/

Even if your patch is a pure internal feature with no uAPI parts, I wonder
if this is the correct API to have.

Maybe the right move would be to ask phylink to configure the loopback,
and let it figure-out where to do so (in the PHY ? in the PCS ? Somewhere
else ?)

With Björn's work we may end-up with an phylink api that may look like:

phylink_set_loopback(struct phylink *pl, bool enable, enum loopback_location loc)

and for cases like this one where we don't care about where the loopback
is set, we may have an enum value 'LOOPBACK_LOC_ANY' ?

Besides that, I don't see and PCS that supports that loopback, I think
it would be nice to also have the PCS code for loopback as well...

Maxime
> 
> Signed-off-by: Zxyan Zhu <zxyan0222@gmail.com>
> ---
>  .../stmicro/stmmac/stmmac_selftests.c         | 36 ++++++++++++++-----
>  drivers/net/phy/phylink.c                     | 19 ++++++++++
>  include/linux/phylink.h                       | 16 +++++++++
>  3 files changed, 63 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_selftests.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_selftests.c
> index 29e824bd90ca..e6ac51018a65 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_selftests.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_selftests.c
> @@ -377,20 +377,36 @@ static int stmmac_test_mac_loopback(struct stmmac_priv *priv)
>  static int stmmac_test_phy_loopback(struct stmmac_priv *priv)
>  {
>  	struct stmmac_packet_attrs attr = { };
> +	struct phylink_pcs *pcs;
>  	int ret;
>  
> -	if (!priv->dev->phydev)
> -		return -EOPNOTSUPP;
> +	if (priv->dev->phydev) {
> +		ret = phy_loopback(priv->dev->phydev, true, 0);
> +		if (ret)
> +			return ret;
>  
> -	ret = phy_loopback(priv->dev->phydev, true, 0);
> -	if (ret)
> +		attr.dst = priv->dev->dev_addr;
> +		ret = __stmmac_test_loopback(priv, &attr);
> +
> +		phy_loopback(priv->dev->phydev, false, 0);
>  		return ret;
> +	}
>  
> -	attr.dst = priv->dev->dev_addr;
> -	ret = __stmmac_test_loopback(priv, &attr);
> +	/* Use PCS loopback for interfaces without an external PHY. */
> +	pcs = priv->hw->phylink_pcs;
> +	if (pcs) {
> +		ret = phylink_pcs_loopback(pcs, true);
> +		if (ret)
> +			return ret;
>  
> -	phy_loopback(priv->dev->phydev, false, 0);
> -	return ret;
> +		attr.dst = priv->dev->dev_addr;
> +		ret = __stmmac_test_loopback(priv, &attr);
> +
> +		phylink_pcs_loopback(pcs, false);
> +		return ret;
> +	}
> +
> +	return -EOPNOTSUPP;
>  }
>  
>  static int stmmac_test_mmc(struct stmmac_priv *priv)
> @@ -1986,6 +2002,8 @@ void stmmac_selftest_run(struct net_device *dev,
>  			ret = -EOPNOTSUPP;
>  			if (dev->phydev)
>  				ret = phy_loopback(dev->phydev, true, 0);
> +			else if (priv->hw->phylink_pcs)
> +				ret = phylink_pcs_loopback(priv->hw->phylink_pcs, true);
>  			if (!ret)
>  				break;
>  			fallthrough;
> @@ -2019,6 +2037,8 @@ void stmmac_selftest_run(struct net_device *dev,
>  			ret = -EOPNOTSUPP;
>  			if (dev->phydev)
>  				ret = phy_loopback(dev->phydev, false, 0);
> +			else if (priv->hw->phylink_pcs)
> +				ret = phylink_pcs_loopback(priv->hw->phylink_pcs, false);
>  			if (!ret)
>  				break;
>  			fallthrough;
> diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
> index 59dfe35afa54..a7f78c82913a 100644
> --- a/drivers/net/phy/phylink.c
> +++ b/drivers/net/phy/phylink.c
> @@ -997,6 +997,25 @@ int phylink_pcs_pre_init(struct phylink *pl, struct phylink_pcs *pcs)
>  }
>  EXPORT_SYMBOL_GPL(phylink_pcs_pre_init);
>  
> +/**
> + * phylink_pcs_loopback() - Enable or disable loopback at the PCS
> + * @pcs: a pointer to a &struct phylink_pcs.
> + * @enable: true to enable loopback, false to disable
> + *
> + * Enable or disable loopback mode at the PCS level. This is used by MAC
> + * drivers for selftest purposes when no external PHY is present.
> + *
> + * Returns 0 on success, negative error code on failure.
> + */
> +int phylink_pcs_loopback(struct phylink_pcs *pcs, bool enable)
> +{
> +	if (pcs->ops->pcs_loopback)
> +		return pcs->ops->pcs_loopback(pcs, enable);
> +
> +	return -EOPNOTSUPP;
> +}
> +EXPORT_SYMBOL_GPL(phylink_pcs_loopback);
> +
>  static void phylink_mac_config(struct phylink *pl,
>  			       const struct phylink_link_state *state)
>  {
> diff --git a/include/linux/phylink.h b/include/linux/phylink.h
> index 2bc0db3d52ac..66c7016d4acd 100644
> --- a/include/linux/phylink.h
> +++ b/include/linux/phylink.h
> @@ -518,6 +518,7 @@ struct phylink_pcs {
>   *		    the MAC.
>   * @pcs_pre_init: configure PCS components necessary for MAC hardware
>   *                initialization e.g. RX clock for stmmac.
> + * @pcs_loopback: enable/disable loopback mode at the PCS.
>   */
>  struct phylink_pcs_ops {
>  	int (*pcs_validate)(struct phylink_pcs *pcs, unsigned long *supported,
> @@ -542,6 +543,7 @@ struct phylink_pcs_ops {
>  	void (*pcs_disable_eee)(struct phylink_pcs *pcs);
>  	void (*pcs_enable_eee)(struct phylink_pcs *pcs);
>  	int (*pcs_pre_init)(struct phylink_pcs *pcs);
> +	int (*pcs_loopback)(struct phylink_pcs *pcs, bool enable);
>  };
>  
>  #if 0 /* For kernel-doc purposes only. */
> @@ -717,8 +719,22 @@ void pcs_enable_eee(struct phylink_pcs *pcs);
>   */
>  int pcs_pre_init(struct phylink_pcs *pcs);
>  
> +/**
> + * pcs_loopback() - Enable or disable loopback at the PCS
> + * @pcs: a pointer to a &struct phylink_pcs.
> + * @enable: true to enable loopback, false to disable
> + *
> + * Enable or disable loopback mode at the PCS level. This is used by MAC
> + * drivers for selftest purposes when no external PHY is present.
> + *
> + * Returns 0 on success, or a negative error code on failure.
> + */
> +int pcs_loopback(struct phylink_pcs *pcs, bool enable);
> +
>  #endif
>  
> +int phylink_pcs_loopback(struct phylink_pcs *pcs, bool enable);
> +
>  struct phylink *phylink_create(struct phylink_config *,
>  			       const struct fwnode_handle *,
>  			       phy_interface_t,
> 
> base-commit: 1df10cef2d1e7f9f2fb7eddb67fc70d3abf101f9


  reply	other threads:[~2026-07-24  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  8:52 [PATCH net-next] net: phylink: add phylink_pcs_loopback() method for PCS loopback support Zxyan Zhu
2026-07-24  9:25 ` Maxime Chevallier [this message]
2026-07-24 13:05   ` Andrew Lunn
2026-07-27  9:38 ` [PATCH net-next v2] " Zxyan Zhu

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=42606cde-cdef-420d-adf4-b28c353d564b@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bjorn@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux@armlinux.org.uk \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=zxyan0222@gmail.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