Intel-XE Archive on 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: daniele.ceraolospurio@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 1/5] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file
Date: Fri,  9 Feb 2024 15:44:08 +0530	[thread overview]
Message-ID: <20240209101412.1326176-2-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20240209101412.1326176-1-suraj.kandpal@intel.com>

Move intel_hdcp_gsc_message definition into intel_hdcp_gsc_message.c
so that intel_hdcp_gsc_message can be redefined for xe as needed.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
---
 drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 6 ++++++
 drivers/gpu/drm/i915/display/intel_hdcp_gsc.h | 7 +------
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_hdcp_gsc.c b/drivers/gpu/drm/i915/display/intel_hdcp_gsc.c
index 18117b789b16..e44f60f00e8b 100644
--- a/drivers/gpu/drm/i915/display/intel_hdcp_gsc.c
+++ b/drivers/gpu/drm/i915/display/intel_hdcp_gsc.c
@@ -13,6 +13,12 @@
 #include "intel_hdcp_gsc.h"
 #include "intel_hdcp_gsc_message.h"
 
+struct intel_hdcp_gsc_message {
+	struct i915_vma *vma;
+	void *hdcp_cmd_in;
+	void *hdcp_cmd_out;
+};
+
 bool intel_hdcp_gsc_cs_required(struct drm_i915_private *i915)
 {
 	return DISPLAY_VER(i915) >= 14;
diff --git a/drivers/gpu/drm/i915/display/intel_hdcp_gsc.h b/drivers/gpu/drm/i915/display/intel_hdcp_gsc.h
index eba2057c5a9e..5f610df61cc9 100644
--- a/drivers/gpu/drm/i915/display/intel_hdcp_gsc.h
+++ b/drivers/gpu/drm/i915/display/intel_hdcp_gsc.h
@@ -10,12 +10,7 @@
 #include <linux/types.h>
 
 struct drm_i915_private;
-
-struct intel_hdcp_gsc_message {
-	struct i915_vma *vma;
-	void *hdcp_cmd_in;
-	void *hdcp_cmd_out;
-};
+struct intel_hdcp_gsc_message;
 
 bool intel_hdcp_gsc_cs_required(struct drm_i915_private *i915);
 ssize_t intel_hdcp_gsc_msg_send(struct drm_i915_private *i915, u8 *msg_in,
-- 
2.25.1


  reply	other threads:[~2024-02-09 10: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 ` Suraj Kandpal [this message]
2024-02-26  8:18   ` [PATCH 1/5] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file 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
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=20240209101412.1326176-2-suraj.kandpal@intel.com \
    --to=suraj.kandpal@intel.com \
    --cc=daniele.ceraolospurio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox