From: Tero Kristo <t-kristo@ti.com>
To: linux-omap@vger.kernel.org, paul@pwsan.com, khilman@ti.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv9 7/8] ARM: OMAP: PM: update target fpwrst to what pwrdm can reach
Date: Thu, 18 Oct 2012 12:20:09 +0300 [thread overview]
Message-ID: <1350552010-28760-8-git-send-email-t-kristo@ti.com> (raw)
In-Reply-To: <1350552010-28760-1-git-send-email-t-kristo@ti.com>
As the code within pwrdm_set_fpwrst is updating powerstate and logic
states according to powerdomain capabilities, it may alter the target
fpwrst also. Update the target fpwrst status according to these checks,
otherwise rest of the code in this function will malfunction.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
---
arch/arm/mach-omap2/powerdomain.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/powerdomain.c b/arch/arm/mach-omap2/powerdomain.c
index f5786b4..f92a867 100644
--- a/arch/arm/mach-omap2/powerdomain.c
+++ b/arch/arm/mach-omap2/powerdomain.c
@@ -711,6 +711,9 @@ int pwrdm_set_fpwrst(struct powerdomain *pwrdm, enum pwrdm_func_state fpwrst)
return -EINVAL;
}
+ /* Refresh target fprwst according to what we can reach */
+ fpwrst = _pwrdm_pwrst_to_fpwrst(pwrdm, pwrst, logic);
+
pr_debug("%s: set fpwrst %0x to pwrdm %s\n",
__func__, fpwrst, pwrdm->name);
--
1.7.4.1
next prev parent reply other threads:[~2012-10-18 9:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 9:20 [PATCHv9 0/8] ARM: OMAP4: core retention support Tero Kristo
2012-10-18 9:20 ` [PATCHv9 1/8] ARM: OMAP: hwmod: Add support for per hwmod/module context lost count Tero Kristo
2012-10-27 3:00 ` Paul Walmsley
2012-11-21 23:05 ` Paul Walmsley
2012-10-18 9:20 ` [PATCHv9 2/8] ARM: OMAP4: PM: add errata support Tero Kristo
2012-11-05 22:36 ` Kevin Hilman
2012-11-06 21:52 ` Kevin Hilman
2012-11-07 10:11 ` Tero Kristo
2012-10-18 9:20 ` [PATCHv9 3/8] ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register change Tero Kristo
2012-10-18 9:20 ` [PATCHv9 4/8] ARM: OMAP4: suspend: Program all domains to retention Tero Kristo
2012-10-18 9:20 ` [PATCHv9 5/8] ARM: OMAP4: PM: put all domains to OSWR during suspend Tero Kristo
2012-10-18 9:20 ` [PATCHv9 6/8] ARM: OMAP4: retrigger localtimers after re-enabling gic Tero Kristo
2012-10-27 2:51 ` Paul Walmsley
2012-11-05 22:25 ` Kevin Hilman
2012-11-06 9:15 ` Tero Kristo
2012-10-18 9:20 ` Tero Kristo [this message]
2012-10-18 9:20 ` [PATCHv9 8/8] ARM: OMAP4: USB: power down MUSB PHY if not used Tero Kristo
2012-10-18 10:33 ` Felipe Balbi
2012-10-18 12:18 ` Tero Kristo
2012-10-18 13:53 ` Felipe Balbi
2012-10-18 14:39 ` Tero Kristo
2012-10-18 14:41 ` Felipe Balbi
2012-10-22 8:54 ` kishon
2012-10-22 9:07 ` Felipe Balbi
2012-10-22 9:25 ` kishon
2012-10-27 2:52 ` Paul Walmsley
2012-10-27 3:02 ` [PATCHv9 0/8] ARM: OMAP4: core retention support Paul Walmsley
2012-11-05 22:23 ` Kevin Hilman
2012-11-06 9:18 ` Tero Kristo
2012-11-06 21:19 ` Kevin Hilman
2012-11-07 10:17 ` Tero Kristo
2012-11-12 14:41 ` Tero Kristo
2012-11-13 19:18 ` Kevin Hilman
2012-11-07 18:35 ` Paul Walmsley
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=1350552010-28760-8-git-send-email-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).