From: Alexander Kochetkov <al.kochet@gmail.com>
To: linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexander Kochetkov <al.kochet@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@ti.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [PATCH] i2c: omap: fix i207 errata handling
Date: Fri, 21 Nov 2014 03:29:40 +0300 [thread overview]
Message-ID: <089B5BDA-682D-46B6-869F-A6ADDFE691C3@gmail.com> (raw)
In-Reply-To: <1416529011-21803-1-git-send-email-al.kochet@gmail.com>
21 нояб. 2014 г., в 3:16, Alexander Kochetkov <al.kochet@gmail.com> написал(а):
> commit 6d9939f651419a63e091105663821f9c7d3fec37 (i2c: omap: split out [XR]DR
> and [XR]RDY) changed the way how errata i207 (I2C: RDR Flag May Be Incorrectly
> Set) get handled.
It's is seen if open 6d9939f651419a63e09^ and 6d9939f651419a63e09 side by side:
6d9939f651419a63e09^:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/i2c/busses/i2c-omap.c?id=540a4790f7da0d3ca5ad9d726f198a5eb4db05ec#n800
6d9939f651419a63e09:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/i2c/busses/i2c-omap.c?id=6d9939f651419a63e091105663821f9c7d3fec37#n800
Errata "2C: RDR Flag May Be Incorrectly Set"
http://www.ti.com/lit/er/sprz319f/sprz319f.pdf
21 нояб. 2014 г., в 3:16, Alexander Kochetkov <al.kochet@gmail.com> написал(а):
> Found by code review. Real impact haven't seen.
> Tested on Beagleboard XM C.
Does anybody know the "certain rare conditions" when RDR errata appears?
I tested without luck (Beagleboard XM C).
next prev parent reply other threads:[~2014-11-21 0:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 0:16 [PATCH] i2c: omap: fix i207 errata handling Alexander Kochetkov
2014-11-21 0:29 ` Alexander Kochetkov [this message]
[not found] ` <089B5BDA-682D-46B6-869F-A6ADDFE691C3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-21 23:16 ` Alexander Kochetkov
2014-11-21 16:08 ` Felipe Balbi
2014-11-21 23:02 ` Alexander Kochetkov
[not found] ` <B174E67D-9CCF-48B6-A5E5-911668161823-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-22 21:13 ` Wolfram Sang
2014-11-22 21:08 ` 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=089B5BDA-682D-46B6-869F-A6ADDFE691C3@gmail.com \
--to=al.kochet@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=wsa@the-dreams.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox