| commit | b524da60bf43ada0bdc6959f53a66052333af4e7 | |
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Tue, 11 Nov 2008 01:46:20 +0000 (10 23:46 -0200) | ||
| committer | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Tue, 11 Nov 2008 01:46:20 +0000 (10 23:46 -0200) | ||
| tree | 90d2a3cfbe2a9a13ad26e1ef04325f9213fd9ed7 | treesnapshot (tar.gz zip) |
| parent | b2ae2a0d5e2a4cdf3d1071a15c7a9507e4cdb8c7 | commitdiff |
rfkill: add uevent notifications
Use the notification chains to also send uevents, so that userspace can be
notified of state changes of every rfkill switch.
Userspace should use these events for OSD/status report applications and
rfkill GUI frontends. HAL might want to broadcast them over DBUS, for
example. It might be also useful for userspace implementations of
rfkill-input, or to use HAL as the platform driver which promotes rfkill
switch change events into input events (to synchronize all other switches)
when necessary for platforms that lack a convenient platform-specific
kernel module to do it.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
Cc: Dmitry Torokhov <dtor@mail.ru>
Use the notification chains to also send uevents, so that userspace can be
notified of state changes of every rfkill switch.
Userspace should use these events for OSD/status report applications and
rfkill GUI frontends. HAL might want to broadcast them over DBUS, for
example. It might be also useful for userspace implementations of
rfkill-input, or to use HAL as the platform driver which promotes rfkill
switch change events into input events (to synchronize all other switches)
when necessary for platforms that lack a convenient platform-specific
kernel module to do it.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
Cc: Dmitry Torokhov <dtor@mail.ru>
| net/rfkill/rfkill.c | diffblobblamehistory |