On Mon, Oct 05, 2009 at 11:04:02AM +0200, Jean Delvare wrote: > On Mon, 5 Oct 2009 11:50:31 +0300, Aleksandr V. Piskunov wrote: > > > Try: > > > > > > # modprobe ivtv newi2c=1 > > > > > > to see if that works first. > > > > > > > udelay=10, newi2c=0 => BAD > > udelay=10, newi2c=1 => BAD > > udelay=5, newi2c=0 => OK > > udelay=5, newi2c=1 => BAD > > The udelay value is only used by i2c-algo-bit, not newi2c, so the last > test was not needed. > Yup, also tried udelay=4, IR controller handles it without problems, though cx25840 and xc2028 doesn't seem to like the 125 KHz frequency, refusing to communicate. xc2028 even stopped responding, requiring a cold reboot. So for M116 board, the most stable combination seems to be 100 KHz i2c bus and 150ms polling delay (up from 100 default). With this combination I can quickly press 1234567890 on remote and driver gets the combination without any losses. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
