Re: IR code autorepeat issue?

[Mauro Carvalho Chehab <mchehab@redhat.com>]

Em 29-08-2010 12:44, Mauro Carvalho Chehab escreveu:
> Em 29-08-2010 03:40, Anton Blanchard escreveu:
>>
>> I'm seeing double IR events on 2.6.36-rc2 and a DViCO FusionHDTV DVB-T Dual
>> Express.
> There's one issue on touching on this constant: it is currently just one global 
> timeout value that will be used by all protocols. This timeout should be enough to
> retrieve and proccess the repeat key event on all protocols, and on all devices, or 
> we'll need to do a per-protocol (and eventually per device) timeout init. From 
> http://www.sbprojects.com/knowledge/ir/ir.htm, we see that NEC prococol uses 110 ms
> for repeat code, and we need some aditional time to wake up the decoding task. I'd
> say that anything lower than 150-180ms would risk to not decode repeat events with
> NEC.
> 
> I got exactly the same problem when adding RC CORE support at the dib0700 driver. At
> that driver, there's an additional time of sending/receiving URB's from USB. So, we
> probably need a higher timeout. Even so, I tried to reduce the timeout to 200ms or 150ms 
> (not sure), but it didn't work. So, I ended by just patching the dibcom driver to do 
> dev->rep[REP_DELAY] = 500:

Ok, just sent a patch adding it to rc-core, and removing from dib0700 driver.

Cheers,
Mauro.