Messages in this thread | | | Subject | Re: [RFC] [PATCH] Make ACPI button driver an input device | From | Xavier Bestel <> | Date | Thu, 20 Apr 2006 18:11:00 +0200 |
| |
On Thu, 2006-04-20 at 17:57, Alexey Starikovskiy wrote: > Matthew Garrett wrote: > > On Thu, Apr 20, 2006 at 07:35:53PM +0400, Alexey Starikovskiy wrote: > > > >> Could it be more sensible to use kevent and dbus for sending all events > >> from ACPI? > > > > For most of the events, probably. I'm less convinced by the button > > driver - sleep and power buttons can also generate keycodes rather than > > ACPI events, and so getting the button driver to behave like an input > > device adds consistency. > > > I think you will agree that ACPI buttons are special and will need special handling even in input stream... > Generic application does not need to know if power, sleep, or lid button is pressed, so you will need to intercept them from input stream... I cannot find any reason to mix these buttons into input, do you?
There are keyboards with power/sleep buttons. It makes sense they have the same behavior than ACPI buttons.
Xav
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |