From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rajeev kumar Subject: Re: [PATCH ] i2c: omap: recover from Bus Busy condition Date: Mon, 24 Oct 2011 12:40:55 +0530 Message-ID: <4EA50F7F.6000400@st.com> References: <1319439118-3800-1-git-send-email-shubhrajyoti@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1319439118-3800-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Shubhrajyoti D Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Vikram Pandita List-Id: linux-i2c@vger.kernel.org On 10/24/2011 12:21 PM, Shubhrajyoti D wrote: > From: Vikram Pandita > > 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 > Signed-off-by: Shubhrajyoti D > --- > drivers/i2c/busses/i2c-omap.c | 15 +++++++++++++-- > 1 files changed, 13 insertions(+), 2 deletions(-) Reviewed-by: Rajeev Kumar ~Rajeev