public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Kevin Hilman <khilman@ti.com>,
	Grazvydas Ignotas <notasas@gmail.com>,
	linux-omap@vger.kernel.org, Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 3/3] ARM: OMAP3: PM: cpuidle: optimize the clkdm idle latency in C1 state
Date: Wed, 20 Jun 2012 14:22:10 +0530	[thread overview]
Message-ID: <4FE18F3A.8090103@ti.com> (raw)
In-Reply-To: <4FE18E02.6020008@ti.com>

Hi Jean,

On Wednesday 20 June 2012 02:16 PM, Rajendra Nayak wrote:
> On Wednesday 20 June 2012 02:01 PM, Jean Pihet wrote:
>> Hi Rajendra,
>>
>> On Wed, Jun 20, 2012 at 10:19 AM, Rajendra Nayak<rnayak@ti.com> wrote:
>>> Hi Jean,
>>>
>>>
>>> On Friday 01 June 2012 08:41 PM, Jean Pihet wrote:
>>>>
>>>> For a power domain to idle all the clock domains in it must idle.
>>>> This patch implements an optimization of the cpuidle code by
>>>> denying and later allowing only the first registered clock domain
>>>> of a power domain, and so optimizes the latency of the low power code.
>>>
>>>
>>> How much do we really save doing this? I understand what you are doing
>>> by looking at the patch but the changelog seems very confusing.
>> The gain is on the registers accesses and the internal PRCM state
>> machine.
>> If needed the changelog can be updated.
>
> Can you explain a bit more on which register accesses are you talking
> about? and some more on the PRCM state machine.

never mind, I looked at the patch again and then the cpuidle code and
figured what you are doing. Makes sense to me now :-)

regards,
Rajendra
>
>>
>>> What the patch does is get rid of a few function indirection
>>> and assumes there is only *one* clkdm for mpu and core. Is that right?
>> Not exactly. The patch does not assume that there is only one clkdm
>> per power domain. It just allows or denies only one clkdm to idle,
>> which has the same effect at the power domain level.
>
> Ok, so lets assume mpu on OMAP3 has 2 clkdms, and you allow only one
> of them to idle. Will that have the same effect at the power domain
> level?
> The first line of the change log says "For a power domain to idle *all*
> the clock domains in it must idle" and now you say allowing only *one*
> clkdm to idle should have the same effect at the power domain level.
> I am confused.
>
>>
>> Thanks for reviewing,
>> Jean
>>
>>>
>>> regards,
>>> Rajendra
>>>
>>>
>>>>
>>>> The functions _cpuidle_allow_idle and _cpuidle_deny_idle are
>>>> not used anymore and so are removed.
>>>>
>>>> Signed-off-by: Jean Pihet<j-pihet@ti.com>
>>>> ---
>>>> arch/arm/mach-omap2/cpuidle34xx.c | 22 ++++------------------
>>>> 1 files changed, 4 insertions(+), 18 deletions(-)
>>>>
>>>> diff --git a/arch/arm/mach-omap2/cpuidle34xx.c
>>>> b/arch/arm/mach-omap2/cpuidle34xx.c
>>>> index 2e2f1c6..e6ae3fe 100644
>>>> --- a/arch/arm/mach-omap2/cpuidle34xx.c
>>>> +++ b/arch/arm/mach-omap2/cpuidle34xx.c
>>>> @@ -77,20 +77,6 @@ static struct omap3_idle_statedata
>>>> omap3_idle_data[] =
>>>> {
>>>>
>>>> static struct powerdomain *mpu_pd, *core_pd, *per_pd, *cam_pd;
>>>>
>>>> -static int _cpuidle_allow_idle(struct powerdomain *pwrdm,
>>>> - struct clockdomain *clkdm)
>>>> -{
>>>> - clkdm_allow_idle(clkdm);
>>>> - return 0;
>>>> -}
>>>> -
>>>> -static int _cpuidle_deny_idle(struct powerdomain *pwrdm,
>>>> - struct clockdomain *clkdm)
>>>> -{
>>>> - clkdm_deny_idle(clkdm);
>>>> - return 0;
>>>> -}
>>>> -
>>>> static int __omap3_enter_idle(struct cpuidle_device *dev,
>>>> struct cpuidle_driver *drv,
>>>> int index)
>>>> @@ -108,8 +94,8 @@ static int __omap3_enter_idle(struct cpuidle_device
>>>> *dev,
>>>>
>>>> /* Deny idle for C1 */
>>>> if (index == 0) {
>>>> - pwrdm_for_each_clkdm(mpu_pd, _cpuidle_deny_idle);
>>>> - pwrdm_for_each_clkdm(core_pd, _cpuidle_deny_idle);
>>>> + clkdm_deny_idle(mpu_pd->pwrdm_clkdms[0]);
>>>> + clkdm_deny_idle(core_pd->pwrdm_clkdms[0]);
>>>> }
>>>>
>>>> /*
>>>> @@ -131,8 +117,8 @@ static int __omap3_enter_idle(struct cpuidle_device
>>>> *dev,
>>>>
>>>> /* Re-allow idle for C1 */
>>>> if (index == 0) {
>>>> - pwrdm_for_each_clkdm(mpu_pd, _cpuidle_allow_idle);
>>>> - pwrdm_for_each_clkdm(core_pd, _cpuidle_allow_idle);
>>>> + clkdm_allow_idle(mpu_pd->pwrdm_clkdms[0]);
>>>> + clkdm_allow_idle(core_pd->pwrdm_clkdms[0]);
>>>> }
>>>>
>>>> return_sleep_time:
>>>
>>>
>


  reply	other threads:[~2012-06-20  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 15:11 [PATCH 0/3] ARM: OMAP3: PM: optimize cpuidle C1 state latency Jean Pihet
2012-06-01 15:11 ` [PATCH 1/3] ARM: OMAP3: PM: cpuidle: default to C1 in next_valid_state Jean Pihet
2012-06-01 15:11 ` [PATCH 2/3] ARM: OMAP3: PM: cpuidle: optimize the PER latency in C1 state Jean Pihet
2012-06-01 15:11 ` [PATCH 3/3] ARM: OMAP3: PM: cpuidle: optimize the clkdm idle " Jean Pihet
2012-06-20  8:19   ` Rajendra Nayak
2012-06-20  8:31     ` Jean Pihet
2012-06-20  8:46       ` Rajendra Nayak
2012-06-20  8:52         ` Rajendra Nayak [this message]
2012-06-20  8:57           ` Rajendra Nayak
2012-06-20 11:34             ` Jean Pihet
2012-06-28 18:03               ` Kevin Hilman
2012-06-01 16:26 ` [PATCH 0/3] ARM: OMAP3: PM: optimize cpuidle C1 state latency Kevin Hilman
2012-06-01 16:29   ` Jean Pihet

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=4FE18F3A.8090103@ti.com \
    --to=rnayak@ti.com \
    --cc=j-pihet@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=notasas@gmail.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