I've been following this discussion on lkml and found it really painful to watch. The discussion on whether this belongs in kernel space or not seems to be ignored and in stead the debate focusses on how to translate IR codes to key codes.
Doing this in kernel-space is not the right place IMHO.
- IR drivers can exist in user-space too (e.g. libusb) and are perfectly valid, many of the current IR drivers are in user-space. Decoding IR in kernel-space for a user-space IR driver can't be right
- Decoding IR is not trivial at all. I've written a NEC decoder for a laserdisc emulator[3] and I've had to make any tweaks to make it match the behaviour of the original laserdisc player. I'd rather not reboot to apply changes to a IR decoder
- Having another daemon in user-space is not a problem at all, this allows extra security, can be swapped out, etc etc
Now my opinion is of no consequence, however noone has convinced Alan Cox either[1][2] which I find telling for whole thread.