From: Kevin Hilman <khilman@ti.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
paul@pwsan.com, Jean Pihet <j-pihet@ti.com>,
Vibhore Vardhan <vvardhan@ti.com>
Subject: Re: [PATCH 2/2] OMAP: PM: implement devices constraints APIs
Date: Thu, 10 Mar 2011 11:51:58 -0800 [thread overview]
Message-ID: <87y64mbvoh.fsf@ti.com> (raw)
In-Reply-To: <AANLkTikQOfsteZUAzSWjO-BbAW=ZEX22mhRUFHBMeFTR@mail.gmail.com> (Jean Pihet's message of "Wed, 9 Mar 2011 20:37:51 +0100")
Jean Pihet <jean.pihet@newoldbits.com> writes:
[...]
>> + if (pwrdm_read_pwrst(pwrdm) != new_state) {
>> + ret = omap_set_pwrdm_state(pwrdm, new_state);
>
> The function pwrdms_setup (called from omap3_pm_init for every pwrdm)
> runs late in the boot process and so it overwrites the registers
> values programmed by omap_set_pwrdm_state with the default values.
> Could the default values get written earlier in the boot process (e.g.
> at hwmod init) before the devices can put constraints on the power
> domains?
Yes, default vaules for each power domain's next state should probably
be written earlier in the boot. Probably when the powerdomain is
initialized, or at least when this constraints framework is initialized.
Then, the initial states set in omap3_pm_init() can just be removed.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] OMAP: PM: implement devices constraints APIs
Date: Thu, 10 Mar 2011 11:51:58 -0800 [thread overview]
Message-ID: <87y64mbvoh.fsf@ti.com> (raw)
In-Reply-To: <AANLkTikQOfsteZUAzSWjO-BbAW=ZEX22mhRUFHBMeFTR@mail.gmail.com> (Jean Pihet's message of "Wed, 9 Mar 2011 20:37:51 +0100")
Jean Pihet <jean.pihet@newoldbits.com> writes:
[...]
>> + ? ? ? if (pwrdm_read_pwrst(pwrdm) != new_state) {
>> + ? ? ? ? ? ? ? ret = omap_set_pwrdm_state(pwrdm, new_state);
>
> The function pwrdms_setup (called from omap3_pm_init for every pwrdm)
> runs late in the boot process and so it overwrites the registers
> values programmed by omap_set_pwrdm_state with the default values.
> Could the default values get written earlier in the boot process (e.g.
> at hwmod init) before the devices can put constraints on the power
> domains?
Yes, default vaules for each power domain's next state should probably
be written earlier in the boot. Probably when the powerdomain is
initialized, or at least when this constraints framework is initialized.
Then, the initial states set in omap3_pm_init() can just be removed.
Kevin
next prev parent reply other threads:[~2011-03-10 19:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 14:52 [PATCH 0/2] OMAP: PM: implement devices wakeup latency constraints APIs Jean Pihet
2011-03-04 14:52 ` Jean Pihet
2011-03-04 14:52 ` [PATCH 1/2] OMAP PM: create a PM layer plugin for the devices wakeup latency constraints Jean Pihet
2011-03-04 14:52 ` Jean Pihet
2011-03-08 1:09 ` Kevin Hilman
2011-03-08 1:09 ` Kevin Hilman
2011-03-04 14:52 ` [PATCH 2/2] OMAP: PM: implement devices wakeup latency constraints APIs Jean Pihet
2011-03-04 14:52 ` Jean Pihet
2011-03-08 2:15 ` Kevin Hilman
2011-03-08 2:15 ` Kevin Hilman
2011-03-08 15:54 ` Jean Pihet
2011-03-08 15:54 ` Jean Pihet
2011-03-08 17:33 ` Kevin Hilman
2011-03-08 17:33 ` Kevin Hilman
2011-03-09 19:19 ` [PATCH 2/2] OMAP: PM: implement devices " Jean Pihet
2011-03-09 19:19 ` Jean Pihet
2011-03-09 19:37 ` Jean Pihet
2011-03-09 19:37 ` Jean Pihet
2011-03-10 19:51 ` Kevin Hilman [this message]
2011-03-10 19:51 ` Kevin Hilman
2011-03-10 4:03 ` Paul Walmsley
2011-03-10 4:03 ` Paul Walmsley
2011-03-10 10:03 ` Jean Pihet
2011-03-10 10:03 ` Jean Pihet
2011-03-10 18:03 ` Kevin Hilman
2011-03-10 18:03 ` 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=87y64mbvoh.fsf@ti.com \
--to=khilman@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=vvardhan@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.