From: Santosh <santosh.shilimkar@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
linux-omap@vger.kernel.org, Tero Kristo <t-kristo@ti.com>,
linux-arm-kernel@lists.infradead.org, khilman@ti.com,
p-titiano@ti.com, b-cousson@ti.com
Subject: Re: [PATCH] OMAP: clockdomain: Wait for powerdomain to be ON when using clockdomain force wakeup
Date: Wed, 17 Aug 2011 10:41:44 +0530 [thread overview]
Message-ID: <4E4B4D90.9040103@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1108161946550.9948@utopia.booyaka.com>
On Wednesday 17 August 2011 07:17 AM, Paul Walmsley wrote:
>
> Hi everyone
>
> I've updated this patch per my earlier comments and also to apply.
> Please let me know if you have any issues with it ASAP.
>
>
> - Paul
>
> From: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Date: Sat, 13 Aug 2011 08:56:28 +0530
> Subject: [PATCH] [PATCH] OMAP: clockdomain: Wait for powerdomain to be ON
> when using clockdomain force wakeup
>
> While using clockdomain force wakeup method, not waiting for powerdomain
> to be effectively ON may end up locking the clockdomain FSM until a
> next wakeup event occurs.
>
> One such issue was seen on OMAP4430, where L4_PER was periodically
> getting stuck in in-transition state when transitioning from from OSWR to ON.
>
> This issue was reported and investigated by Patrick Titiano<p-titiano@ti.com>
>
> Signed-off-by: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Signed-off-by: Rajendra Nayak<rnayak@ti.com>
> Reported-by: Patrick Titiano<p-titiano@ti.com>
> Cc: Kevin Hilman<khilman@ti.com>
> Cc: Benoit Cousson<b-cousson@ti.com>
> Cc: Paul Walmsley<paul@pwsan.com>
> [paul@pwsan.com: updated to apply; added transition wait on clkdm_deny_idle();
> remove two superfluous pwrdm_wait_transition() calls]
> Signed-off-by: Paul Walmsley<paul@pwsan.com>
> ---
Thanks Paul. Patch looks good to me.
Regards
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP: clockdomain: Wait for powerdomain to be ON when using clockdomain force wakeup
Date: Wed, 17 Aug 2011 10:41:44 +0530 [thread overview]
Message-ID: <4E4B4D90.9040103@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1108161946550.9948@utopia.booyaka.com>
On Wednesday 17 August 2011 07:17 AM, Paul Walmsley wrote:
>
> Hi everyone
>
> I've updated this patch per my earlier comments and also to apply.
> Please let me know if you have any issues with it ASAP.
>
>
> - Paul
>
> From: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Date: Sat, 13 Aug 2011 08:56:28 +0530
> Subject: [PATCH] [PATCH] OMAP: clockdomain: Wait for powerdomain to be ON
> when using clockdomain force wakeup
>
> While using clockdomain force wakeup method, not waiting for powerdomain
> to be effectively ON may end up locking the clockdomain FSM until a
> next wakeup event occurs.
>
> One such issue was seen on OMAP4430, where L4_PER was periodically
> getting stuck in in-transition state when transitioning from from OSWR to ON.
>
> This issue was reported and investigated by Patrick Titiano<p-titiano@ti.com>
>
> Signed-off-by: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Signed-off-by: Rajendra Nayak<rnayak@ti.com>
> Reported-by: Patrick Titiano<p-titiano@ti.com>
> Cc: Kevin Hilman<khilman@ti.com>
> Cc: Benoit Cousson<b-cousson@ti.com>
> Cc: Paul Walmsley<paul@pwsan.com>
> [paul at pwsan.com: updated to apply; added transition wait on clkdm_deny_idle();
> remove two superfluous pwrdm_wait_transition() calls]
> Signed-off-by: Paul Walmsley<paul@pwsan.com>
> ---
Thanks Paul. Patch looks good to me.
Regards
Santosh
next prev parent reply other threads:[~2011-08-17 5:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 3:26 [PATCH] OMAP: powerdomains: Make all powerdomain target states as ON at init Santosh Shilimkar
2011-07-13 3:26 ` Santosh Shilimkar
2011-07-13 3:26 ` [PATCH] OMAP: clockdomain: Wait for powerdomain to be ON when using clockdomain force wakeup Santosh Shilimkar
2011-07-13 3:26 ` Santosh Shilimkar
2011-07-15 8:03 ` Paul Walmsley
2011-07-15 8:03 ` Paul Walmsley
2011-07-16 7:48 ` Santosh Shilimkar
2011-07-16 7:48 ` Santosh Shilimkar
2011-08-11 14:07 ` Santosh
2011-08-11 14:07 ` Santosh
2011-08-12 14:27 ` Paul Walmsley
2011-08-12 14:27 ` Paul Walmsley
2011-08-17 1:47 ` Paul Walmsley
2011-08-17 1:47 ` Paul Walmsley
2011-08-17 5:11 ` Santosh [this message]
2011-08-17 5:11 ` Santosh
2011-07-15 7:54 ` [PATCH] OMAP: powerdomains: Make all powerdomain target states as ON at init Paul Walmsley
2011-07-15 7:54 ` Paul Walmsley
2011-07-16 7:28 ` Santosh Shilimkar
2011-07-16 7:28 ` Santosh Shilimkar
2011-08-17 1:50 ` Paul Walmsley
2011-08-17 1:50 ` Paul Walmsley
2011-07-15 8:03 ` Felipe Balbi
2011-07-15 8:03 ` Felipe Balbi
2011-07-15 8:10 ` Paul Walmsley
2011-07-15 8:10 ` Paul Walmsley
2011-07-15 8:17 ` Felipe Balbi
2011-07-15 8:17 ` Felipe Balbi
2011-07-15 8:23 ` Paul Walmsley
2011-07-15 8:23 ` Paul Walmsley
2011-07-15 8:37 ` Felipe Balbi
2011-07-15 8:37 ` Felipe Balbi
2011-08-17 1:56 ` Paul Walmsley
2011-08-17 1:56 ` Paul Walmsley
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=4E4B4D90.9040103@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=p-titiano@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=t-kristo@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.