mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-29 16:10:58 +00:00
92c23c9226
Writing zero into I2Ci.I2C_CNT register causes random I2C failures in OMAP3 based devices. This seems to be related to the following advisory which apears in multiple erratas for OMAP3 SoCs (OMAP35xx, DM37xx), as well as OMAP4430 TRM: Advisory: I2C Module Does Not Allow 0-Byte Data Requests Details: When configured as the master, the I2C module does not allow 0-byte data transfers. Note: Programming I2Ci.I2C_CNT[15:0]: DCOUNT = 0 will cause undefined behavior. Workaround(s): No workaround. Do not use 0-byte data requests. The writes in question are unnecessary from a functional point of view. Most of them are done after I/O has finished, and the only one that preceds I/O (in i2c_probe()) is also unnecessary because a stop bit is sent before actual data transmission takes place. Therefore, remove all writes that zero the cnt register. Cc: Heiko Schocher <hs@denx.de> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Tom Rini <trini@ti.com> Cc: Lubomir Popov <lpopov@mm-sol.com> Cc: Enric Balletbo Serra <eballetbo@gmail.com> Signed-off-by: Nikita Kiryanov <nikita@compulab.co.il> Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: Lubomir Popov <lpopov@mm-sol.com> |
||
|---|---|---|
| .. | ||
| bfin-twi_i2c.c | ||
| davinci_i2c.c | ||
| designware_i2c.c | ||
| designware_i2c.h | ||
| fsl_i2c.c | ||
| fti2c010.c | ||
| fti2c010.h | ||
| i2c_core.c | ||
| Makefile | ||
| mv_i2c.c | ||
| mv_i2c.h | ||
| mvtwsi.c | ||
| mxc_i2c.c | ||
| mxs_i2c.c | ||
| omap24xx_i2c.c | ||
| omap24xx_i2c.h | ||
| pca9564_i2c.c | ||
| ppc4xx_i2c.c | ||
| rcar_i2c.c | ||
| s3c24x0_i2c.c | ||
| s3c24x0_i2c.h | ||
| sh_i2c.c | ||
| sh_sh7734_i2c.c | ||
| soft_i2c.c | ||
| tegra_i2c.c | ||
| tsi108_i2c.c | ||
| u8500_i2c.c | ||
| u8500_i2c.h | ||
| zynq_i2c.c | ||