From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: Len Brown <lenb@hera.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"rjw@sisk.pl" <rjw@sisk.pl>
Subject: Re: /proc/acpi/ removal plan
Date: Thu, 18 Sep 2008 23:43:43 -0400 [thread overview]
Message-ID: <20080919034343.GA7594@core.corenet.prv> (raw)
In-Reply-To: <7C8E86B73C916D47820B1A143DB97BC00887719AEE@pdsmsx502.ccr.corp.intel.com>
On Fri, Sep 19, 2008 at 10:12:25AM +0800, Zhang, Rui wrote:
> >
> >> button sys I/F can be found at /sys/class/input/.
> >> e.g.
> >> # cat /sys/class/input/input*/device/hid
> >> LNXPWRBN
> >> PNP0C0C
> >
> >The /proc files for power and sleep buttons simply
> >told us what kind of button they were, just info, not API.
> >
> >The functional one is PNP0C0D, the lid switch.
> >It is also reflected in /sys/class/input, but I don't
> >see a way to find from /sys the open/closed state
> >like we have in /proc. (I ran into this when I tried
> >to delete the button /proc I/F some time ago).
> >
> You're right. Lid device still needs such an I/F.
>
Input devices do not export their state through sysfs (1 file per
every possible event would mean 100s of files per keyboard) but writing
an tiny utility to get thos information through /dev/input/event for
use by scripts should be trivial.
--
Dmitry
next prev parent reply other threads:[~2008-09-19 3:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 16:33 /proc/acpi/ removal plan Len Brown
2008-09-19 2:12 ` Zhang, Rui
2008-09-19 3:43 ` Dmitry Torokhov [this message]
2008-09-19 22:07 ` Rafael J. Wysocki
2008-09-22 1:33 ` Zhang Rui
2008-09-22 15:51 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 6:32 Len Brown
2008-09-18 7:39 ` Zhang Rui
2008-09-23 0:42 ` Henrique de Moraes Holschuh
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=20080919034343.GA7594@core.corenet.prv \
--to=dmitry.torokhov@gmail.com \
--cc=lenb@hera.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
--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