public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fox <pgf@laptop.org>
To: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: a question about lid input device
Date: Mon, 05 Jul 2010 16:04:06 -0400	[thread overview]
Message-ID: <2022.1278360246@foxharp.boston.ma.us> (raw)
In-Reply-To: <20100705194945.GA11096@khazad-dum.debian.net> (sfid-20100705_154958_487997_A01EF40D)

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.

indeed, this is true for almost any event-on-change interface -- tablet mode,
AC insertion, etc.  the change event alone is never enough.

paul
=---------------------
 paul fox, pgf@laptop.org

  reply	other threads:[~2010-07-05 20:21 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 [this message]
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=2022.1278360246@foxharp.boston.ma.us \
    --to=pgf@laptop.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