TODO RC: Difference between revisions
Jump to navigation
Jump to search
(Remove parts merged for v4.14 (and some cleanups)) |
No edit summary |
||
| (18 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Minor bugs/improvement == |
== Minor bugs/improvement == |
||
* struct ir_raw_event_ctrl member prev_ev. Investigate if this can be removed. |
|||
* serial_ir tx w/ softcarrier, does it work on 32 bit? "new_duty_cycle * NSEC_PER_SEC" > 2^32. |
|||
* if driver depends on RC_CORE, change this to select RC_CORE, depends on INPUT? OR use a patch like https://patchwork.linuxtv.org/patch/40601/ and remove "depends on RC_CORE". |
* if driver depends on RC_CORE, change this to select RC_CORE, depends on INPUT? OR use a patch like https://patchwork.linuxtv.org/patch/40601/ and remove "depends on RC_CORE". |
||
* mceusb can do wakeups. Allow this to be configured |
|||
* RC device RC_DRIVER_IR_RAW_TX leaks dev->raw on rc_unregister_device()? |
|||
* ir-keytable should display and allow you to configure wakeup protocol and scancode (protocol?) |
|||
* Unplug iguanair with lirc chardev open causes kernel to go bang |
|||
* Can sir_ir and/or serial_ir use serdev |
|||
| ⚫ | |||
== Larger work == |
|||
* ir-ctl should list available devices if run without any argument and allow to select device based on rc (based on /sys/class/rc/). |
|||
* Make it possible to load multiple keymaps with ir-keytable. It should detect if the new keymap conflicts with any already loaded keymap, and ensure the right protocols are selected. |
|||
* bpf ir decoders need a way of specifying minimum timeout and repeat period |
|||
| ⚫ | |||
* driver for sasem remote controller |
|||
* lirc_zilog rc core driver (Sean Young working on this) |
|||
* test if pwm-ir-tx can replace ir-rx51.c driver on n900 hardware |
|||
* Once lirc_zilog is removed, remove lirc kapi. Example is here: https://git.linuxtv.org/syoung/media_tree.git/log/?h=remove-lirc-dev |
|||
* Implement scancode reading and transmitting: |
|||
** It's very hard to tell what protocol a remote is using |
|||
** Kernel already has encoders, make sure they can be used for tx |
|||
** CEC might want to reuse this interface |
|||
** Patch series already exist for this |
|||
* MS MCE Keyboard keymap needs multiple protocols. Keymap needed to select it. https://www.mail-archive.com/linux-media@vger.kernel.org/msg115706.html |
|||
Latest revision as of 15:32, 21 September 2018
Minor bugs/improvement
- if driver depends on RC_CORE, change this to select RC_CORE, depends on INPUT? OR use a patch like https://patchwork.linuxtv.org/patch/40601/ and remove "depends on RC_CORE".
- mceusb can do wakeups. Allow this to be configured
- ir-keytable should display and allow you to configure wakeup protocol and scancode (protocol?)
- Can sir_ir and/or serial_ir use serdev
- Make the kernel mapping rc_proto:scancode -> keycode, not just scancode. This should reduce the number of possible conflicts.
- ir-ctl should list available devices if run without any argument and allow to select device based on rc (based on /sys/class/rc/).
- bpf ir decoders need a way of specifying minimum timeout and repeat period
- driver for sasem remote controller
- test if pwm-ir-tx can replace ir-rx51.c driver on n900 hardware