From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>, tomas.winkler@intel.com
Subject: [PATCH v10 0/6] drm/i915: Enable HDCP 1.4 and 2.2 on Gen12+
Date: Tue, 27 Aug 2019 16:20:08 +0530 [thread overview]
Message-ID: <20190827105014.14181-1-ramalingam.c@intel.com> (raw)
Enabling the HDCP1.4 and 2.2 on TGL by supporting the HW block movement
from DDI into transcoder.
v10:
Review comments from shashank addressed
Ramalingam C (6):
drm/i915: mei_hdcp: I915 sends ddi index as per ME FW
drm: Move port definition back to i915 header
drm: Extend I915 mei interface for transcoder info
misc/mei/hdcp: Fill transcoder index in port info
drm/i915/hdcp: update current transcoder into intel_hdcp
drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+
drivers/gpu/drm/i915/display/intel_bios.h | 1 +
drivers/gpu/drm/i915/display/intel_display.h | 18 ++
.../drm/i915/display/intel_display_types.h | 7 +
drivers/gpu/drm/i915/display/intel_dp.c | 3 +
drivers/gpu/drm/i915/display/intel_dp.h | 1 +
drivers/gpu/drm/i915/display/intel_hdcp.c | 212 +++++++++++++-----
drivers/gpu/drm/i915/display/intel_hdcp.h | 4 +
drivers/gpu/drm/i915/display/intel_hdmi.c | 13 +-
drivers/gpu/drm/i915/display/intel_hdmi.h | 1 +
drivers/gpu/drm/i915/display/intel_hotplug.h | 1 +
drivers/gpu/drm/i915/display/intel_sdvo.h | 1 +
drivers/gpu/drm/i915/i915_reg.h | 124 +++++++++-
drivers/misc/mei/hdcp/mei_hdcp.c | 45 ++--
drivers/misc/mei/hdcp/mei_hdcp.h | 16 +-
include/drm/i915_drm.h | 18 --
include/drm/i915_mei_hdcp_interface.h | 29 ++-
16 files changed, 372 insertions(+), 122 deletions(-)
--
2.20.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-08-27 10:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 10:50 Ramalingam C [this message]
2019-08-27 10:50 ` [PATCH v10 1/6] drm/i915: mei_hdcp: I915 sends ddi index as per ME FW Ramalingam C
2019-08-27 10:50 ` [PATCH v10 2/6] drm: Move port definition back to i915 header Ramalingam C
2019-08-27 10:50 ` [PATCH v10 3/6] drm: Extend I915 mei interface for transcoder info Ramalingam C
2019-08-27 14:00 ` Winkler, Tomas
2019-08-27 14:20 ` Ramalingam C
2019-08-27 10:50 ` [PATCH v10 4/6] misc/mei/hdcp: Fill transcoder index in port info Ramalingam C
2019-08-27 14:19 ` Winkler, Tomas
2019-08-27 14:31 ` Ramalingam C
2019-08-27 14:37 ` Winkler, Tomas
2019-08-27 14:41 ` Ramalingam C
2019-08-27 10:50 ` [PATCH v10 5/6] drm/i915/hdcp: update current transcoder into intel_hdcp Ramalingam C
2019-08-27 14:33 ` Winkler, Tomas
2019-08-27 14:52 ` Ramalingam C
2019-08-27 20:31 ` Winkler, Tomas
2019-08-28 7:05 ` Ramalingam C
2019-08-27 10:50 ` [PATCH v10 6/6] drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+ Ramalingam C
2019-08-27 12:25 ` ✓ Fi.CI.BAT: success for drm/i915: Enable HDCP 1.4 and 2.2 on Gen12+ (rev8) Patchwork
2019-08-27 13:02 ` [PATCH v10 0/6] drm/i915: Enable HDCP 1.4 and 2.2 on Gen12+ Winkler, Tomas
2019-08-27 13:22 ` Ramalingam C
2019-08-27 13:32 ` Winkler, Tomas
2019-08-28 11:00 ` ✓ Fi.CI.IGT: success for drm/i915: Enable HDCP 1.4 and 2.2 on Gen12+ (rev8) 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=20190827105014.14181-1-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=tomas.winkler@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