[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250321-optimistic-prompt-civet-bdcdba@houat>
Date: Fri, 21 Mar 2025 10:48:04 +0100
From: Maxime Ripard <mripard@...nel.org>
To: Andy Yan <andyshrk@....com>
Cc: lumag@...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 1/1] drm/bridge: Pass down connector to drm bridge detect
hook
On Fri, Mar 21, 2025 at 04:53:38PM +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>
FTR, I'm against it and would have appreciated that you wait for a
meaningful closure to the discussion we've had on this.
Maxime
Download attachment "signature.asc" of type "application/pgp-signature" (274 bytes)
Powered by blists - more mailing lists