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: Sat, 16 Aug 2014 10:10:07 +0200 [thread overview]
Message-ID: <20140816081007.GA21682@Nokia-N900> (raw)
In-Reply-To: <3319219.i7p5TE6seQ@vostro.rjw.lan>
On Fri 2014-08-01 15:54:32, Rafael J. Wysocki wrote:
> On Wednesday, July 30, 2014 12:55:29 PM Pavel Machek wrote:
> >
> > > For this reason I'm considering changing the defaul behavior going forward (so
> > > that "mem" is always present and means "the deepest sleep state available other
> > > than hibernation"), but I don't want to do that in one go.
> >
> > Actually, I don't think that's good idea, at least on PC.
> >
> > The way to wake up from S3 is power button. The way to wake up from
> > "echo freeze > state" is going to be different, right?
>
> No, it isn't. That's the point among other things.
There's difference, actually.
>From S3, power button event is consumed.
>From freeze, after resume, "what you want to do? power off,
suspend, hibernate" dialog appears.
next prev parent reply other threads:[~2014-08-16 8:10 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
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 [this message]
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=20140816081007.GA21682@Nokia-N900 \
--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