diff options
| author | Chris Packham <chris.packham@alliedtelesis.co.nz> | 2020-07-02 10:39:11 +1200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-07-09 09:37:11 +0200 |
| commit | c6b239e3fef600a04d1cb20d8c73447003e21edd (patch) | |
| tree | 34c8b47ff9e73bc57d5775bd1f7a8a5ba7273442 /drivers/i2c/busses | |
| parent | 5f7d0fddff15a2fffa1fa2007eef42e160813062 (diff) | |
| download | linux-stable-c6b239e3fef600a04d1cb20d8c73447003e21edd.tar.gz linux-stable-c6b239e3fef600a04d1cb20d8c73447003e21edd.tar.bz2 linux-stable-c6b239e3fef600a04d1cb20d8c73447003e21edd.zip | |
i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
[ Upstream commit cd217f2300793a106b49c7dfcbfb26e348bc7593 ]
The PCA9665 datasheet says that I2CSTA = 78h indicates that SCL is stuck
low, this differs to the PCA9564 which uses 90h for this indication.
Treat either 0x78 or 0x90 as an indication that the SCL line is stuck.
Based on looking through the PCA9564 and PCA9665 datasheets this should
be safe for both chips. The PCA9564 should not return 0x78 for any valid
state and the PCA9665 should not return 0x90.
Fixes: eff9ec95efaa ("i2c-algo-pca: Add PCA9665 support")
Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/i2c/busses')
0 files changed, 0 insertions, 0 deletions