[pvrusb2] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)

[Mike Isely]

On Sat, 25 Apr 2009, Martin Dauskardt wrote:

> Hi Mike,
> 
> first, thanks for fixing the bug with the wrong default values. It works now 
> fine.
> 
> I am using a 2.6.29 with a current v4l-dvb hg.
> 
> This is was dmesg reports:
> 
> [17051.484813] pvrusb2: Attached sub-driver saa7115
> [17051.500433] msp3400 0-0040: MSP3415G-B8 found @ 0x80 (pvrusb2_a)
> [17051.500436] msp3400 0-0040: msp3400 supports nicam and radio, mode is 
> autodetect and autoselect
> [17051.500484] pvrusb2: Attached sub-driver msp3400
> [17051.540421] tuner 0-0061: chip found @ 0xc2 (pvrusb2_a)
> [17051.540425] pvrusb2: Attached sub-driver tuner
> [17051.550529] tuner 0-0043: chip found @ 0x86 (pvrusb2_a)
> [17051.550609] tda9887 0-0043: creating new instance
> [17051.550611] tda9887 0-0043: tda988[5/6/7] found
> [17051.551055] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)

Martin:

I'm sorry I don't maintain tda9887 here.  It's obviously the source of 
the error message, but I don't know what it is trying to do.

Assuming that it is printing out a standard errno value, then I believe 
that would be -EIO which is what one would expect if there were a 
problem performing I2C I/O to the chip.  I would guess that the expected 
value corresponds to the number of bytes that should have been 
transferred.

It's possible that the tda9887 module is incorrectly detecting the chip 
(which would be on the I2C bus in your device, made available to v4l-dvb 
via the I2C adapter driver within the pvrusb2 driver).  But there are a 
lot of factors specific to the type of tuner module in use that factor 
into this.

If you don't see any outward problems then I would chalk this one up as 
benign.  For now...

  -Mike

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8