[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090721151058.GA22182@khazad-dum.debian.net>
Date: Tue, 21 Jul 2009 12:10:58 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: "Luis R. Rodriguez" <mcgrof@...il.com>
Cc: Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
linux-kernel@...r.kernel.org,
Johannes Berg <johannes@...solutions.net>,
"John W. Linville" <linville@...driver.com>,
Jouni Malinen <j@...fi>,
linux-wireless <linux-wireless@...r.kernel.org>,
Stephen Chen <Stephen.Chen@...eros.com>
Subject: Re: Generic events for wake up from S1-S4
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists