All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Suraj Kandpal <suraj.kandpal@intel.com>,
	Arun R Murthy <arun.r.murthy@intel.com>
Subject: [PATCH 2/4] drm/xe/hdcp: Use xe_device struct
Date: Wed,  6 Mar 2024 08:12:46 +0530	[thread overview]
Message-ID: <20240306024247.1857881-4-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20240306024247.1857881-2-suraj.kandpal@intel.com>

Use xe_device struct instead of drm_i915_private so as to not
cause confusion and comply with Xe standards as drm_i915_private is
xe_device under the hood.

--v2
-Fix commit message [Daniele]

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@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)
 {
-- 
2.43.2


  parent reply	other threads:[~2024-03-06  2:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  2:42 [PATCH 0/4] XE HDCP Enablement Suraj Kandpal
2024-03-06  2:42 ` [PATCH 1/4] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file Suraj Kandpal
2024-03-06  2:47   ` Suraj Kandpal
2024-03-06  2:42 ` Suraj Kandpal [this message]
2024-03-06  2:42 ` [PATCH 3/4] drm/xe: Use gsc_proxy_init_done to check proxy status Suraj Kandpal
2024-03-06  2:42 ` [PATCH 4/4] drm/xe/hdcp: Enable HDCP for XE Suraj Kandpal
2024-03-06  2:49 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev9) Patchwork
2024-03-06  2:50 ` ✓ CI.checkpatch: " Patchwork
2024-03-06  2:50 ` ✓ CI.KUnit: " Patchwork
2024-03-06  3:01 ` ✓ CI.Build: " Patchwork
2024-03-06  3:01 ` ✗ CI.Hooks: failure " Patchwork
2024-03-06  3:03 ` ✗ CI.checksparse: warning " Patchwork
2024-03-06  3:45 ` ✓ CI.BAT: success " Patchwork
2024-03-06  3:49 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev10) Patchwork
2024-03-06  3:50 ` ✓ CI.checkpatch: " Patchwork
2024-03-06  3:51 ` ✓ CI.KUnit: " Patchwork
2024-03-06  4:01 ` ✓ CI.Build: " Patchwork
2024-03-06  4:02 ` ✗ CI.Hooks: failure " Patchwork
2024-03-06  4:03 ` ✗ CI.checksparse: warning " Patchwork
2024-03-06  4:33 ` ✓ CI.BAT: success " Patchwork
2024-03-06  7:58 ` ✗ Fi.CI.SPARSE: warning " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27  5:32 [PATCH 0/4] XE HDCP Enablement Suraj Kandpal
2024-02-27  5:32 ` [PATCH 2/4] drm/xe/hdcp: Use xe_device struct 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=20240306024247.1857881-4-suraj.kandpal@intel.com \
    --to=suraj.kandpal@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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.