In commit 53cb55b20208 ("drm/lima: handle spurious timeouts due to high
irq latency") a check was added to detect an unexpectedly high interrupt
latency timeout.
With further investigation it was noted that on Mali-450 the pp bcast
irq may also be a trigger of race conditions against the timeout
handler, so add it to this check too.

Signed-off-by: Erico Nunes <nunes.er...@gmail.com>
---
 drivers/gpu/drm/lima/lima_sched.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/lima/lima_sched.c 
b/drivers/gpu/drm/lima/lima_sched.c
index 00b19adfc888..66841503a618 100644
--- a/drivers/gpu/drm/lima/lima_sched.c
+++ b/drivers/gpu/drm/lima/lima_sched.c
@@ -422,6 +422,8 @@ static enum drm_gpu_sched_stat 
lima_sched_timedout_job(struct drm_sched_job *job
         */
        for (i = 0; i < pipe->num_processor; i++)
                synchronize_irq(pipe->processor[i]->irq);
+       if (pipe->bcast_processor)
+               synchronize_irq(pipe->bcast_processor->irq);
 
        if (dma_fence_is_signaled(task->fence)) {
                DRM_WARN("%s unexpectedly high interrupt latency\n", 
lima_ip_name(ip));
-- 
2.44.0

Reply via email to