linux-kernel - Re:Re:Re: [PATCH 1/1] drm/bridge: Pass down connector to drm bridge detect hook

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20cd09da.5462.196a95cce13.Coremail.andyshrk@163.com>
Date: Wed, 7 May 2025 14:09:13 +0800 (CST)
From: "Andy Yan" <andyshrk@....com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@....qualcomm.com>,
	"Maxime Ripard" <mripard@...nel.org>
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:Re:Re: [PATCH 1/1] drm/bridge: Pass down connector to drm bridge
 detect hook



Ping......

At 2025-04-22 15:59:27, "Andy Yan" <andyshrk@....com> wrote:
>
>Hi all,
>
>At 2025-03-21 17:48:04, "Maxime Ripard" <mripard@...nel.org> wrote:
>>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.
>
>Can we start to review this patch? Since it's been almost a month now and
>no one has raised any objection to Dmitry's suggestion[1].
>
>
>[1]https://lore.kernel.org/dri-devel/vw2ncdomx3rwltb2xlo6nf3rapgcdtcjcodofgmecrzzabf7ji@pybsfv27jkq2/
>
>
>>
>>Maxime