From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tero.Kristo@nokia.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv6 9/9] OMAP3: PM: Added support for suspending to INACTIVE state
Date: Tue, 09 Mar 2010 11:02:42 -0800 [thread overview]
Message-ID: <87hboppbcd.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1F18D6510CF0474A8C9500565A7E41A224FCDB82E6@NOK-EUMSG-02.mgdnok.nokia.com> (Tero Kristo's message of "Tue\, 9 Mar 2010 09\:07\:09 +0100")
<Tero.Kristo@nokia.com> writes:
>
>
>>-----Original Message-----
>>From: ext Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>Sent: 08 March, 2010 19:16
>>To: Kristo Tero (Nokia-D/Tampere)
>>Cc: linux-omap@vger.kernel.org
>>Subject: Re: [PATCHv6 9/9] OMAP3: PM: Added support for
>>suspending to INACTIVE state
>>
>><Tero.Kristo@nokia.com> writes:
>>
>>[...]
>>
>>> True, ancient info there. OFF for example has been supported
>>for ages already.
>>>
>>>>
>>>>
>>>>> + if (state != PWRDM_POWER_INACTIVE)
>>>>> + while (!(pwrdm->pwrsts & (1 << state))) {
>>>>> + if (state == PWRDM_POWER_OFF)
>>>>> + return ret;
>>>>> + state--;
>>>>> + }
>>>>
>>>>I think all powerdomains can be inactive right?
>>>
>>> Yes.
>>>
>>>>I think it would be cleaner to just have all the pwrdm->pwrsts fields
>>>>include intactive as a valid option.
>>>>
>>>>Something like the patch below. IIRC, you did something like this in
>>>>one of the earlier versions of the patch.
>>>
>>> Yeah, something like this was done previously, however Paul did not
>>> like the idea of changing the generic powerdomain code too much so I
>>> dropped it completely. It is now done only via the support functions
>>> in patch #1, and only done for the powerdomains that actually need
>>> it for the cpuidle (mpu/core/neon.) It would be possible to add
>>> support for the rest of the powerdomains also, but I decided to drop
>>> this in favor of getting the patch set in.
>>
>>I'm not proposing changing any of the other powerdomain code. Just
>>changing the PWRSTS_* defines, essentially so that INACTIVE is
>>a valid state.
>>
>>That will eliminate the need for a special check for inactive in this
>>patch.
>
> This is a chicken-egg problem. If you alter the PWRSTS_* defines,
> you need to change implementation of pwrdm_set_next_pwrst() as it
> would accept INACTIVE also, which is not supported by the code right
> now.
OK, I see the chicken-egg problem now.
You're original version is ok with me.
Thanks,
Kevin
next prev parent reply other threads:[~2010-03-09 19:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 18:27 [PATCHv6 0/9] Refreshed idlestatus patches with minor fixes Tero Kristo
2010-02-12 18:27 ` [PATCHv6 1/9] OMAP3: PM: Added support functions for omap3 pwrdm handling Tero Kristo
2010-02-12 18:27 ` [PATCHv6 2/9] OMAP3: PM: Added support for INACTIVE and ON states in omap_sram_idle Tero Kristo
2010-02-12 18:27 ` [PATCHv6 3/9] OMAP3: CPUidle: Fixed support for ON / INACTIVE states Tero Kristo
2010-02-12 18:27 ` [PATCHv6 4/9] OMAP3: PM: Removed pwrdm state hacking from omap_sram_idle Tero Kristo
2010-02-12 18:27 ` [PATCHv6 5/9] OMAP3: Clock: Added IDLEST definitions for SGX Tero Kristo
2010-02-12 18:27 ` [PATCHv6 6/9] OMAP: Powerdomains: Add support for checking if pwrdm/clkdm can idle Tero Kristo
2010-02-12 18:27 ` [PATCHv6 7/9] OMAP3: CPUidle: Added peripheral pwrdm checks into bm check Tero Kristo
2010-02-12 18:27 ` [PATCHv6 8/9] OMAP3: CPUidle: Fixed off-mode support to fall-back to proper C state Tero Kristo
2010-02-12 18:27 ` [PATCHv6 9/9] OMAP3: PM: Added support for suspending to INACTIVE state Tero Kristo
2010-03-01 23:43 ` Kevin Hilman
2010-03-02 10:12 ` Tero.Kristo
2010-03-08 17:16 ` Kevin Hilman
2010-03-09 8:07 ` Tero.Kristo
2010-03-09 19:02 ` Kevin Hilman [this message]
2010-03-01 23:32 ` [PATCHv6 6/9] OMAP: Powerdomains: Add support for checking if pwrdm/clkdm can idle Kevin Hilman
2010-03-01 23:31 ` [PATCHv6 4/9] OMAP3: PM: Removed pwrdm state hacking from omap_sram_idle Kevin Hilman
2010-03-02 10:13 ` Tero.Kristo
2010-03-01 23:17 ` [PATCHv6 1/9] OMAP3: PM: Added support functions for omap3 pwrdm handling Kevin Hilman
2010-03-02 10:20 ` Tero.Kristo
2010-03-02 17:14 ` Kevin Hilman
2010-03-01 23:17 ` [PATCHv6 0/9] Refreshed idlestatus patches with minor fixes Kevin Hilman
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=87hboppbcd.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=Tero.Kristo@nokia.com \
--cc=linux-omap@vger.kernel.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