From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] OMAP3: cpuidle: add more details to the DSS-related CORE power domain state restriction
Date: Tue, 01 Mar 2011 15:49:25 -0700 [thread overview]
Message-ID: <20110301224924.32613.57042.stgit@twilight.localdomain> (raw)
In-Reply-To: <20110301220833.32613.54669.stgit@twilight.localdomain>
Provide some more details about the rationale behind the CORE power domain
state restriction while DSS is enabled -- hopefully, enough to enable others
to implement an approach based on the DSS's required wakeup latency,
which can vary based on quite a few parameters.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Tero Kristo <tero.kristo@nokia.com>
Cc: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: Senthilvadivu Guruswamy <svadivu@ti.com>
Cc: Sumit Semwal <sumit.semwal@ti.com>
Cc: Jean Pihet <j-pihet@ti.com>
---
arch/arm/mach-omap2/cpuidle34xx.c | 28 +++++++++++++++++++++++++++-
1 files changed, 27 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/cpuidle34xx.c b/arch/arm/mach-omap2/cpuidle34xx.c
index d1b7789..6bdbb33 100644
--- a/arch/arm/mach-omap2/cpuidle34xx.c
+++ b/arch/arm/mach-omap2/cpuidle34xx.c
@@ -269,7 +269,33 @@ static int omap3_enter_idle_bm(struct cpuidle_device *dev,
goto select_state;
}
- /* If DSS is active, prevent CORE RET/OFF */
+ /*
+ * If DSS is active, prevent any CORE power domain transition
+ * to RETENTION or lower. This is because we don't currently
+ * have the infrastructure in the DSS driver or kernel to
+ * enter CORE RET without causing DSS FIFO underflows. When
+ * the DSS FIFO underflows, the screen image can be distorted,
+ * because the CORE may not be able to come back on-line
+ * quickly enough to service DSS requests to the SDRAM
+ * framebuffer. The DSS may also interrupt the MPU when the
+ * FIFO underflows, potentially wasting power.
+ *
+ * The approach below is easy to implement, but potentially
+ * wastes power, especially with screens that don't require a
+ * backlight. Probably the best long-term way to fix this is
+ * for the DSS driver to constrain the CORE and SDRAM minimum
+ * power state with omap_pm_set_max_dev_wakeup_lat(), based on
+ * the DSS FIFO size(s), watermark levels, drain rate, and
+ * refill time. Based on that constraint, the OMAP PM code
+ * should adjust the CORE maximum power state, CORE DPLL
+ * autoidle mode, CORE_CLK rate, and voltage scaling to ensure
+ * the required wakeup latency at the lowest power
+ * consumption.
+ *
+ * (More information on the DSS low-power refresh mode can be
+ * found in _Using Display Low-Power Refresh on the OMAP3430
+ * Device_, TI Application Report, SWPA158 - October 2008.)
+ */
dss_state = pwrdm_read_pwrst(dss_pd);
if (dss_state == PWRDM_POWER_ON &&
core_next_state != PWRDM_POWER_ON)
next prev parent reply other threads:[~2011-03-01 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 22:49 [PATCH 0/2] OMAP3: cpuidle: prevent CORE pwrdm from entering low-power state when DSS active Paul Walmsley
2011-03-01 22:49 ` [PATCH 1/2] OMAP3: cpuidle: prevent CORE power domain from going to RET or OFF when DSS is on Paul Walmsley
2011-03-03 23:24 ` Kevin Hilman
2011-03-04 8:14 ` Tero.Kristo at nokia.com
2011-03-04 16:56 ` Kevin Hilman
2011-03-07 12:02 ` Tero.Kristo at nokia.com
2011-03-07 19:06 ` Kevin Hilman
2011-03-10 10:17 ` Paul Walmsley
2011-03-09 0:04 ` Paul Walmsley
2011-03-01 22:49 ` Paul Walmsley [this message]
2011-03-02 8:18 ` [PATCH 0/2] OMAP3: cpuidle: prevent CORE pwrdm from entering low-power state when DSS active Tero.Kristo at nokia.com
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=20110301224924.32613.57042.stgit@twilight.localdomain \
--to=paul@pwsan.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