From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Falempe Jocelyn <jocelyn.falempe@motorola.com>
Cc: linux-acpi@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: New feature proposal "quickwakeup"
Date: Fri, 6 Nov 2009 17:03:21 +0000 [thread overview]
Message-ID: <20091106170321.GA24312@srcf.ucam.org> (raw)
In-Reply-To: <1257523241.1318.367.camel@xhp836-11>
Hmm. This is an interesting approach. Just to understand the usecase
better, though - my understanding is that Nokia's approach on Omap-based
devices has been to treat "suspend" as a runtime state, without actually
performing a systemwide transition. What are the constraints that make
shifting into a different hardware state more efficient for you?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-11-06 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:00 New feature proposal "quickwakeup" Falempe Jocelyn
2009-11-06 17:03 ` Matthew Garrett [this message]
2009-11-06 17:42 ` Falempe Jocelyn
2009-11-06 18:09 ` Matthew Garrett
2009-11-09 14:20 ` Falempe Jocelyn
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=20091106170321.GA24312@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jocelyn.falempe@motorola.com \
--cc=linux-acpi@vger.kernel.org \
--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