From: Sebastian Reichel <sre@kernel.org>
To: Vignesh R <vigneshr@ti.com>
Cc: Claudio Foellmi <claudio.foellmi@ergon.ch>,
"Strashko, Grygorii" <grygorii.strashko@ti.com>,
Tony Lindgren <tony@atomide.com>, "Nori, Sekhar" <nsekhar@ti.com>,
"Cooper Jr., Franklin" <fcooper@ti.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Wolfram Sang <wsa@the-dreams.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] i2c-omap: Trigger bus recovery in lockup case
Date: Wed, 20 Sep 2017 17:02:16 +0200 [thread overview]
Message-ID: <20170920150215.fw7dcru6m234pp56@earth> (raw)
In-Reply-To: <cbb3aaa2-44d1-8a7d-1d8e-1433b0a7b9d3@ti.com>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Hi,
On Tue, Sep 19, 2017 at 04:20:49PM +0530, Vignesh R wrote:
> I hit a situation where when communicating with a faulty i2c device, the
> last transaction on the bus does not end with proper STOP condition on
> the i2c bus.
Yeah, omap-i2c seems to have big issues with a device not acking a
transaction properly. It can be easily triggered on N950 (OMAP3 based):
https://patchwork.kernel.org/patch/9914785/
Please Cc me when sending a patch, so that I can test it on N950.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-20 15:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 15:39 [PATCH] i2c-omap: Trigger bus recovery in lockup case Claudio Foellmi
2017-09-15 23:31 ` Grygorii Strashko
2017-09-18 5:24 ` Vignesh R
2017-09-18 12:01 ` Claudio Foellmi
2017-09-19 10:50 ` Vignesh R
2017-09-20 9:24 ` Claudio Foellmi
2017-09-20 15:02 ` Sebastian Reichel [this message]
2017-09-26 12:24 ` Claudio Foellmi
2017-09-29 12:52 ` Sebastian Reichel
2017-09-29 15:17 ` Claudio Foellmi
2017-09-29 16:37 ` Sebastian Reichel
2017-10-02 23:01 ` Grygorii Strashko
2017-10-06 15:22 ` Sebastian Reichel
2017-10-03 10:32 ` Vignesh R
2017-10-04 9:43 ` [PATCH v2] i2c: omap: " Claudio Foellmi
2017-10-05 6:01 ` Vignesh R
2017-10-05 12:30 ` Grygorii Strashko
2017-10-28 20:52 ` Wolfram Sang
2017-10-30 9:11 ` Claudio Foellmi
2017-10-30 14:19 ` 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=20170920150215.fw7dcru6m234pp56@earth \
--to=sre@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=claudio.foellmi@ergon.ch \
--cc=fcooper@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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