From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Russell King <rmk+kernel@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: Marcin Wojtas <marcin.s.wojtas@gmail.com>,
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>,
Richard Cochran <richardcochran@gmail.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: mvpp2: tai: warn once if we fail to update our timestamp
Date: Wed, 11 Dec 2024 12:48:21 +0100 [thread overview]
Message-ID: <07eeb151-008b-4b92-8db9-31cd51ec3e77@intel.com> (raw)
In-Reply-To: <E1tLKNm-006eTd-FD@rmk-PC.armlinux.org.uk>
On 12/11/2024 11:55 AM, Russell King wrote:
> The hardware timestamps for packets contain a truncated seconds field,
> only containing two bits of seconds. In order to provide the full
> number of seconds, we need to keep track of the full hardware clock by
> reading it every two seconds.
>
> However, if we fail to read the clock, we silently ignore the error.
> Print a warning indicating that the PP2 TAI clock timestamps have
> become unreliable.
>
> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> --
> v2: correct dev_warn_once() indentation
> ---
> drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c b/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c
> index 95862aff49f1..6b60beb1f3ed 100644
> --- a/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c
> +++ b/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c
> @@ -54,6 +54,7 @@
> #define TCSR_CAPTURE_0_VALID BIT(0)
>
> struct mvpp2_tai {
> + struct device *dev;
> struct ptp_clock_info caps;
> struct ptp_clock *ptp_clock;
> void __iomem *base;
> @@ -303,7 +304,8 @@ static long mvpp22_tai_aux_work(struct ptp_clock_info *ptp)
> {
> struct mvpp2_tai *tai = ptp_to_tai(ptp);
>
> - mvpp22_tai_gettimex64(ptp, &tai->stamp, NULL);
> + if (mvpp22_tai_gettimex64(ptp, &tai->stamp, NULL) < 0)
> + dev_warn_once(tai->dev, "PTP timestamps are unreliable");
Only small nitpick/question - shouldn't text end with '\n'? I see in the
code that most of calls of dev_warn_once has '\n' at the end.
>
> return msecs_to_jiffies(2000);
> }
> @@ -401,6 +403,7 @@ int mvpp22_tai_probe(struct device *dev, struct mvpp2 *priv)
>
> spin_lock_init(&tai->lock);
>
> + tai->dev = dev;
> tai->base = priv->iface_base;
>
> /* The step size consists of three registers - a 16-bit nanosecond step
Nevertheless the code itself looks good to me, nice improvement.
Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
next prev parent reply other threads:[~2024-12-11 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:55 [PATCH net-next v2] net: mvpp2: tai: warn once if we fail to update our timestamp Russell King
2024-12-11 11:48 ` Mateusz Polchlopek [this message]
2024-12-11 11:54 ` Russell King (Oracle)
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=07eeb151-008b-4b92-8db9-31cd51ec3e77@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=marcin.s.wojtas@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
/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).