From: Ahmad Byagowi <ahmadexp@gmail.com>
To: netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
richardcochran@gmail.com
Cc: andrew+netdev@lunn.ch, arkadiusz.kubalewski@intel.com,
davem@davemloft.net, edumazet@kernel.org, jiri@resnulli.us,
kuba@kernel.org, linux-kernel@vger.kernel.org, pabeni@redhat.com
Subject: [PATCH net 0/4] ptp: ocp: fix timestamp teardown and DPLL routing
Date: Wed, 18 Nov 2026 12:05:04 -0800 [thread overview]
Message-ID: <20261118-timecard-common-301f823ddd-0-ahmadexp@gmail.com> (raw)
These fixes affect existing ptp_ocp boards and do not add WiWi support.
They were identified in the public review of the WiWi series and are
split out so they can be reviewed and backported independently.
Prevent timestamp rearming during detach with a mutex-protected stopping
state. Then correct DPLL selector values, disabled-input frequency
reporting and the DCF77 output frequency. Each fix has its own Fixes tag.
Validation used source-derived C tests under ASan/UBSan. The old source
reproduces rearming after detach's disable. The new source rejects late
enables, waits for an enable already in progress, and drains a mocked
active IRQ. Targeted mutations of each DPLL fix fail the regression
tests. The driver object builds against this net base with W=1 and
KCFLAGS=-Werror. No physical card, real IRQ delivery or in-kernel
use-after-free reproduction was tested for these fixes.
The report came from netdev's Sashiko AI review. Codex prepared the code,
tests and changelogs from that review and the upstream sources, following
the request to separate common fixes and validate removal ordering.
This origin information follows Documentation/process/generated-content.rst.
Related review:
https://lore.kernel.org/r/179502617840.3136.12704245716223038161@kernel.org
WiWi v4 will be based on these fixes after they are available in
net-next; it will not carry a second copy of the common fixes.
Ahmad Byagowi (4):
ptp: ocp: prevent timestamp rearming during detach
ptp: ocp: use hardware selectors in DPLL frequency operations
ptp: ocp: report disabled SMA inputs consistently over DPLL
ptp: ocp: correct the DCF output frequency
drivers/ptp/ptp_ocp.c | 30 ++++++++++++++++++++++++++----
1 file changed, 26 insertions(+), 4 deletions(-)
base-commit: 2a324a58a084c5cfd7e5a2f55e0786bee170a4a5
--
2.54.0 (Apple Git-157)
next reply other threads:[~2026-11-18 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 20:05 Ahmad Byagowi [this message]
2026-11-18 20:05 ` [PATCH net 1/4] ptp: ocp: prevent timestamp rearming during detach Ahmad Byagowi
2026-11-18 20:05 ` [PATCH net 2/4] ptp: ocp: use hardware selectors in DPLL frequency operations Ahmad Byagowi
2026-11-18 20:05 ` [PATCH net 3/4] ptp: ocp: report disabled SMA inputs consistently over DPLL Ahmad Byagowi
2026-11-18 20:05 ` [PATCH net 4/4] ptp: ocp: correct the DCF output frequency Ahmad Byagowi
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=20261118-timecard-common-301f823ddd-0-ahmadexp@gmail.com \
--to=ahmadexp@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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