From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Cc: Pavel Machek <pavel@ucw.cz>, Todd Poynor <tpoynor@mvista.com>,
linux-pm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] [PATCH] Custom power states for non-ACPI systems
Date: Thu, 3 Mar 2005 18:17:06 -0800 [thread overview]
Message-ID: <200503031817.06993.david-b@pacbell.net> (raw)
In-Reply-To: <20050302085619.GA1364@elf.ucw.cz>
On Wednesday 02 March 2005 12:56 am, Pavel Machek wrote:
>
> If OMAP has "big sleep" and "deep sleep", why not simply map them to
> "standby" and "suspend-to-ram"?
Or even "cpu idle". Entering power saving modes shouldn't be such
a Big Deal. Some of the variable scheduling timeout work has been
done specifically with the goal of letting the system use those low
power modes more generally, without needing user(space) input to
suggest that now would be a good time to conserve more milliWatts.
Of course, on systems that don't swap (or swsusp) there may be
dozens of different low-power "standby" states. I'm not sure it
helps to try labeling them all through /sys/power/files.
- Dave
next prev parent reply other threads:[~2005-03-04 2:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 2:03 [PATCH] Custom power states for non-ACPI systems Todd Poynor
2005-03-02 2:41 ` Todd Poynor
2005-03-02 2:57 ` [linux-pm] " Benjamin Herrenschmidt
2005-03-02 8:56 ` Pavel Machek
2005-03-02 21:58 ` Todd Poynor
2005-03-02 22:11 ` Pavel Machek
2005-03-03 0:26 ` Todd Poynor
2005-03-03 14:55 ` Pavel Machek
2005-03-04 2:01 ` David Brownell
2005-03-04 8:31 ` Pavel Machek
2005-03-04 2:10 ` Todd Poynor
2005-03-04 2:17 ` David Brownell [this message]
2005-03-04 4:49 ` Nigel Cunningham
2005-03-04 6:31 ` David Brownell
2005-03-04 20:50 ` Todd Poynor
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=200503031817.06993.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=linux-pm@osdl.org \
--cc=pavel@ucw.cz \
--cc=tpoynor@mvista.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