From: Alok Chauhan <alokc@nvidia.com>
To: khali@linux-fr.org, ben-linux@fluff.org, swarren@nvidia.com,
olof@lixom.net, bones@secretlab.ca, paul.gortmaker@windriver.com
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Alok Chauhan <alokc@nvidia.com>
Subject: [PATCH] i2c: tegra: Add delay before reset the controller
Date: Thu, 22 Dec 2011 16:11:20 +0530 [thread overview]
Message-ID: <1324550480-26308-1-git-send-email-alokc@nvidia.com> (raw)
From: Alok Chauhan <alokc@nvidia.com>
In NACK error condition, I2C controller violates
clock-to-data setup time before stop. In Software,
because of this reset of controller is happening
before I2C controller could complete STOP condition.
Added worst case delay of 1 ms (assuming lowest
clock frequency will be 1 KHZ) before reset the
controller in case of NACK error.
Signed-off-by: Alok Chauhan <alokc@nvidia.com>
---
drivers/i2c/busses/i2c-tegra.c | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
index 6381604..b731499 100644
--- a/drivers/i2c/busses/i2c-tegra.c
+++ b/drivers/i2c/busses/i2c-tegra.c
@@ -517,6 +517,15 @@ static int tegra_i2c_xfer_msg(struct tegra_i2c_dev *i2c_dev,
if (likely(i2c_dev->msg_err == I2C_ERR_NONE))
return 0;
+ /*
+ * In NACK error condition resetting of I2C controller happens
+ * before STOP condition is properly completed by I2C controller,
+ * so wait for worst case delay of 1 ms (assuming lowest clock
+ * frequency will be 1 KHz) to complete STOP condition.
+ */
+ if (i2c_dev->msg_err == I2C_ERR_NO_ACK)
+ mdelay(1);
+
tegra_i2c_init(i2c_dev);
if (i2c_dev->msg_err == I2C_ERR_NO_ACK) {
if (msg->flags & I2C_M_IGNORE_NAK)
--
1.7.4.1
next reply other threads:[~2011-12-22 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 10:41 Alok Chauhan [this message]
2011-12-22 21:17 ` Olof Johansson
2011-12-23 11:15 ` Alok Chauhan
2011-12-23 11:20 ` Laxman Dewangan
2012-03-30 12:06 Alok Chauhan
2012-03-30 15:54 ` Stephen Warren
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=1324550480-26308-1-git-send-email-alokc@nvidia.com \
--to=alokc@nvidia.com \
--cc=ben-linux@fluff.org \
--cc=bones@secretlab.ca \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul.gortmaker@windriver.com \
--cc=swarren@nvidia.com \
/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
all inboxes | Powered by JetHome®