> -Original Message-
> From: Menon, Nishanth
> Sent: Monday, June 22, 2009 11:21 PM
> To: Hald, Ulrik Bech; linux-omap@vger.kernel.org
> Cc: Hald, Ulrik Bech
> Subject: RE: [PATCH 1/1] i2c:OMAP3:Errata workaround for spurious RDR
> event
>
>
> > -Orig
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Ulrik Bech Hald
> Sent: Monday, June 22, 2009 11:25 PM
> To: linux-omap@vger.kernel.org
> Cc: Hald, Ulrik Bech
> Subject: [PATCH 1/1] i2c:OMAP3:
.kernel.org
> Cc: Hald, Ulrik Bech
> Subject: RE: [PATCH 1/1] i2c:OMAP3:Errata workaround for spurious RDR
> event
>
> Signed-off-by: Jagadeesh Bhaskar Pakaravoor
>
> > -Original Message-
> > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> > ow
rik Bech
> Subject: [PATCH 1/1] i2c:OMAP3:Errata workaround for spurious RDR event
>
> Under certain rare conditions, I2C_STAT[13].RDR bit may be set,
> and the corresponding interrupt fire, even when there is no
> data in the receive FIFO, or the I2C data transfer is still
> ongoin
Under certain rare conditions, I2C_STAT[13].RDR bit may be set,
and the corresponding interrupt fire, even when there is no
data in the receive FIFO, or the I2C data transfer is still
ongoing. These spurious RDR events must be ignored by the
software.
A check for OMAP_I2C_STAT_BB is introduced in
