public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fox <pgf@foxharp.boston.ma.us>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Zhang Rui <rui.zhang@intel.com>,
	dmitry.torokhov@gmail.com,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"Brown, Len" <lenb@kernel.org>
Subject: Re: a question about lid input device
Date: Wed, 07 Jul 2010 11:14:20 -0400	[thread overview]
Message-ID: <8005.1278515660@foxharp.boston.ma.us> (raw)
In-Reply-To: <20100614020127.GA30773@khazad-dum.debian.net> (sfid-20100613_220136_963531_F0446252)

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?

paul
=---------------------
 paul fox, pgf@foxharp.boston.ma.us (arlington, ma, where it's 87.1 degrees)

  parent reply	other threads:[~2010-07-07 15:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13  6:53 a question about lid input device Zhang Rui
2010-06-14  2:01 ` Henrique de Moraes Holschuh
2010-06-22  1:56   ` Len Brown
2010-07-04  8:35     ` Dmitry Torokhov
2010-07-05  1:09       ` Zhang Rui
2010-07-05  1:28         ` Dmitry Torokhov
2010-07-05  1:47           ` Zhang Rui
2010-07-05 19:49             ` Henrique de Moraes Holschuh
2010-07-05 20:04               ` Paul Fox
2010-07-05 20:27               ` Dmitry Torokhov
2010-07-07  3:08                 ` Zhang Rui
2010-07-07  5:36                   ` Dmitry Torokhov
2010-07-07 15:14   ` Paul Fox [this message]
2010-07-07 16:25     ` Dmitry Torokhov
2010-07-07 16:51       ` Paul Fox
2010-07-07 17:01         ` Dmitry Torokhov
2010-07-07 17:08           ` Paul Fox
2010-07-07 17:19             ` Dmitry Torokhov
2010-09-29  1:12       ` Len Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8005.1278515660@foxharp.boston.ma.us \
    --to=pgf@foxharp.boston.ma.us \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox