On 05/14/2016 04:30 AM, Crestez Dan Leonard wrote:
On 05/14/2016 03:38 AM, Guenter Roeck wrote:
On 05/13/2016 11:54 AM, Crestez Dan Leonard wrote:
This adds mode 'i' for I2C_SMBUS_I2C_BLOCK_DATA. This is the same mode
letter from i2cdump.
Length is optional and defaults to 32 (maximum).
The indended use is debugging i2c devices with shell commands.
How does this differ from the 'i' option of i2cdump ?
Apparently i2cdump doesn't support a range in "i" mode. I considered adding a range to i2cdump in all modes but:
- i2cdump code is a more complicated
Maybe, but it already supports the command.
- Not all devices interpret i2c bulk read as a register range. Reading X bytes from register Y can be different from reading registers from X to X+Y.
Not sure I understand what that has to do with supporting i2c block data.
Both commands call i2c_smbus_read_i2c_block_data(). Please explain.
Guenter
--
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
