public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "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: Sat, 18 Jul 2009 12:37:56 +0200	[thread overview]
Message-ID: <20090718103756.GA11381@elf.ucw.cz> (raw)
In-Reply-To: <43e72e890907151100j37feb30av7281d09960ca5db2@mail.gmail.com>

On Wed 2009-07-15 11:00:07, Luis R. Rodriguez wrote:
> On Wed, Jul 15, 2009 at 8:51 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> > On Tue, Jul 14, 2009 at 4:53 PM, Pavel Machek<pavel@ucw.cz> wrote:
> >> On Tue 2009-07-14 15:11:45, Luis R. Rodriguez wrote:
> >>> I'm working on Wake-on-Wireless support for wireless right now [1].
> >>> Upon wake up I wanted to inform the kernel of the event which caused
> >>> the wake up but am not clear if there is a generic API for this. Mind
> >>> you, for WoW we'll need at least some AC power to the card so we'll
> >>> need to at least be in S3-Hot so we'll only need events for that for
> >>> now.
> >>>
> >>> Do we have some generic infrastructure to gather reasons for wake up
> >>> from S1-S4 and pass this to userspace yet?
> >>
> >> I do not think generic api exists...
> 
> Going back to this topic -- any suggestions? Will a generic netlink
> family be OK? Or perhaps easier a udev event for some suitable
> existing parent ?

Is "who woke me" information even relevant? Yes, it may be interesting
enough for printk, but... What will userspace do with that information?

Imagine WoW packet comes, 5msec later WoL packet comes, 5msec later
user opens the lid. You report WoW as wakeup reason, but it is
inherently "racy".

What about simply reporting "wake event happened on this device" and
doing that for all the devices?


									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-07-18 10:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 22:11 Generic events for wake up from S1-S4 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 [this message]
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
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=20090718103756.GA11381@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Stephen.Chen@atheros.com \
    --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