From: Jani Nikula <jani.nikula@intel.com>
To: Ramalingam C <ramalingam.c@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: tomas.winkler@intel.com
Subject: Re: [PATCH v7 0/6] drm/i915: Enable HDCP 1.4 and 2.2 on Gen12+
Date: Thu, 22 Aug 2019 14:47:31 +0300 [thread overview]
Message-ID: <87a7c1ctgs.fsf@intel.com> (raw)
In-Reply-To: <20190822111445.29350-1-ramalingam.c@intel.com>
On Thu, 22 Aug 2019, Ramalingam C <ramalingam.c@intel.com> wrote:
> Enabling the HDCP1.4 and 2.2 on TGL by supporting the HW block movement
> from DDI into transcoder.
>
> v7:
> port, transcoder definitions are kept within I915.
> corresponding changes in i915-mei interface.
I had some superficial comments here and there, won't do detailed review
of the series, but I like this overall approach better than exposing the
definitions from i915.
Acked-by: Jani Nikula <jani.nikula@intel.com>
>
> Ramalingam C (6):
> drm/i915: mei_hdcp: I915 sends ddi index as per ME FW
> drm: port definition is moved back into i915 header
> drm: I915 mei interface is extended for transcoder info
> misc/mei/hdcp: transcoder index in port info
> drm/i915/hdcp: updating the transcoder of the hdcp port
> drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+
>
> drivers/gpu/drm/i915/display/intel_bios.h | 2 +
> 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 | 191 +++++++++++++-----
> drivers/gpu/drm/i915/display/intel_hdcp.h | 2 +
> drivers/gpu/drm/i915/display/intel_hdmi.c | 12 +-
> 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 ++-
> 13 files changed, 348 insertions(+), 120 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-08-22 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 11:14 [PATCH v7 0/6] drm/i915: Enable HDCP 1.4 and 2.2 on Gen12+ Ramalingam C
2019-08-22 11:14 ` [PATCH v7 1/6] drm/i915: mei_hdcp: I915 sends ddi index as per ME FW Ramalingam C
2019-08-22 11:14 ` [PATCH v7 2/6] drm: port definition is moved back into i915 header Ramalingam C
2019-08-22 11:34 ` [PATCH v8 " Ramalingam C
2019-08-22 11:42 ` [PATCH v7 " Jani Nikula
2019-08-22 11:14 ` [PATCH v7 3/6] drm: I915 mei interface is extended for transcoder info Ramalingam C
2019-08-22 11:14 ` [PATCH v7 4/6] misc/mei/hdcp: transcoder index in port info Ramalingam C
2019-08-22 11:14 ` [PATCH v7 5/6] drm/i915/hdcp: updating the transcoder of the hdcp port Ramalingam C
2019-08-22 11:45 ` Jani Nikula
2019-08-22 11:14 ` [PATCH v7 6/6] drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+ Ramalingam C
2019-08-22 11:46 ` Jani Nikula
2019-08-22 11:47 ` Jani Nikula [this message]
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=87a7c1ctgs.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@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