From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP4: PM: Set static dependency between MPUSS and EMIF
Date: Tue, 08 Mar 2011 16:12:17 -0800 [thread overview]
Message-ID: <87ei6hnoda.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103081619500.15132@utopia.booyaka.com> (Paul Walmsley's message of "Tue, 8 Mar 2011 16:22:52 -0700 (MST)")
Paul Walmsley <paul@pwsan.com> writes:
> On Tue, 8 Mar 2011, Santosh Shilimkar wrote:
>
>> As per OMAP4430 TRM, the dynamic dependency between MEMIF and MPUSS
>> clockdomains is enable by default. Refer register CM_MPU_DYNAMICDEP
>> description for details.
>>
>> But it doesn't seems to work as expected and MPUSS doesn't wakeup
>> from off-mode if the static dependency is not set between MPUSS and
>> EMIF clockdomains. i.e CM_MPU_STATICDEP.MEMIF_STATDEP = 0
>>
>> The issue is under investigation with hardware team.
>>
>> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> Cc: Paul Walmsley <paul@pwsan.com>
>> Cc: Kevin Hilman <khilman@ti.com>
>
> Nice work!
>
> Kevin, you want to take this one?
Yup
> My only comment is that it might be nice to add a pr_info("OMAP4
> PM: Temporary static dependency added between EMIF and MPUSS");
> in there to reduce the risk that the issue will be forgotten...
>
> Acked-by: Paul Walmsley <paul@pwsan.com>
Santosh,
Please update with the pr_info() as suggested by Paul, repost with
linux-arm-kernel in Cc, add Paul's ack and I'll queue for 2.6.39.
Thanks,
Kevin
next prev parent reply other threads:[~2011-03-09 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 15:09 [PATCH] OMAP4: PM: Set static dependency between MPUSS and EMIF Santosh Shilimkar
2011-03-08 23:22 ` Paul Walmsley
2011-03-09 0:12 ` Kevin Hilman [this message]
2011-03-09 4:59 ` Santosh Shilimkar
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=87ei6hnoda.fsf@ti.com \
--to=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 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.