Re: rcar-i2c: always reads a byte

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/03/14 16:41, Ben Dooks wrote:
On 11/03/14 16:40, Wolfram Sang wrote:
On Tue, Mar 11, 2014 at 04:15:02PM +0000, Ben Dooks wrote:
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;

The system issues an address transaction followed by a single byte
read.

This fits to my observation that the rcar driver cannot do SMBUS_QUICK
(e.g. via i2cdetect). I assumed that handling a length of 0 is broken. I
haven't had a deeper look yet, so I can't say much. So, you either go
for it yourself, or you wait until I posted my IIC enablement series for
Lager. Then, you can switch to the IIC core with the sh_mobile driver.
That one does SMBUS_QUICK correctly.

I'll have a deeper look into this, I think there may be a solution.

I've tried issuing the ESG + FSB  bits as a command, however that
did not work.

--
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius
--
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




[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux