On Sat, 2011-01-15 at 01:56 -0500, Jarod Wilson wrote: > On Jan 15, 2011, at 12:37 AM, Jarod Wilson wrote:
> >>>>>> Registered IR keymap rc-hauppauge-new > >>>>>> input: i2c IR (HD PVR) as /devices/virtual/rc/rc1/input6 > >>>>>> rc1: i2c IR (HD PVR) as /devices/virtual/rc/rc1 > >>>>>> ir-kbd-i2c: i2c IR (HD PVR) detected at i2c-1/1-0071/ir0 [Hauppage HD > >>>>>> PVR I2C] > Okay, last spam before I head off to bed... :) > > I can get ir-kbd-i2c behavior to pretty much match lirc_zilog wrt key repeat, > by simply setting init_data->polling_interval = 260; in hdpvr-i2c.c, which > matches up with the delay in lirc_zilog. With the 260 interval: RC-5 has a repetition interval of about 4096/36kHz = 113.8 ms, IIRC. Using 260 ms, you are throwing away one repeat from the remote for sure, maybe two. Maybe that will help you understand what may be going on. (I've lost the bubble on hdpvr with ir-kbd-i2c.) Regards, Andy > Event: time 1295072449.490542, -------------- Report Sync ------------ > Event: time 1295072453.321206, type 4 (Misc), code 4 (ScanCode), value 15 > Event: time 1295072453.321245, type 1 (Key), code 108 (Down), value 1 > Event: time 1295072453.321252, -------------- Report Sync ------------ > Event: time 1295072453.570512, type 1 (Key), code 108 (Down), value 0 > Event: time 1295072453.570544, -------------- Report Sync ------------ > Event: time 1295072453.575718, type 4 (Misc), code 4 (ScanCode), value 15 > Event: time 1295072453.575744, type 1 (Key), code 108 (Down), value 1 > Event: time 1295072453.575752, -------------- Report Sync ------------ > Event: time 1295072453.816215, type 4 (Misc), code 4 (ScanCode), value 15 > Event: time 1295072454.065515, type 1 (Key), code 108 (Down), value 0 > Event: time 1295072454.065544, -------------- Report Sync ------------ > > Lowering this a bit, I can get split personality, one press will look like > what I was originally seeing, another will look like the 260 output. > > Adding filtering (return 0 if buf[0] != 0x80) doesn't help any. > > The final thing I've noticed tonight is that ir-kbd-i2c calls rc_keydown > using a value of 0 for its 3rd parameter. From rc-main.c: > > * @toggle: the toggle value (protocol dependent, if the protocol doesn't > * support toggle values, this should be set to zero) > > Well, in this case, the protocol *does* use a toggle, so that's probably > something that could use fixing. Not sure it actually has anything to do with > the odd repeats I'm seeing. Okay, wasn't too much work to pass along toggle > values too, but it didn't help any. > > I'll sleep on it. -- 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
