[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACvgo50eb5_jp_6B5tkV9cX_X2_y2Xnavu+wvUUhHN5FsV9hiw@mail.gmail.com>
Date: Tue, 2 Jun 2020 15:13:10 +0100
From: Emil Velikov <emil.l.velikov@...il.com>
To: Krishna Manikandan <mkrishn@...eaurora.org>
Cc: ML dri-devel <dri-devel@...ts.freedesktop.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
freedreno@...ts.freedesktop.org,
devicetree <devicetree@...r.kernel.org>,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Sean Paul <seanpaul@...omium.org>, kalyan_t@...eaurora.org,
"Kristian H . Kristensen" <hoegsberg@...omium.org>,
mka@...omium.org
Subject: Re: [v2] drm/msm: add shutdown support for display platform_driver
Hi Krishna,
On Tue, 2 Jun 2020 at 08:17, Krishna Manikandan <mkrishn@...eaurora.org> wrote:
>
> Define shutdown callback for display drm driver,
> so as to disable all the CRTCS when shutdown
> notification is received by the driver.
>
> This change will turn off the timing engine so
> that no display transactions are requested
> while mmu translations are getting disabled
> during reboot sequence.
>
> Signed-off-by: Krishna Manikandan <mkrishn@...eaurora.org>
>
AFAICT atomics is setup in msm_drm_ops::bind and shutdown in
msm_drm_ops::unbind.
Are you saying that unbind never triggers? If so, then we should
really fix that instead, since this patch seems more like a
workaround.
-Emil
Powered by blists - more mailing lists