Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/5] drm/xe/hdcp: Use xe_device struct
Date: Tue, 13 Feb 2024 15:16:46 -0800	[thread overview]
Message-ID: <e00cb734-2bab-4607-b1ac-a57d994184a0@intel.com> (raw)
In-Reply-To: <20240209101412.1326176-3-suraj.kandpal@intel.com>



On 2/9/2024 2:14 AM, Suraj Kandpal wrote:
> Use xe_device struct instead of drm_i915_private so as to not
> cause confusion and comply with Xe standards even though xe_device
> gets translated to drm_i915_private.

AFAIU xe_device does not get translated to drm_i915_private, it's really 
an xe_device struct under the hood.
The change itself looks ok to me, but I'll leave the final r-b to 
someone on the display side to confirm this is the correct approach.

Daniele

>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
>   drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 15 ++++++++-------
>   1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c b/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> index 0f11a39333e2..5d1d0054b578 100644
> --- a/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> +++ b/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> @@ -3,30 +3,31 @@
>    * Copyright 2023, Intel Corporation.
>    */
>   
> -#include "i915_drv.h"
> +#include <drm/drm_print.h>
>   #include "intel_hdcp_gsc.h"
> +#include "xe_device_types.h"
>   
> -bool intel_hdcp_gsc_cs_required(struct drm_i915_private *i915)
> +bool intel_hdcp_gsc_cs_required(struct xe_device *xe)
>   {
>   	return true;
>   }
>   
> -bool intel_hdcp_gsc_check_status(struct drm_i915_private *i915)
> +bool intel_hdcp_gsc_check_status(struct xe_device *xe)
>   {
>   	return false;
>   }
>   
> -int intel_hdcp_gsc_init(struct drm_i915_private *i915)
> +int intel_hdcp_gsc_init(struct xe_device *xe)
>   {
> -	drm_info(&i915->drm, "HDCP support not yet implemented\n");
> +	drm_dbg_kms(&xe->drm, "HDCP support not yet implemented\n");
>   	return -ENODEV;
>   }
>   
> -void intel_hdcp_gsc_fini(struct drm_i915_private *i915)
> +void intel_hdcp_gsc_fini(struct xe_device *xe)
>   {
>   }
>   
> -ssize_t intel_hdcp_gsc_msg_send(struct drm_i915_private *i915, u8 *msg_in,
> +ssize_t intel_hdcp_gsc_msg_send(struct xe_device *xe, u8 *msg_in,
>   				size_t msg_in_len, u8 *msg_out,
>   				size_t msg_out_len)
>   {


  reply	other threads:[~2024-02-13 23:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 10:14 [PATCH 0/5] XE HDCP Enablement Suraj Kandpal
2024-02-09 10:14 ` [PATCH 1/5] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file Suraj Kandpal
2024-02-26  8:18   ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 2/5] drm/xe/hdcp: Use xe_device struct Suraj Kandpal
2024-02-13 23:16   ` Daniele Ceraolo Spurio [this message]
2024-02-14  5:30     ` Kandpal, Suraj
2024-02-26  8:45       ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 3/5] drm/xe: Use gsc_proxy_init_done to check proxy status Suraj Kandpal
2024-02-13 23:22   ` Daniele Ceraolo Spurio
2024-02-26 10:21     ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 4/5] drm/xe/hdcp: Enable HDCP for XE Suraj Kandpal
2024-02-09 17:50   ` kernel test robot
2024-02-13 23:30   ` Daniele Ceraolo Spurio
2024-02-14  5:33     ` Kandpal, Suraj
2024-02-14 17:05       ` Daniele Ceraolo Spurio
2024-02-15  6:12   ` Suraj Kandpal
2024-02-26 11:01     ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 5/5] drm/xe/hdcp: Add intel_hdcp_gsc_message to Makefile Suraj Kandpal
2024-02-16 13:52   ` Maarten Lankhorst
2024-02-19  5:09     ` Kandpal, Suraj
2024-02-09 10:56 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev4) Patchwork
2024-02-09 10:57 ` ✓ CI.checkpatch: " Patchwork
2024-02-09 10:58 ` ✓ CI.KUnit: " Patchwork
2024-02-09 11:08 ` ✓ CI.Build: " Patchwork
2024-02-09 11:09 ` ✗ CI.Hooks: failure " Patchwork
2024-02-09 11:10 ` ✗ CI.checksparse: warning " Patchwork
2024-02-09 11:54 ` ✗ CI.BAT: failure " Patchwork
2024-02-15  6:17 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev5) Patchwork
2024-02-15  6:18 ` ✓ CI.checkpatch: " Patchwork
2024-02-15  6:19 ` ✓ CI.KUnit: " Patchwork
2024-02-15  6:29 ` ✓ CI.Build: " Patchwork
2024-02-15  6:29 ` ✗ CI.Hooks: failure " Patchwork
2024-02-15  6:31 ` ✗ CI.checksparse: warning " Patchwork
2024-02-15  7:02 ` ✓ CI.BAT: success " 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=e00cb734-2bab-4607-b1ac-a57d994184a0@intel.com \
    --to=daniele.ceraolospurio@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