linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hein Tibosch <hein_tibosch@yahoo.es>
To: Vikram Pandita <vikram.pandita@ti.com>,
	Shubhrajyoti D <shubhrajyoti@ti.com>,
	Tony Lindgren <tony@atomide.com>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] i2c-omap: always send stop after nack
Date: Tue, 16 Jul 2013 16:19:35 +0800	[thread overview]
Message-ID: <51E50217.1000507@yahoo.es> (raw)

Hi Vikram,

On a OMAP4460, i2c-bus-3:

A driver (lm75) is causing many 'timeout waiting for bus ready' errors.
SDA remains high (as it should), but SCL remains low after a NACK.
The bus becomes _unusable for other clients_.

While probing, "lm75" writes a command, followed by a read + stop,
but the write command is NACK'd. The chip does accept other writes/reads,
it just refuses to ack invalid commands.

Can you tell me if the patch below would make any sense? Or is it the
responsibility of the client to reset the i2c_smbus?

In case of M_IGNORE_NAK there is no problem, a STOP will follow after the
last command.


Thanks, Hein

Signed-off-by: Hein Tibosch <hein_tibosch@yahoo.es>

---
 drivers/i2c/busses/i2c-omap.c |    8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index e02f9e3..2f7a712 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -615,11 +615,9 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
 	if (dev->cmd_err & OMAP_I2C_STAT_NACK) {
 		if (msg->flags & I2C_M_IGNORE_NAK)
 			return 0;
-		if (stop) {
-			w = omap_i2c_read_reg(dev, OMAP_I2C_CON_REG);
-			w |= OMAP_I2C_CON_STP;
-			omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, w);
-		}
+		w = omap_i2c_read_reg(dev, OMAP_I2C_CON_REG);
+		w |= OMAP_I2C_CON_STP;
+		omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, w);
 		return -EREMOTEIO;
 	}
 	return -EIO;
-- 
1.7.9.5

             reply	other threads:[~2013-07-16  8:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  8:19 Hein Tibosch [this message]
2013-07-16  9:03 ` [PATCH] i2c-omap: always send stop after nack Felipe Balbi
     [not found]   ` <20130716090300.GG8880-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-07-16  9:33     ` Hein Tibosch
2013-07-16  9:42       ` Felipe Balbi
     [not found]         ` <20130716094212.GL8880-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-07-16 11:01           ` Grygorii Strashko
2013-07-16 11:27             ` Felipe Balbi
2013-07-16 12:08               ` Grygorii Strashko
     [not found]                 ` <51E537A4.40300-l0cyMroinI0@public.gmane.org>
2013-07-16 13:00                   ` Felipe Balbi
2013-07-16 16:17                     ` Hein Tibosch
     [not found]                       ` <51E57211.2040001-mRCrAkd8dF0@public.gmane.org>
2013-08-19 12:11                         ` Wolfram Sang
2013-08-19 13:57                           ` Felipe Balbi
2013-08-19 14:05                             ` Wolfram Sang
2013-08-20 16:39                           ` Grygorii Strashko

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=51E50217.1000507@yahoo.es \
    --to=hein_tibosch@yahoo.es \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=shubhrajyoti@ti.com \
    --cc=tony@atomide.com \
    --cc=vikram.pandita@ti.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;
as well as URLs for NNTP newsgroup(s).