summaryrefslogtreecommitdiff
path: root/drivers/i2c/pca9564_i2c.c
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2014-06-25 10:57:27 -0600
committerHeiko Schocher <hs@denx.de>2014-07-03 06:29:19 +0200
commit68049a082b8aedf09e769e61885e000e598bb516 (patch)
tree26780e2fead018bee3b9e1d9a9f25f41e47d401a /drivers/i2c/pca9564_i2c.c
parentfe8b3212b7938861eacdefe6115810303a96f9cc (diff)
downloadu-boot-imx-68049a082b8aedf09e769e61885e000e598bb516.zip
u-boot-imx-68049a082b8aedf09e769e61885e000e598bb516.tar.gz
u-boot-imx-68049a082b8aedf09e769e61885e000e598bb516.tar.bz2
i2c: tegra: use repeated start for reads
I2C read transactions are typically implemented as follows: START(write) address REPEATED_START(read) data... STOP However, Tegra's I2C driver currently implements reads as follows: START(write) address STOP START(read) data... STOP This sequence confuses at least the AS3722 PMIC on the Jetson TK1 board, leading to corrupted read data in some cases. Fix the driver to chain the transactions together using repeated starts to solve this. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Yen Lin <yelin@nvidia.com>
Diffstat (limited to 'drivers/i2c/pca9564_i2c.c')
0 files changed, 0 insertions, 0 deletions