From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/2] I2C: OMAP: spurious IRQ fixes
Date: Sat, 25 Apr 2009 22:28:05 -0600 [thread overview]
Message-ID: <20090426042504.31316.68357.stgit@localhost.localdomain> (raw)
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(-)
next reply other threads:[~2009-04-26 4:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 4:28 Paul Walmsley [this message]
2009-04-26 4:28 ` [PATCH 1/2] I2C: OMAP: use consolidated flags field rather than bitfields Paul Walmsley
2009-04-26 4:28 ` [PATCH 2/2] I2C: OMAP: overhaul the rev2+ interrupt service routine and omap_i2c_xfer_msg() Paul Walmsley
2009-04-27 11:56 ` [PATCH 0/2] I2C: OMAP: spurious IRQ fixes Aaro Koskinen
2009-05-11 7:29 ` Paul Walmsley
2009-05-12 17:14 ` Woodruff, Richard
2009-05-12 18:33 ` Paul Walmsley
2009-05-12 18:41 ` Paul Walmsley
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=20090426042504.31316.68357.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.