From: Pavel Machek <pavel@ucw.cz>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Derek Basehore <dbasehore@google.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Subject: Re: selective wakeups
Date: Tue, 3 Feb 2015 13:14:37 +0100 [thread overview]
Message-ID: <20150203121437.GA26492@amd> (raw)
In-Reply-To: <54D09AC7.5080503@collabora.com>
Hi!
> I'm looking at how to support wakeup sources that resume a subset of the
> suspended devices. The goal is for the machine to be able to wakeup the
> CPU but not the display or sound card when the wakeup source isn't
> user-initiated, such as RTC or a network card (we can call it automatic
> resume).
>
> http://www.chromium.org/chromium-os/packages/power_manager/suspend-and-resume#TOC-Dark-Resume
> My first idea is for userspace to be able to configure via sysfs which
> devices aren't going to be resumed when a given wakeup source fires.
> We'll also need a way to resume the display and sound card if there's
> user interaction when the system has resumed automatically.
Well.. the web page describes quite different use case.
Anyway... right solution would be not to resume devices that were
runtime-suspended, no? With that, additional sysfs tweaks should not
be needed?
For the "periodically wakeup from S3 to prevent battery
draining".. Some machines (Sharp Zaurus) already do similar tricks
directly from kernel, and you may want to do the same. Battery
completely draining when in S3 is quite bad situation, and preventing
it even without userspace support would be good.
Best regards,
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:[~2015-02-03 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 9:54 selective wakeups Tomeu Vizoso
2015-02-03 12:14 ` Pavel Machek [this message]
2015-02-03 15:33 ` Alan Stern
2015-02-04 9:05 ` Oliver Neukum
2015-02-09 9:48 ` Tomeu Vizoso
2015-02-09 15:45 ` Alan Stern
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=20150203121437.GA26492@amd \
--to=pavel@ucw.cz \
--cc=dbasehore@google.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tomeu.vizoso@collabora.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