From: "Andy Yan" <andyshrk@163.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Maxime Ripard" <mripard@kernel.org>
Cc: lumag@kernel.org, neil.armstrong@linaro.org,
dri-devel@lists.freedesktop.org, dianders@chromium.org,
jani.nikula@intel.com, lyude@redhat.com, jonathanh@nvidia.com,
p.zabel@pengutronix.de, simona@ffwll.ch, victor.liu@nxp.com,
rfoss@kernel.org, chunkuang.hu@kernel.org,
cristian.ciocaltea@collabora.com,
Laurent.pinchart@ideasonboard.com, linux-arm-msm@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
freedreno@lists.freedesktop.org,
"Andy Yan" <andy.yan@rock-chips.com>
Subject: Re:Re:Re: [PATCH 1/1] drm/bridge: Pass down connector to drm bridge detect hook
Date: Wed, 7 May 2025 14:09:13 +0800 (CST) [thread overview]
Message-ID: <20cd09da.5462.196a95cce13.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <1bb549f4.746e.1965c8256e4.Coremail.andyshrk@163.com>
Ping......
At 2025-04-22 15:59:27, "Andy Yan" <andyshrk@163.com> wrote:
>
>Hi all,
>
>At 2025-03-21 17:48:04, "Maxime Ripard" <mripard@kernel.org> wrote:
>>On Fri, Mar 21, 2025 at 04:53:38PM +0800, Andy Yan wrote:
>>> From: Andy Yan <andy.yan@rock-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@rock-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
prev parent reply other threads:[~2025-05-07 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 8:53 [PATCH 0/1] Pass down connector to drm bridge detect hook Andy Yan
2025-03-21 8:53 ` [PATCH 1/1] drm/bridge: " Andy Yan
2025-03-21 9:48 ` Maxime Ripard
2025-03-21 10:05 ` Andy Yan
2025-04-22 7:59 ` Andy Yan
2025-05-07 6:09 ` Andy Yan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20cd09da.5462.196a95cce13.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andy.yan@rock-chips.com \
--cc=chunkuang.hu@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lumag@kernel.org \
--cc=lyude@redhat.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=victor.liu@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox