From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Paul Walmsley <paul@pwsan.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org
Subject: RE: State of SDP4430 platform
Date: Mon, 17 Jan 2011 15:37:34 +0530 [thread overview]
Message-ID: <ceedbf20a12a6e821fda1496b10297a2@mail.gmail.com> (raw)
In-Reply-To: <a40bc7a304b60cef73a3a0cfb84b2ee8@mail.gmail.com>
> -----Original Message-----
> From: Santosh Shilimkar [mailto:santosh.shilimkar@ti.com]
> Sent: Sunday, January 16, 2011 11:56 AM
> To: Paul Walmsley; Russell King - ARM Linux
> Cc: linux-omap@vger.kernel.org
> Subject: RE: State of SDP4430 platform
>
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > owner@vger.kernel.org] On Behalf Of Paul Walmsley
> > Sent: Sunday, January 16, 2011 11:37 AM
> > To: Russell King - ARM Linux
> > Cc: linux-omap@vger.kernel.org
> > Subject: Re: State of SDP4430 platform
> >
[.....]
> > > Other stuff that shows in this boot log:
> >
> > ...
> >
> > > - Bunch of regulators are returning errors (is this a problem?)
> > > - I2C timeouts which add quite a bit to the boot-time
> >
> > These two are probably related. Looks like something is wrong
> with
> > communication with the TWL/TPS PMIC on that board. Those problems
> > don't
> > show up on the OMAP4430ES2 Panda here, so they are probably
> > 4430SDP-specific.
> >
> >
> Actually I don't see these errors which ring a bell. There was an
> I2C pull related issue with ES1.0 silicon. I guess these timeouts
> would show up only on ES1.0 OMAP4 boards and not on ES2.0 boards.
>
> Monday I will check on my ES1.0 board and if needed send an updated
> bootloader ( setting up right pull values) or a patch to kernel.
>
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.
Regards,
Santosh
next prev parent reply other threads:[~2011-01-17 10:07 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 [this message]
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
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=ceedbf20a12a6e821fda1496b10297a2@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 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).