From: "Krishnamoorthy, Balaji T" <balajitk@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org
Subject: Re: State of SDP4430 platform
Date: Thu, 3 Mar 2011 20:53:38 +0530 [thread overview]
Message-ID: <AANLkTim2KXZBac_4oBYKkjbebtxmvWAnNAyZUYPecpgm@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103021149450.16349@utopia.booyaka.com>
>> > > > in ES1, timeouts were observed only with RTC.
>> > > > I2C burst access to IRQ registers and bq24156 were OK
>> > >
>> > > Was an errata generated for this bug?
>> >
>> > er, erratum, pardon me...
>>
>> Is an erratum present for this bug?
>>
>> Also, will you generate a patch for this to at least warn the user when
>> this situation occurs?
>
> Still waiting for a response to this.
Apologies for the delay
Could only find Phoenix TWL6030 - ProDB00107890 for this errata
This is not related to I2C module on OMAP4 so fixing in twl-core.c
Description:
I2C FS burst mode not functional
Glitch in the I2C Data line when the I2C controller does a Burst Read
Have tried to workaround by using single byte read for Phoenix ES1.0
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg46054.html
>
>
> - Paul
>
next prev parent reply other threads:[~2011-03-03 15:23 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 [this message]
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=AANLkTim2KXZBac_4oBYKkjbebtxmvWAnNAyZUYPecpgm@mail.gmail.com \
--to=balajitk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.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).