linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] OMAP4: PM: Use the lowpwrstatechange feature on OMAP4
Date: Wed, 15 Dec 2010 20:47:52 +0530	[thread overview]
Message-ID: <c454400af490d75c274f19a5d0a5a655@mail.gmail.com> (raw)
In-Reply-To: <87zks8rv3b.fsf@deeprootsystems.com>

Hi Kevin,

<snip>..

> >  	if (pwrdm_read_pwrst(pwrdm) < PWRDM_POWER_ON) {
> > +		if ((pwrdm_read_pwrst(pwrdm) > state) &&
> > +			(pwrdm->flags & PWRDM_HAS_LOWPOWERSTATECHANGE)) {
> > +				ret = pwrdm_set_next_pwrst(pwrdm, state);
> > +				pwrdm_set_lowpwrstchange(pwrdm);
> > +				pwrdm_wait_transition(pwrdm);
> > +				pwrdm_state_switch(pwrdm);
> > +				return ret;
>
> Personally, I'd prefer if this function flowed through better instead of
> the early return in order to emphasize the common code.
>
> Rather than the return here, can you just set the low-power state change
> bit here (and put the clkdm_wakeup + sleep_switch = 1 into the else
> clause?
>
> Or, does the next state have to be set before the low-power state change
> bit?

Yes, that sequencing is needed.

>
> Basically, what I'm getting at is this should be a single function with
> common flow.  The conditional code based on low-power state change
> should be isolated instead of having a special path.

I get your point. See if the below approach looks better.
If it looks fine, I'll do some more testing (currently only tested
on OMAP4430sdp) and repost the 2 patches.

  reply	other threads:[~2010-12-15 15:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 21:49 [PATCH 0/5] OMAP3&4: Fixes in setup/suspend/powerdomain Benoit Cousson
2010-12-13 21:49 ` [PATCH 1/5] OMAP4: PM: Use the lowpwrstatechange feature on OMAP4 Benoit Cousson
2010-12-14 19:51   ` Kevin Hilman
2010-12-15 15:17     ` Rajendra Nayak [this message]
2010-12-15 23:40       ` Kevin Hilman
2010-12-13 21:49 ` [PATCH 2/5] OMAP4: PM: Do not assume clkdm supports hw transitions Benoit Cousson
2010-12-14 19:52   ` Kevin Hilman
2010-12-13 21:49 ` [PATCH 3/5] OMAP4: powerdomain: l4per pwrdm does not support OFF Benoit Cousson
2010-12-13 21:49 ` [PATCH 4/5] OMAP4: powerdomain: Remove L3INIT_PD OFF state Benoit Cousson
2010-12-13 21:49 ` [PATCH 5/5] OMAP4: clock data: Keep L3INSTR clock domain modulemode under HW control Benoit Cousson
2010-12-14  6:43 ` [PATCH 0/5] OMAP3&4: Fixes in setup/suspend/powerdomain Paul Walmsley
2010-12-14 19:53   ` Kevin Hilman
2010-12-22  3:43 ` Paul Walmsley
2010-12-22  3:45   ` Paul Walmsley
2010-12-22  3:44 ` Paul Walmsley
2010-12-22 11:42   ` 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=c454400af490d75c274f19a5d0a5a655@mail.gmail.com \
    --to=rnayak@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).