All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Voss, Nikolaus" <N.Voss@weinmann.de>
To: "'devel@ayanes.com'" <devel@ayanes.com>,
	"'Wolfram Sang'" <w.sang@pengutronix.de>,
	"'linux-arm-kernel@lists.infradead.org'" 
	<linux-arm-kernel@lists.infradead.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-i2c@vger.kernel.org'" <linux-i2c@vger.kernel.org>
Cc: "'Hubert Feurstein'" <h.feurstein@gmail.com>,
	"'rmallon@gmail.com'" <rmallon@gmail.com>,
	"'nicolas.ferre@atmel.com'" <nicolas.ferre@atmel.com>,
	"'balbi@ti.com'" <balbi@ti.com>,
	"'ben-linux@fluff.org'" <ben-linux@fluff.org>
Subject: RE: [PATCH] i2c-at91: fix data-loss issue
Date: Mon, 23 Apr 2012 07:39:55 +0200	[thread overview]
Message-ID: <EF2E73589CA71846A15D0B2CDF79505D0905DB4657@wm021.weinmann.com> (raw)
In-Reply-To: <4F930B77.8070909@ayanes.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1962 bytes --]

Adrian Yanes wrote on 2012-04-21:
> On the other hand we found that the Underrun Error (UNRE) is not handled
> in the driver. When we send data up > 2-4 bytes (quite random to say
> when it really fails) and we add some dev_dbg() to print
> dev->transfer_status we get 141 (==UNRE). According with the datasheet,
> after the first UNRE received "this action automatically generated a
> STOP bit in Master Mode. Reset by read in TWI_SR when TXCOMP is set."
> 
> We thought that one possibility for this was that the board was too slow
> to process the requests or that other interrupts were interfering.
> Disabling the interrupts inside of the twi interrupt handler did not
> help either.
> 
> The datasheet does not mention any method to implement some mechanism to
> avoid the UNRE telling the hardware to wait a bit longer for the next
> byte. Thus, one way will be to restart the transfer with the remaining
> bytes (maybe only applicable to at91rm9200) or just to return some
> error/message to userland informing that could not send all the data.

The latter is probably the easiest and most transparent solution.
There is no UNRE on G45, it just pauses the clock on an underrun
condition.

So in case UNRE is set, EIO should be returned similar to the already
handled OVRE:

diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
index a6f9e73..a84e19b 100644
--- a/drivers/i2c/busses/i2c-at91.c
+++ b/drivers/i2c/busses/i2c-at91.c
@@ -238,6 +238,11 @@ static int at91_do_twi_transfer(struct at91_twi_dev *dev)
 		dev_err(dev->dev, "overrun while reading\n");
 		return -EIO;
 	}
+	if (dev->transfer_status & AT91_TWI_UNRE && dev->is_rm9200) {
+		dev_err(dev->dev, "underrun while writing\n");
+		return -EIO;
+	}
+
 	dev_dbg(dev->dev, "transfer complete\n");
 
 	return 0;

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

WARNING: multiple messages have this Message-ID (diff)
From: "Voss, Nikolaus" <N.Voss@weinmann.de>
To: "'devel@ayanes.com'" <devel@ayanes.com>,
	'Wolfram Sang' <w.sang@pengutronix.de>,
	"'linux-arm-kernel@lists.infradead.org'"
	<linux-arm-kernel@lists.infradead.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-i2c@vger.kernel.org'" <linux-i2c@vger.kernel.org>
Cc: 'Hubert Feurstein' <h.feurstein@gmail.com>,
	"'ben-linux@fluff.org'" <ben-linux@fluff.org>,
	"'nicolas.ferre@atmel.com'" <nicolas.ferre@atmel.com>,
	"'rmallon@gmail.com'" <rmallon@gmail.com>,
	"'balbi@ti.com'" <balbi@ti.com>
Subject: RE: [PATCH] i2c-at91: fix data-loss issue
Date: Mon, 23 Apr 2012 07:39:55 +0200	[thread overview]
Message-ID: <EF2E73589CA71846A15D0B2CDF79505D0905DB4657@wm021.weinmann.com> (raw)
In-Reply-To: <4F930B77.8070909@ayanes.com>

Adrian Yanes wrote on 2012-04-21:
> On the other hand we found that the Underrun Error (UNRE) is not handled
> in the driver. When we send data up > 2-4 bytes (quite random to say
> when it really fails) and we add some dev_dbg() to print
> dev->transfer_status we get 141 (==UNRE). According with the datasheet,
> after the first UNRE received "this action automatically generated a
> STOP bit in Master Mode. Reset by read in TWI_SR when TXCOMP is set."
> 
> We thought that one possibility for this was that the board was too slow
> to process the requests or that other interrupts were interfering.
> Disabling the interrupts inside of the twi interrupt handler did not
> help either.
> 
> The datasheet does not mention any method to implement some mechanism to
> avoid the UNRE telling the hardware to wait a bit longer for the next
> byte. Thus, one way will be to restart the transfer with the remaining
> bytes (maybe only applicable to at91rm9200) or just to return some
> error/message to userland informing that could not send all the data.

The latter is probably the easiest and most transparent solution.
There is no UNRE on G45, it just pauses the clock on an underrun
condition.

So in case UNRE is set, EIO should be returned similar to the already
handled OVRE:

diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
index a6f9e73..a84e19b 100644
--- a/drivers/i2c/busses/i2c-at91.c
+++ b/drivers/i2c/busses/i2c-at91.c
@@ -238,6 +238,11 @@ static int at91_do_twi_transfer(struct at91_twi_dev *dev)
 		dev_err(dev->dev, "overrun while reading\n");
 		return -EIO;
 	}
+	if (dev->transfer_status & AT91_TWI_UNRE && dev->is_rm9200) {
+		dev_err(dev->dev, "underrun while writing\n");
+		return -EIO;
+	}
+
 	dev_dbg(dev->dev, "transfer complete\n");
 
 	return 0;

WARNING: multiple messages have this Message-ID (diff)
From: N.Voss@weinmann.de (Voss, Nikolaus)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c-at91: fix data-loss issue
Date: Mon, 23 Apr 2012 07:39:55 +0200	[thread overview]
Message-ID: <EF2E73589CA71846A15D0B2CDF79505D0905DB4657@wm021.weinmann.com> (raw)
In-Reply-To: <4F930B77.8070909@ayanes.com>

Adrian Yanes wrote on 2012-04-21:
> On the other hand we found that the Underrun Error (UNRE) is not handled
> in the driver. When we send data up > 2-4 bytes (quite random to say
> when it really fails) and we add some dev_dbg() to print
> dev->transfer_status we get 141 (==UNRE). According with the datasheet,
> after the first UNRE received "this action automatically generated a
> STOP bit in Master Mode. Reset by read in TWI_SR when TXCOMP is set."
> 
> We thought that one possibility for this was that the board was too slow
> to process the requests or that other interrupts were interfering.
> Disabling the interrupts inside of the twi interrupt handler did not
> help either.
> 
> The datasheet does not mention any method to implement some mechanism to
> avoid the UNRE telling the hardware to wait a bit longer for the next
> byte. Thus, one way will be to restart the transfer with the remaining
> bytes (maybe only applicable to at91rm9200) or just to return some
> error/message to userland informing that could not send all the data.

The latter is probably the easiest and most transparent solution.
There is no UNRE on G45, it just pauses the clock on an underrun
condition.

So in case UNRE is set, EIO should be returned similar to the already
handled OVRE:

diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
index a6f9e73..a84e19b 100644
--- a/drivers/i2c/busses/i2c-at91.c
+++ b/drivers/i2c/busses/i2c-at91.c
@@ -238,6 +238,11 @@ static int at91_do_twi_transfer(struct at91_twi_dev *dev)
 		dev_err(dev->dev, "overrun while reading\n");
 		return -EIO;
 	}
+	if (dev->transfer_status & AT91_TWI_UNRE && dev->is_rm9200) {
+		dev_err(dev->dev, "underrun while writing\n");
+		return -EIO;
+	}
+
 	dev_dbg(dev->dev, "transfer complete\n");
 
 	return 0;

  reply	other threads:[~2012-04-23  5:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 15:07 [PATCH v9 0/4] AT91: replace broken TWI driver i2c-at91.c Nikolaus Voss
2012-03-19 15:07 ` Nikolaus Voss
2011-11-08 10:49 ` [PATCH v9 1/4] drivers/i2c/busses/i2c-at91.c: remove broken driver Nikolaus Voss
2011-11-08 10:49   ` Nikolaus Voss
2011-11-08 10:49 ` [PATCH v9 3/4] drivers/i2c/busses/i2c-at91.c: add new driver Nikolaus Voss
2011-11-08 10:49   ` Nikolaus Voss
2012-04-13 10:17   ` Hubert Feurstein
2012-04-13 10:17     ` Hubert Feurstein
2012-04-13 10:17     ` Hubert Feurstein
2012-04-13 10:39     ` Felipe Balbi
2012-04-13 10:39       ` Felipe Balbi
2012-04-13 10:39       ` Felipe Balbi
2012-04-13 11:44       ` [PATCH] i2c-at91: fix data-loss issue Hubert Feurstein
2012-04-13 11:44         ` Hubert Feurstein
2012-04-13 11:44         ` Hubert Feurstein
2012-04-13 22:06         ` Ryan Mallon
2012-04-13 22:06           ` Ryan Mallon
2012-04-13 22:06           ` Ryan Mallon
2012-04-16  7:30         ` Voss, Nikolaus
2012-04-16  7:30           ` Voss, Nikolaus
2012-04-16  7:30           ` Voss, Nikolaus
2012-04-16  9:27           ` Hubert Feurstein
2012-04-16  9:27             ` Hubert Feurstein
2012-04-16  9:27             ` Hubert Feurstein
2012-04-18 14:39           ` Wolfram Sang
2012-04-18 14:39             ` Wolfram Sang
2012-04-18 14:39             ` Wolfram Sang
2012-04-21 19:33             ` Adrian Yanes
2012-04-23  5:39               ` Voss, Nikolaus [this message]
2012-04-23  5:39                 ` Voss, Nikolaus
2012-04-23  5:39                 ` Voss, Nikolaus
2012-04-23  6:24                 ` Adrian Yanes
2012-04-23  6:24                   ` Adrian Yanes
2012-04-23  6:24                   ` Adrian Yanes
2012-04-25  5:26                   ` Adrian Yanes
2011-11-08 11:09 ` [PATCH v9 2/4] Replace clk_lookup.con_id with clk_lookup.dev_id entries for twi clk Nikolaus Voss
2011-11-08 11:09   ` Nikolaus Voss
2011-11-08 11:11 ` [PATCH v9 4/4] G45 TWI: remove open drain setting for twi function gpios Nikolaus Voss
2011-11-08 11:11   ` Nikolaus Voss

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=EF2E73589CA71846A15D0B2CDF79505D0905DB4657@wm021.weinmann.com \
    --to=n.voss@weinmann.de \
    --cc=balbi@ti.com \
    --cc=ben-linux@fluff.org \
    --cc=devel@ayanes.com \
    --cc=h.feurstein@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=rmallon@gmail.com \
    --cc=w.sang@pengutronix.de \
    /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.