From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v8 1/9] drm/connector: report out-of-band IRQ_HPD events
Date: Sat, 24 Oct 2026 00:45:30 +0000 [thread overview]
Message-ID: <sashiko-outbox-183468@kernel.org> (raw)
In-Reply-To: <20261024-hpd-irq-events-v8-1-6ee949e7a384@oss.qualcomm.com>
> The DisplayPort standard defines a special kind of events called IRQ.
> These events are used to notify DP Source about the events on the Sink
> side. It is extremely important for DP MST handling, where the MST
> events are reported through this IRQ.
>
> In case of the USB-C DP AltMode there is no actual HPD pulse, but the
> events are reported through the bits in the AltMode VDOs.
>
> Rename drm_connector_oob_hotplug_event() to drm_connector_dp_oob_status()
> and extend its interface to report IRQ events to the DisplayPort Sink
> drivers.
>
> Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261024-hpd-irq-events-v8-0-6ee949e7a384@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-10-24 0:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 0:35 [PATCH v8 0/9] drm: handle IRQ_HPD events correctly Dmitry Baryshkov
2026-10-24 0:35 ` [PATCH v8 1/9] drm/connector: report out-of-band IRQ_HPD events Dmitry Baryshkov
2026-10-24 0:45 ` sashiko-bot [this message]
2026-10-24 0:35 ` [PATCH v8 2/9] drm/connector: pass down IRQ_HPD to the drivers Dmitry Baryshkov
2026-10-24 0:41 ` sashiko-bot
2026-10-24 0:35 ` [PATCH v8 3/9] drm/bridge: " Dmitry Baryshkov
2026-10-24 0:41 ` sashiko-bot
2026-10-24 0:35 ` [PATCH v8 4/9] drm/bridge: pass extra events to the HPD callback Dmitry Baryshkov
2026-10-24 0:41 ` sashiko-bot
2026-10-24 0:35 ` [PATCH v8 5/9] drm/bridge: aux-hpd: let drivers pass IRQ_HPD events Dmitry Baryshkov
2026-10-24 0:40 ` sashiko-bot
2026-10-24 0:35 ` [PATCH v8 6/9] drm/msm/dp: don't take extra references on multiple plug events Dmitry Baryshkov
2026-10-24 0:54 ` sashiko-bot
2026-10-24 0:35 ` [PATCH v8 7/9] drm/msm/dp: handle the IRQ_HPD events reported by USB-C Dmitry Baryshkov
2026-10-24 1:02 ` sashiko-bot
2026-10-24 0:35 ` [PATCH v8 8/9] soc: qcom: pmic-glink-altmode: pass down HPD_IRQ events Dmitry Baryshkov
2026-10-24 0:40 ` sashiko-bot
2026-10-24 0:35 ` [PATCH v8 9/9] usb: typec: ucsi: huawei-gaokun: " Dmitry Baryshkov
2026-10-24 0:40 ` sashiko-bot
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=sashiko-outbox-183468@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox