On Wed, May 13, 2020 at 10:16:46AM +0200, Greg KH wrote:

On Tue, May 12, 2020 at 10:07:24AM +0100, Sean Young wrote:

quoted

So this device is the infrared kind which rc-core (in drivers/media/rc/)
supports, remotes and such things (not for serial IR). So by using a 
rc-core driver, it can use kernel IR decoding, BPF decoding, lirc chardev
and rc keymaps, etc.

So why do you want to user serio for this?  serio should only be for
input devices with a serial protocol.

Admittedly this is a bit tenuous.

What I'm trying to do is write a kernel driver which uses the usb serial
drivers, and not write a poor man's version of usb serial in the IR driver.

I think a custom usb driver that exposes the interfaces as input devices
is going to be the simplest thing for you to do here as you will have
full control over the packet size and format much easier.  Odds are it
will be less work overall for this.

Admittedly I don't think it will be much code, so maybe it won't be so
ugly. It's just the code duplication I was trying to avoid.

So, I'll go ahead and as you suggest.

Thank you for your time and thoughts on this.


Sean