From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Petr Oros <poros@redhat.com>,
Chris du Quesnay <Chris.duQuesnay@microchip.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@resnulli.us>,
Min Li <min.li@microchip.com>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 3/3] dpll: zl3073x: add PTP clock support
Date: Wed, 12 Aug 2026 08:58:52 +0200 [thread overview]
Message-ID: <e9898fd0-32fa-4b9b-baf7-fdea2484abe4@redhat.com> (raw)
In-Reply-To: <20260811134700.1211010-4-ivecera@redhat.com>
Sashiko findings. Replies inline.
> Since there is no delay or sleep inside this loop, will it exhaust
> all 20 retries almost instantly on fast control buses?
See reply to the same finding on patch 2/3 — testing on I2C at both
100 kHz and 400 kHz shows each iteration takes 17-19 ms regardless
of bus speed (dominated by device internal processing). 20 retries
give 340-380 ms of budget, well beyond the 20 ms margin window.
> If zl3073x_chan_tod_ready_wait() fails here, the function returns rc
> directly. [...] wouldn't returning an error cause the PTP servo to
> retry and apply the seconds adjustment a second time?
If tod_ready_wait fails, we cannot be certain that WR_NEXT_1HZ was
actually applied — the semaphore timeout means we do not know whether
the hardware committed the seconds or not. Returning the error is
the safer choice, because setting sec_adjusted = true before
confirmation would mask a genuine hardware failure and silently
report success when the adjustment may not have been applied at all.
Thanks,
Ivan
prev parent reply other threads:[~2026-08-12 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:46 [PATCH net-next v7 0/3] dpll: zl3073x: add PTP clock support Ivan Vecera
2026-08-11 13:46 ` [PATCH net-next v7 1/3] dpll: zl3073x: scale poll interval proportionally to timeout Ivan Vecera
2026-08-12 10:05 ` Vadim Fedorenko
2026-08-11 13:46 ` [PATCH net-next v7 2/3] dpll: zl3073x: add channel ToD, phase step and TIE operations Ivan Vecera
2026-08-12 6:57 ` Ivan Vecera
2026-08-12 10:04 ` Vadim Fedorenko
2026-08-12 11:00 ` Ivan Vecera
2026-08-11 13:47 ` [PATCH net-next v7 3/3] dpll: zl3073x: add PTP clock support Ivan Vecera
2026-08-12 6:58 ` Ivan Vecera [this message]
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=e9898fd0-32fa-4b9b-baf7-fdea2484abe4@redhat.com \
--to=ivecera@redhat.com \
--cc=Chris.duQuesnay@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
/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