From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 0/2] Fix modeset locking issue in HDCP MST
Date: Thu, 11 May 2023 15:26:48 +0530 [thread overview]
Message-ID: <20230511095650.631387-1-suraj.kandpal@intel.com> (raw)
HDCP MST scenario sees modeset locking issue ever since
topology_state was added to drm_atomic_state and all modeset
locks were being taken for us causing a locking issue to occur
when we iterate over connectors to assign vcpi id, the fix
being to pass acquire_ctx to drm_modeset_lock
--v2
-call intel_hdcp_prepare_stream instead of intel_hdcp_required_stream
in the beginning [Ankit]
-replace intel_connector argument with intel_encoder [Jani]
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Suraj Kandpal (2):
drm/i915/hdcp: add intel_atomic_state argument to hdcp_enable function
drm/i915/hdcp: Fix modeset locking issue in hdcp mst
drivers/gpu/drm/i915/display/intel_ddi.c | 4 +-
drivers/gpu/drm/i915/display/intel_dp_mst.c | 4 +-
drivers/gpu/drm/i915/display/intel_hdcp.c | 55 ++++++++++-----------
drivers/gpu/drm/i915/display/intel_hdcp.h | 6 ++-
4 files changed, 32 insertions(+), 37 deletions(-)
--
2.25.1
next reply other threads:[~2023-05-11 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 9:56 Suraj Kandpal [this message]
2023-05-11 9:56 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/hdcp: add intel_atomic_state argument to hdcp_enable function Suraj Kandpal
2023-05-11 9:56 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/hdcp: Fix modeset locking issue in hdcp mst Suraj Kandpal
2023-05-12 11:26 ` Nautiyal, Ankit K
2023-05-11 11:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fix modeset locking issue in HDCP MST (rev2) Patchwork
2023-05-11 11:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-11 14:27 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20230511095650.631387-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=intel-gfx@lists.freedesktop.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