From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c-at91: fix data-loss issue
Date: Sat, 14 Apr 2012 08:06:13 +1000 [thread overview]
Message-ID: <4F88A355.2060303@gmail.com> (raw)
In-Reply-To: <1334317476-10044-1-git-send-email-h.feurstein@gmail.com>
On 13/04/12 21:44, Hubert Feurstein wrote:
> In the interrupt handler both status-flags (TXCOMP and RXRDY) might be
> pending at the same time. In this case TXCOMP is handled but NOT RXRDY
> which causes a data-loss on the current transfer. As a consequence also the
> next transfer will be corrupt, because old data is pending in RHR.
>
> To make sure that we do not start with old data in any case, SR and RHR is
> read empty before initiating a new transfer.
>
> Signed-off-by: Hubert Feurstein <h.feurstein@gmail.com>
Couple of very minor comments below.
~Ryan
> ---
> This patch applies on top of [PATCH v9 3/4] drivers/i2c/busses/i2c-at91.c: add new driver
>
> drivers/i2c/busses/i2c-at91.c | 23 ++++++++++++++++-------
> 1 files changed, 16 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
> index 40c39a2..295835f 100644
> --- a/drivers/i2c/busses/i2c-at91.c
> +++ b/drivers/i2c/busses/i2c-at91.c
> @@ -161,18 +161,22 @@ static irqreturn_t atmel_twi_interrupt(int irq, void *dev_id)
> {
> struct at91_twi_dev *dev = dev_id;
> const unsigned status = at91_twi_read(dev, AT91_TWI_SR);
> - const unsigned irqstatus = status & at91_twi_read(dev, AT91_TWI_IMR);
> + unsigned irqstatus = status & at91_twi_read(dev, AT91_TWI_IMR);
> +
> + irqstatus &= (AT91_TWI_RXRDY | AT91_TWI_TXRDY | AT91_TWI_TXCOMP);
> + if (!irqstatus)
> + return IRQ_NONE;
> +
> + if (irqstatus & AT91_TWI_RXRDY)
> + at91_twi_read_next_byte(dev);
> +
> + if (irqstatus & AT91_TWI_TXRDY)
> + at91_twi_write_next_byte(dev);
>
> if (irqstatus & AT91_TWI_TXCOMP) {
> at91_disable_twi_interrupts(dev);
> dev->transfer_status = status;
> complete(&dev->cmd_complete);
> - } else if (irqstatus & AT91_TWI_RXRDY) {
> - at91_twi_read_next_byte(dev);
> - } else if (irqstatus & AT91_TWI_TXRDY) {
> - at91_twi_write_next_byte(dev);
> - } else {
> - return IRQ_NONE;
> }
>
> return IRQ_HANDLED;
> @@ -189,6 +193,10 @@ static int at91_do_twi_transfer(struct at91_twi_dev *dev)
> if (dev->msg->flags & I2C_M_RD) {
> unsigned start_flags = AT91_TWI_START;
>
> + /* clear any pending data */
> + (void)at91_twi_read(dev, AT91_TWI_SR);
> + (void)at91_twi_read(dev, AT91_TWI_RHR);
Drop the void cast.
> +
> /* if only one byte is to be read, immediately stop transfer */
> if (dev->buf_len <= 1 && !(dev->msg->flags & I2C_M_RECV_LEN))
> start_flags |= AT91_TWI_STOP;
> @@ -259,6 +267,7 @@ static int at91_twi_xfer(struct i2c_adapter *adap, struct i2c_msg *msg, int num)
> internal_address |= addr << (8 * i);
> int_addr_flag += AT91_TWI_IADRSZ_1;
> }
> +
Please don't make unrelated whitespace changes.
> at91_twi_write(dev, AT91_TWI_IADR, internal_address);
> }
>
With those fixed, please add:
Reviewed-by: Ryan Mallon <rmallon@gmail.com>
next prev parent reply other threads:[~2012-04-13 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1322479017a.git.n.voss@weinmann.de>
[not found] ` <201203191534.q2JFYl1b012744@gatekeeper.vosshq.de>
2012-04-13 10:17 ` [PATCH v9 3/4] drivers/i2c/busses/i2c-at91.c: add new driver Hubert Feurstein
2012-04-13 10:39 ` Felipe Balbi
2012-04-13 11:44 ` [PATCH] i2c-at91: fix data-loss issue Hubert Feurstein
2012-04-13 22:06 ` Ryan Mallon [this message]
2012-04-16 7:30 ` Voss, Nikolaus
2012-04-16 9:27 ` Hubert Feurstein
2012-04-18 14:39 ` Wolfram Sang
[not found] ` <4F930B77.8070909@ayanes.com>
2012-04-23 5:39 ` Voss, Nikolaus
2012-04-23 6:24 ` Adrian Yanes
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=4F88A355.2060303@gmail.com \
--to=rmallon@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).