From: Pavel Machek <pavel@ucw.cz>
To: Brian Norris <briannorris@chromium.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
linux-pm@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH] PM / wakeirq: report wakeup events in dedicated wake-IRQs
Date: Thu, 10 Nov 2016 21:57:20 +0100 [thread overview]
Message-ID: <20161110205720.GB31728@amd> (raw)
In-Reply-To: <1478801227-65527-1-git-send-email-briannorris@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Thu 2016-11-10 10:07:07, Brian Norris wrote:
> It's important that user space can figure out what device woke the
> system from suspend -- e.g., for debugging, or for implementing
> conditional wake behavior. Dedicated wakeup IRQs don't currently do
> that.
>
> Let's report the event (pm_wakeup_event()) and also allow drivers to
> synchronize with these events in their resume path (hence, disable_irq()
> instead of disable_irq_nosync()).
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
How is this supposed to be presented to userspace?
There was big flamewar about that some time ago, and "what woke up the
system" is pretty much meaningless, and certainly unavailable on most
PC class hardware. Good question to ask is "what wakeup events
happened while the userspace was not available"....
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-11-10 20:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 18:07 [PATCH] PM / wakeirq: report wakeup events in dedicated wake-IRQs Brian Norris
2016-11-10 18:13 ` Dmitry Torokhov
2016-11-10 18:49 ` Brian Norris
2016-11-10 20:49 ` Tony Lindgren
2016-11-10 21:30 ` Brian Norris
2016-11-11 16:47 ` Tony Lindgren
2016-11-11 19:40 ` Brian Norris
2016-11-11 20:17 ` Tony Lindgren
2016-11-11 21:09 ` Alan Stern
2016-11-11 21:40 ` Rafael J. Wysocki
2016-11-11 0:06 ` Rafael J. Wysocki
2016-11-11 16:31 ` Tony Lindgren
2016-11-11 21:33 ` Rafael J. Wysocki
2016-11-11 22:29 ` Tony Lindgren
2016-11-11 22:32 ` Tony Lindgren
2016-11-11 23:34 ` Rafael J. Wysocki
2016-11-12 0:19 ` Tony Lindgren
2016-11-12 0:35 ` Rafael J. Wysocki
2016-11-18 20:18 ` Tony Lindgren
2016-11-23 22:37 ` Rafael J. Wysocki
2016-11-24 14:27 ` Tony Lindgren
2016-11-10 20:57 ` Pavel Machek [this message]
2016-11-10 21:39 ` Brian Norris
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=20161110205720.GB31728@amd \
--to=pavel@ucw.cz \
--cc=briannorris@chromium.org \
--cc=computersforpeace@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).