From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Todd Poynor <tpoynor@mvista.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>, linux-pm@osdl.org
Subject: Re: [linux-pm] [PATCH] Custom power states for non-ACPI systems
Date: Wed, 02 Mar 2005 13:57:16 +1100 [thread overview]
Message-ID: <1109732236.5680.89.camel@gaston> (raw)
In-Reply-To: <20050302020306.GA5724@slurryseal.ddns.mvista.com>
On Tue, 2005-03-01 at 18:03 -0800, Todd Poynor wrote:
> Advertise custom sets of system power states for non-ACPI systems.
> Currently, /sys/power/state shows and accepts a static set of choices
> that are not necessarily meaningful on all platforms (for example,
> suspend-to-disk is an option even on diskless embedded systems, and the
> meaning of standby vs. suspend-to-mem is not well-defined on
> non-ACPI-systems). This patch allows the platform to register power
> states with meaningful names that correspond to the platform's
> conventions (for example, "big sleep" and "deep sleep" on TI OMAP), and
> only those states that make sense for the platform.
> .../...
Note that I'd like to rework the whole notion of power states
ultimately. Devices themselves need custom state if we want anything
sane other than global system wide suspend.
Ben.
next prev parent reply other threads:[~2005-03-02 2:59 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 ` Benjamin Herrenschmidt [this message]
2005-03-02 8:56 ` [linux-pm] " 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
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=1109732236.5680.89.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--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