Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 1/2] drm/915/hdcp: Use new MST topology state in intel_conn_to_vcpi()
Date: Mon, 4 May 2026 11:50:33 +0530	[thread overview]
Message-ID: <91a7158e-cbc6-4e88-9fb1-f18590cc5cb7@intel.com> (raw)
In-Reply-To: <20260430032902.3409731-2-suraj.kandpal@intel.com>

Hi Suraj,

fix typo in commit message /drm/915 to drm/i915.

On 30-04-2026 08:59, Suraj Kandpal wrote:
> intel_conn_to_vcpi() runs from the HDCP enable path in commit_tail
> and looks up the VCPI via mgr->base.state. When an ALLOCATE_PAYLOAD
> is being driven on the mgr just before HDCP enable, that payload
> list is being mutated in place, so the lookup can miss the port and
> trip drm_WARN_ON(!payload), causing HDCP to be programmed with
> VCPI 0.
> Use drm_atomic_get_new_mst_topology_state() to read the topology
> state attached to this atomic commit (stable, decided in
> atomic_check), and bail out cleanly when no topology state or
> payload is present for this port instead of WARNing.
> 
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
>   drivers/gpu/drm/i915/display/intel_hdcp.c | 10 ++++++++--
>   1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 9b4ff3b80b05..91d2d7d823cc 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -72,6 +72,7 @@ intel_hdcp_adjust_hdcp_line_rekeying(struct intel_encoder *encoder,
>   static int intel_conn_to_vcpi(struct intel_atomic_state *state,
>   			      struct intel_connector *connector)
>   {
> +	struct intel_display *display = to_intel_display(state);
>   	struct drm_dp_mst_topology_mgr *mgr;
>   	struct drm_dp_mst_atomic_payload *payload;
>   	struct drm_dp_mst_topology_state *mst_state;
> @@ -82,9 +83,14 @@ static int intel_conn_to_vcpi(struct intel_atomic_state *state,
>   	mgr = connector->mst.port->mgr;
>   
>   	drm_modeset_lock(&mgr->base.lock, state->base.acquire_ctx);
> -	mst_state = to_drm_dp_mst_topology_state(mgr->base.state);
> +	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");
> +		return 0;
> +	}
> +
>   	payload = drm_atomic_get_mst_payload_state(mst_state, connector->mst.port);
> -	if (drm_WARN_ON(mgr->dev, !payload))
> +	if (!payload)
     is it good to have a debug message here to trace payload in mst 
state. Rest LGTM.

Tested-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
Reviewed-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
>   		return 0;
>   
>   	return payload->vcpi;


  reply	other threads:[~2026-05-04  6:20 UTC|newest]

Thread overview: 8+ 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 [this message]
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
2026-04-30  4:33 ` ✓ i915.CI.BAT: success for series starting with [1/2] drm/915/hdcp: Use new MST topology state " Patchwork
2026-04-30 10:09 ` ✓ i915.CI.Full: " 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 1/2] drm/915/hdcp: Use new MST topology state 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=91a7158e-cbc6-4e88-9fb1-f18590cc5cb7@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