Skip to contentSkip to conversation

Implementation of IR support using the input subsystem

RFC PATCH Emmanuel Fusté 3 participants 4 messages Sep 29, 2008 – Sep 30, 2008

lore
Share & tools
lore
#0 lore raw
Quoted 56 lines

Jon Smirl wrote:

Quoted 3 lines · Maxim Levitsky
Quoted 2 lines · Jon Smirl

Second pass at implementing evdev support for IR. The goal of

in-kernel IR

Quoted 8 lines
Quoted 8 lines

is to integrate IR events into the evdev input event queue and maintain ordering of events from all input devices.

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

Quoted 3 lines
Quoted 3 lines

device.

Two drivers are supplied. mceusb2 implements send and receive

support for

Quoted 5 lines
Quoted 5 lines

the Microsoft USB IR dongle.
The GPT driver implements receive only support for a GPT pin - GPT is a GPIO with a timer attached.

Encoders and decoders have not been written for all protocols.

Repeat is

Quoted 8 lines
Quoted 2 lines

not handled for any protocol. I'm looking for help. There are 15 more existing LIRC drivers.

Hi,

One thing worries me, there are bazillion of different IR protocols, but in-kernel decode support will mean that only handful of known

protocols

Quoted 4 lines

will work.
Suppose I take an old remote which has some unknown protocol. I want to be able to teach the system to listen to it. But how this can be done if protocols are hard coded?

There's not a bazillion different protocols.

For example thirty different vendors may use the NEC encoding. They will each use a unique device number and their own commands. While each of the thirty vendors may assign different device/command codes they are all still using the NEC encoding. These remotes won't trigger the other devices because the device fields won't match.

This code only converts raw IR timing of NEC/etc encoding into device/command. User space has to then figure out how to interpret device/command.

Christoph has pointed out that their are some more obscure encodings from RCMM, Grundig, Bang&Olufsen, Goldstar, Serial, Denon, RECS80, and Motorola that are different than the common ones at
http://www.sbprojects.com.

Quoted 6 lines

It takes about 1KB of code to add an encoding. We could make an "extra encoding" module for these obscure ones.

You can't have an infinite variety of encodings or table based universal remote controls wouldn't work.

Yes, in kernel clean/smalls (encoding/)decoding engines abstracted by the input subsystem are a good thing.
But you still need a way to send and received raw IR signal to be able to send or decode very out of spec signals like RC5 timing dependent Philips service mode codes. Or simply to decode / reverse engineer an IR protocol not already implemented by a kernel encoder/decoder.

Quoted 6 lines
Quoted 3 lines

I think that it would be much better to pass raw ir codes to

userspace, and

Quoted 1 line

make it deal with bazillion protocols, and you can always make it

auto learn

Quoted 14 lines
Quoted 8 lines

too, and save
results in configuration file.

My .02 cents.

Best regards,
Maxim Levitsky

Signature · 2 lines
Jon Smirl
[email protected]

Best regards,
Emmanuel.

#1 lore raw
Quoted 63 lines · Emmanuel Fusté
Quoted 57 lines

Jon Smirl wrote:

Quoted 29 lines · Maxim Levitsky
Quoted 20 lines · Jon Smirl

Second 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.

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.

Quoted 4 lines

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.

Hi,

Quoted 7 lines

One thing worries me, there are bazillion of different IR protocols, but in-kernel decode support will mean that only handful of known protocols
will work.
Suppose I take an old remote which has some unknown protocol. I want to be able to teach the system to listen to it. But how this can be done if protocols are hard coded?

There's not a bazillion different protocols.

For example thirty different vendors may use the NEC encoding. They will each use a unique device number and their own commands. While each of the thirty vendors may assign different device/command codes they are all still using the NEC encoding. These remotes won't trigger the other devices because the device fields won't match.

This code only converts raw IR timing of NEC/etc encoding into device/command. User space has to then figure out how to interpret device/command.

Christoph has pointed out that their are some more obscure encodings from RCMM, Grundig, Bang&Olufsen, Goldstar, Serial, Denon, RECS80, and Motorola that are different than the common ones at
http://www.sbprojects.com.

Quoted 6 lines

It takes about 1KB of code to add an encoding. We could make an "extra encoding" module for these obscure ones.

You can't have an infinite variety of encodings or table based universal remote controls wouldn't work.

Quoted 10 lines

Yes, in kernel clean/smalls (encoding/)decoding engines abstracted by the input subsystem
are a good thing.
But you still need a way to send and received raw IR signal to be able to send or
decode very out of spec signals like RC5 timing dependent Philips service mode
codes. Or simply to decode / reverse engineer an IR protocol not already implemented
by a kernel encoder/decoder.

I've been considering a sysfs interface for raw signals. Specialized apps that can handle raw signal could use this interface. It's not hard to add support for raw codes, maybe in the next pass. Something like a "raw" attribute. Write ints to it and they get sent, read ints from it to see what was received.

I'd don't think we should expose raw codes on the main evdev interfaces.

Quoted 31 lines
Quoted 18 lines
Quoted 10 lines

I think that it would be much better to pass raw ir codes to userspace, and
make it deal with bazillion protocols, and you can always make it auto learn
too, and save
results in configuration file.

Quoted 5 lines

My .02 cents.

Best regards,
Maxim Levitsky

Quoted 3 lines

--
Jon Smirl
[email protected]

Best regards,
Emmanuel.

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

Signature · 2 lines
Jon Smirl
[email protected]
#2 lore raw
Quoted 73 lines · Jon Smirl
Quoted 60 lines · Emmanuel Fusté
Quoted 54 lines

Jon Smirl wrote:

Quoted 27 lines · Maxim Levitsky
Quoted 19 lines · Jon Smirl

Second 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.

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.

Quoted 4 lines

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.

Hi,

Quoted 7 lines

One thing worries me, there are bazillion of different IR protocols, but in-kernel decode support will mean that only handful of known protocols
will work.
Suppose I take an old remote which has some unknown protocol. I want to be able to teach the system to listen to it. But how this can be done if protocols are hard coded?

There's not a bazillion different protocols.

For example thirty different vendors may use the NEC encoding. They will each use a unique device number and their own commands. While each of the thirty vendors may assign different device/command codes they are all still using the NEC encoding. These remotes won't trigger the other devices because the device fields won't match.

This code only converts raw IR timing of NEC/etc encoding into device/command. User space has to then figure out how to interpret device/command.

Christoph has pointed out that their are some more obscure encodings from RCMM, Grundig, Bang&Olufsen, Goldstar, Serial, Denon, RECS80, and Motorola that are different than the common ones at
http://www.sbprojects.com.

Quoted 6 lines

It takes about 1KB of code to add an encoding. We could make an "extra encoding" module for these obscure ones.

You can't have an infinite variety of encodings or table based universal remote controls wouldn't work.

Quoted 10 lines

Yes, in kernel clean/smalls (encoding/)decoding engines abstracted by the input subsystem
are a good thing.
But you still need a way to send and received raw IR signal to be able to send or
decode very out of spec signals like RC5 timing dependent Philips service mode
codes. Or simply to decode / reverse engineer an IR protocol not already implemented
by a kernel encoder/decoder.

Quoted 7 lines

I've been considering a sysfs interface for raw signals. Specialized apps that can handle raw signal could use this interface. It's not hard to add support for raw codes, maybe in the next pass. Something like a "raw" attribute. Write ints to it and they get sent, read ints from it to see what was received.

I'd don't think we should expose raw codes on the main evdev interfaces.

Just one question,

Suppose I have non-standard remote, and I want to teach lirc to use it, and I have general purpose receiver, how can I do this?

Best regards,
Maxim Levitsky

Quoted 31 lines
Quoted 28 lines
Quoted 11 lines
Quoted 11 lines

I think that it would be much better to pass raw ir codes to userspace, and
make it deal with bazillion protocols, and you can always make it auto learn
too, and save
results in configuration file.

My .02 cents.

Quoted 8 lines
Quoted 3 lines

Best regards,
Maxim Levitsky

--
Jon Smirl
[email protected]

Best regards,
Emmanuel.

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

#3 lore raw
Quoted 2 lines · Maxim Levitsky

Suppose I have non-standard remote, and I want to teach lirc to use it, and I have general purpose receiver, how can I do this?

You need to write an app to use the sysfs interface for raw code. Or you could write an in-kernel encoder/decoder and use the standard interfaces. Or you could throw it away and spend $10 for a standard one.

Signature · 2 lines
Jon Smirl
[email protected]