I2C: OMAP: spurious IRQ fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | I2C: OMAP: use consolidated flags field rather than bitfieldsdrivers/ | +33 | 0 replies | |
| 2/2 | I2C: OMAP: overhaul the rev2+ interrupt service routine and omap_i2c_xfer_msg()drivers/ | +63 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] I2C: OMAP: spurious IRQ fixes
Hi,
This is a set of I2C fixes. Its primary purpose is to deal with the I2C spurious IRQ problem:
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
It seems to work: under constant I2C load, no spurious IRQ messages showed up after several hours of testing. (Without these patches, spurious IRQs usually show up in a few minutes.) Some of the code has also been cleaned up.
Any feedback on how this series works for others is appreciated.
Tested on N800, Beagle and 3430SDP.
- Paul
---
text data bss dec hex filename
3636832 210560 104320 3951712 3c4c60 vmlinux.3430sdp.orig 3636896 210560 104320 3951776 3c4ca0 vmlinux.3430sdp
Paul Walmsley (2):
I2C: OMAP: overhaul the rev2+ interrupt service routine and omap_i2c_xfer_msg()
I2C: OMAP: use consolidated flags field rather than bitfields
drivers/i2c/busses/i2c-omap.c | 150 ++++++++++++++++++++++++++--------------- 1 files changed, 95 insertions(+), 55 deletions(-)