From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
daniel.vetter@ffwll.ch, maarten.lankhorst@linux.intel.com
Subject: [PATCH v2 0/8] HDCP2.2 Phase II
Date: Sat, 9 Mar 2019 09:34:44 +0530 [thread overview]
Message-ID: <20190309040452.23699-1-ramalingam.c@intel.com> (raw)
HDCP2.2 phase-II mojorly adds below features:
Addition of three connector properties
CP_Content_Type
CP_Downstream_Info
Addition of binary sysfs "hdcp_srm"
parsing for HDCP1.4 and 2.2 SRM table
Once HDCP1.4/2.2 authentication is completed gathering the all
downstream topology for userspace
Extending debugfs entry to provide the HDCP2.2 capability too.
CP_Content_Type:
This property is used to indicate the content type
classification of a stream. Which indicate the HDCP version required
for the rendering of that streams. This conten type is one of the
parameter in the HDCP2.2 authentication flow, as even downstream
repeaters will mandate the HDCP version requirement.
Two values possible for content type of a stream:
Type 0: Stream can be rendered only on HDCP encrypted link no
restriction on HDCP versions.
Type 1: Stream can be rendered only on HDCP2.2 encrypted link.
There is a parallel effort in #wayland community to add the support for
HDCP2.2 along with content type support. Patches are under review in
#wayland community.
CP_downstream_info:
This blob property is used by the kernel to pass the downstream topology
of the HDCP encrypted port to the userspace.
This is used by the userspace to implement the HDCP repeater, which KMD
implementing the HDCP transmitters(downstream ports) and userspace
implementing the upstream port(HDCP receiver).
Discussion is on going to add the downstream_info support in the
weston HDCP stack.
hdcp_srm: write only binary sysfs used by the userspace to pass the SRM
table of HDCP1.4 and 2.2. These are nothing but revocated list of
receiver IDs of the HDCP sinks. KMD will use this list to identify the
revocated devices in the HDCP authentication and deny the hdcp encryption to it.
v2:
srm is passed through binary sysfs [Daniel]
CP abbreviation is expanded except for downstream_info [Daniel]
restrictions at atomic_set_property is removed [Maarten]
upon content type change durin encryption, HDCP is restarted within
kernel [Maarten]
Resending it as previous submission was failed find the mentioned igt
version.
Series can be cloned from github
https://github.com/ramalingampc2008/drm-tip.git hdcp2_2_p2_v2
Test-with: <20190308163049.9016-2-ramalingam.c@intel.com>
Ramalingam C (8):
drm/i915: debugfs: HDCP2.2 capability read
drm: Add Content protection type property
drm/i915: Attach content type property
drm/i915: HDCP SRM parsing and revocation check
drm/i915/sysfs: Node for hdcp srm
drm: Add CP downstream_info property
drm/i915: Populate downstream info for HDCP1.4
drm/i915: Populate downstream info for HDCP2.2
drivers/gpu/drm/drm_atomic_uapi.c | 8 +
drivers/gpu/drm/drm_connector.c | 152 +++++++++++
drivers/gpu/drm/i915/i915_debugfs.c | 13 +-
drivers/gpu/drm/i915/i915_drv.c | 1 +
drivers/gpu/drm/i915/i915_drv.h | 6 +
drivers/gpu/drm/i915/i915_sysfs.c | 32 +++
drivers/gpu/drm/i915/intel_ddi.c | 21 +-
drivers/gpu/drm/i915/intel_drv.h | 7 +-
drivers/gpu/drm/i915/intel_hdcp.c | 405 ++++++++++++++++++++++++++--
include/drm/drm_connector.h | 27 ++
include/drm/drm_hdcp.h | 33 +++
include/uapi/drm/drm_mode.h | 39 +++
12 files changed, 712 insertions(+), 32 deletions(-)
--
2.19.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-09 4:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 4:04 Ramalingam C [this message]
2019-03-09 4:04 ` [PATCH v2 1/8] drm/i915: debugfs: HDCP2.2 capability read Ramalingam C
2019-03-09 4:04 ` [PATCH v2 2/8] drm: Add Content protection type property Ramalingam C
2019-03-09 4:04 ` [PATCH v2 3/8] drm/i915: Attach content " Ramalingam C
2019-03-09 4:04 ` [PATCH v2 4/8] drm/i915: HDCP SRM parsing and revocation check Ramalingam C
2019-03-09 4:04 ` [PATCH v2 5/8] drm/i915/sysfs: Node for hdcp srm Ramalingam C
2019-03-11 13:57 ` Daniel Vetter
2019-03-09 4:04 ` [PATCH v2 6/8] drm: Add CP downstream_info property Ramalingam C
2019-03-09 4:04 ` [PATCH v2 7/8] drm/i915: Populate downstream info for HDCP1.4 Ramalingam C
2019-03-09 4:04 ` [PATCH v2 8/8] drm/i915: Populate downstream info for HDCP2.2 Ramalingam C
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=20190309040452.23699-1-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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