From: Alexander Shishkin <virtuoso@slind.org>
To: ben-linux@fluff.org
Cc: linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
Alexander Shishkin <virtuoso@slind.org>
Subject: [PATCH 1/2] omap i2c: make errata 1.153 workaround a separate function
Date: Wed, 16 Dec 2009 15:43:03 +0200 [thread overview]
Message-ID: <1260970986-26613-2-git-send-email-virtuoso@slind.org> (raw)
In-Reply-To: <1260970986-26613-1-git-send-email-virtuoso@slind.org>
This is to avoid insanely long lines and levels of indentation.
Signed-off-by: Alexander Shishkin <virtuoso@slind.org>
CC: linux-i2c@vger.kernel.org
CC: linux-omap@vger.kernel.org
---
drivers/i2c/busses/i2c-omap.c | 43 ++++++++++++++++++++++------------------
1 files changed, 24 insertions(+), 19 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 75bf3ad..ad8242a 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -671,6 +671,27 @@ omap_i2c_rev1_isr(int this_irq, void *dev_id)
#define omap_i2c_rev1_isr NULL
#endif
+/*
+ * OMAP3430 Errata 1.153: When an XRDY/XDR is hit, wait for XUDF before writing
+ * data to DATA_REG. Otherwise some data bytes can be lost while transferring
+ * them from the memory to the I2C interface.
+ */
+static int omap3430_workaround(struct omap_i2c_dev *dev, u16 *stat, int *err)
+{
+ while (!(*stat & OMAP_I2C_STAT_XUDF)) {
+ if (*stat & (OMAP_I2C_STAT_NACK | OMAP_I2C_STAT_AL)) {
+ omap_i2c_ack_stat(dev, *stat & (OMAP_I2C_STAT_XRDY |
+ OMAP_I2C_STAT_XDR));
+ *err |= OMAP_I2C_STAT_XUDF;
+ return -1;
+ }
+ cpu_relax();
+ *stat = omap_i2c_read_reg(dev, OMAP_I2C_STAT_REG);
+ }
+
+ return 0;
+}
+
static irqreturn_t
omap_i2c_isr(int this_irq, void *dev_id)
{
@@ -794,25 +815,9 @@ complete:
break;
}
- /*
- * OMAP3430 Errata 1.153: When an XRDY/XDR
- * is hit, wait for XUDF before writing data
- * to DATA_REG. Otherwise some data bytes can
- * be lost while transferring them from the
- * memory to the I2C interface.
- */
-
- if (dev->rev <= OMAP_I2C_REV_ON_3430) {
- while (!(stat & OMAP_I2C_STAT_XUDF)) {
- if (stat & (OMAP_I2C_STAT_NACK | OMAP_I2C_STAT_AL)) {
- omap_i2c_ack_stat(dev, stat & (OMAP_I2C_STAT_XRDY | OMAP_I2C_STAT_XDR));
- err |= OMAP_I2C_STAT_XUDF;
- goto complete;
- }
- cpu_relax();
- stat = omap_i2c_read_reg(dev, OMAP_I2C_STAT_REG);
- }
- }
+ if (dev->rev <= OMAP_I2C_REV_ON_3430 &&
+ omap3430_workaround(dev, &stat, &err))
+ goto complete;
omap_i2c_write_reg(dev, OMAP_I2C_DATA_REG, w);
}
--
1.6.3.3
next prev parent reply other threads:[~2009-12-16 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 13:43 [PATCH 0/2] omap i2c interrupt handler fixes Alexander Shishkin
2009-12-16 13:43 ` Alexander Shishkin [this message]
2009-12-16 13:43 ` [PATCH 1/2] omap i2c: make errata 1.153 workaround a separate function Alexander Shishkin
[not found] ` <1260970986-26613-3-git-send-email-virtuoso-0lOfPCoBze7YtjvyW6yDsg@public.gmane.org>
2009-12-16 13:46 ` [PATCH 2/2] omap i2c: add a timeout to the busy waiting Alexander Shishkin
2009-12-16 13:57 ` [PATCH 1/2] omap i2c: make errata 1.153 workaround a separate function Alexander Shishkin
-- strict thread matches above, loose matches on Subject: below --
2009-12-16 14:02 [PATCH 0/2][RESEND] omap i2c interrupt handler fixes Alexander Shishkin
[not found] ` <1260972144-31593-1-git-send-email-virtuoso-0lOfPCoBze7YtjvyW6yDsg@public.gmane.org>
2009-12-16 14:02 ` [PATCH 1/2] omap i2c: make errata 1.153 workaround a separate function Alexander Shishkin
[not found] ` <1260972144-31593-2-git-send-email-virtuoso-0lOfPCoBze7YtjvyW6yDsg@public.gmane.org>
2009-12-17 3:06 ` Menon, Nishanth
[not found] ` <4B29A036.2040807-l0cyMroinI0@public.gmane.org>
2009-12-17 12:48 ` Alexander Shishkin
2009-12-17 13:18 ` Menon, Nishanth
2010-03-16 11:27 ` Alexander Shishkin
[not found] ` <20100316112741.GA13389-rKUxRSusx2MF9cI+BDt40OTW4wlIGRCZ@public.gmane.org>
2010-03-16 14:30 ` Tony Lindgren
[not found] ` <20100316143025.GR2900-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-03-25 9:52 ` Alexander Shishkin
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=1260970986-26613-2-git-send-email-virtuoso@slind.org \
--to=virtuoso@slind.org \
--cc=ben-linux@fluff.org \
--cc=linux-i2c@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).