Linux I2C development
 help / color / mirror / Atom feed
From: Ahmad Byagowi <ahmadexp@gmail.com>
To: netdev@vger.kernel.org, vadim.fedorenko@linux.dev, andi.shyti@kernel.org
Cc: linux-i2c@vger.kernel.org
Subject: [PATCH net-next 0/3] ptp: ocp: support the WiWi production Time Card
Date: Tue, 10 Nov 2026 20:19:00 -0800	[thread overview]
Message-ID: <20261111041904.48916-1-ahmadexp@gmail.com> (raw)

The WiWi 2163:1008 card has a Celestica-compatible register map behind
a LitePCIe bridge, but subword MMIO can cause a machine check. Teach
XIIC to use aligned word accesses on request, test both access modes,
and bind ptp_ocp only to the verified 0x800f production layout.
Other boards retain their existing access modes. WiWi devlink flash
updates are deliberately unsupported.

Patch 3 consumes the platform-data field from patch 1. Can the I2C
maintainers Ack patches 1 and 2 for the series to go through net-next?

On the hardware-tested base (4dd16e31135e), the driver bound with
64 MSI-X vectors and registered the PHC, PPS and three UARTs. The PHC
advanced 3.000429460 s over three one-second reads, within the host
monotonic brackets. SPI NOR and two at24 devices bound. The card was
UNSYNCED at probe; no PPS lock or UTC accuracy is claimed. Rebasing
onto the base below did not change the driver sources or patch IDs.
The rebased series passed x86-64 module/built-in and i386 module
object builds and four XIIC KUnit cases in x86-64 QEMU.
Full W=1 allmodconfig and allyesconfig builds encountered the same GCC
format-truncation error in lockdep_proc.c on this series and the clean
base. Neither full configuration is reported as passing.

Codex assisted with the driver changes, tests and changelogs from
the supplied board layout and crash evidence. The net-next series
does not include a firmware update or front-panel LED policy.

Ahmad Byagowi (3):
  i2c: xiic: allow platforms to require 32-bit register accesses
  i2c: xiic: add KUnit coverage for register access modes
  ptp: ocp: add WiWi Time Card production image support

 Documentation/networking/devlink/ptp_ocp.rst |  35 +++-
 MAINTAINERS                                  |   1 +
 drivers/i2c/busses/Kconfig                   |  14 ++
 drivers/i2c/busses/i2c-xiic.c                |  60 ++++--
 drivers/i2c/busses/tests/i2c_xiic_kunit.c    |  88 +++++++++
 drivers/ptp/ptp_ocp.c                        | 198 ++++++++++++++++++-
 include/linux/platform_data/i2c-xiic.h       |   3 +
 7 files changed, 374 insertions(+), 25 deletions(-)
 create mode 100644 drivers/i2c/busses/tests/i2c_xiic_kunit.c


base-commit: 97ced2c090bfc2156db31fca9f52cf253e4bc186

             reply	other threads:[~2026-11-11  4:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  4:19 Ahmad Byagowi [this message]
2026-11-11  4:19 ` [PATCH net-next 1/3] i2c: xiic: allow platforms to require 32-bit register accesses Ahmad Byagowi
2026-11-11  4:19 ` [PATCH net-next 2/3] i2c: xiic: add KUnit coverage for register access modes Ahmad Byagowi
2026-11-11  4:19 ` [PATCH net-next 3/3] ptp: ocp: add WiWi Time Card production image support 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=20261111041904.48916-1-ahmadexp@gmail.com \
    --to=ahmadexp@gmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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