From: Paul Fox <pgf@laptop.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: NeilBrown <neilb@suse.de>, "Arve Hjønnevåg" <arve@android.com>,
linux-input@vger.kernel.org, linux-pm@vger.kernel.org,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Matthew Garrett" <mjg@redhat.com>,
"Chase Douglas" <chase.douglas@canonical.com>,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: Add ioctl to block suspend while event queue is not empty.
Date: Wed, 15 Feb 2012 20:53:31 -0500 [thread overview]
Message-ID: <20867.1329357211@foxharp.boston.ma.us> (raw)
In-Reply-To: <201202160030.26503.rjw@sisk.pl> (sfid-20120215_182725_824505_3D84E0E2)
rafael j. wysocki wrote:
> On Tuesday, February 14, 2012, NeilBrown wrote:
>
> > (or just keep this stuff out of the kernel and let a user-space daemon make
> > those decisions).
>
> Which is never going to really work, IMHO.
>
> Realistically, do you know of any distro, vendor, whoever, who tried to
> actually do that in a released product (or even in a release candidate,
> or milestone, or whatever different from a prototype running only on one's
> personal desktop)? I don't.
well, depending on your decision of "that", there are something like
2.5 million OLPC XO laptops that do it. do they count? ;-)
we're still in the middle of converting our 2.6-era home-grown power
management mechanisms to the 3.0-era level, using the
.../power/wakeup[_count] and /sys/power/wakeup_count mechanisms.
(change comes slowly to shipping products.) but we do have a
user-level suspend manager.
to the real point of your question: no, i don't think it does what
you're talking about yet -- i.e., control by applications over whether
suspend should be permitted or not exists, but isn't nearly as
reliable or as foolproof as any of the mechanisms discussed here
recently.
paul
=---------------------
paul fox, pgf@laptop.org
next prev parent reply other threads:[~2012-02-16 2:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 2:24 [PATCH] Input: Add ioctl to block suspend while event queue is not empty Arve Hjønnevåg
2012-02-11 23:28 ` Rafael J. Wysocki
2012-02-13 23:52 ` Arve Hjønnevåg
2012-02-15 23:51 ` Rafael J. Wysocki
2012-02-16 5:24 ` Arve Hjønnevåg
2012-02-16 22:31 ` Rafael J. Wysocki
2012-02-16 22:33 ` Mark Brown
2012-02-14 3:25 ` NeilBrown
2012-02-15 23:30 ` Rafael J. Wysocki
2012-02-16 1:53 ` Paul Fox [this message]
2012-02-16 21:44 ` Rafael J. Wysocki
2012-02-15 23:18 ` 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=20867.1329357211@foxharp.boston.ma.us \
--to=pgf@laptop.org \
--cc=arve@android.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=neilb@suse.de \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).