From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-amlogic@lists.infradead.org,
intel-xe@lists.freedesktop.org, neil.armstrong@linaro.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 6/8] drm/msm: dp: handle the IRQ_HPD events reported by USB-C
Date: Sun, 20 Sep 2026 15:13:57 +0000 [thread overview]
Message-ID: <20260920151357.A9CB21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260920-hpd-irq-events-v5-6-ff1de0090c72@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] drm/msm/dp: missing display initialization on coalesced plug and IRQ_HPD events
--
commit de969f3016008fcb55e0b380cb8e0c733c719543
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
drm/msm: dp: handle the IRQ_HPD events reported by USB-C
This commit allows the MSM DisplayPort driver to handle IRQ_HPD events
delivered over OOB events (like USB-C AltMode).
> diff --git a/drivers/gpu/drm/msm/dp/dp_display.c b/drivers/gpu/drm/msm/dp/dp_display.c
> --- a/drivers/gpu/drm/msm/dp/dp_display.c
> +++ b/drivers/gpu/drm/msm/dp/dp_display.c
> @@ -1559,11 +1559,12 @@ void msm_dp_bridge_hpd_notify(struct drm_bridge *bridge,
[ ... ]
> if (status == connector_status_connected) {
> - if (hpd_link_status == ISR_HPD_REPLUG_COUNT) {
> + if (hpd_link_status == ISR_IRQ_HPD_PULSE_COUNT ||
> + event == DRM_CONNECTOR_DP_IRQ_HPD) {
> + msm_dp_irq_hpd_handle(dp);
> + } else if (hpd_link_status == ISR_HPD_REPLUG_COUNT) {
> msm_dp_hpd_unplug_handle(dp);
> msm_dp_hpd_plug_handle(dp);
> - } else if (hpd_link_status == ISR_IRQ_HPD_PULSE_COUNT) {
> - msm_dp_irq_hpd_handle(dp);
> } else {
> msm_dp_hpd_plug_handle(dp);
> }
[Severity: High]
Does this code handle coalesced connection and IRQ_HPD events correctly?
If the USB Type-C AltMode driver coalesces an initial connection and a pending
IRQ_HPD event into a single notification, msm_dp_bridge_hpd_notify() receives
both status == connector_status_connected and event ==
DRM_CONNECTOR_DP_IRQ_HPD.
The mutual exclusion block in drivers/gpu/drm/msm/dp/dp_display.c prioritizes
event == DRM_CONNECTOR_DP_IRQ_HPD, branching to msm_dp_irq_hpd_handle() and
entirely skipping msm_dp_hpd_plug_handle().
Because msm_dp_hpd_plug_handle() is skipped, dp->plugged remains false,
the DP PHY is not initialized, and AUX transfers remain disabled. The
subsequent msm_dp_irq_hpd_handle() then attempts an AUX read which immediately
fails with -ENXIO, abandoning the initialization and leaving the display
blank.
Is it possible to ensure msm_dp_hpd_plug_handle() is still called when a new
connection occurs alongside an IRQ_HPD event?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260920-hpd-irq-events-v5-0-ff1de0090c72@oss.qualcomm.com?part=6
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-amlogic@lists.infradead.org,
intel-xe@lists.freedesktop.org, neil.armstrong@linaro.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 6/8] drm/msm: dp: handle the IRQ_HPD events reported by USB-C
Date: Sun, 20 Sep 2026 15:13:57 +0000 [thread overview]
Message-ID: <20260920151357.A9CB21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260920-hpd-irq-events-v5-6-ff1de0090c72@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] drm/msm/dp: missing display initialization on coalesced plug and IRQ_HPD events
--
commit de969f3016008fcb55e0b380cb8e0c733c719543
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
drm/msm: dp: handle the IRQ_HPD events reported by USB-C
This commit allows the MSM DisplayPort driver to handle IRQ_HPD events
delivered over OOB events (like USB-C AltMode).
> diff --git a/drivers/gpu/drm/msm/dp/dp_display.c b/drivers/gpu/drm/msm/dp/dp_display.c
> --- a/drivers/gpu/drm/msm/dp/dp_display.c
> +++ b/drivers/gpu/drm/msm/dp/dp_display.c
> @@ -1559,11 +1559,12 @@ void msm_dp_bridge_hpd_notify(struct drm_bridge *bridge,
[ ... ]
> if (status == connector_status_connected) {
> - if (hpd_link_status == ISR_HPD_REPLUG_COUNT) {
> + if (hpd_link_status == ISR_IRQ_HPD_PULSE_COUNT ||
> + event == DRM_CONNECTOR_DP_IRQ_HPD) {
> + msm_dp_irq_hpd_handle(dp);
> + } else if (hpd_link_status == ISR_HPD_REPLUG_COUNT) {
> msm_dp_hpd_unplug_handle(dp);
> msm_dp_hpd_plug_handle(dp);
> - } else if (hpd_link_status == ISR_IRQ_HPD_PULSE_COUNT) {
> - msm_dp_irq_hpd_handle(dp);
> } else {
> msm_dp_hpd_plug_handle(dp);
> }
[Severity: High]
Does this code handle coalesced connection and IRQ_HPD events correctly?
If the USB Type-C AltMode driver coalesces an initial connection and a pending
IRQ_HPD event into a single notification, msm_dp_bridge_hpd_notify() receives
both status == connector_status_connected and event ==
DRM_CONNECTOR_DP_IRQ_HPD.
The mutual exclusion block in drivers/gpu/drm/msm/dp/dp_display.c prioritizes
event == DRM_CONNECTOR_DP_IRQ_HPD, branching to msm_dp_irq_hpd_handle() and
entirely skipping msm_dp_hpd_plug_handle().
Because msm_dp_hpd_plug_handle() is skipped, dp->plugged remains false,
the DP PHY is not initialized, and AUX transfers remain disabled. The
subsequent msm_dp_irq_hpd_handle() then attempts an AUX read which immediately
fails with -ENXIO, abandoning the initialization and leaving the display
blank.
Is it possible to ensure msm_dp_hpd_plug_handle() is still called when a new
connection occurs alongside an IRQ_HPD event?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260920-hpd-irq-events-v5-0-ff1de0090c72@oss.qualcomm.com?part=6
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-09-20 15:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 15:01 [PATCH v5 0/8] drm: handle IRQ_HPD events correctly Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 1/8] drm/connector: report out-of-band IRQ_HPD events Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-21 1:43 ` Chaoyi Chen
2026-09-21 1:43 ` Chaoyi Chen
2026-09-20 15:01 ` [PATCH v5 2/8] drm/connector: pass down IRQ_HPD to the drivers Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-21 1:53 ` Chaoyi Chen
2026-09-21 1:53 ` Chaoyi Chen
2026-09-20 15:01 ` [PATCH v5 3/8] drm/bridge: aux-hpd: let drivers pass IRQ_HPD events Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 4/8] drm/bridge: pass extra events to the HPD callback Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 5/8] drm/bridge: pass down IRQ_HPD to the drivers Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-20 15:10 ` sashiko-bot
2026-09-20 15:10 ` sashiko-bot
2026-09-20 15:01 ` [PATCH v5 6/8] drm/msm: dp: handle the IRQ_HPD events reported by USB-C Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-20 15:13 ` sashiko-bot [this message]
2026-09-20 15:13 ` sashiko-bot
2026-09-20 15:01 ` [PATCH v5 7/8] soc: qcom: pmic-glink-altmode: pass down HPD_IRQ events Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 8/8] usb: typec: ucsi: huawei-gaokun: " Dmitry Baryshkov
2026-09-20 15:01 ` Dmitry Baryshkov
2026-09-20 15:09 ` ✗ CI.checkpatch: warning for drm: handle IRQ_HPD events correctly (rev6) Patchwork
2026-09-20 15:11 ` ✓ CI.KUnit: success " Patchwork
2026-09-20 15:44 ` ✓ i915.CI.BAT: " Patchwork
2026-09-20 15:49 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-09-20 17:12 ` ✗ Xe.CI.FULL: " Patchwork
2026-09-20 17:36 ` ✗ i915.CI.Full: " Patchwork
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=20260920151357.A9CB21F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.