[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD=FV=UQzM=cEsEYbR4QwaovT377dn4vLxqcK7xrLMutZPVDeQ@mail.gmail.com>
Date: Thu, 27 May 2021 16:14:17 -0700
From: Doug Anderson <dianders@...omium.org>
To: Krishna Manikandan <mkrishn@...eaurora.org>
Cc: dri-devel <dri-devel@...ts.freedesktop.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
freedreno <freedreno@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>,
Rob Clark <robdclark@...il.com>,
Sean Paul <seanpaul@...omium.org>,
Kalyan Thota <kalyan_t@...eaurora.org>,
Stephen Boyd <swboyd@...omium.org>
Subject: Re: [v1] drm/msm/disp/dpu1: avoid perf update in frame done event
Hi,
On Wed, May 26, 2021 at 10:08 PM Krishna Manikandan
<mkrishn@...eaurora.org> wrote:
>
> Crtc perf update from frame event work can result in
> wrong bandwidth and clock update from dpu if the work
> is scheduled after the swap state has happened.
>
> Avoid such issues by moving perf update to complete
> commit once the frame is accepted by the hardware.
>
> Fixes: a29c8c024165 ("drm/msm/disp/dpu1: fix display underruns during modeset")
> Signed-off-by: Krishna Manikandan <mkrishn@...eaurora.org>
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
I don't know much about this code or any of the theory behind it, but
I can confirm that this fixes the hang I was seeing with the previous
patch. On sc7180-trogdor-lazor:
Tested-by: Douglas Anderson <dianders@...omium.org>
Powered by blists - more mailing lists