From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org,
Jean Pihet <jean.pihet@newoldbits.com>,
Tero Kristo <t-kristo@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH/RFT 1/3] ARM: OMAP2+: powerdomain: allow pre/post transtion to be per pwrdm
Date: Thu, 26 Apr 2012 06:35:26 -0700 [thread overview]
Message-ID: <87mx5ybopt.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204252130080.30642@utopia.booyaka.com> (Paul Walmsley's message of "Wed, 25 Apr 2012 21:31:21 -0600 (MDT)")
Paul Walmsley <paul@pwsan.com> writes:
> On Tue, 24 Apr 2012, Kevin Hilman wrote:
>
>> Iteration over all power domains in the idle path is unnecessary since
>> only power domains that are transitioning need to be accounted for.
>> Also PRCM register accesses are known to be expensive, so the
>> additional latency added to the idle path is signficiant.
>>
>> In order allow the pre/post transitions to be isolated and called
>> per-pwrdm, change the API so passing in a specific power domain will
>> trigger the pre/post transtion accounting for only that specific power
>> domain. Passing NULL means iterating over all power domains as is
>> current behavior.
>>
>> Signed-off-by: Kevin Hilman <khilman@ti.com>
>
> Based on a quick glance, it looks good to me:
>
> Acked-by: Paul Walmsley <paul@pwsan.com>
>
> Want to queue this one?
Yes, I'll queue this along with the others.
Thanks,
Kevin
next prev parent reply other threads:[~2012-04-26 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 14:23 [PATCH/RFT 0/3] ARM: OMAP: PM: reduce overhead of pwrdm pre/post transitions Kevin Hilman
2012-04-24 14:23 ` [PATCH/RFT 1/3] ARM: OMAP2+: powerdomain: allow pre/post transtion to be per pwrdm Kevin Hilman
2012-04-24 14:31 ` Shilimkar, Santosh
2012-04-25 8:44 ` Shilimkar, Santosh
2012-04-26 3:31 ` Paul Walmsley
2012-04-26 13:35 ` Kevin Hilman [this message]
2012-04-24 14:23 ` [PATCH/RFT 2/3] ARM: OMAP3: PM: call pre/post transition per powerdomain Kevin Hilman
2012-06-19 16:51 ` Kevin Hilman
2012-04-24 14:23 ` [PATCH/RFT 3/3] ARM: OMAP3: PM: cleanup cam_pwrdm leftovers Kevin Hilman
2012-04-27 7:20 ` Tero Kristo
2012-04-27 20:18 ` Kevin Hilman
2012-04-28 14:47 ` Grazvydas Ignotas
2012-04-30 20:45 ` Kevin Hilman
2012-04-24 23:01 ` [PATCH/RFT 0/3] ARM: OMAP: PM: reduce overhead of pwrdm pre/post transitions Grazvydas Ignotas
2012-04-25 13:24 ` Shilimkar, Santosh
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=87mx5ybopt.fsf@ti.com \
--to=khilman@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@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 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).