On Thu, Jan 03, 2013 at 01:16:57AM +0100, David Härdeman wrote: > On Wed, Oct 24, 2012 at 10:22:41PM +0100, Sean Young wrote: > >This is needed for carrier reporting. > > > >Signed-off-by: Sean Young <s...@mess.org> > >--- > > drivers/media/rc/winbond-cir.c | 14 +++++++++----- > > 1 file changed, 9 insertions(+), 5 deletions(-) > > Using a resolution of 2us rather than 10us means that the resolution > (and amount of work necessary for decoding a given signal) is about 25x > higher than in the windows driver (which uses a 50us resolution IIRC)... > > Most of it is mitigated by using RLE (which I don't think the windows > driver uses....again...IIRC), but it still seems unnecessary for the > general case.
You're right, the hardware will generate more data for 2us rather than 10us. For one key press on a nec remote, I get 69 interrupts before this patch and 302 after. That's almost 5 times as much, but not a ridiculous amount of work. > Wouldn't it be possible to only use the high-res mode when carrier > reports are actually enabled? That is possible, although is it really worth the effort? I'll have a look at implementing it and see what the code will look like. Sean -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
