Re: [PATCH 1/3] i2c_intel_mid: Improve error reporting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 27 Jan 2011 00:44:23 +0000
Ben Dooks <ben-i2c@xxxxxxxxx> wrote:

> On Tue, Jan 25, 2011 at 02:20:48PM +0000, Alan Cox wrote:
> > From: Catalin Popescu <catalinx.popescu@xxxxxxxxx>
> > 
> > The error messages printed from mrst_i2c_abort() didn't give slave address info.
> > 
> > But I2C device driver developers always need this to check which slave device
> > has the problem.
> 
> Erm, surely the driver itself should know what i2c device it is communicating
> with? Secondly, does this swamp the kernel dmesg buffer when run with the

It lets you see what is going on if you need to and stuff is misbehaving
- its a debug aid.

> i2c-detect tool?

Only if you turn all the debug on and do that which presumably is when
you want it. Not that you would as on these platforms the i2c bus
configuration is enumerated in a firmware table.


--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux