From: Kory Maincent <kory.maincent@bootlin.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: 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>, Simon Horman <horms@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Jacob Keller <jacob.e.keller@intel.com>,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH net-next v4 2/7] phy: add hwtstamp_get callback to phy drivers
Date: Thu, 20 Nov 2025 18:51:26 +0100 [thread overview]
Message-ID: <20251120185126.6e536058@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20251120174540.273859-3-vadim.fedorenko@linux.dev>
On Thu, 20 Nov 2025 17:45:35 +0000
Vadim Fedorenko <vadim.fedorenko@linux.dev> wrote:
> PHY devices had lack of hwtstamp_get callback even though most of them
> are tracking configuration info. Introduce new call back to
> mii_timestamper.
It's a pity you didn't take my comment into account. :/
" It would be nice to update this kdoc note:
https://elixir.bootlin.com/linux/v6.18-rc6/source/net/core/dev_ioctl.c#L252 "
> Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> Reviewed-by: Kory Maincent <kory.maincent@bootlin.com>
> Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
> ---
> drivers/net/phy/phy.c | 3 +++
> include/linux/mii_timestamper.h | 5 +++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
> index 350bc23c1fdb..13dd1691886d 100644
> --- a/drivers/net/phy/phy.c
> +++ b/drivers/net/phy/phy.c
> @@ -478,6 +478,9 @@ int __phy_hwtstamp_get(struct phy_device *phydev,
> if (!phydev)
> return -ENODEV;
>
> + if (phydev->mii_ts && phydev->mii_ts->hwtstamp_get)
> + return phydev->mii_ts->hwtstamp_get(phydev->mii_ts, config);
> +
> return -EOPNOTSUPP;
> }
>
> diff --git a/include/linux/mii_timestamper.h b/include/linux/mii_timestamper.h
> index 08863c0e9ea3..3102c425c8e0 100644
> --- a/include/linux/mii_timestamper.h
> +++ b/include/linux/mii_timestamper.h
> @@ -29,6 +29,8 @@ struct phy_device;
> *
> * @hwtstamp_set: Handles SIOCSHWTSTAMP ioctl for hardware time stamping.
> *
> + * @hwtstamp_get: Handles SIOCGHWTSTAMP ioctl for hardware time stamping.
> + *
> * @link_state: Allows the device to respond to changes in the link
> * state. The caller invokes this function while holding
> * the phy_device mutex.
> @@ -55,6 +57,9 @@ struct mii_timestamper {
> struct kernel_hwtstamp_config *kernel_config,
> struct netlink_ext_ack *extack);
>
> + int (*hwtstamp_get)(struct mii_timestamper *mii_ts,
> + struct kernel_hwtstamp_config *kernel_config);
> +
> void (*link_state)(struct mii_timestamper *mii_ts,
> struct phy_device *phydev);
>
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-11-20 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 17:45 [PATCH net-next v4 0/7] add hwtstamp_get callback to phy drivers Vadim Fedorenko
2025-11-20 17:45 ` [PATCH net-next v4 1/7] phy: rename hwtstamp callback to hwtstamp_set Vadim Fedorenko
2025-11-20 17:45 ` [PATCH net-next v4 2/7] phy: add hwtstamp_get callback to phy drivers Vadim Fedorenko
2025-11-20 17:51 ` Kory Maincent [this message]
2025-11-24 17:09 ` Vadim Fedorenko
2025-11-20 17:45 ` [PATCH net-next v4 3/7] net: phy: broadcom: add HW timestamp configuration reporting Vadim Fedorenko
2025-11-20 17:45 ` [PATCH net-next v4 4/7] net: phy: dp83640: " Vadim Fedorenko
2025-11-20 17:45 ` [PATCH net-next v4 5/7] phy: mscc: " Vadim Fedorenko
2025-11-20 17:45 ` [PATCH net-next v4 6/7] net: phy: nxp-c45-tja11xx: " Vadim Fedorenko
2025-11-20 17:45 ` [PATCH net-next v4 7/7] ptp: ptp_ines: " 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=20251120185126.6e536058@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--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=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=vadim.fedorenko@linux.dev \
--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