Exporting EV_SW SW_LID events from thinkpad-acpi to input layer

Exporting EV_SW SW_LID events from thinkpad-acpi to input layer

[Henrique de Moraes Holschuh]

thinkpad-acpi can now be made to export EV_SW SW_LID events to the input
layer.

However, most (all?) thinkpads will also generate ACPI notifications to
\_SB.LID, on LID changes, i.e. this would duplicate an ACPI LID event, and I
undertand ACPI is already moving to provide those over an input device by
itself.

Given that situation, is it desireable for thinkpad-acpi to export EV_SW
SW_LID events by itself (possibly duplicating an event that the ACPI layer
will also issue)?  Or should I just ignore the lid events, and leave them
for the ACPI layer to deal with?

-- 
  "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

Re: Exporting EV_SW SW_LID events from thinkpad-acpi to input layer

[Dmitry Torokhov]

On Saturday 16 June 2007 10:44, Henrique de Moraes Holschuh wrote:
> thinkpad-acpi can now be made to export EV_SW SW_LID events to the input
> layer.
> 
> However, most (all?) thinkpads will also generate ACPI notifications to
> \_SB.LID, on LID changes, i.e. this would duplicate an ACPI LID event, and I
> undertand ACPI is already moving to provide those over an input device by
> itself.
> 
> Given that situation, is it desireable for thinkpad-acpi to export EV_SW
> SW_LID events by itself (possibly duplicating an event that the ACPI layer
> will also issue)?  Or should I just ignore the lid events, and leave them
> for the ACPI layer to deal with?
> 

I would just rely on ACPI button driver to deliver EV_SW/SW_LID events.
After all there is only one lid switch on the box so having 2 input
devices rep[orting it is counter-intuitive.
 
-- 
Dmitry