[PATCH v2] media: aspeed-video: ignore interrupts that aren't enabled
Zev Weiss
zev at bewilderbeest.net
Fri May 7 09:40:48 AEST 2021
As partially addressed in commit 65d270acb2d6, the ASpeed video engine
sometimes asserts interrupts that the driver hasn't enabled. In
addition to the CAPTURE_COMPLETE and FRAME_COMPLETE interrupts
addressed in that patch, COMP_READY has also been observed. Instead
of playing whack-a-mole with each one individually, we can instead
just blanket ignore everything we haven't explicitly enabled.
Signed-off-by: Zev Weiss <zev at bewilderbeest.net>
---
Changes since v1 [0]:
- dropped error message
- switched to a blanket-ignore approach as suggested by Ryan
[0] https://lore.kernel.org/linux-arm-kernel/20201215024542.18888-1-zev@bewilderbeest.net/
drivers/media/platform/aspeed-video.c | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/media/platform/aspeed-video.c b/drivers/media/platform/aspeed-video.c
index 7bb6babdcade..77611c296a25 100644
--- a/drivers/media/platform/aspeed-video.c
+++ b/drivers/media/platform/aspeed-video.c
@@ -563,6 +563,12 @@ static irqreturn_t aspeed_video_irq(int irq, void *arg)
struct aspeed_video *video = arg;
u32 sts = aspeed_video_read(video, VE_INTERRUPT_STATUS);
+ /*
+ * Hardware sometimes asserts interrupts that we haven't actually
+ * enabled; ignore them if so.
+ */
+ sts &= aspeed_video_read(video, VE_INTERRUPT_CTRL);
+
/*
* Resolution changed or signal was lost; reset the engine and
* re-initialize
@@ -629,16 +635,6 @@ static irqreturn_t aspeed_video_irq(int irq, void *arg)
aspeed_video_start_frame(video);
}
- /*
- * CAPTURE_COMPLETE and FRAME_COMPLETE interrupts come even when these
- * are disabled in the VE_INTERRUPT_CTRL register so clear them to
- * prevent unnecessary interrupt calls.
- */
- if (sts & VE_INTERRUPT_CAPTURE_COMPLETE)
- sts &= ~VE_INTERRUPT_CAPTURE_COMPLETE;
- if (sts & VE_INTERRUPT_FRAME_COMPLETE)
- sts &= ~VE_INTERRUPT_FRAME_COMPLETE;
-
return sts ? IRQ_NONE : IRQ_HANDLED;
}
--
2.31.1
More information about the openbmc
mailing list