Re: [RFC] What are the goals for the architecture of an in-kernel IR system?

Christoph Bartelmus
2009-12-03T21:52:45Z

Hi Mauro,

on 03 Dec 09 at 19:10, Mauro Carvalho Chehab wrote:
[...]
>>> So the lirc_imon I submitted supports all device types, with the
>>> onboard decode devices defaulting to operating as pure input devices,
>>> but an option to pass hex values out via the lirc interface (which is
>>> how they've historically been used -- the pure input stuff I hacked
>>> together just a few weeks ago), to prevent functional setups from
>>> being broken for those who prefer the lirc way.
>>
>> Hmm. I'd tend to limit the lirc interface to the 'raw samples' case.

>> Historically it has also been used to pass decoded data (i.e. rc5) from
>> devices with onboard decoding, but for that in-kernel mapping + input
>> layer really fits better.

> I agree.

Consider passing the decoded data through lirc_dev.
- there's a large user base already that uses this mode through lirc and
would be forced to switch to input layer if it disappears.
- that way all IR drivers would consistently use lirc interface and all
PnP hooks could be implemented there in one place.
- drivers like lirc_imon that have to support both raw and decoded mode,
currently have to implement both the lirc and the input interface.
Complexity could be reduced in such cases. But maybe this is necessary
anyway for lirc_imon that also includes mouse functionality. Jarod?

Christoph