From: Rajeev kumar <rajeev-dlh.kumar-qxv4g6HH51o@public.gmane.org>
To: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@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: Mon, 24 Oct 2011 12:40:55 +0530 [thread overview]
Message-ID: <4EA50F7F.6000400@st.com> (raw)
In-Reply-To: <1319439118-3800-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
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>
~Rajeev
WARNING: multiple messages have this Message-ID (diff)
From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: Shubhrajyoti D <shubhrajyoti@ti.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vikram Pandita <vikram.pandita@ti.com>
Subject: Re: [PATCH ] i2c: omap: recover from Bus Busy condition
Date: Mon, 24 Oct 2011 12:40:55 +0530 [thread overview]
Message-ID: <4EA50F7F.6000400@st.com> (raw)
In-Reply-To: <1319439118-3800-1-git-send-email-shubhrajyoti@ti.com>
On 10/24/2011 12:21 PM, Shubhrajyoti D wrote:
> From: Vikram Pandita<vikram.pandita@ti.com>
>
> 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@ti.com>
> Signed-off-by: Shubhrajyoti D<shubhrajyoti@ti.com>
> ---
> drivers/i2c/busses/i2c-omap.c | 15 +++++++++++++--
> 1 files changed, 13 insertions(+), 2 deletions(-)
Reviewed-by: Rajeev Kumar <rajeev-dlh.kumar@st.com>
~Rajeev
next prev parent reply other threads:[~2011-10-24 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 6:51 [PATCH ] i2c: omap: recover from Bus Busy condition Shubhrajyoti D
2011-10-24 6:51 ` Shubhrajyoti D
[not found] ` <1319439118-3800-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-10-24 7:10 ` Rajeev kumar [this message]
2011-10-24 7:10 ` Rajeev kumar
[not found] ` <4EA50F7F.6000400-qxv4g6HH51o@public.gmane.org>
2011-10-25 13:09 ` Shubhrajyoti
2011-10-25 13:09 ` Shubhrajyoti
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=4EA50F7F.6000400@st.com \
--to=rajeev-dlh.kumar-qxv4g6hh51o@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shubhrajyoti-l0cyMroinI0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.