Tim, On Mon, Nov 19, 2012 at 1:05 PM, Tim Michals <tcmichals@xxxxxxxxx> wrote: > I tested both patches using Linux version 3.7.0-rc4 with the following > command: > # i2cdetect -r 0 20 30 > Usage: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST] > i2cdetect -F I2CBUS > i2cdetect -l > I2CBUS is an integer or an I2C bus name > If provided, FIRST and LAST limit the probing range. > # i2cdetect -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] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: > 10: -- [ 31.830000] mxs-i2c 80058000.i2c: Failed to get PIO > reg. . > -- -- [ 32.830000] mxs-i2c 80058000.i2c: Failed to get PIO reg. write > descrip. > -- -- [ 33.830000] mxs-i2c 80058000.i2c: Failed to get PIO reg. write > descrip. > -- -- [ 34.830000] mxs-i2c 80058000.i2c: Failed to get PIO reg. write > descrip. > -- -- [ 35.830000] mxs-i2c 80058000.i2c: Failed to get PIO reg. write > descrip. Which I2C device you have in the bus? Can you share your dts? Regards, Fabio Estevam -- 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
