Hi,
Ben Dooks schrieb:
I have noticed the following behaviour with the i2c-rcar driver
with the following single i2c_msg structure:
msg[0].addr = 0x12;
msg[0].flags = I2C_M_RD;
msg[0].len = 0;
msg[0].buf = data;
isn't this illegal?
This should lead to 50% chance of blocked bus: After sending read-bit
the slave ACK's and puts first data bit onto SDL. If it is '0', master
won't be able to signal stop nor arbitrate the bus for other transaction
until slave runs into internal timeout (*if* supported).
Only 9 SCL toggles will be able to free bus again.
But maybe I'm missing something.
KR
Michael
--
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