From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3][update] PM / sleep: Introduce command line argument for sleep state enumeration
Date: Tue, 10 Jun 2014 15:12:06 +0200 [thread overview]
Message-ID: <20140610131206.GA7626@amd.pavel.ucw.cz> (raw)
In-Reply-To: <1579932.qSkFQPvI6f@vostro.rjw.lan>
Hi!
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> On some systems the platform doesn't support neither
> PM_SUSPEND_MEM nor PM_SUSPEND_STANDBY, so PM_SUSPEND_FREEZE is the
> only available system sleep state. However, some user space frameworks
> only use the "mem" and (sometimes) "standby" sleep state labels, so
> the users of those systems need to modify user space in order to be
> able to use system suspend at all and that is not always possible.
I'd say we should fix the frameworks, not add option to change kernel
interfaces.
Because, as you mentioned, if we add this, we are probably going to
get stuck with it forever :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-06-10 13:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 23:21 [PATCH 0/3] PM / sleep: Make it possible to change the labeling of sleep states Rafael J. Wysocki
2014-05-22 23:22 ` [PATCH 1/3] PM / sleep: Add state field to pm_states[] entries Rafael J. Wysocki
2014-05-22 23:23 ` [PATCH 2/3] PM / sleep: Use valid_state() for platform-dependent sleep states only Rafael J. Wysocki
2014-05-23 13:01 ` [PATCH 2/3][update] " Rafael J. Wysocki
2014-05-22 23:24 ` [PATCH 3/3] PM / sleep: Introduce command line argument for sleep states enumeration Rafael J. Wysocki
2014-05-23 13:03 ` [PATCH 3/3][update] PM / sleep: Introduce command line argument for sleep state enumeration Rafael J. Wysocki
2014-05-26 8:31 ` Srivatsa S. Bhat
2014-05-26 11:00 ` Rafael J. Wysocki
2014-05-26 10:55 ` Srivatsa S. Bhat
2014-06-10 13:12 ` Pavel Machek [this message]
2014-06-10 15:23 ` Rafael J. Wysocki
2014-06-10 15:25 ` Rafael J. Wysocki
2014-06-10 19:59 ` Pavel Machek
2014-06-10 20:34 ` Rafael J. Wysocki
2014-06-13 21:46 ` Pavel Machek
2014-06-13 22:16 ` Rafael J. Wysocki
2014-06-13 22:23 ` Rafael J. Wysocki
2014-06-13 23:19 ` Rafael J. Wysocki
2014-07-30 10:55 ` Pavel Machek
2014-08-01 13:54 ` Rafael J. Wysocki
2014-08-16 8:10 ` Pavel Machek
2014-08-17 4:16 ` Rafael J. Wysocki
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=20140610131206.GA7626@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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