From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Russell King <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrei Botila <andrei.botila@oss.nxp.com>,
Richard Cochran <richardcochran@gmail.com>,
Andrew Lunn <andrew@lunn.ch>
Cc: Simon Horman <horms@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Kory Maincent <kory.maincent@bootlin.com>,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
Vadim Fedorenko <vadim.fedorenko@linux.dev>
Subject: [PATCH net-next v3 3/9] net: phy: broadcom: add HW timestamp configuration reporting
Date: Wed, 19 Nov 2025 12:47:19 +0000 [thread overview]
Message-ID: <20251119124725.3935509-4-vadim.fedorenko@linux.dev> (raw)
In-Reply-To: <20251119124725.3935509-1-vadim.fedorenko@linux.dev>
The driver stores configuration information and can technically report
it. Implement hwtstamp_get callback to report the configuration.
Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
---
drivers/net/phy/bcm-phy-ptp.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/drivers/net/phy/bcm-phy-ptp.c b/drivers/net/phy/bcm-phy-ptp.c
index 6815e844a62e..65d609ed69fb 100644
--- a/drivers/net/phy/bcm-phy-ptp.c
+++ b/drivers/net/phy/bcm-phy-ptp.c
@@ -780,6 +780,18 @@ static void bcm_ptp_txtstamp(struct mii_timestamper *mii_ts,
kfree_skb(skb);
}
+static int bcm_ptp_hwtstamp_get(struct mii_timestamper *mii_ts,
+ struct kernel_hwtstamp_config *cfg)
+{
+ struct bcm_ptp_private *priv = mii2priv(mii_ts);
+
+ cfg->rx_filter = priv->hwts_rx ? HWTSTAMP_FILTER_PTP_V2_EVENT
+ : HWTSTAMP_FILTER_NONE;
+ cfg->tx_type = priv->tx_type;
+
+ return 0;
+}
+
static int bcm_ptp_hwtstamp_set(struct mii_timestamper *mii_ts,
struct kernel_hwtstamp_config *cfg,
struct netlink_ext_ack *extack)
@@ -899,6 +911,7 @@ static void bcm_ptp_init(struct bcm_ptp_private *priv)
priv->mii_ts.rxtstamp = bcm_ptp_rxtstamp;
priv->mii_ts.txtstamp = bcm_ptp_txtstamp;
priv->mii_ts.hwtstamp_set = bcm_ptp_hwtstamp_set;
+ priv->mii_ts.hwtstamp_get = bcm_ptp_hwtstamp_get;
priv->mii_ts.ts_info = bcm_ptp_ts_info;
priv->phydev->mii_ts = &priv->mii_ts;
--
2.47.3
next prev parent reply other threads:[~2025-11-19 12:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 12:47 [PATCH net-next v3 0/9] add hwtstamp_get callback to phy drivers Vadim Fedorenko
2025-11-19 12:47 ` [PATCH net-next v3 1/9] phy: rename hwtstamp callback to hwtstamp_set Vadim Fedorenko
2025-11-19 13:23 ` Russell King (Oracle)
2025-11-19 13:50 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 2/9] phy: add hwtstamp_get callback to phy drivers Vadim Fedorenko
2025-11-19 13:24 ` Russell King (Oracle)
2025-11-19 14:09 ` Kory Maincent
2025-11-19 12:47 ` Vadim Fedorenko [this message]
2025-11-19 14:12 ` [PATCH net-next v3 3/9] net: phy: broadcom: add HW timestamp configuration reporting Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 4/9] net: phy: dp83640: " Vadim Fedorenko
2025-11-19 14:13 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 5/9] net: phy: micrel: " Vadim Fedorenko
2025-11-19 14:44 ` Kory Maincent
2025-11-19 15:10 ` Vadim Fedorenko
2025-11-19 15:26 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 6/9] net: phy: microchip_rds_ptp: " Vadim Fedorenko
2025-11-19 14:46 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 7/9] phy: mscc: " Vadim Fedorenko
2025-11-19 14:48 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 8/9] net: phy: nxp-c45-tja11xx: " Vadim Fedorenko
2025-11-19 14:50 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 9/9] ptp: ptp_ines: " Vadim Fedorenko
2025-11-19 14:59 ` Kory Maincent
2025-11-19 15:14 ` Vadim Fedorenko
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=20251119124725.3935509-4-vadim.fedorenko@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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;
as well as URLs for NNTP newsgroup(s).