> Actually, scanning i2c_init shows what looks to be a problem.
>
> 235 static int omap_i2c_init(struct omap_i2c_dev *dev)
> 236 {
> 237 u16 psc = 0, scll = 0, sclh = 0;
> 238 u16 fsscll = 0, fssclh = 0, hsscll = 0, hssclh = 0;
> 239 unsigned long fclk_rate = 12000000;
> 240 unsigned long timeout;
> 241 unsigned long internal_clk = 0;
> 242
> 243 if (!dev->rev1) {
> 244 omap_i2c_write_reg(dev, OMAP_I2C_SYSC_REG,
> OMAP_I2C_SYSC_SRST);
>
> None of the module local OCP registers are being setup properly. A
> write of a 0x2 kills other settings. If after this operation the SSYC
> reg will say:
> -Forced Idle
> -Locally gate I+F clock on ocp-segment idle request
> -wake up disabled
BTW, I see these settings are correct in Zoom tree in clock functions.
http://git.omapzoom.org/?p=omapkernel;a=blob;f=drivers/i2c/busses/i2c-omap.c;hb=d0b4bad4926f9a147a73498f7a62a0ae1cf6f83a
Regards,
Richard W.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
