All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, nicolas.ferre@atmel.com,
	peda@lysator.liu.se, cyrille.pitchen@atmel.com
Subject: Re: [PATCH v3] i2c: at91: manage unexpected RXRDY flag when starting a transfer
Date: Mon, 26 Oct 2015 15:47:26 +0100	[thread overview]
Message-ID: <20151026144726.GB5588@katana> (raw)
In-Reply-To: <1445852312-28389-1-git-send-email-ludovic.desroches@atmel.com>

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

On Mon, Oct 26, 2015 at 10:38:27AM +0100, Ludovic Desroches wrote:
> In some cases, we could start a new i2c transfer with the RXRDY flag
> set. It is not a clean state and it leads to print annoying error
> messages even if there no real issue. The cause is only having garbage
> data in the Receive Holding Register because of a weird behavior of the
> RXRDY flag.
> 
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> Fixes: 93563a6a71bb ("i2c: at91: fix a race condition when using the DMA
> controller")
> Reported-by: Peter Rosin <peda@lysator.liu.se>
> Tested-by: Peter Rosin <peda@lysator.liu.se>
> Cc: stable@vger.kernel.org #4.1

Applied to for-next, thanks!


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] i2c: at91: manage unexpected RXRDY flag when starting a transfer
Date: Mon, 26 Oct 2015 15:47:26 +0100	[thread overview]
Message-ID: <20151026144726.GB5588@katana> (raw)
In-Reply-To: <1445852312-28389-1-git-send-email-ludovic.desroches@atmel.com>

On Mon, Oct 26, 2015 at 10:38:27AM +0100, Ludovic Desroches wrote:
> In some cases, we could start a new i2c transfer with the RXRDY flag
> set. It is not a clean state and it leads to print annoying error
> messages even if there no real issue. The cause is only having garbage
> data in the Receive Holding Register because of a weird behavior of the
> RXRDY flag.
> 
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> Fixes: 93563a6a71bb ("i2c: at91: fix a race condition when using the DMA
> controller")
> Reported-by: Peter Rosin <peda@lysator.liu.se>
> Tested-by: Peter Rosin <peda@lysator.liu.se>
> Cc: stable at vger.kernel.org #4.1

Applied to for-next, thanks!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151026/4c8e17df/attachment.sig>

  reply	other threads:[~2015-10-26 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 13:44 [PATCH v2 1/2] i2c: at91: fix write transfers by clearing pending interrupt first Ludovic Desroches
2015-10-21 13:44 ` Ludovic Desroches
2015-10-21 13:44 ` Ludovic Desroches
2015-10-21 13:44 ` [PATCH v2 2/2] i2c: at91: manage unexpected RXRDY flag when starting a transfer Ludovic Desroches
2015-10-21 13:44   ` Ludovic Desroches
2015-10-21 13:44   ` Ludovic Desroches
2015-10-22 13:08   ` Wolfram Sang
2015-10-22 13:08     ` Wolfram Sang
2015-10-26  9:38     ` [PATCH v3] " Ludovic Desroches
2015-10-26  9:38       ` Ludovic Desroches
2015-10-26  9:38       ` Ludovic Desroches
2015-10-26 14:47       ` Wolfram Sang [this message]
2015-10-26 14:47         ` Wolfram Sang
2015-10-22 13:07 ` [PATCH v2 1/2] i2c: at91: fix write transfers by clearing pending interrupt first Wolfram Sang
2015-10-22 13:07   ` Wolfram Sang

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=20151026144726.GB5588@katana \
    --to=wsa@the-dreams.de \
    --cc=cyrille.pitchen@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=peda@lysator.liu.se \
    /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.