i2c: rcar: fix MNR interrupt handling
authorSergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Mon, 1 Sep 2014 21:15:26 +0000 (01:15 +0400)
committerSimon Horman <horms@verge.net.au>
Fri, 5 Dec 2014 00:25:20 +0000 (09:25 +0900)
commit44af3867589b94c9005f94b3360a2587cd5ddc28
treeea77890efe926959300bc9664bc39c55755eb49c
parentd48d837e320b2956b82398d8d54eecaaa5f1b41c
i2c: rcar: fix MNR interrupt handling

Sometimes the MNR and MST interrupts happen simultaneously  (stop  automatically
follows NACK, according to the manuals) and in such case the ID_NACK flag  isn't
set since the MST interrupt handling precedes MNR and all interrupts are cleared
and disabled then, so that MNR interrupt is never noticed -- this causes NACK'ed
transfers to be falsely reported as successful. Exchanging MNR and  MST handlers
fixes this issue, however the MNR bit  somehow  gets set again even after  being
explicitly cleared, so I decided to completely suppress handling of all disabled
interrupts (which is a good thing anyway)...

Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: stable@vger.kernel.org
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
(cherry picked from commit dd318b0df27c582ac0d72a346fd6e693700be23c)
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
drivers/i2c/busses/i2c-rcar.c