Skip to content

Introduce driver for IMS PCU devices

Dmitry Torokhov linux-input 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3Input: add new keycodes for passenger control unitsinclude/uapi/linux/input.h+5 -00 replies
2/3Input: add IMS Passenger Control Unit driverdrivers/input/misc/Kconfig drivers/input/misc/Makefile drivers/input/misc/ims-pcu.c+1918 -00 replies
3/3USB: cdc-acm - blacklist IMS PCU devicedrivers/usb/class/cdc-acm.c drivers/usb/class/cdc-acm.h+14 -01 reply

Reviews trailers per patch

1 of 3 patches has a Reviewed-by or Acked-by.

PatchGreg Kroah-Hartman
1/3
2/3
3/3A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/3] Introduce driver for IMS PCU devices

IMS, an In Flight Entertainment System provider, has a number of seat displays Linux. To interact with the user IMS uses a passenger Control Unit (PCU), which communicates with Rave Display Unit via a USB interface.

Originally large part of the PCU handling was done from userspace and so it presents itself as two distinct USB devices: one is a standard HID mouse and another is a CDC-ACM modem-like device. The latter one was used by IMS userspace software to get the status of all PCU buttons and perform other operations. However the fact that with the custom userspace handling the device resides outside of the standard input framework hinders use of the device elsewhere in the stack and this patch series attempts to fix this issue by creating a proper input driver for the device. If the device was purely input device it would also be possible to use cdc-acm + userspace solution and loop the input events back into the kernel via uinput, however the device also allows control its key backlight, which exported as a standard LED device, and this functionality is not available through uinput (nor should it be). Firmware update is also implemented via the standard "request_firmware" mechanism.

The patch series consists of 3 parts:

- a patch adding new keycodes needed for PCU;
- the driver itself;
- a patch to cdc-acm driver to ignore PCU devices when ims-pcu driver is enabled.

Thanks.

Signature · 1 line
Dmitry