From: Jakub Kicinski <kuba@kernel.org>
To: James Clark <jjc@jclark.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Richard Cochran" <richardcochran@gmail.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Doug Berger" <opendmb@gmail.com>,
"Nicolai Buchwitz" <nb@tipi-net.de>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Russell King" <linux@armlinux.org.uk>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"John Stultz" <jstultz@google.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Miroslav Lichvar" <mlichvar@redhat.com>,
"Vladimir Oltean" <olteanv@gmail.com>,
"Hubert Feurstein" <h.feurstein@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/6] net: mdio: add timestamped MDIO writes for PHY gettimex64
Date: Tue, 10 Nov 2026 15:16:02 -0800 [thread overview]
Message-ID: <20261110151602.7a065b73@kernel.org> (raw)
In-Reply-To: <20261105054839.2248046-1-jjc@jclark.com>
On Thu, 5 Nov 2026 12:48:33 +0700 James Clark wrote:
> PTP_SYS_OFFSET_EXTENDED uses gettimex64 to bracket each PHC read with
> system clock reads. Some PHYs have a PTP hardware clock (PHC) that is
> read over MDIO and sometimes multiple MDIO transfers are needed to read
> the clock. This leads to brackets in the tens of microseconds.
> Applications that synchronize the system clock from the PHC typically
> use the midpoint of the bracket as the system time of the PHC reading.
> With multiple transfers, the midpoint of the bracket is typically far
> from the time when the PHC reading actually occurred.
There are some AI nit picks available:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261105054839.2248046-1-jjc@jclark.com
But frankly unless someone with time expertise reviews this it is going
nowhere.
next prev parent reply other threads:[~2026-11-10 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 5:48 [PATCH net-next v3 0/6] net: mdio: add timestamped MDIO writes for PHY gettimex64 James Clark
2026-11-05 5:48 ` [PATCH net-next v3 1/6] timekeeping: add ktime_scale_raw_ns() James Clark
2026-11-05 5:48 ` [PATCH net-next v3 2/6] ptp: add functions to adjust system timestamps James Clark
2026-11-05 5:48 ` [PATCH net-next v3 3/6] net: mdio: add timestamped write operation James Clark
2026-11-05 5:48 ` [PATCH net-next v3 4/6] net: phy: broadcom: use timestamped MDIO writes in gettimex64 James Clark
2026-11-05 5:48 ` [PATCH net-next v3 5/6] net: macb: implement timestamped MDIO writes James Clark
2026-11-05 5:48 ` [PATCH net-next v3 6/6] net: mdio: bcm-unimac: " James Clark
2026-11-10 23:16 ` Jakub Kicinski [this message]
2026-11-12 19:30 ` [PATCH net-next v3 0/6] net: mdio: add timestamped MDIO writes for PHY gettimex64 Nicolai Buchwitz
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=20261110151602.7a065b73@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=h.feurstein@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jjc@jclark.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mlichvar@redhat.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sboyd@kernel.org \
--cc=tglx@kernel.org \
--cc=theo.lebrun@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.