Re: a question about lid input device

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Wed, Jul 07, 2010 at 11:14:20AM -0400, Paul Fox wrote:
> henrique de moraes holschuh wrote:
>  > On Sun, 13 Jun 2010, Zhang Rui wrote:
>  > > Then we update the lid switch status when a Lid notification comes.
>  > > right?
>  > 
>  > Yes.
>  > 
>  > > Then, IMO, userspace can get the lid status
>  > > via /sys/class/input/inputX/uevent, right?
>  > 
>  > No, only through an IOCTL.
>  > 
>  > > /sys/class/input/input1/uevent:EV==21
>  > 
>  > That's an bitmap of al EV_EV it supports.
>  > 
>  > > /sys/class/input/input1/uevent:SW==1
>  > 
>  > That's an bitmap of al EV_SW it supports.
>  > 
>  > > Lid is opened but SW is set, I tried to close/open the lid and found
>  > > that this bit never changes. is there something I misunderstand? can we
>  > > get the lid status in userspace?
>  > 
>  > IOCTL(), only.
>  > 
>  > Since nobody got a input-utils standard package (or added something to
>  > util-linux) yet to do that (AFAIK anyway), it is a MAJOR annoyance for
>  > shell scripts that want to query EV_SW state...
> 
> i understand that it's not fully general, but for the case of
> the lid:  is /proc/acpi/button/lid/LID/state going away?
> 

Yes, according to feature-removal.txt ACPI procfs interface shoudl have
been gone back in 2008.

-- 
Dmitry