On Mon, 11 May 2009, ÒÁÔó wrote:
> 2009/5/11 Michael Abbott <michael@xxxxxxxxxxxxxxx>
> > Now this is very odd. I'd assumed the error messages I was getting were
> > just noise, but the commit you point me to uses KERN_ERR instead -- and so
> > I get a brief storm of these messages on boot on my target:
> >
> > [ 20.667923] i2c: error: exhausted retries
> > [ 20.671962] i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
> > [ 20.677113] i2c: ICR: 000007e0 ISR: 00000002
> > [ 20.677128] i2c: log: [00000446:000007e0]
> >
> > This is repeated nine times in total with exactly the same numbers. Any
> > thoughts as to what this means? Other than these messages on startup my
> > I2C sensors seem to work perfectly well.
> If all error messages seem like "exhausted retries",not "timeout or
> master error",there maybe some operation conflicts,and i2c controller
> cannot succeed operateing after max times retry. And which mode do
> your i2c work? Poll or Interrupt?
Well, to be honest I don't actually know (I've inherited the driver and I
haven't figured out how the I2C drivers work), but here's how the i2c is
initialised:
static struct i2c_pxa_platform_data xcep_i2c_platform_data = {
.class = I2C_CLASS_HWMON
};
...
pxa_set_i2c_info(&xcep_i2c_platform_data);
This is called in the .init_machine method, and the target system is a
PXA255.
However, after the error messages on startup, all the sensors seem to be
detected and seem to be operating normally.
