From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: daniele.ceraolospurio@intel.com, chaitanya.kumar.borah@intel.com,
ankit.k.nautiyal@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 1/3] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file
Date: Fri, 2 Feb 2024 14:07:36 +0530 [thread overview]
Message-ID: <20240202083737.1088306-2-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20240202083737.1088306-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
next prev parent reply other threads:[~2024-02-02 8:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 8:37 [PATCH 0/3] XE HDCP Enablement Suraj Kandpal
2024-02-02 8:37 ` Suraj Kandpal [this message]
2024-02-02 8:37 ` [PATCH 2/3] drm/xe/hdcp: Enable HDCP for XE Suraj Kandpal
2024-02-03 0:41 ` kernel test robot
2024-02-05 22:50 ` Daniele Ceraolo Spurio
2024-02-06 16:24 ` Kandpal, Suraj
2024-02-06 16:51 ` Daniele Ceraolo Spurio
2024-02-07 9:40 ` Jani Nikula
2024-02-02 8:37 ` [PATCH 3/3] drm/xe/hdcp: Add intel_hdcp_gsc_message to Makefile Suraj Kandpal
2024-02-02 8:43 ` ✓ CI.Patch_applied: success for XE HDCP Enablement Patchwork
2024-02-02 8:43 ` ✓ CI.checkpatch: " Patchwork
2024-02-02 8:44 ` ✓ CI.KUnit: " Patchwork
2024-02-02 8:51 ` ✓ CI.Build: " Patchwork
2024-02-02 8:51 ` ✓ CI.Hooks: " Patchwork
2024-02-02 8:53 ` ✗ CI.checksparse: warning " Patchwork
2024-02-02 9:19 ` ✗ CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 16:47 [PATCH 0/3] " Suraj Kandpal
2024-02-06 16:47 ` [PATCH 1/3] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file 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=20240202083737.1088306-2-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=chaitanya.kumar.borah@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