From: Michael Tokarev <mjt@tls.msk.ru>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: acpi/apm events as inputs: how to handle?
Date: Mon, 07 Jan 2008 17:50:16 +0300 [thread overview]
Message-ID: <47823C28.8010800@msgid.tls.msk.ru> (raw)
In-Reply-To: <d120d5000801070620i1505e697jf73fa001a9c884db@mail.gmail.com>
Dmitry Torokhov wrote:
[]
>> Well, you use event device in any case; as for finding right one - I guess
>> you look at device capabilities and filter what you need ...
>>
>> {pts/0}%
>> cat /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/capabilities/key
>> 100000 0 0 0
>
> Exactly. Any driver working through evdev interface should examine
> device's capabilities and decide whether it is interested in the
> device or not.
Ok, got it.
But I can't open the device multiple times, can I?
Like, there's a daemon listening on volume up/down and other
multimedia keys for example, and it can't listen to the same
eventX as a daemon that's watching for power/sleep buttons, --
instead, they should be combined into the same executable.
Unless there's a way to multiplex the events...
(Hmm, this becoming quite... ugly. Oh well.)
By the way, where are all the capabilities of input devices
documented?
/mjt
next prev parent reply other threads:[~2008-01-07 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 9:56 acpi/apm events as inputs: how to handle? Michael Tokarev
2008-01-05 23:30 ` Pavel Machek
2008-01-06 2:05 ` Dmitry Torokhov
2008-01-07 10:42 ` Michael Tokarev
2008-01-07 13:03 ` Andrey Borzenkov
2008-01-07 14:20 ` Dmitry Torokhov
2008-01-07 14:50 ` Michael Tokarev [this message]
2008-01-07 15:47 ` Michael Tokarev
2008-01-07 15:51 ` Dmitry Torokhov
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=47823C28.8010800@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=arvidjaar@mail.ru \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.