HDCP2.2 phase-II introduces below features: Addition of three connector properties HDCP Content Type HDCP Topology 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. uevent for HDCP state change. HDCP 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. HDCP Topology: 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. Daniel has suggested about moving the SRM node implementation into DRM core. Still dome more clarification is required. Once that is done another respin on SRM patches are expected. 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] v3: property names are reworked [Pekka and Daniel] uevent is generated for HDCP state change. [Pekka and Daniel] Series can be cloned from github https://github.com/ramalingampc2008/drm-tip.git hdcp2_2_p2_v3 Test-with: <20190321174444.10099-1-ramalingam.c@xxxxxxxxx> Ramalingam C (10): 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 drm: uevent for connector status change drm/i915: uevent for HDCP status change drivers/gpu/drm/drm_atomic_uapi.c | 8 + drivers/gpu/drm/drm_connector.c | 149 ++++++++++ drivers/gpu/drm/drm_sysfs.c | 28 ++ 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 | 407 ++++++++++++++++++++++++++-- include/drm/drm_connector.h | 27 ++ include/drm/drm_hdcp.h | 33 +++ include/drm/drm_sysfs.h | 5 +- include/uapi/drm/drm_mode.h | 39 +++ 14 files changed, 743 insertions(+), 33 deletions(-) -- 2.19.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
