From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Suraj Kandpal <suraj.kandpal@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 1/4] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file
Date: Mon, 04 Mar 2024 17:59:01 +0200 [thread overview]
Message-ID: <87il223s56.fsf@intel.com> (raw)
In-Reply-To: <20240227053204.1748920-2-suraj.kandpal@intel.com>
On Tue, 27 Feb 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Move intel_hdcp_gsc_message definition into intel_hdcp_gsc.h
> so that intel_hdcp_gsc_message can be redefined for xe as needed.
>
> --v2
> -Correct commit message to reflect what patch is actually doing [Arun]
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Acked-by: Jani Nikula <jani.nikula@intel.com>
for merging this patch via drm-xe-next.
BR,
Jani.
> ---
> 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 302bff75b06c..35823e1f65d6 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,
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-03-04 15:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 5:32 [PATCH 0/4] XE HDCP Enablement Suraj Kandpal
2024-02-27 5:32 ` [PATCH 1/4] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file Suraj Kandpal
2024-02-27 6:33 ` Suraj Kandpal
2024-02-28 6:01 ` Murthy, Arun R
2024-02-28 5:59 ` Kandpal, Suraj
2024-03-04 15:59 ` Jani Nikula [this message]
2024-02-27 5:32 ` [PATCH 2/4] drm/xe/hdcp: Use xe_device struct Suraj Kandpal
2024-02-27 5:32 ` [PATCH 3/4] drm/xe: Use gsc_proxy_init_done to check proxy status Suraj Kandpal
2024-02-28 5:47 ` Suraj Kandpal
2024-02-27 5:32 ` [PATCH 4/4] drm/xe/hdcp: Enable HDCP for XE Suraj Kandpal
2024-03-05 13:36 ` Lucas De Marchi
2024-02-27 5:39 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev6) Patchwork
2024-02-27 5:39 ` ✓ CI.checkpatch: " Patchwork
2024-02-27 5:40 ` ✓ CI.KUnit: " Patchwork
2024-02-27 5:51 ` ✓ CI.Build: " Patchwork
2024-02-27 5:52 ` ✗ CI.Hooks: failure " Patchwork
2024-02-27 5:53 ` ✗ CI.checksparse: warning " Patchwork
2024-02-27 6:23 ` ✗ CI.BAT: failure " Patchwork
2024-02-27 6:40 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev7) Patchwork
2024-02-27 6:40 ` ✓ CI.checkpatch: " Patchwork
2024-02-27 6:41 ` ✓ CI.KUnit: " Patchwork
2024-02-27 6:52 ` ✓ CI.Build: " Patchwork
2024-02-27 6:53 ` ✗ CI.Hooks: failure " Patchwork
2024-02-27 6:54 ` ✗ CI.checksparse: warning " Patchwork
2024-02-27 7:15 ` ✓ CI.BAT: success " Patchwork
2024-02-28 5:54 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev8) Patchwork
2024-02-28 5:54 ` ✓ CI.checkpatch: " Patchwork
2024-02-28 5:55 ` ✓ CI.KUnit: " Patchwork
2024-02-28 6:06 ` ✓ CI.Build: " Patchwork
2024-02-28 6:07 ` ✗ CI.Hooks: failure " Patchwork
2024-02-28 6:08 ` ✗ CI.checksparse: warning " Patchwork
2024-02-28 6:36 ` ✓ CI.BAT: success " Patchwork
2024-03-05 13:38 ` [PATCH 0/4] XE HDCP Enablement Lucas De Marchi
-- strict thread matches above, loose matches on Subject: below --
2024-03-06 2:42 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-02-07 11:35 [PATCH 0/4] XE HDCP Enablement Suraj Kandpal
2024-02-07 11:35 ` [PATCH 1/4] 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=87il223s56.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--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