diff options
| author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-05-11 22:36:47 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-05-20 20:25:06 -0300 |
| commit | ca540c8b66874aaf704c64d43d33e39369c428fb (patch) | |
| tree | f45895fb75d80dee42d69d3349b36e265c976a99 /drivers | |
| parent | 612031c0771def54dd202cef76bb9bd654e47b5b (diff) | |
[media] Use a more consistent value for RC repeat period
The default REP_PERIOD is 33 ms. This doesn't make sense for IR's,
as, in general, an IR repeat scancode is provided at every 110/115ms,
depending on the RC protocol. So, increase its default, to do a
better job avoiding ghost repeat events.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Jarod Wilson <jarod@redhat.com>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/media/rc/rc-main.c | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c index 0d4fcd911b8..f57cd5677ac 100644 --- a/drivers/media/rc/rc-main.c +++ b/drivers/media/rc/rc-main.c @@ -1078,6 +1078,13 @@ int rc_register_device(struct rc_dev *dev) */ dev->input_dev->rep[REP_DELAY] = 500; + /* + * As a repeat event on protocols like RC-5 and NEC take as long as + * 110/114ms, using 33ms as a repeat period is not the right thing + * to do. + */ + dev->input_dev->rep[REP_PERIOD] = 125; + path = kobject_get_path(&dev->dev.kobj, GFP_KERNEL); printk(KERN_INFO "%s: %s as %s\n", dev_name(&dev->dev), |