diff options
author | Wolfram Sang <[email protected]> | 2024-07-07 10:28:47 +0200 |
---|---|---|
committer | Andi Shyti <[email protected]> | 2024-07-10 09:57:49 +0200 |
commit | 3291d2327e4f1e83f290c26ab7e9d17fd8e1bb2e (patch) | |
tree | 7251e84433397973b69dd368b9524576e3f663a0 | |
parent | 00fa2450c11138c1c3171224cd2727a3a6240bae (diff) |
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 <[email protected]>
Signed-off-by: Andi Shyti <[email protected]>
-rw-r--r-- | drivers/i2c/busses/i2c-rcar.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/i2c/busses/i2c-rcar.c b/drivers/i2c/busses/i2c-rcar.c index 828aa2ea0fe4..efa306076493 100644 --- 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) |