From: "Reddy Guddati, Santhosh" <santhosh.reddy.guddati@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>
Cc: <ankit.k.nautiyal@intel.com>, <fnu.vishwanatha@intel.com>
Subject: Re: [PATCH 2/2] drm/i915/hdcp: Drop mgr->base.lock acquisition in intel_conn_to_vcpi()
Date: Mon, 4 May 2026 15:23:36 +0530 [thread overview]
Message-ID: <8c67967d-9a53-43d0-a454-b9ece1934db7@intel.com> (raw)
In-Reply-To: <20260430032902.3409731-3-suraj.kandpal@intel.com>
Hi Suraj,
LGTM,
Tested-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
Reviewed-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
On 30-04-2026 08:59, Suraj Kandpal wrote:
> Now that intel_conn_to_vcpi() reads the MST topology state via
> drm_atomic_get_new_mst_topology_state(), the topology state belongs
> to this atomic commit and is already serialized through the atomic
> state's private object machinery. There is no need to additionally
> take mgr->base.lock here.
> Taking it from the HDCP enable path in commit_tail with
> state->base.acquire_ctx is also unsafe: by this point the
> acquire_ctx is no longer in a state where new modeset locks may be
> acquired through it, which produces a modeset-lock splat on MST +
> HDCP. Drop the drm_modeset_lock() call.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 91d2d7d823cc..a5d4e77f810f 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -80,9 +80,8 @@ static int intel_conn_to_vcpi(struct intel_atomic_state *state,
> /* For HDMI this is forced to be 0x0. For DP SST also this is 0x0. */
> if (!connector->mst.port)
> return 0;
> - mgr = connector->mst.port->mgr;
>
> - drm_modeset_lock(&mgr->base.lock, state->base.acquire_ctx);
> + mgr = connector->mst.port->mgr;
> mst_state = drm_atomic_get_new_mst_topology_state(&state->base, mgr);
> if (!mst_state) {
> drm_dbg_kms(display->drm, "MST topology still not created\n");
next prev parent reply other threads:[~2026-05-04 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 3:29 Fix MST VCPI lookup and modeset-lock splat Suraj Kandpal
2026-04-30 3:29 ` [PATCH 1/2] drm/915/hdcp: Use new MST topology state in intel_conn_to_vcpi() Suraj Kandpal
2026-05-04 6:20 ` Reddy Guddati, Santhosh
2026-04-30 3:29 ` [PATCH 2/2] drm/i915/hdcp: Drop mgr->base.lock acquisition " Suraj Kandpal
2026-05-04 9:53 ` Reddy Guddati, Santhosh [this message]
2026-04-30 3:36 ` ✓ CI.KUnit: success for series starting with [1/2] drm/915/hdcp: Use new MST topology state " Patchwork
2026-04-30 4:25 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-30 14:44 ` ✗ Xe.CI.FULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-04-30 3:32 [PATCH 0/2] Fix MST VCPI lookup and modeset-lock splat Suraj Kandpal
2026-04-30 3:32 ` [PATCH 2/2] drm/i915/hdcp: Drop mgr->base.lock acquisition in intel_conn_to_vcpi() Suraj Kandpal
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=8c67967d-9a53-43d0-a454-b9ece1934db7@intel.com \
--to=santhosh.reddy.guddati@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=fnu.vishwanatha@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
/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