From: Kevin Hilman <khilman@deeprootsystems.com>
To: Russ Dill <russ.dill@gmail.com>
Cc: "Premi, Sanjeev" <premi@ti.com>,
Peter Barada <peterb@logicpd.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: PM branch rebased to 2.6.29
Date: Tue, 31 Mar 2009 21:11:46 -0700 [thread overview]
Message-ID: <873actrp19.fsf@deeprootsystems.com> (raw)
In-Reply-To: <f9d2a5e10903311830u1ea8b5dgb485a19c523f845f@mail.gmail.com> (Russ Dill's message of "Tue\, 31 Mar 2009 18\:30\:33 -0700")
Russ Dill <russ.dill@gmail.com> writes:
[...]
>
> root@beagleboard:/sys/power# echo 1 > clocks_off_while_idle
> root@beagleboard:/sys/power# echo 1 > enable_off_mode
> root@beagleboard:/sys/power# echo 1 > voltage_off_while_idle
> root@beagleboard:/sys/power# echo mem > state
> PM: Syncing filesystems ... done.
> Freezing user space processes ... (elapsed 0.00 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
> Successfully put all powerdomains to target state
> Restarting tasks ... done.
>
> Neato :) This is still with all the user processes running an with a
> NAND filesystem. I'm still getting rather high ~80mA@5V power
> consumption, so I'll need to further investigate what rails the
> twl4030 is actually turning off.
Great! glad it worked for you.
The kernel has some work to do to be sure that *everything* is
properly init'd to allow proper idle states. Until then,
unfortunately we have to rely on more gentle bootloaders.
And FWIW, on my Beagle, I've never seen < 80mA either, but I haven't
done any further digging.
Kevin
next prev parent reply other threads:[~2009-04-01 4:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 5:21 PM branch rebased to 2.6.29 Kevin Hilman
2009-03-18 7:41 ` Artem Bityutskiy
2009-03-18 15:51 ` Kevin Hilman
2009-03-19 22:20 ` David Brownell
2009-03-20 18:59 ` Tony Lindgren
2009-03-20 19:46 ` David Brownell
2009-03-20 19:57 ` Tony Lindgren
2009-03-20 21:27 ` Tony Lindgren
2009-03-20 22:36 ` David Brownell
2009-03-24 17:10 ` Peter Barada
2009-03-24 18:08 ` Kevin Hilman
2009-03-24 20:11 ` Peter Barada
2009-03-24 20:21 ` Kevin Hilman
2009-03-24 20:37 ` Peter Barada
2009-03-27 20:50 ` Russ Dill
2009-03-30 10:08 ` Premi, Sanjeev
2009-03-30 10:42 ` Koen Kooi
2009-03-30 13:22 ` Premi, Sanjeev
2009-03-30 17:44 ` Russ Dill
2009-03-30 17:57 ` Kevin Hilman
2009-03-30 18:18 ` Peter Barada
2009-03-30 18:43 ` Kevin Hilman
2009-03-30 23:01 ` Russ Dill
2009-03-31 7:01 ` Russ Dill
2009-03-31 18:25 ` Kevin Hilman
2009-03-31 21:31 ` Russ Dill
2009-03-31 23:33 ` Kevin Hilman
2009-04-01 1:30 ` Russ Dill
2009-04-01 4:11 ` Kevin Hilman [this message]
2009-03-26 16:54 ` Jean Pihet
2009-03-26 17:01 ` 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=873actrp19.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=peterb@logicpd.com \
--cc=premi@ti.com \
--cc=russ.dill@gmail.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