[i2c] [patch 3/3] i2c: add support for i2c bus on Freescale CPM1/CPM2 controllers
khali at linux-fr.org
Mon Jun 2 09:08:50 CEST 2008
On Sun, 1 Jun 2008 23:24:28 +0100, Ben Dooks wrote:
> On Mon, May 19, 2008 at 06:49:07PM +0200, Jean Delvare wrote:
> > Oh, BTW, nacks should be reported with -ENXIO according to:
> > http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/i2c-document-standard-fault-codes.patch
> > It might be worth checking that this new driver complies with these
> > freshly adopted error codes standard.
> Hmm, where ECONREFUSED or EPIPE (if NAK in already selected device)
There's no such thing as an "already selected device". The bus driver
doesn't know whether a given transaction is meant for probing purposes
(in which case a failure is more or less expected) or if it is a real
transaction. So it must either always log (which can spam the log) or
never log (which can cause some errors to go unnoticed.) Once a bus
driver returns proper error codes, I think that the best approach is to
not log anything (or only at debug level) on NAK and to let the chip
driver deal with the error.
As for the error code, it doesn't matter that much I think, as long as
it is consistent. We've settled for ENXIO and I wouldn't change this
now without a very good reason.
More information about the i2c