From: Shubhrajyoti <shubhrajyoti-l0cyMroinI0@public.gmane.org>
To: Rajeev kumar <rajeev-dlh.kumar-qxv4g6HH51o@public.gmane.org>
Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Vikram Pandita <vikram.pandita-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH ] i2c: omap: recover from Bus Busy condition
Date: Tue, 25 Oct 2011 18:39:35 +0530 [thread overview]
Message-ID: <4EA6B50F.40805@ti.com> (raw)
In-Reply-To: <4EA50F7F.6000400-qxv4g6HH51o@public.gmane.org>
On Monday 24 October 2011 12:40 PM, Rajeev kumar wrote:
> On 10/24/2011 12:21 PM, Shubhrajyoti D wrote:
>> From: Vikram Pandita<vikram.pandita-l0cyMroinI0@public.gmane.org>
>>
>> In case a peripheral is holding the DATA bus low, provide a 400Khz
>> constant clock output using the TEST register.
>>
>> Also soft reset the I2C controller so that there is no stale state
>> left in the HW state machine.
>>
>> A WARN_ON() will be generated when a BB timeout happens.
>>
>> Signed-off-by: Vikram Pandita<vikram.pandita-l0cyMroinI0@public.gmane.org>
>> Signed-off-by: Shubhrajyoti D<shubhrajyoti-l0cyMroinI0@public.gmane.org>
>> ---
>> drivers/i2c/busses/i2c-omap.c | 15 +++++++++++++--
>> 1 files changed, 13 insertions(+), 2 deletions(-)
>
>
> Reviewed-by: Rajeev Kumar <rajeev-dlh.kumar-qxv4g6HH51o@public.gmane.org>
Thanks for your review.
>
>
> ~Rajeev
prev parent reply other threads:[~2011-10-25 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 6:51 [PATCH ] i2c: omap: recover from Bus Busy condition Shubhrajyoti D
[not found] ` <1319439118-3800-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-10-24 7:10 ` Rajeev kumar
[not found] ` <4EA50F7F.6000400-qxv4g6HH51o@public.gmane.org>
2011-10-25 13:09 ` Shubhrajyoti [this message]
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=4EA6B50F.40805@ti.com \
--to=shubhrajyoti-l0cymroini0@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rajeev-dlh.kumar-qxv4g6HH51o@public.gmane.org \
--cc=vikram.pandita-l0cyMroinI0@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).