From: Stephen Warren <swarren@wwwdotorg.org>
To: ben-linux@fluff.org, w.sang@pengutronix.de
Cc: Alok Chauhan <alokc@nvidia.com>,
khali@linux-fr.org, olof@lixom.net, bones@secretlab.ca,
omaplinuxkernel@gmail.com, ccross@android.com,
ldewangan@nvidia.com, linux-tegra@vger.kernel.org,
linux-i2c@vger.kernel.org, dgreid@chromium.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: tegra: Add delay before reset the controller
Date: Fri, 13 Apr 2012 16:51:20 -0600 [thread overview]
Message-ID: <4F88ADE8.4020200@wwwdotorg.org> (raw)
In-Reply-To: <4F7A0500.3060305@wwwdotorg.org>
On 04/02/2012 01:58 PM, Stephen Warren wrote:
> On 04/01/2012 11:53 PM, Alok Chauhan wrote:
>> NACK interrupt generated before I2C controller generates
>> the STOP condition on bus. In Software, because of this
>> reset of controller is happening before I2C controller could
>> complete STOP condition. So wait for some time before resetting
>> the controller so that STOP condition has delivered properly on bus.
>>
>> Added delay of 2 clock period before reset the
>> controller in case of NACK error.
>>
>> Signed-off-by: Alok Chauhan <alokc@nvidia.com>
>
> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
Wolfram, Ben, can this be picked up for 3.5?
next prev parent reply other threads:[~2012-04-13 22:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 5:53 [PATCH v2] i2c: tegra: Add delay before reset the controller Alok Chauhan
2012-04-02 5:59 ` Alok Chauhan
2012-04-02 10:19 ` Shubhrajyoti Datta
2012-04-02 12:06 ` Alok Chauhan
2012-04-02 19:58 ` Stephen Warren
2012-04-13 22:51 ` Stephen Warren [this message]
2012-04-18 14:27 ` Wolfram Sang
2012-04-18 20:02 ` Stephen Warren
2012-04-18 20:20 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2011-12-26 11:14 Alok Chauhan
2012-01-06 16:18 ` Ben Dooks
2012-01-10 4:12 ` Alok Chauhan
2012-02-10 9:20 ` Alok Chauhan
2012-02-10 9:35 ` Shubhrajyoti Datta
2012-02-14 5:49 ` Alok Chauhan
2012-03-08 6:29 ` Alok Chauhan
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=4F88ADE8.4020200@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alokc@nvidia.com \
--cc=ben-linux@fluff.org \
--cc=bones@secretlab.ca \
--cc=ccross@android.com \
--cc=dgreid@chromium.org \
--cc=khali@linux-fr.org \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=omaplinuxkernel@gmail.com \
--cc=w.sang@pengutronix.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