From: "Cousson, Benoit" <b-cousson@ti.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Nayak, Rajendra" <rnayak@ti.com>,
"Hilman, Kevin" <khilman@ti.com>
Subject: Re: Integration branch base switchover to Tony's omap-for-linus branch
Date: Tue, 8 Mar 2011 17:28:10 +0100 [thread overview]
Message-ID: <4D76591A.7060508@ti.com> (raw)
In-Reply-To: <02124a94c82909eff5a589819ec86357@mail.gmail.com>
On 3/8/2011 4:16 PM, Shilimkar, Santosh wrote:
> Paul,
>> -----Original Message-----
>> From: Santosh Shilimkar [mailto:santosh.shilimkar@ti.com]
>> Sent: Friday, March 04, 2011 10:14 PM
>> To: Rajendra Nayak
>> Cc: linux-omap@vger.kernel.org; Benoit Cousson; Paul Walmsley
>> Subject: RE: Integration branch base switchover to Tony's omap-for-
>> linus branch
>>
>
> [....]
>
>>> Some more debugging by the Hardware team and analyzing
>>> the register dumps showed that the I2C_WE register of the i2c
>>> modules needs to be programmed correctly for i2c wakeups to
>>> function as expected.
>>> This turned out to be the root cause for the i2c issues observed
>>> by clearing the staticdeps and a patch has been posted
>>> to address this...
>>> http://marc.info/?l=linux-omap&m=129924557219813&w=2
>>>
>>>>
>>>> Also some more testing showed up a lockup in suspend on OMAP4
>>> which I
>>>> could narrow down to a similar case with GPT1. Either keeping
>> the
>>>> staticdep between MPU and L4_WKUP _or_ forcing GPT1 to use
>>> software
>>>> idle control seems to help.
>>>
>>> This however is still not rootcaused and is not the same as the
>>> issue
>>> seen with i2c as the WE for GPT1 is already programmed for
>> enabling
>>> wakeup.
>>>
>>> The one way to fix this for now is to put GPT1 block in software
>>> controlled idle as was done by your test patch for i2c.
>>>
>> I tried all the floating patches for static dependency. It did
>> worked when CPU RET was tried but with MPU OFF I see the hang.
>>
>> Below is the global hack I have which works as expected for
>> all cases.
>>
> Thanks to Rajendra for isolating the OMAP4 MPU OFF issue
> with static dependency series. The issue is isolated
> to MPU<-> EMIF clock dependency. There issue appears
> if we clear this static dependency.
>
> I have posted a patch to work-around this issue till its
> being root-caused with help of hardware team so that
> OMAP4 PM series continue to work.
>
> 'OMAP4: PM: Set static dependency between MPUSS and EMIF'
> http://www.listware.net/201103/linux-omap/2628-patch-omap4-pm-set-static-d
> ependency-between-mpuss-and-emif.html
Cool, so the timer1 fix is not longer needed?
Benoit
next prev parent reply other threads:[~2011-03-08 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 0:26 Integration branch base switchover to Tony's omap-for-linus branch Paul Walmsley
2011-03-01 12:38 ` Santosh Shilimkar
2011-03-01 21:33 ` Paul Walmsley
2011-03-03 12:30 ` Rajendra Nayak
2011-03-04 14:08 ` Rajendra Nayak
2011-03-04 14:59 ` Cousson, Benoit
2011-03-04 15:01 ` Santosh Shilimkar
2011-03-04 15:25 ` Cousson, Benoit
2011-03-04 16:43 ` Santosh Shilimkar
2011-03-08 15:16 ` Santosh Shilimkar
2011-03-08 16:28 ` Cousson, Benoit [this message]
2011-03-09 5:08 ` Santosh Shilimkar
2011-03-07 23:25 ` Paul Walmsley
2011-03-08 8:04 ` Cousson, Benoit
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=4D76591A.7060508@ti.com \
--to=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.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).