Message-ID: <47823C28.8010800@msgid.tls.msk.ru>
Date: Mon, 07 Jan 2008 17:50:16 +0300
From: Michael Tokarev <mjt@tls.msk.ru>
Organization: Telecom Service, JSC
User-Agent: Icedove 1.5.0.14pre (X11/20071018)
MIME-Version: 1.0
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?
References: <477B5FD8.5070503@msgid.tls.msk.ru>	 <200801052105.03068.dtor@insightbb.com>	 <47820224.2020902@msgid.tls.msk.ru>	 <20080107130332.5973A2D6BF@smtp02.mtu.ru> <d120d5000801070620i1505e697jf73fa001a9c884db@mail.gmail.com>
In-Reply-To: <d120d5000801070620i1505e697jf73fa001a9c884db@mail.gmail.com>
OpenPGP: id=4F9CF57E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1156
Lines: 32

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/