From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: uma.shankar@intel.com, ankit.k.nautiyal@intel.com,
jani.nikula@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 0/2] HDCP intel_display refactors
Date: Tue, 10 Sep 2024 13:17:09 +0530 [thread overview]
Message-ID: <20240910074712.544007-1-suraj.kandpal@intel.com> (raw)
Refactors related to intel_hdcp/xe_hdcp in which we replace
drm_i915_private usage with intel_display wherever possible for
the ongoing efforts to try use intel_display structure more.
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Suraj Kandpal (2):
drm/i915/hdcp: Move to using intel_display in intel_hdcp
drm/i915/hdcp: Use intel_display in hdcp_gsc
drivers/gpu/drm/i915/display/intel_hdcp.c | 673 +++++++++---------
drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 40 +-
drivers/gpu/drm/i915/display/intel_hdcp_gsc.h | 9 +-
.../drm/i915/display/intel_hdcp_gsc_message.c | 44 +-
.../drm/i915/display/intel_hdcp_gsc_message.h | 3 +-
drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 30 +-
6 files changed, 406 insertions(+), 393 deletions(-)
--
2.43.2
next reply other threads:[~2024-09-10 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 7:47 Suraj Kandpal [this message]
2024-09-10 7:47 ` [PATCH 1/2] drm/i915/hdcp: Move to using intel_display in intel_hdcp Suraj Kandpal
2024-09-10 9:11 ` Jani Nikula
2024-09-10 12:54 ` Kandpal, Suraj
2024-09-10 7:47 ` [PATCH 2/2] drm/i915/hdcp: Use intel_display in hdcp_gsc Suraj Kandpal
2024-09-10 9:18 ` Jani Nikula
2024-09-10 12:52 ` Kandpal, Suraj
2024-09-10 13:30 ` ✓ Fi.CI.BAT: success for HDCP intel_display refactors Patchwork
2024-09-11 6:52 ` ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-09-11 9:05 [PATCH 0/2] " Suraj Kandpal
2024-09-11 13:56 ` Jani Nikula
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=20240910074712.544007-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=uma.shankar@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