[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a40e7406-892b-f3be-f309-8857085ff3c5@codeaurora.org>
Date: Mon, 1 Jul 2019 12:39:49 -0600
From: Jeffrey Hugo <jhugo@...eaurora.org>
To: Rob Clark <robdclark@...il.com>, dri-devel@...ts.freedesktop.org,
linux-arm-msm@...r.kernel.org
Cc: freedreno@...ts.freedesktop.org, aarch64-laptops@...ts.linaro.org,
linux-clk@...r.kernel.org, linux-pm@...r.kernel.org,
Rob Clark <robdclark@...omium.org>,
Andrzej Hajda <a.hajda@...sung.com>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] drm/bridge: ti-sn65dsi86: support booloader enabled
display
On 6/30/2019 9:01 AM, Rob Clark wrote:
> From: Rob Clark <robdclark@...omium.org>
>
> Request the enable gpio ASIS to avoid disabling bridge during probe, if
> already enabled. And if already enabled, defer enabling runpm until
> attach to avoid cutting off the power to the bridge.
>
> Once we get to attach, we know panel and drm driver are probed
> successfully, so at this point it i s safe to enable runpm and reset the
is?
> bridge. If we do it earlier, we kill efifb (in the case that panel or
> drm driver do not probe successfully, giving the user no way to see what
> is going on.
Where should the missing ")" be?
Powered by blists - more mailing lists