From: Zhang Rui <rui.zhang@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: a question about lid input device
Date: Mon, 05 Jul 2010 09:47:24 +0800 [thread overview]
Message-ID: <1278294444.4537.6134.camel@rzhang1-desktop> (raw)
In-Reply-To: <C5204E20-E9CE-40D7-9398-A32D6E993EE0@gmail.com>
On Mon, 2010-07-05 at 09:28 +0800, Dmitry Torokhov wrote:
> On Jul 4, 2010, at 6:09 PM, Zhang Rui <rui.zhang@intel.com> wrote:
>
> > On Sun, 2010-07-04 at 16:35 +0800, Dmitry Torokhov wrote:
> >> On Mon, Jun 21, 2010 at 09:56:37PM -0400, Len Brown wrote:
> >>> Dmitry,
> >>> Is there a reason not to simply add a "state" attribute
> >>> to a LID input device?
> >>>
> >>
> >> Len,
> >>
> >> There is no LED input device, there is an input device that happens
> >> to
> >> report EV_SW/SW_LID state. If we did that we'd need to add attributes
> >> for all types of switches, keys, current values of REL and ABS axis,
> >> min/max/fuzz/flat settings of ABS axis and so forth that input device
> >> might report. I do not think it is a good idea.
> >>
> > I agree.
> > How about adding a field in uevent file that reports the switch
> > status?
> >
>
>
> 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.
thank,
rui
next prev parent reply other threads:[~2010-07-05 1:46 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 [this message]
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
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=1278294444.4537.6134.camel@rzhang1-desktop \
--to=rui.zhang@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/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