Re: [PATCH][I2C] Marvell mv64xxx i2c driver
From: Mark A. Greer
Date: Thu Feb 03 2005 - 19:08:05 EST
Alexey Dobriyan wrote:
On Thursday 03 February 2005 21:12, Mark A. Greer wrote:
+ mv64xxx_i2c_fsm(drv_data, status);
It can set drv_data->rc to -ENODEV or -EIO. In both cases ->action goes to
MV64XXX_I2C_ACTION_SEND_STOP and mv64xxx_i2c_do_action() will writel()
something. Is it correct to _not_ check ->rc here?
I think so. It still needs to go into do_action even when rc != 0 (in
which case it'll do a STOP condition).
Ok. Thanks for the explanation. Agree, ->rc should be left as is.
Okay.
--- a/include/linux/i2c-id.h
+++ b/include/linux/i2c-id.h
+ /* 0x170000 - USB */
+ /* 0x180000 - Virtual buses */
+#define I2C_ALGO_MV64XXX 0x190000 /* Marvell mv64xxx i2c ctlr */
While I searched for typos and you're fixing them, au1550 owned 0x170000.
2.6.11-rc3 says:
#define I2C_ALGO_AU1550 0x170000 /* Au1550 PSC algorithm */
So, I'd remove first two comments.
I added the comments b/c of this email from Jean Delvare,
http://www.uwsg.iu.edu/hypermail/linux/kernel/0501.3/0977.html. The
relevant part being:
"0x170000 is reserved within the legacy i2c project for an USB algorithm,
and 0x180000 for virtual busses. Could you please use 0x190000 instead,
so as to avoid future collisions?"
It looks like I2C_ALGO_AU1550 was just added so my guess is Jean is
correct and I2C_ALGO_AU1550 should be made 0x1a0000 (or I move mine back
one). Would someone confirm that 0x170000 is used by legacy i2c stuffs?
I don't really know where to look. If so, I can easily make a patch
moving it back.
Oh, and the last note: current sparse and gcc 4 don't produce any warnings.
Cool!
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/