From: Kevin Hilman <khilman@deeprootsystems.com>
To: Peter Tseng <tsenpet09@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: ARM suspend to disk?
Date: Thu, 29 Apr 2010 10:58:40 -0700 [thread overview]
Message-ID: <87y6g6w373.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4BD881A7.2020402@gmail.com> (Peter Tseng's message of "Wed\, 28 Apr 2010 14\:42\:47 -0400")
Peter Tseng <tsenpet09@gmail.com> writes:
> I last posted a few weeks ago; I'm Peter Tseng, using the Gumstix Overo
> for a project. I'm interested in power management and a few related
> things. A few of the things I am interested in are suspend to disk and
> snapshot boot.
>
> I found a page on elinux.org with a few notes on the issue for ARM.
> However, it looks to be a bit outdated:
> http://elinux.org/Suspend_To_Disk_For_ARM
>
> I am wondering how applicable anything on this page is to the current
> omap-pm developments. Or, if not, any pointers on how it might be done -
> for example, if I felt like I should do some hacking to try to get this
> working and contribute these back, a general outline of what I might
> have to do)
Not really and answer to your question since I don't know the answer,
but just curious about your goals, since there may be an easier way.
What do you expect to gain from suspend-to-disk + snapshot boot that
you don't already get from suspend-to-RAM using off-mode?
On OMAP, with off-mode enabled, a suspend to RAM puts the entire OMAP
into full-chip off, and essentially reboots the ARM when waking up
from suspend (or idle) already.
Kevin
next prev parent reply other threads:[~2010-04-30 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 18:42 ARM suspend to disk? Peter Tseng
2010-04-29 17:58 ` Kevin Hilman [this message]
2010-04-30 21:46 ` Cliff Brake
2010-04-30 22:06 ` Kevin Hilman
2010-05-01 7:12 ` Shilimkar, Santosh
2010-05-03 5:11 ` Peter Tseng
2010-05-03 6:59 ` Reddy, Teerth
2010-05-03 5:09 ` Peter Tseng
-- strict thread matches above, loose matches on Subject: below --
2011-02-09 4:39 David Fries
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=87y6g6w373.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tsenpet09@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 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.