[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <chznjpcx6p2vn3i5jt52peikhipzjiwzlr74gx6mzp3wjstr6p@6zhhknnl3zek>
Date: Fri, 4 Jul 2025 00:27:43 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Andy Yan <andyshrk@....com>
Cc: mripard@...nel.org, neil.armstrong@...aro.org,
dri-devel@...ts.freedesktop.org, dianders@...omium.org,
jani.nikula@...el.com, lyude@...hat.com, jonathanh@...dia.com,
p.zabel@...gutronix.de, simona@...ll.ch, victor.liu@....com,
rfoss@...nel.org, chunkuang.hu@...nel.org,
cristian.ciocaltea@...labora.com, Laurent.pinchart@...asonboard.com,
linux-arm-msm@...r.kernel.org, linux-mediatek@...ts.infradead.org,
linux-kernel@...r.kernel.org, freedreno@...ts.freedesktop.org,
Andy Yan <andy.yan@...k-chips.com>
Subject: Re: [PATCH v3 2/2] drm/bridge: Pass down connector to drm bridge
detect hook
On Thu, Jul 03, 2025 at 08:49:53PM +0800, Andy Yan wrote:
> From: Andy Yan <andy.yan@...k-chips.com>
>
> In some application scenarios, we hope to get the corresponding
> connector when the bridge's detect hook is invoked.
>
> In most cases, we can get the connector by drm_atomic_get_connector_for_encoder
> if the encoder attached to the bridge is enabled, however there will
> still be some scenarios where the detect hook of the bridge is called
> but the corresponding encoder has not been enabled yet. For instance,
> this occurs when the device is hot plug in for the first time.
>
> Since the call to bridge's detect is initiated by the connector, passing
> down the corresponding connector directly will make things simpler.
>
> Signed-off-by: Andy Yan <andy.yan@...k-chips.com>
> ---
>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
--
With best wishes
Dmitry
Powered by blists - more mailing lists