Re: [RFC PATCH 0/4] V3 - Implementation of IR support using theinput subsystem
From: Maxim Levitsky
Date: Thu May 28 2009 - 11:06:57 EST
On Mon, 2008-10-06 at 15:43 -0400, Jon Smirl wrote:
> Third pass at implementing evdev support for IR. The goal of in-kernel IR is to integrate IR events into the evdev input event queue and maintain ordering of events from all input devices.
> New feature, raw mode. There are three sysfs attributes - ir_raw, ir_carrier, ir_xmitter. Read from ir_raw to get the raw timing data from the IR device. Set carrier and active xmitters and then copy raw data to ir_raw to send. These attributes may be better on a debug switch. You would use raw mode when decoding a new protocol. After you figure out the new protocol, write an in-kernel encoder/decoder for it.
> What should the IR API look like?
> How are IR events mapped into keyboard events? Should they be mapped? Map them in the kernel or in user space? The maps are tiny, less than 1K per remote. Sysfs can be used to load maps into the kernel driver. Make maps only for the common buttons and don't map unusual ones?
> How should multiple remotes be handled? Split them out into individual input devices, or group them onto a single IR device? I can implement either.
> The in-kernel code is tiny, about 20K including a driver.
> >From last post...
> Note that user space IR device drivers can use the existing support in evdev to inject events into the input queue.
> Send and receive are implemented. Received IR messages are decoded and sent to user space as input messages. Send is done via an IOCTL on the input device.
> Two drivers are supplied. mceusb2 implements send and receive support for the Microsoft USB IR dongle.
> The GPT driver implements receive only support for a GPT pin - GPT is a GPIO with a timer attached.
> Code is only lightly tested. Encoders and decoders have not been written for all protocols.
> Repeat is not handled for any protocol.
> I'm looking for help. There are 15 more existing LIRC drivers.
Any update on that?
I have a suggestion:
Instead of decoding protocols in kernel, why not to allow userspace to
upload timing signatures as specified in lirc.conf ?
As a example, what protocol this is:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/