From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Sam Ravnborg <sam@ravnborg.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Yongxing Mou <yongxing.mou@oss.qualcomm.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/bridge: display-connector: trigger initial HPD event for DP
Date: Wed, 18 Mar 2026 19:40:00 +0200 [thread overview]
Message-ID: <20260318174000.GK633439@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20260314-dp-connector-hpd-v1-2-786044cedc17@oss.qualcomm.com>
Hi Dmitry,
Thank you for the patch.
On Sat, Mar 14, 2026 at 02:43:12AM +0200, Dmitry Baryshkov wrote:
> If the DisplayPort drivers use display-connector for the HPD detection,
> the internal HPD state machine might be not active and thus the hardware
> might be not able to handle cable detection correctly. Instead it will
> depend on the externall HPD notifications to set the cable state,
> bypassing the internal HPD state machine (for example this is the case
> for the msm DP driver).
>
> However if the cable has been plugged before the HPD IRQ has been
> enabled, there will be no HPD event coming. The drivers might fail
> detection in such a case. Trigger the HPD notification after enabling
> the HPD IRQ, propagating the cable insertion state.
The explanation makes sense, but it sounds like to could apply the same
way to HDMI. What am I missing ?
Also, wouldn't it be better if the DRM core interrogated the state of
the HPD signal when enabling HPD, instead of relying on all drivers to
implement something similar as this patch ?
> Fixes: 2e2bf3a5584d ("drm/bridge: display-connector: add DP support")
> Reported-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> drivers/gpu/drm/bridge/display-connector.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/gpu/drm/bridge/display-connector.c b/drivers/gpu/drm/bridge/display-connector.c
> index 6bb1134f75c3..f7a5bfd9c075 100644
> --- a/drivers/gpu/drm/bridge/display-connector.c
> +++ b/drivers/gpu/drm/bridge/display-connector.c
> @@ -12,6 +12,7 @@
> #include <linux/of.h>
> #include <linux/platform_device.h>
> #include <linux/regulator/consumer.h>
> +#include <linux/workqueue.h>
>
> #include <drm/drm_atomic_helper.h>
> #include <drm/drm_bridge.h>
> @@ -25,6 +26,8 @@ struct display_connector {
>
> struct regulator *supply;
> struct gpio_desc *ddc_en;
> +
> + struct work_struct hpd_work;
> };
>
> static inline struct display_connector *
> @@ -92,15 +95,29 @@ static void display_connector_hpd_enable(struct drm_bridge *bridge)
> struct display_connector *conn = to_display_connector(bridge);
>
> enable_irq(conn->hpd_irq);
> +
> + if (conn->bridge.type == DRM_MODE_CONNECTOR_DisplayPort)
> + schedule_work(&conn->hpd_work);
> }
>
> static void display_connector_hpd_disable(struct drm_bridge *bridge)
> {
> struct display_connector *conn = to_display_connector(bridge);
>
> + if (conn->bridge.type == DRM_MODE_CONNECTOR_DisplayPort)
> + cancel_work_sync(&conn->hpd_work);
> +
> disable_irq(conn->hpd_irq);
> }
>
> +static void display_connector_hpd_work(struct work_struct *work)
> +{
> + struct display_connector *conn = container_of(work, struct display_connector, hpd_work);
> + struct drm_bridge *bridge = &conn->bridge;
> +
> + drm_bridge_hpd_notify(bridge, display_connector_detect(bridge));
> +}
> +
> static const struct drm_edid *display_connector_edid_read(struct drm_bridge *bridge,
> struct drm_connector *connector)
> {
> @@ -395,6 +412,8 @@ static int display_connector_probe(struct platform_device *pdev)
> conn->bridge.ops |= DRM_BRIDGE_OP_DETECT;
> if (conn->hpd_irq >= 0)
> conn->bridge.ops |= DRM_BRIDGE_OP_HPD;
> + if (conn->hpd_irq >= 0 && type == DRM_MODE_CONNECTOR_DisplayPort)
> + INIT_WORK(&conn->hpd_work, display_connector_hpd_work);
>
> dev_dbg(&pdev->dev,
> "Found %s display connector '%s' %s DDC bus and %s HPD GPIO (ops 0x%x)\n",
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-03-18 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 0:43 [PATCH 0/2] drm/bridge: display-connector: detect DP state if cable is plugged on boot Dmitry Baryshkov
2026-03-14 0:43 ` [PATCH 1/2] drm/bridge: display-connector: don't autoenable HPD IRQ Dmitry Baryshkov
2026-03-14 0:43 ` [PATCH 2/2] drm/bridge: display-connector: trigger initial HPD event for DP Dmitry Baryshkov
2026-03-18 17:40 ` Laurent Pinchart [this message]
2026-03-25 4:21 ` Dmitry Baryshkov
2026-06-08 6:49 ` [PATCH 0/2] drm/bridge: display-connector: detect DP state if cable is plugged on boot Dmitry Baryshkov
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=20260318174000.GK633439@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=boris.brezillon@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=sam@ravnborg.org \
--cc=sebastian.reichel@collabora.com \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ti.com \
--cc=tzimmermann@suse.de \
--cc=yongxing.mou@oss.qualcomm.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
all inboxes | Powered by JetHome®