* Alexander Kochetkov al.koc...@gmail.com [141128 15:27]:
Hello, Tony!
I just want to know, is multimaster i2c feature is interesting for TI SOC,
so I could send another patches?
Sure and thanks for looking into fixing things.
Or it's better to leave the thing without changes, as current
* Kevin Hilman khil...@kernel.org [141126 13:27]:
Alexander Kochetkov al.koc...@gmail.com writes:
NOT FOR UPSTREAM
The patch checks if IP reset during probe could bring I2C bus
to a free state on omap2430 - omap3530 boards.
I guess, IP hold one of I2C lines in a low state.
I
Hello, Tony!
I just want to know, is multimaster i2c feature is interesting for TI SOC,
so I could send another patches?
Or it's better to leave the thing without changes, as current single master
version
well tested and work?
Also I have a draft version of mixed multimaster/slave version. But
29 нояб. 2014 г., в 1:13, Tony Lindgren t...@atomide.com написал(а):
Looks like for some time 2430 i2c has not been behaving
reliably
commit dd74548ddece4b9d68e5528287a272fa552c81d0 (i2c: omap:
resize fifos before each message) dropped check for dev-buf_len.
As result, data
NOT FOR UPSTREAM
The patch checks if IP reset during probe could bring I2C bus
to a free state on omap2430 - omap3530 boards.
I guess, IP hold one of I2C lines in a low state.
I guess, u-boot haven't sent a stop condition.
The patch is rebased on branch 'i2c/for-next' of
Alexander Kochetkov al.koc...@gmail.com writes:
NOT FOR UPSTREAM
The patch checks if IP reset during probe could bring I2C bus
to a free state on omap2430 - omap3530 boards.
I guess, IP hold one of I2C lines in a low state.
I guess, u-boot haven't sent a stop condition.
The patch is