Re: [PATCH net-next v3 2/3] i2c: xiic: add KUnit coverage for register access modes

From
Ahmad Byagowi <hidden>
Date
2026-11-18 20:05:34
Also in
linux-doc, linux-i2c, lkml
Reply to
netdev-bot+sashiko@kernel.org, 2026-11-18
Agreed. RAM cannot distinguish a byte read from a truncated word read
returning the same value. I have stated that explicitly in the Kconfig
help and test comment, and retained the direct-x86-64 restriction.

All four KUnit cases pass in x86-64 QEMU. Separately, the source-derived
accessor fixture records which I/O accessor was called, including its
width and address. Removing the forced-word read branch makes that
fixture fail. This is software accessor coverage, not a measurement of
PCIe transaction widths, and I have not added runtime indirection to the
driver just for testing.
Thread (12 messages) 12 messages, 3 authors, last reply 22h ago
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help