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>
Subject: [PATCH 0/4] XE HDCP Enablement
Date: Tue, 27 Feb 2024 11:02:00 +0530 [thread overview]
Message-ID: <20240227053204.1748920-1-suraj.kandpal@intel.com> (raw)
This patch series enables HDCP on XE.
Mainly includes rewriting functions that were responsible for
sending hdcp messages via gsc cs.
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Suraj Kandpal (4):
drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file
drm/xe/hdcp: Use xe_device struct
drm/xe: Use gsc_proxy_init_done to check proxy status
drm/xe/hdcp: Enable HDCP for XE
drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 6 +
drivers/gpu/drm/i915/display/intel_hdcp_gsc.h | 7 +-
drivers/gpu/drm/xe/Makefile | 1 +
drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 241 +++++++++++++++++-
drivers/gpu/drm/xe/xe_gsc_proxy.c | 4 +-
drivers/gpu/drm/xe/xe_gsc_proxy.h | 1 +
drivers/gpu/drm/xe/xe_gsc_submit.c | 15 ++
drivers/gpu/drm/xe/xe_gsc_submit.h | 1 +
8 files changed, 258 insertions(+), 18 deletions(-)
--
2.43.2
next reply other threads:[~2024-02-27 5:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 5:32 Suraj Kandpal [this message]
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
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-02-07 11:35 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=20240227053204.1748920-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@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