Re: [RESEND PATCH] i2c: rk3x: Handle a spurious start completion interrupt flag

[RESEND PATCH] i2c: rk3x: Handle a spurious start completion interrupt flag · Ondrej Jirman <hidden> · 2021-09-24
Re: [RESEND PATCH] i2c: rk3x: Handle a spurious start completion interrupt flag · John Keeping <hidden> · 2021-11-18
Re: [RESEND PATCH] i2c: rk3x: Handle a spurious start completion interrupt flag · Wolfram Sang <wsa@kernel.org> · 2021-11-29
Re: [RESEND PATCH] i2c: rk3x: Handle a spurious start completion interrupt flag · Ondřej Jirman <hidden> · 2021-11-30
Re: [RESEND PATCH] i2c: rk3x: Handle a spurious start completion interrupt flag · Wolfram Sang <wsa@kernel.org> · 2021-11-30
Re: [RESEND PATCH] i2c: rk3x: Handle a spurious start completion interrupt flag · Wolfram Sang <wsa@kernel.org> · 2021-11-30

From: Wolfram Sang <wsa@kernel.org>
Date: 2021-11-29 09:58:12
Also in: linux-i2c, linux-rockchip, lkml

This causes I2C transfer being aborted in polled mode from a stop completion
handler:

I wonder why this only happens in polling mode? The question behind that
is: is it really a spurious irq from the HW or is it maybe a race in the
driver? Because polling uses the same interrupt handler but just
periodically polls it.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help