mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Jouni Malinen <j@w1.fi>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Stephen Chen <Stephen.Chen@atheros.com>
Subject: Re: Generic events for wake up from S1-S4
Date: Thu, 23 Jul 2009 16:57:57 +0200	[thread overview]
Message-ID: <20090723145757.GB28158@elf.ucw.cz> (raw)
In-Reply-To: <20090718235609.GC25343@khazad-dum.debian.net>

On Sat 2009-07-18 20:56:10, Henrique de Moraes Holschuh wrote:
> On Sat, 18 Jul 2009, Luis R. Rodriguez wrote:
> > Hm yeah, but I doubt someone will do that, generally we'd get one wake
> > up event. Can't we just report the first one and ignore the rest?
> 
> Well, I'd say keeping it simple is best, here.  What if you ignore the more
> interesting wakeup events by chance (and it is really up to userspace to
> know what it considers interesting...)?  IMHO, just issue as many
> notifications as needed, let userspace filter it if it wants.
> 
> But if you guys are talking about something really generic, shouldn't it
> also provide the important "why" along with the "who"?
> 
> Even for the most common cases, the "why" is useful: userspace may well want
> to run special routines when it wakes up because of WoL and WoW (instead of
> a key press, lid open or mouse movement...).

What special routines?

Note that the "why" is unreliable by design. Network driver will
ignore WoL during run-time, right?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2009-07-23 14:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 22:11 Luis R. Rodriguez
2009-07-14 23:53 ` Pavel Machek
2009-07-15 15:51   ` Luis R. Rodriguez
2009-07-15 15:56     ` Luis R. Rodriguez
2009-07-15 18:00     ` Luis R. Rodriguez
2009-07-18 10:37       ` Pavel Machek
2009-07-18 20:02         ` Luis R. Rodriguez
2009-07-18 23:56           ` Henrique de Moraes Holschuh
2009-07-20 16:27             ` Luis R. Rodriguez
2009-07-21 15:10               ` Henrique de Moraes Holschuh
2009-07-23 14:57             ` Pavel Machek [this message]
2009-07-23 18:57               ` Henrique de Moraes Holschuh
2009-07-23 19:13                 ` Pavel Machek
2009-07-23 19:45                   ` Henrique de Moraes Holschuh
2009-07-23 19:51                     ` Pavel Machek
2009-07-23 20:10                       ` Henrique de Moraes Holschuh
2009-07-23 21:27                         ` Rafael J. Wysocki
2009-07-24  0:53                           ` ykzhao
2009-07-24 13:39                             ` Henrique de Moraes Holschuh
2009-07-24 14:49                               ` Johannes Berg
2009-07-24 15:25                               ` Luis R. Rodriguez
2009-07-23 20:31                       ` Valdis.Kletnieks

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=20090723145757.GB28158@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Stephen.Chen@atheros.com \
    --cc=hmh@hmh.eng.br \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --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

all inboxes | Powered by JetHome®