i2c: rcar: WARN about spurious irqs

The FIXME is very old and probably needed because of some driver bug
like insufficient initialization. It may well be that it was fixed
meanwhile but we never know because the spurious irq is silently
ignored. Add now a call trace when this happens so we have more
information in case the issue still exists.

Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Signed-off-by: Andi Shyti <andi.shyti@kernel.org>

diff --git a/drivers/i2c/busses/i2c-rcar.c b/drivers/i2c/busses/i2c-rcar.c
index 828aa2ea0fe4c90785cbdc5e65b5b28cdf86b40b..efa30607649307f3b0bc03125ec9d0a2bca015ee 100644 (file)
--- a/drivers/i2c/busses/i2c-rcar.c
+++ b/drivers/i2c/busses/i2c-rcar.c
@@ -545,7 +545,7 @@ static void rcar_i2c_irq_send(struct rcar_i2c_priv *priv, u32 msr)
        u32 irqs_to_clear = MDE;
 
        /* FIXME: sometimes, unknown interrupt happened. Do nothing */
-       if (!(msr & MDE))
+       if (WARN(!(msr & MDE), "spurious irq"))
                return;
 
        if (msr & MAT)