Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	<intel-xe@lists.freedesktop.org>,
	 <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/hdcp: Take force_hdcp14 into account during check_link
Date: Thu, 12 Mar 2026 16:51:17 +0530	[thread overview]
Message-ID: <e1d32e36-aac3-4184-808b-fdce8643205b@intel.com> (raw)
In-Reply-To: <20260225065045.3040787-1-suraj.kandpal@intel.com>


On 2/25/2026 12:20 PM, Suraj Kandpal wrote:
> During intel_hdcp_check_link phase we need to take into account
> if we are currently forcing HDCP 1.4 or not. This is because
> we check for HDCP 2.x Link first and only if HDCP 2.x is not being
> used check for HDCP 1.4. With force_hdcp14 in picture we should not
> be going into intel_hdcp2_check_link because of which we may end
> up trying to disable HDCP2.x even if HDCP 1.4 was enabled causing
> a lot of issues while IGT tests this.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>

Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>


> ---
>   drivers/gpu/drm/i915/display/intel_hdcp.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 116d2e0af878..892eab4b6f92 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -2231,7 +2231,7 @@ static void intel_hdcp_check_work(struct work_struct *work)
>   	if (drm_connector_is_unregistered(&connector->base))
>   		return;
>   
> -	if (!intel_hdcp2_check_link(connector))
> +	if (!hdcp->force_hdcp14 && !intel_hdcp2_check_link(connector))
>   		queue_delayed_work(display->wq.unordered, &hdcp->check_work,
>   				   DRM_HDCP2_CHECK_PERIOD_MS);
>   	else if (!intel_hdcp_check_link(connector))

  parent reply	other threads:[~2026-03-12 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  6:50 [PATCH] drm/i915/hdcp: Take force_hdcp14 into account during check_link Suraj Kandpal
2026-02-25  7:58 ` ✗ i915.CI.BAT: failure for " Patchwork
2026-03-09  9:19 ` ✗ i915.CI.BAT: failure for drm/i915/hdcp: Take force_hdcp14 into account during check_link (rev2) Patchwork
2026-03-12  5:17 ` ✓ i915.CI.BAT: success for drm/i915/hdcp: Take force_hdcp14 into account during check_link (rev3) Patchwork
2026-03-12 11:21 ` Nautiyal, Ankit K [this message]
2026-03-13  2:47 ` ✗ i915.CI.Full: 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=e1d32e36-aac3-4184-808b-fdce8643205b@intel.com \
    --to=ankit.k.nautiyal@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