[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241012150710.261767-1-devarsht@ti.com>
Date: Sat, 12 Oct 2024 20:37:08 +0530
From: Devarsh Thakkar <devarsht@...com>
To: <jyri.sarha@....fi>, <tomi.valkeinen@...asonboard.com>,
<airlied@...il.com>, <maarten.lankhorst@...ux.intel.com>,
<mripard@...nel.org>, <tzimmermann@...e.de>,
<dri-devel@...ts.freedesktop.org>, <simona@...ll.ch>,
<linux-kernel@...r.kernel.org>
CC: <praneeth@...com>, <vigneshr@...com>, <aradhya.bhatia@...ux.dev>,
<s-jain1@...com>, <r-donadkar@...com>, <sam@...nborg.org>,
<bparrot@...com>, <jcormier@...ticallink.com>, <devarsht@...com>
Subject: [PATCH 0/2] DSS interrupt related bug fixes
While reviewing the interrupt related code and register dump, we found couple
of issues related to interrupt related register programming. Firstly, the
function enabling/disabling the interrupts was trying to clear the
interrupts which were not enabled in first place and secondly there is a
potential race scenario between interrupt subroutine and interrupt
enable/disable related functions as they both access interrupt registers
without a common lock. This series addresses the aforementioned problems.
Devarsh Thakkar (2):
drm/tidss: Clear the interrupt status for interrupts being disabled
drm/tidss: Avoid race condition while handling interrupt registers
drivers/gpu/drm/tidss/tidss_dispc.c | 12 ++++++++----
drivers/gpu/drm/tidss/tidss_irq.c | 2 ++
2 files changed, 10 insertions(+), 4 deletions(-)
--
2.39.1
Powered by blists - more mailing lists