public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, "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: Tue, 21 Jul 2009 12:10:58 -0300	[thread overview]
Message-ID: <20090721151058.GA22182@khazad-dum.debian.net> (raw)
In-Reply-To: <43e72e890907200927j40ee0f35j6c9c2ede09f5dca6@mail.gmail.com>

On Mon, 20 Jul 2009, Luis R. Rodriguez wrote:
> >> > What about simply reporting "wake event happened on this device" and
> >> > doing that for all the devices?
> >>
> >> That's fine too. Just think it would be nice to be more specific if possible.
> >
> > A generic way for a device (of any sort, not just network devices!) to
> > report that they just issued a system wakeup message, as well as the reason
> > it did that seems like a good way to do it to me.
> 
> This should be easy to do via udev events.
> 
> How about an generic platform registered, and udev events issues for
> wake-up-triggers, and also for wake-up-events, and leave all the
> sorting out to userspace? All we'd need in-kernel would be the trigger
> registration and event trigger notifications.

I am fine with it.  Please CC me if you write some code for that ;-)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2009-07-21 15:11 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
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 [this message]
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=20090721151058.GA22182@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --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=pavel@ucw.cz \
    --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