netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Babroski <cbabroski@nvidia.com>
To: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <cbabroski@nvidia.com>, <davthompson@nvidia.com>,
	<hkallweit1@gmail.com>, <linux@armlinux.org.uk>
Subject: [PATCH net-next v2] mlxbf_gige: report unknown speed and duplex when link is down
Date: Tue, 14 Oct 2025 12:16:31 -0400	[thread overview]
Message-ID: <20251014161631.769596-1-cbabroski@nvidia.com> (raw)

The "Speed" and "Duplex" fields displayed by ethtool for the OOB
interface should report "Unknown" when the link is down to match the
behavior of other network interfaces on BlueField (implemented by the
mlx5 driver). Currently, the mlxbf_gige driver always reports the
initially configured link speed and duplex, regardless of the actual
link state.

The link speed and duplex are not updated for two reasons:
  1. On BlueField the OOB phy is internally hardwired to a three port
     switch. This means the physical link between the phy and link
     partner is always up, regardless of the administrative link state
     configured with ifconfig.
  2. phy_ethtool_get_link_ksettings() reads cached values that are only
     updated when phy_read_status() is called by the phy state machine.
     Doing "ifconfig down" will trigger phy_stop() in the
     ndo_stop() handler. This halts the phy state machine and sets
     phydev->link without calling phy_read_status() or explicitly
     updating other values, so the speed and duplex returned by
     future phy_ethtool_get_link_ksettings() calls will be stale.

While #2 could potentially be fixed (assuming this is even an issue for
other devices), #1 is unique to BlueField.

Implement a custom get_link_ksettings() handler in mlxbf_gige that calls
phy_ethtool_get_link_ksettings() and updates the speed and duplex based
on the link state. When the link is brought down with ifconfig, the
driver now reports unknown speed and duplex to ethtool as expected.

Signed-off-by: Chris Babroski <cbabroski@nvidia.com>
---
v2:
  - Update commit message to clarify why phy_ethtool_get_link_ksettings()
    does not return unknown link speed and duplex when the link is down
    on BlueField.
v1: https://lore.kernel.org/netdev/20250813163346.302186-1-cbabroski@nvidia.com/#t

 .../mellanox/mlxbf_gige/mlxbf_gige_ethtool.c  | 26 ++++++++++++++++++-
 1 file changed, 25 insertions(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_ethtool.c b/drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_ethtool.c
index 8b63968bbee9..c519eeb8ec48 100644
--- a/drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_ethtool.c
+++ b/drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_ethtool.c
@@ -159,6 +159,30 @@ static void mlxbf_gige_get_pause_stats(struct net_device *netdev,
 	}
 }
 
+static int mlxbf_gige_get_link_ksettings(struct net_device *ndev,
+					 struct ethtool_link_ksettings *cmd)
+{
+	struct phy_device *phydev;
+	int ret;
+
+	ret = phy_ethtool_get_link_ksettings(ndev, cmd);
+	if (ret)
+		return ret;
+
+	phydev = ndev->phydev;
+	if (!phydev)
+		return -ENODEV;
+
+	mutex_lock(&phydev->lock);
+	if (!phydev->link) {
+		cmd->base.speed = SPEED_UNKNOWN;
+		cmd->base.duplex = DUPLEX_UNKNOWN;
+	}
+	mutex_unlock(&phydev->lock);
+
+	return 0;
+}
+
 const struct ethtool_ops mlxbf_gige_ethtool_ops = {
 	.get_link		= ethtool_op_get_link,
 	.get_ringparam		= mlxbf_gige_get_ringparam,
@@ -170,6 +194,6 @@ const struct ethtool_ops mlxbf_gige_ethtool_ops = {
 	.nway_reset		= phy_ethtool_nway_reset,
 	.get_pauseparam		= mlxbf_gige_get_pauseparam,
 	.get_pause_stats	= mlxbf_gige_get_pause_stats,
-	.get_link_ksettings	= phy_ethtool_get_link_ksettings,
+	.get_link_ksettings	= mlxbf_gige_get_link_ksettings,
 	.set_link_ksettings	= phy_ethtool_set_link_ksettings,
 };
-- 
2.34.1


             reply	other threads:[~2025-10-14 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 16:16 Chris Babroski [this message]
2025-10-17 22:54 ` [PATCH net-next v2] mlxbf_gige: report unknown speed and duplex when link is down Jakub Kicinski
2025-10-22 17:08   ` Chris Babroski
2025-10-23  0:09     ` Jakub Kicinski

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=20251014161631.769596-1-cbabroski@nvidia.com \
    --to=cbabroski@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=davthompson@nvidia.com \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).