From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org
Subject: [RFC PATCH v2 0/5] drm/msm/dp: implement HPD notifications handling
Date: Fri, 29 Apr 2022 22:57:26 +0300 [thread overview]
Message-ID: <20220429195731.3716446-1-dmitry.baryshkov@linaro.org> (raw)
USB altmodes code would send OOB notifications to the drm_connector
specified in the device tree. However as the MSM DP driver uses
drm_bridge_connector, there is no way to receive these event directly.
Implement a bridge between oob_hotplug_event and drm_bridge's hpd_notify
and use it to deliver altmode messages to the MSM DP driver.
Note, I left the original 'bool connected' field to be used by the
notifiers. However I think that it should be replaced in favour of using
the dp->hpd_state properly.
Changes since RFC v1:
- Incorporated old patch dropping old usbpd code. Most of it remained
unused.
Bjorn Andersson (2):
drm: Add HPD state to drm_connector_oob_hotplug_event()
drm/msm/dp: Implement hpd_notify()
Dmitry Baryshkov (3):
drm/bridge_connector: stop filtering events in
drm_bridge_connector_hpd_cb()
drm/bridge_connector: implement oob_hotplug_event
drm/msm/dp: remove most of usbpd-related remains
drivers/gpu/drm/drm_bridge_connector.c | 17 ++++--
drivers/gpu/drm/drm_connector.c | 6 +-
drivers/gpu/drm/i915/display/intel_dp.c | 17 +++++-
drivers/gpu/drm/i915/i915_drv.h | 3 +
drivers/gpu/drm/msm/Makefile | 1 -
drivers/gpu/drm/msm/dp/dp_ctrl.h | 1 -
drivers/gpu/drm/msm/dp/dp_debug.c | 6 +-
drivers/gpu/drm/msm/dp/dp_debug.h | 4 +-
drivers/gpu/drm/msm/dp/dp_display.c | 65 +++++++++-----------
drivers/gpu/drm/msm/dp/dp_display.h | 1 +
drivers/gpu/drm/msm/dp/dp_drm.c | 3 +
drivers/gpu/drm/msm/dp/dp_drm.h | 2 +
drivers/gpu/drm/msm/dp/dp_hpd.c | 67 --------------------
drivers/gpu/drm/msm/dp/dp_hpd.h | 78 ------------------------
drivers/gpu/drm/msm/dp/dp_panel.h | 1 -
drivers/gpu/drm/msm/dp/dp_power.c | 2 +-
drivers/gpu/drm/msm/dp/dp_power.h | 3 +-
drivers/usb/typec/altmodes/displayport.c | 10 +--
include/drm/drm_connector.h | 6 +-
19 files changed, 82 insertions(+), 211 deletions(-)
delete mode 100644 drivers/gpu/drm/msm/dp/dp_hpd.c
delete mode 100644 drivers/gpu/drm/msm/dp/dp_hpd.h
--
2.35.1
next reply other threads:[~2022-04-29 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 19:57 Dmitry Baryshkov [this message]
2022-04-29 19:57 ` [RFC PATCH v2 1/5] drm/bridge_connector: stop filtering events in drm_bridge_connector_hpd_cb() Dmitry Baryshkov
2022-04-29 19:57 ` [RFC PATCH v2 2/5] drm: Add HPD state to drm_connector_oob_hotplug_event() Dmitry Baryshkov
2022-04-29 19:57 ` [RFC PATCH v2 3/5] drm/bridge_connector: implement oob_hotplug_event Dmitry Baryshkov
2022-04-29 19:57 ` [RFC PATCH v2 4/5] drm/msm/dp: remove most of usbpd-related remains Dmitry Baryshkov
2022-04-29 19:57 ` [RFC PATCH v2 5/5] drm/msm/dp: Implement hpd_notify() Dmitry Baryshkov
2022-04-29 21:02 ` [Freedreno] [RFC PATCH v2 0/5] drm/msm/dp: implement HPD notifications handling Abhinav Kumar
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=20220429195731.3716446-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).