From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Zhang Rui <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: a question about lid input device
Date: Mon, 5 Jul 2010 13:27:32 -0700 [thread overview]
Message-ID: <20100705202731.GA17013@core.coreip.homeip.net> (raw)
In-Reply-To: <20100705194945.GA11096@khazad-dum.debian.net>
On Mon, Jul 05, 2010 at 04:49:45PM -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 05 Jul 2010, Zhang Rui wrote:
> > > I think if you can listen to uevents you can just as easily open /dev/
> > > input/eventX and listen to proper input events.
> > >
> > the question is users may want to get the lid switch STATUS,
> > asynchronously.
>
> More often than not, you need to know the current state when dealing
> with EV_SW, to be able to do anything sensbile with it in GUIs, etc.
>
I understand the need of getting the current state of a lid
switch/key/etc (and for that someone just need to write a utility
useable from shell scripts). But I do not understand how adding switch
state to uevents (that are emitted normally only when a new device is
created) will help here.
--
Dmitry
next prev parent reply other threads:[~2010-07-05 20:27 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 [this message]
2010-07-07 3:08 ` Zhang Rui
2010-07-07 5:36 ` Dmitry Torokhov
2010-07-07 15:14 ` Paul Fox
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=20100705202731.GA17013@core.coreip.homeip.net \
--to=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