All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Subject: RE: State of SDP4430 platform
Date: Mon, 7 Feb 2011 11:35:00 +0530	[thread overview]
Message-ID: <db3a1ff9033b3a83b93c42a2857812e1@mail.gmail.com> (raw)
In-Reply-To: <20110206094919.GA11707@n2100.arm.linux.org.uk>

> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux@arm.linux.org.uk]
> Sent: Sunday, February 06, 2011 3:19 PM
> To: Santosh Shilimkar
> Cc: Paul Walmsley; linux-omap@vger.kernel.org
> Subject: Re: State of SDP4430 platform
>
> On Mon, Jan 17, 2011 at 03:37:34PM +0530, Santosh Shilimkar wrote:
> > The I2C timeout issue I could reproduce on my ES1.0 board. It's
> ES1.0
> > specific issue because I2C burst mode wasn't fuctional on it. Twl
> RTC
> > driver uses I2C burst mode and hence it times out. Other TWL I2C
> > module has no such issue.
> > The pull work-around we tried was not reliable hence it was
> dropped.
> >
> > In short the TWL RTC driver won't function on ES1.0. Apart from
> that
> > rest of the I2C clients should work as usual.
>
> The ES2.2 OMAP4 arrived on Friday.  Fitting it resulted in no change
> to the I2C timeouts:
>
Good that finally the tile reached you. Will have somebody look at
this. Meanwhile, can you send your .config? With the regular
omap2plus defconfig, we didn't see the issue last time.

Regards,
Santosh

  reply	other threads:[~2011-02-07  6:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16  1:09 State of SDP4430 platform Russell King - ARM Linux
2011-01-16  6:06 ` Paul Walmsley
2011-01-16  6:25   ` Santosh Shilimkar
2011-01-17 10:07     ` Santosh Shilimkar
2011-01-17 23:19       ` Paul Walmsley
2011-01-18  6:53         ` Santosh Shilimkar
2011-01-19 15:26         ` Krishnamoorthy, Balaji T
2011-01-19 23:26           ` Paul Walmsley
2011-01-19 23:27             ` Paul Walmsley
2011-02-07 23:49               ` Paul Walmsley
2011-03-02 18:50                 ` Paul Walmsley
2011-03-03 15:23                   ` Krishnamoorthy, Balaji T
2011-02-06  9:49       ` Russell King - ARM Linux
2011-02-07  6:05         ` Santosh Shilimkar [this message]
2011-02-07  6:58         ` Krishnamoorthy, Balaji T
2011-02-07  8:18 ` Gulati, Shweta

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=db3a1ff9033b3a83b93c42a2857812e1@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.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 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.