Double Presses on IR device [Nuvoton cir] - ir-keytable ignores delay period parameter

Hi,

on my intel NUC machine i use my ir-device [Nuvoton w836x7hg] quite a long time without any bigger issues. Since last weeks i recognize double presses. Maybe there was some update in nuvoton-cir modul or anywhere else, but i have no clue.

i found some (older) workaround. Unfortunately i cant post links :unamused:

i changed delay and repeat rate and used
ir-keytable --delay=500 --period=250

Repeat delay = 500 ms, repeat period = 125 ms
Changed Repeat delay to 500 ms and repeat period to 250 ms

i tried other values but without success. nuvoton-cir still recognizes repeating key presses during
repeat/delay time. (i believe this delay and repeat parameter never worked on my system.)

evtest /dev/input/event4

Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1050 product 0xc3 version 0x33
Input device name: “Nuvoton w836x7hg Infrared Remote Transceiver”
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 2 (KEY_1)
Event code 3 (KEY_2)
Event code 4 (KEY_3)
Event code 5 (KEY_4)
Event code 6 (KEY_5)
Event code 7 (KEY_6)
Event code 8 (KEY_7)
Event code 9 (KEY_8)
Event code 10 (KEY_9)
Event code 11 (KEY_0)
Event code 14 (KEY_BACKSPACE)
Event code 15 (KEY_TAB)
Event code 18 (KEY_E)
Event code 19 (KEY_R)
Event code 20 (KEY_T)
Event code 21 (KEY_Y)
Event code 23 (KEY_I)
Event code 24 (KEY_O)
Event code 28 (KEY_ENTER)
Event code 30 (KEY_A)
Event code 37 (KEY_K)
Event code 38 (KEY_L)
Event code 45 (KEY_X)
Event code 48 (KEY_B)
Event code 50 (KEY_M)
Event code 57 (KEY_SPACE)
Event code 103 (KEY_UP)
Event code 104 (KEY_PAGEUP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Event code 109 (KEY_PAGEDOWN)
Event code 119 (KEY_PAUSE)
Event code 168 (KEY_REWIND)
Event code 208 (KEY_FASTFORWARD)
Event code 226 (KEY_MEDIA)
Event code 407 (KEY_NEXT)
Event code 412 (KEY_PREVIOUS)
Event type 2 (EV_REL)
Event code 0 (REL_X)
Event code 1 (REL_Y)
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Key repeat handling:
Repeat type 20 (EV_REP)
Repeat code 0 (REP_DELAY)
Value 500
Repeat code 1 (REP_PERIOD)
Value 250
Properties:
Property type 5 (INPUT_PROP_POINTING_STICK)
Testing … (interrupt to exit)
Event: time 1611415415.123893, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f041f
Event: time 1611415415.123893, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1611415415.123893, -------------- SYN_REPORT ------------
Event: time 1611415415.227368, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f041f
Event: time 1611415415.227368, -------------- SYN_REPORT ------------
Event: time 1611415415.328677, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f041f
Event: time 1611415415.328677, -------------- SYN_REPORT ------------
Event: time 1611415415.446072, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1611415415.446072, -------------- SYN_REPORT ------------
Event: time 1611415415.484942, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f041f
Event: time 1611415415.484942, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1611415415.484942, -------------- SYN_REPORT ------------
Event: time 1611415415.602703, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1611415415.602703, -------------- SYN_REPORT ------------

Time between 2 presses is still around 125ms. What I am doing wrong ?

uname -r

5.10.2-2-MANJARO

Interesting side effect… Since i have cir issues my system is also more responsive! :slight_smile:
i guess this is no coincidence.

Any help would be nice :grin:

Greetings
Sebastian