summaryrefslogtreecommitdiff
path: root/drivers/i2c/muxes/i2c-mux-pca954x.c
diff options
context:
space:
mode:
authorChris Brandt <chris.brandt@renesas.com>2017-02-07 21:41:22 -0500
committerWolfram Sang <wsa@the-dreams.de>2017-02-09 17:43:31 +0100
commit71ccea095ea1d4efd004dab971be6d599e06fc3f (patch)
treee383f17ab4460be5eb9a82b0d9a2a24a1e85ced2 /drivers/i2c/muxes/i2c-mux-pca954x.c
parent9827f9eb79c56424eac6409197a290601cf78eee (diff)
i2c: riic: correctly finish transfers
This fixes the condition where the controller has not fully completed its final transfer and leaves the bus and controller in a undesirable state. At the end of the last transmitted byte, the existing driver would just signal for a STOP condition to be transmitted then immediately signal completion. However, the full STOP procedure might not have fully taken place by the time the runtime PM shuts off the peripheral clock, leaving the bus in a suspended state. Alternatively, the STOP condition on the bus may have completed, but when the next transaction is requested by the upper layer, not all the necessary register cleanup was finished from the last transfer which made the driver return BUS BUSY when it really wasn't. This patch now makes all transmit and receive transactions wait for the STOP condition to fully complete before signaling a completed transaction. With this new method, runtime PM no longer seems to be an issue. Fixes: 310c18a41450 ("i2c: riic: add driver") Signed-off-by: Chris Brandt <chris.brandt@renesas.com> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'drivers/i2c/muxes/i2c-mux-pca954x.c')
0 files changed, 0 insertions, 0 deletions