public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: pramod gurav <pramodforum@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: I2C1 controller timed out issue
Date: Sat, 20 Dec 2008 16:09:29 +0200	[thread overview]
Message-ID: <20081220131321.GB10866@frodo> (raw)
In-Reply-To: <f502236f0812200204h1ef1df01sf79243e6e276074d@mail.gmail.com>

On Sat, Dec 20, 2008 at 03:34:00PM +0530, pramod gurav wrote:
> Hi,
> I am working on OMAP3430 board. The kernel is linux-omap-2.6.
> The twl5030 module is sitting on i2c1.
> I often come across a error saying
> 
> i2c_omap i2c_omap.1: controller timed out
> i2c_omap i2c_omap.1: controller timed out
> 
> This is all what appears in logs when i2c1 times out and all the
> other slave devices on i2c1 stop responding. Other i2c busses(2)
> work properly. if try to reboot the I2C fails to respnd in u-boot also
> saying
> 
> timed out in wait_for_pin: I2C_STAT=0
> I2C read failed
> timed out in wait_for_pin: I2C_STAT=0
> I2C read failed
> timed out in wait_for_pin: I2C_STAT=0
> I2C read failed
> 
> I have to to do hard reset to progress with the boot.
> 
> I gone through the changes happened to i2-omap driver in between
> and tried applying the patches manually.
> The problem still persists.
> May be I am missing some more changes.
> 
> The i2-omap.c source is attached herewith this mail.
> Somebody please suggest me on this issue if this has been seen as
> a issue and if fixed.

Are you using current linux-omap from git ? This problem is long gone.

-- 
balbi

  reply	other threads:[~2008-12-20 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20 10:04 I2C1 controller timed out issue pramod gurav
2008-12-20 14:09 ` Felipe Balbi [this message]
2008-12-22  5:14   ` pramod gurav
     [not found]     ` <f502236f0812212114p4b20e81br52d9031c4673f886-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-22  5:22       ` pramod gurav
     [not found]         ` <f502236f0812212122x3cb45444ld30c5e56d3546726-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-22  7:26           ` David Brownell
     [not found]   ` <c236f0530812200935y1397d03bm54fe7f3714776b0@mail.gmail.com>
2008-12-22 16:03     ` Felipe Balbi
2008-12-22 16:07       ` Kainan Cha

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=20081220131321.GB10866@frodo \
    --to=me@felipebalbi.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pramodforum@gmail.com \
    /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