Dear Tim Michals, [...] > > ~ # /i2cdetect.static -r 0 20 30 > > WARNING! This program can confuse your I2C bus, cause data loss and > > worse! I will probe file /dev/i2c-0 using read byte commands. > > I will probe address range 0x14-0x1e. > > Continue? [Y/n] > > > > 0 1 2 3 4 5 6 7 8 9 a b c d e f > > > > 00: > > 10: -- -- -- -- -- -- -- -- -- -- -- > > 20: > > 30: > > 40: > > 50: > > 60: > > 70: > > > > Best regards, > > Marek Vasut > > I'm using a imx233, I don't know what would be different or cause this > issue. The register layout differs. You might want to check if all the register programing is correct. Make sure the placement of various bits is correct. Also see how the DMA operates with the transfer length on MX23 and MX28 ... there are quite a few differences and I didn't test the driver on MX23 like that. I recall someone testing it on a different MX23 board but only by some "standard" usage. -- 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
