Hi
Is this the right list to discuss the i2c-tools user space software? If
not, please disregard this email.
I have noticed that I can't seem to be able to use these tools out of
box for very many i2c devices, as the i2cget/i2cset isn't using a very
common protocol that these chips use.
E.g. the protocol for byte/word read (which is also found in the SMBUS
spec) is:
START - WR:SLAVE - DADR - START - RD:SLAVE - DATA - STOP
From what I have tested, it seems "i2cget BUS SLAVE DADR" does the
following
START - WR:SLAVE - DADR - START - RD:SLAVE - DADR - DATA - STOP
It contains an extra read DADR byte, which is the slot where the actual
data is being returned.
(My workaround is to run "i2cset BUS SLAVE CMD; i2cget BUS SLAVE")
Is this something that patches will be accepted for?
Best regards,
sveinse
--
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
