From: Jean Pihet <jpihet@mvista.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: 2.6.29 PM and CPUIDLE
Date: Fri, 10 Apr 2009 16:54:58 +0200 [thread overview]
Message-ID: <200904101654.58917.jpihet@mvista.com> (raw)
Hi,
I am having problems using CPUIDLE PM_SLEEP on Beagleboard with the latest pm
tree.
It looks like CPUIDLE prevents the system to go into retention mode, while it
works fine without CPUIDLE enabled:
root@beagleboard:~# echo 1 > /sys/power/clocks_off_while_idle
root@beagleboard:~# echo mem > /sys/power/state
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.02 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
omapfb omapfb: timeout waiting for FRAME DONE
Powerdomain (core_pwrdm) didn't enter target state 1
Powerdomain (dss_pwrdm) didn't enter target state 1
Could not enter target state in pm_suspend
Restarting tasks ... done.
The registers dump shows the next power state in PM_PWSTCTRL is set to ON
instead of RET for MPU and CORE. Furthermore DSS is not reaching RET (stays
ON).
Are the CPUIDLE and suspend/resume features compatible with each other? Am I
missing something, e.g. a way to change the behavior from /sys?
Regards,
Jean
next reply other threads:[~2009-04-10 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 14:54 Jean Pihet [this message]
2009-04-10 23:11 ` 2.6.29 PM and CPUIDLE 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=200904101654.58917.jpihet@mvista.com \
--to=jpihet@mvista.com \
--cc=khilman@deeprootsystems.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