All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-xe@lists.freedesktop.org
Cc: Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH] drm/xe/hdcp: Fix condition for hdcp gsc cs requirement
Date: Fri, 08 Mar 2024 17:04:33 +0200	[thread overview]
Message-ID: <87zfv8u5mm.fsf@intel.com> (raw)
In-Reply-To: <20240308134817.1940638-2-suraj.kandpal@intel.com>

On Fri, 08 Mar 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Add condition for check of hdcp gsc cs requirement rather than
> assuming gsc cs to always be required when xe is loaded. It is not
> required for Gen pre-MTL
>
> Fixes: 152f2df954d8 ("drm/xe/hdcp: Enable HDCP for XE")
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>

Acked-by: Jani Nikula <jani.nikula@intel.com>


> ---
>  drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c b/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> index dcde1d0ac1f8..25c73602ef55 100644
> --- a/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> +++ b/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> @@ -32,7 +32,7 @@ struct intel_hdcp_gsc_message {
>  
>  bool intel_hdcp_gsc_cs_required(struct xe_device *xe)
>  {
> -	return true;
> +	return DISPLAY_VER(xe) >= 14;
>  }
>  
>  bool intel_hdcp_gsc_check_status(struct xe_device *xe)

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-03-08 15:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 13:48 [PATCH] drm/xe/hdcp: Fix condition for hdcp gsc cs requirement Suraj Kandpal
2024-03-08 15:04 ` Jani Nikula [this message]
2024-03-08 15:23 ` Lucas De Marchi
2024-03-08 15:34 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-08 15:34 ` ✓ CI.checkpatch: " Patchwork
2024-03-08 15:35 ` ✓ CI.KUnit: " Patchwork
2024-03-08 15:49 ` [PATCH] " Suraj Kandpal
2024-03-11  5:24   ` Shankar, Uma
2024-03-08 15:50 ` ✓ CI.Build: success for " Patchwork
2024-03-08 15:50 ` ✓ CI.Hooks: " Patchwork
2024-03-08 15:52 ` ✓ CI.checksparse: " Patchwork
2024-03-08 16:16 ` ✓ CI.BAT: " Patchwork
2024-03-08 16:52 ` ✓ CI.Patch_applied: success for drm/xe/hdcp: Fix condition for hdcp gsc cs requirement (rev2) Patchwork
2024-03-08 16:52 ` ✓ CI.checkpatch: " Patchwork
2024-03-08 16:54 ` ✓ CI.KUnit: " Patchwork
2024-03-08 17:05 ` ✓ CI.Build: " Patchwork
2024-03-08 17:05 ` ✓ CI.Hooks: " Patchwork
2024-03-08 17:07 ` ✓ CI.checksparse: " Patchwork
2024-03-08 17:33 ` ✓ CI.BAT: " 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=87zfv8u5mm.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.