From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jessica Zhang <jessica.zhang@oss.qualcomm.com>
Subject: Re: [PATCH v3 5/8] drm/msm/dp: Drop EV_USER_NOTIFICATION
Date: Thu, 15 Jan 2026 10:41:25 +0100 [thread overview]
Message-ID: <17990836-4278-4c5b-afa4-eb631930ba2a@oss.qualcomm.com> (raw)
In-Reply-To: <20260115-hpd-refactor-v3-5-08e2f3bcd2e0@oss.qualcomm.com>
On 1/15/26 8:29 AM, Dmitry Baryshkov wrote:
> From: Jessica Zhang <jessica.zhang@oss.qualcomm.com>
>
> Currently, we queue an event for signalling HPD connect/disconnect. This
> can mean a delay in plug/unplug handling and notifying DRM core when a
> hotplug happens.
>
> Drop EV_USER_NOTIFICATION and signal the IRQ event as part of hotplug
> handling.
IIUC, the drm_helper_hpd_irq_event() -> drm_bridge_hpd_notify() change
also prevents us from checking *all* connectors if we get *any* HPD?
Konrad
next prev parent reply other threads:[~2026-01-15 9:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 7:29 [PATCH v3 0/8] drm/msm/dp: Drop the HPD state machine Dmitry Baryshkov
2026-01-15 7:29 ` [PATCH v3 1/8] drm/msm/dp: fix HPD state status bit shift value Dmitry Baryshkov
2026-01-15 9:12 ` Konrad Dybcio
2026-01-15 7:29 ` [PATCH v3 2/8] drm/msm/dp: Fix the ISR_* enum values Dmitry Baryshkov
2026-01-15 9:12 ` Konrad Dybcio
2026-01-15 7:29 ` [PATCH v3 3/8] drm/msm/dp: Read DPCD and sink count in bridge detect() Dmitry Baryshkov
2026-01-15 9:19 ` Konrad Dybcio
2026-01-15 9:40 ` Dmitry Baryshkov
2026-01-15 14:57 ` Bjorn Andersson
2026-01-15 18:48 ` Dmitry Baryshkov
2026-02-02 7:04 ` Yongxing Mou
2026-01-15 7:29 ` [PATCH v3 4/8] drm/msm/dp: Move link training to atomic_enable() Dmitry Baryshkov
2026-01-15 9:30 ` Konrad Dybcio
2026-01-15 15:39 ` Bjorn Andersson
2026-01-15 18:50 ` Dmitry Baryshkov
2026-01-15 15:30 ` Bjorn Andersson
2026-01-15 18:51 ` Dmitry Baryshkov
2026-01-15 7:29 ` [PATCH v3 5/8] drm/msm/dp: Drop EV_USER_NOTIFICATION Dmitry Baryshkov
2026-01-15 9:41 ` Konrad Dybcio [this message]
2026-01-15 9:42 ` Dmitry Baryshkov
2026-01-15 10:12 ` Konrad Dybcio
2026-01-15 15:42 ` Bjorn Andersson
2026-01-15 7:29 ` [PATCH v3 6/8] drm/msm/dp: drop event data Dmitry Baryshkov
2026-01-15 9:42 ` Konrad Dybcio
2026-01-15 15:51 ` Bjorn Andersson
2026-01-15 7:29 ` [PATCH v3 7/8] drm/msm/dp: rework HPD handling Dmitry Baryshkov
2026-01-15 16:28 ` Bjorn Andersson
2026-01-15 7:29 ` [PATCH v3 8/8] drm/msm/dp: Add sink_count and link_ready to debug logs Dmitry Baryshkov
2026-01-15 16:25 ` Bjorn Andersson
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=17990836-4278-4c5b-afa4-eb631930ba2a@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=jesszhan0024@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_khsieh@quicinc.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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®