[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B164EEC.9030504@redhat.com>
Date: Wed, 02 Dec 2009 12:26:36 +0100
From: Gerd Hoffmann <kraxel@...hat.com>
To: Mauro Carvalho Chehab <mchehab@...hat.com>
CC: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Devin Heitmueller <dheitmueller@...nellabs.com>,
Jon Smirl <jonsmirl@...il.com>,
Maxim Levitsky <maximlevitsky@...il.com>, awalls@...ix.net,
j@...nau.net, jarod@...hat.com, jarod@...sonet.com, khc@...waw.pl,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, lirc-list@...ts.sourceforge.net,
superm1@...ntu.com, Christoph Bartelmus <lirc@...telmus.de>
Subject: Re: [RFC v2] Another approach to IR
On 12/01/09 22:05, Mauro Carvalho Chehab wrote:
> So, I would just add the IR sysfs parameters at the /sys/class/input, if
> the device is an IR (or create it is /sys/class/input/IR).
No, you add it to the physical device node.
The usb mouse on the system I'm working on is here:
zweiblum kraxel $ ll /sys/class/input/ | grep usb2
lrwxrwxrwx. 1 root root 0 Dec 2 12:07 event7 ->
../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input7/event7/
lrwxrwxrwx. 1 root root 0 Dec 2 12:07 input7 ->
../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input7/
lrwxrwxrwx. 1 root root 0 Dec 2 12:07 mouse2 ->
../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input7/mouse2/
So "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0" is the device
node of the physical device, and the input devices belonging to it are
in the "input" subdirectory.
If the mouse would be a usb IR receiver the IR attributes should go to
/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0 or maybe a 'ir'
subdirectory there.
HTH,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists