IR: add lirc support to ir-core
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 of 3 patches 2 repliesIn review
- v13 patches 18 repliesSuperseded
2 of 3 patches are in this archive. The cover letter announces 3.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/3 | IR: add ir-core to lirc userspace decoder bridge driverdrivers/ drivers/ drivers/ +4 more | +320 | 0 replies | |
| 3/3 | IR: add empty lirc pseudo-keymapdrivers/ drivers/ include/ | +43 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/3] IR: add lirc support to ir-core
Quoted 16 lines · Jarod Wilson
This patch series adds the core lirc device interface,
lirc_dev, and an ir-core bridge driver. Currently, only the receive side is wired up in the bridge driver, but adding transmit support is up next.Currently, adding this code allows any raw IR ir-core device driver to pass raw IR out to the lirc userspace, without the driver having to have any actual knowledge of lirc -- its just feeding data to another IR protocol decoder engine.
This also (hopefully) makes life easier for any currently out-of-tree pure lirc device drivers, as they can count on the lirc core bits being present. This is a Good Thing(tm) while we work on porting additional lirc device drivers to ir-core, and also makes life easier for users to migrate from lirc decoding to in-kernel decoding (where possible) when their device's driver gets ported.
Quoted 6 lines
This patchset has been tested with the ir-core mceusb driver, and IR receive behaves 100% identical in lirc mode to the old
lirc_mceusb.[PATCH 1/3] IR: add core lirc device interface [PATCH 2/3] IR: add an empty lirc "protocol" keymap [PATCH 3/3] IR: add ir-core to lirc interface bridge driver
Version 2 moves a good chunk of ir tx details that are (probably) specific to providing raw IR data from userspace via lirc into the ir-core lirc bridge driver, instead of having them in the hardware-specific drivers themselves. This greatly reduced the complexity of the mceusb driver's ir tx function, and generalized the tx interface better for a non-lirc tx implementation.
Signature · 2 lines
Jarod Wilson [email protected]