Re: [Gumstix-users] Touchscreen driver TSC2003 i2c timeout

[Dave H. <dhy...@gm...>]

Hi Steve,

> For some reason though, the driver does something that wedges the i2c
> driver or hardware after that initial probe.   That is when you are
> seeing the error messages from the i2c driver.  The i2c command line
> program also fails after that point when it attempts to do an ioctl(
> i2cDev, I2C_SLAVE, gI2cAddr ).  It reports an error of:
>
> ERROR: I2cSetSlaveAddress: Error trying to set slave address to 0x48
> (16 Device or resource busy)

I think this happens when the touch screen registers a proper i2c
driver. There are two modes of using the i2c stuff.

The first, which is used by the i2c program, is to use the i2cdev
interface. This is really a bus level interface.

The second method, is that a particular driver registers itself as an
i2c device. In this case it normally creates a /dev entry that then
takes care of doing all of the i2c transactions, in effect, claiming
that particular device as its own.

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/