From: Kevin Hilman <khilman@deeprootsystems.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: Peter Tseng <tsenpet09@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: ARM suspend to disk?
Date: Fri, 30 Apr 2010 15:06:14 -0700 [thread overview]
Message-ID: <87iq78d295.fsf@deeprootsystems.com> (raw)
In-Reply-To: <p2kf96d234e1004301446l255a8cb4h7287e2502934e9fd@mail.gmail.com> (Cliff Brake's message of "Fri\, 30 Apr 2010 17\:46\:59 -0400")
Cliff Brake <cliff.brake@gmail.com> writes:
> On Thu, Apr 29, 2010 at 1:58 PM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>
>> 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.
>
> What does the resume process look like in off mode? Does the resume
> pass through the bootloader? If so, are the bits that detects resume
> from "off" available in U-boot?
No, it does not pass through the boot loader.
In general terms, resume from off-mode is the same to "normal" resume (from
retention) except that some additional state has to be restored before
continuing where you left off since the ARM core (as well as most the
OMAP itself) was turned off.
Kevin
next prev parent reply other threads:[~2010-04-30 22:06 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
2010-04-30 21:46 ` Cliff Brake
2010-04-30 22:06 ` Kevin Hilman [this message]
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=87iq78d295.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=cliff.brake@gmail.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.