HDCP2.2 Phase II
Subsystems (3)
cover HDCP2.2 Phase II
HDCP2.2 phase-II mojorly adds below features:
Addition of three connector properties
CP_Content_Type
CP_SRM
CP_Downstream_Info
parsing for HDCP1.4 and 2.2 SRM Blobs
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_SRM:
This blob property is 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.
Work in progress to add the SRM support in the weston HDCP stack. Yet to publish the patches in the #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.
Test-with: [email protected]
Ramalingam C (10):
drm: Add CP content type property
drm/i915: Attach content type property
drm: Add CP System Renewability Msg Property drm/i915: Add HDCP SRM Blob parsing drm/i915: Add revocation check on HDCP1.4 Ksvs drm/i915: SRM parsing and revocation check for HDCP2
drm: Add CP downstream_info property drm/i915: Populate downstream info for HDCP1.4 drm/i915: Populate downstream info for HDCP2.2 drm/i915: debugfs: HDCP2.2 capability read
drivers/gpu/drm/drm_atomic_uapi.c | 23 +++ drivers/gpu/drm/drm_connector.c | 204 ++++++++++++++++++++ drivers/gpu/drm/i915/i915_debugfs.c | 13 +- drivers/gpu/drm/i915/intel_ddi.c | 23 ++- drivers/gpu/drm/i915/intel_drv.h | 11 +- drivers/gpu/drm/i915/intel_hdcp.c | 373 ++++++++++++++++++++++++++++++++++-- include/drm/drm_connector.h | 40 ++++ include/drm/drm_hdcp.h | 35 ++++ include/uapi/drm/drm_mode.h | 39 ++++ 9 files changed, 737 insertions(+), 24 deletions(-)
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 1/10 drm: Add CP content type property
This patch adds a DRM ENUM property to the selected connectors. This property is used for pass the protected content's type from userspace to kernel HDCP authentication.
Type of the stream is decided by the protected content providers as Type 0/1.
Type 0 content can be rendered on any HDCP protected display wires. But Type 1 content can be rendered only on HDCP2.2 protected paths.
So upon a content protection request with Type 1 as Content type from userspace, Kernel will declare success only if the HDCP2.2 authentication is successful.
--- drivers/gpu/drm/drm_atomic_uapi.c | 10 ++++++ drivers/gpu/drm/drm_connector.c | 64 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_connector.h | 15 +++++++++ include/uapi/drm/drm_mode.h | 4 +++ 4 files changed, 93 insertions(+)
drivers/gpu/drm/drm_atomic_uapi.c +10 -0
@@ -746,6 +746,14 @@ static int drm_atomic_connector_set_property(struct drm_connector *connector,return -EINVAL ; } state->content_protection = val; + }else if (property == connector->cp_content_type_property) { +if (state->content_protection != +DRM_MODE_CONTENT_PROTECTION_UNDESIRED && + state->cp_content_type != val) { +DRM_DEBUG_KMS ("Disable CP, then change Type\n" ); +return -EINVAL ; + } + state->cp_content_type = val; }else if (property == connector->colorspace_property) { state->colorspace = val; }else if (property == config->writeback_fb_id_property) {
@@ -822,6 +830,8 @@ drm_atomic_connector_get_property(struct drm_connector *connector, *val = state->scaling_mode; }else if (property == connector->content_protection_property) { *val = state->content_protection; + }else if (property == connector->cp_content_type_property) { + *val = state->cp_content_type; }else if (property == config->writeback_fb_id_property) {/* Writeback framebuffer is one-shot, write and forget */ *val =0 ;
drivers/gpu/drm/drm_connector.c +64 -0
82 lines not on this page · raw message
include/drm/drm_connector.h +15 -0
@@ -519,6 +519,12 @@ struct drm_connector_state {unsigned int content_type;/** +* @cp_content_type: Connector property to pass the type of protected +* content. This is most commonly used for HDCP. +*/ +unsigned int cp_content_type; + +/** * @scaling_mode: Connector property to control the * upscaling, mostly used for built-in panels. */
@@ -1036,6 +1042,12 @@ struct drm_connector {struct drm_property *colorspace_property;/** +* @cp_content_type_property: DRM ENUM property for type of +* Protected Content. +*/ +struct drm_property *cp_content_type_property; + +/** * @path_blob_ptr: * * DRM blob property data for the DP MST path property. This should only
@@ -1294,6 +1306,7 @@ const char *drm_get_dvi_i_select_name(int val);const char *drm_get_tv_subconnector_name (int val);const char *drm_get_tv_select_name (int val);const char *drm_get_content_protection_name (int val); +const char *drm_get_cp_content_type_name (int val);int drm_mode_create_dvi_i_properties (struct drm_device *dev);int drm_mode_create_tv_margin_properties (struct drm_device *dev);
@@ -1309,6 +1322,8 @@ int drm_connector_attach_vrr_capable_property( struct drm_connector *connector);int drm_connector_attach_content_protection_property (struct drm_connector *connector); +int drm_connector_attach_cp_content_type_property ( +struct drm_connector *connector);int drm_mode_create_aspect_ratio_property (struct drm_device *dev);int drm_mode_create_colorspace_property (struct drm_connector *connector);int drm_mode_create_content_type_property (struct drm_device *dev);
include/uapi/drm/drm_mode.h +4 -0
@@ -210,6 +210,10 @@ extern "C" {#define DRM_MODE_CONTENT_PROTECTION_DESIRED 1#define DRM_MODE_CONTENT_PROTECTION_ENABLED 2 +/* Content Type classification for HDCP2.2 vs others */ +#define DRM_MODE_CP_CONTENT_TYPE0 0 +#define DRM_MODE_CP_CONTENT_TYPE1 1 +struct drm_mode_modeinfo {__u32 clock;__u16 hdisplay;
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Maarten Lankhorst
maintainerRe: [Intel-gfx] [PATCH 01/10] drm: Add CP content type property
Op 26-02-2019 om 08:36 schreef Ramalingam C:
Quoted 28 lines
This patch adds a DRM ENUM property to the selected connectors. This property is used for pass the protected content's type from userspace to kernel HDCP authentication.
Type of the stream is decided by the protected content providers as Type 0/1.
Type 0 content can be rendered on any HDCP protected display wires. But Type 1 content can be rendered only on HDCP2.2 protected paths.
So upon a content protection request with Type 1 as Content type from userspace, Kernel will declare success only if the HDCP2.2 authentication is successful.
Signed-off-by Ramalingam C <[email protected]>--- drivers/gpu/drm/drm_atomic_uapi.c | 10 ++++++ drivers/gpu/drm/drm_connector.c | 64 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_connector.h | 15 +++++++++ include/uapi/drm/drm_mode.h | 4 +++ 4 files changed, 93 insertions(+)drivers/gpu/drm/drm_atomic_uapi.c +0
-0@@ -746,6 +746,14 @@ static int drm_atomic_connector_set_property(struct drm_connector *connector,return -EINVAL ;
drivers/gpu/drm/drm_atomic_uapi.c static int drm_atomic_connector_set_property(struct drm_connector *connector, · line 756
Quoted 10 lines
drivers/gpu/drm/drm_atomic_uapi.c +8
-0} state->content_protection = val; + }else if (property == connector->cp_content_type_property) { +if (state->content_protection != +DRM_MODE_CONTENT_PROTECTION_UNDESIRED && + state->cp_content_type != val) { +DRM_DEBUG_KMS ("Disable CP, then change Type\n" ); +return -EINVAL ; + } + state->cp_content_type = val;
You can't add checks in atomic_set_property.
Until we have the full state, we can't do any checks. This has to be done in the .atomic_check() callback.
Lets say atomic commit consists of the following:
Set Content_Protection to desired.
Set Content Type to Type 1.
atomic setprop will fail
Plus the check itself is bogus. We should be able to change HDCP strictness without a modeset, the same way we enable and disable HDCP 1.4 with a fastset.
Quoted 43 lines
drivers/gpu/drm/drm_atomic_uapi.c +2
-0}else if (property == connector->colorspace_property) { state->colorspace = val; }else if (property == config->writeback_fb_id_property) {@@ -822,6 +830,8 @@ drm_atomic_connector_get_property(struct drm_connector *connector, *val = state->scaling_mode; }else if (property == connector->content_protection_property) { *val = state->content_protection; + }else if (property == connector->cp_content_type_property) { + *val = state->cp_content_type; }else if (property == config->writeback_fb_id_property) {/* Writeback framebuffer is one-shot, write and forget */ *val =0 ;drivers/gpu/drm/drm_connector.c +16
-0@@ -853,6 +853,13 @@ static const struct drm_prop_enum_list hdmi_colorspaces[] = { { DRM_MODE_COLORIMETRY_DCI_P3_RGB_THEATER, "DCI-P3_RGB_Theater" }, }; +static struct drm_prop_enum_list drm_cp_content_type_enum_list[] = { + {DRM_MODE_CP_CONTENT_TYPE0 ,"Type 0" }, + {DRM_MODE_CP_CONTENT_TYPE1 ,"Type 1" }, +}; + +DRM_ENUM_NAME_FN (drm_get_cp_content_type_name, drm_cp_content_type_enum_list) +/** * DOC: standard connector properties * @@ -958,6 +965,25 @@ static const struct drm_prop_enum_list hdmi_colorspaces[] = {* the value transitions from ENABLED to DESIRED. This signifies the link * is no longer protected and userspace should take appropriate action * (whatever that might be). +* CP_Content_Type: +* This property is used by the userspace to configure the kernel with +* upcoming stream's content type. Content Type of a stream is decided by +* the owner of the stream, as Type 0 or Type 1. +* +* The value of the property can be one the below: +* - DRM_MODE_CP_CONTENT_TYPE0 = 0 +* Type 0 streams can be transmitted on a link which is encrypted +* with HDCP 1.4 or HDCP 2.2.
drivers/gpu/drm/drm_connector.c static const struct drm_prop_enum_list hdmi_colorspaces[] = { · line 986
Quoted 10 lines
drivers/gpu/drm/drm_connector.c +10
-0+* - DRM_MODE_CP_CONTENT_TYPE1 = 1 +* Type 1 streams can be transmitted on a link which is encrypted +* only with HDCP2.2. +* +* Please note this content type is introduced at HDCP2.2 and used in its +* authentication process. +* +* Guideline for programming: +* - Property state can be changed only when "Content Protection state is +* DRM_MODE_CONTENT_PROTECTION_UNDESIRED.
Why? We may need to force a modeset, but this looks like a silly restriction to expose this to userspace.
If userspace doesn't want a modeset, it can clear the DRM_MODE_ATOMIC_ALLOW_MODESET flag on atomic commit.
the intel_atomic_check() callback can force a modeset if required, and atomic core can fail if userspace didn't request it.
~Maarten
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 01/10] drm: Add CP content type property
Quoted 40 lines
-----Original Message-----
From: Maarten Lankhorst [mailto:[email protected]]
Sent: Tuesday, March 5, 2019 8:09 PM
To: C, Ramalingam <[email protected]>; [email protected]; [email protected]; [email protected]; Shankar, Uma <[email protected]>
Subject: Re: [Intel-gfx] [PATCH 01/10] drm: Add CP content type propertyOp 26-02-2019 om 08:36 schreef Ramalingam C:
Quoted 10 lines
This patch adds a DRM ENUM property to the selected connectors. This property is used for pass the protected content's type from userspace to kernel HDCP authentication.
Type of the stream is decided by the protected content providers as Type 0/1.
Type 0 content can be rendered on any HDCP protected display wires. But Type 1 content can be rendered only on HDCP2.2 protected paths.
Quoted 8 lines
So upon a content protection request with Type 1 as Content type from userspace, Kernel will declare success only if the HDCP2.2 authentication is successful.
Signed-off-by Ramalingam C <[email protected]>--- drivers/gpu/drm/drm_atomic_uapi.c | 10 ++++++ drivers/gpu/drm/drm_connector.c | 64+++++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/drm_atomic_uapi.c static int
Quoted 10 lines
include/drm/drm_connector.h | 15 +++++++++ include/uapi/drm/drm_mode.h | 4 +++ 4 files changed, 93 insertions(+)drivers/gpu/drm/drm_atomic_uapi.c +0
-0@@ -746,6 +746,14 @@ static intdrm_atomic_connector_set_property(struct
drm_connector*connector,
Quoted 13 lines
drivers/gpu/drm/drm_atomic_uapi.c static int drm_atomic_connector_set_property(struct drm_connector *connector, · line 756
Quoted 11 lines
drivers/gpu/drm/drm_atomic_uapi.c +8
-0return -EINVAL ; } state->content_protection = val; + }else if (property == connector->cp_content_type_property) { +if (state->content_protection != +DRM_MODE_CONTENT_PROTECTION_UNDESIRED && + state->cp_content_type != val) { +DRM_DEBUG_KMS ("Disable CP, then change Type\n" ); +return -EINVAL ; + } + state->cp_content_type = val;You can't add checks in
atomic_set_property.
Thanks Maarten for the review.
I am afraid we have the similar check for content_protection, just above this.
Quoted 4 lines
Until we have the full state, we can't do any checks. This has to be done in the .atomic_check() callback.
Quoted 8 lines
Lets say atomic commit consists of the following:
SetContent_Protectionto desired.
Set Content Type to Type 1.
atomic setprop will failPlus the check itself is bogus. We should be able to change HDCP strictness without a modeset, the same way we enable and disable HDCP 1.4 with a fastset.
This is not modeset mandating, but the sequence of hdcp_disable->change Type->hdcp_enable from userspace. Reason is we need to redo the hdcp authenticate with new Type value.
Alternate approach would be kernel performing disable and enable on Type change request from userspace. For this we could disable hdcp at intel_hdcp_atomic_check and re-enable with new Type value at atomic_commit.
I thought it is better to leave the required preparation (disable and enable of hdcp) to userspace. But if we prefer to push that into kernel also it is doable. Share your opinion please.
Quoted 60 lines
drivers/gpu/drm/drm_atomic_uapi.c static int drm_atomic_connector_set_property(struct drm_connector *connector,
Quoted 5 lines
drivers/gpu/drm/drm_atomic_uapi.c +1
-0} else if (property == connector->colorspace_property) { state->colorspace = val; } else if (property == config->writeback_fb_id_property) { @@ -822,6 +830,8 @@ drm_atomic_connector_get_property(struct drm_connector*connector,
drivers/gpu/drm/drm_connector.c static const struct drm_prop_enum_list
Quoted 14 lines
drivers/gpu/drm/drm_atomic_uapi.c +2
-0*val = state->scaling_mode; }else if (property == connector->content_protection_property) { *val = state->content_protection; + }else if (property == connector->cp_content_type_property) { + *val = state->cp_content_type; }else if (property == config->writeback_fb_id_property) {/* Writeback framebuffer is one-shot, write and forget */ *val =0 ;(quoted diff) +0
-0
b/drivers/gpu/drm/drm_connector.cindex07d65a16c623..5d7738e1e977100644drivers/gpu/drm/drm_connector.c +0
-0@@ -853,6 +853,13 @@ static const struct drm_prop_enum_listhdmi_colorspaces[] = {
drivers/gpu/drm/drm_connector.c static const struct drm_prop_enum_list · line 853
Quoted 1 line
drivers/gpu/drm/drm_connector.c +0
-0{ DRM_MODE_COLORIMETRY_DCI_P3_RGB_THEATER, "DCI-
P3_RGB_Theater" },drivers/gpu/drm/drm_connector.c static const struct drm_prop_enum_list
Quoted 13 lines
drivers/gpu/drm/drm_connector.c +7
-0}; +static struct drm_prop_enum_list drm_cp_content_type_enum_list[] = { + {DRM_MODE_CP_CONTENT_TYPE0 ,"Type 0" }, + {DRM_MODE_CP_CONTENT_TYPE1 ,"Type 1" }, }; + +DRM_ENUM_NAME_FN (drm_get_cp_content_type_name, +drm_cp_content_type_enum_list) +/** * DOC: standard connector properties * @@ -958,6 +965,25 @@ static const struct drm_prop_enum_listhdmi_colorspaces[] = {
Quoted 12 lines
drivers/gpu/drm/drm_connector.c +9
-0* the value transitions from ENABLED to DESIRED. This signifies the link * is no longer protected and userspace should take appropriate action * (whatever that might be). +* CP_Content_Type: +* This property is used by the userspace to configure the kernel with +* upcoming stream's content type. Content Type of a stream is decided by +* the owner of the stream, as Type 0 or Type 1. +* +* The value of the property can be one the below: +* - DRM_MODE_CP_CONTENT_TYPE0 = 0 +* Type 0 streams can be transmitted on a link which is encrypted +* with HDCP 1.4 or HDCP 2.2. drivers/gpu/drm/drm_connector.c static const struct drm_prop_enum_list hdmi_colorspaces[] = { · line 986
Quoted 10 lines
drivers/gpu/drm/drm_connector.c +10
-0+* - DRM_MODE_CP_CONTENT_TYPE1 = 1 +* Type 1 streams can be transmitted on a link which is encrypted +* only with HDCP2.2. +* +* Please note this content type is introduced at HDCP2.2 and used in its +* authentication process. +* +* Guideline for programming: +* - Property state can be changed only when "Content Protection state is +* DRM_MODE_CONTENT_PROTECTION_UNDESIRED.
Quoted 8 lines
Why? We may need to force a modeset, but this looks like a silly restriction to expose this to userspace.
If userspace doesn't want a modeset, it can clear the
DRM_MODE_ATOMIC_ALLOW_MODESETflag on atomic commit.the
intel_atomic_check()callback can force a modeset if required, and atomic core can fail if userspace didn't request it.
As I have explained above this doesn't force modeset. Just expecting userspace to disable hdcp before changing the Type value.
--Ram
Quoted 2 lines
~Maarten
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/10 drm/i915: Attach content type property
In reply to Ramalingam CAttaches the content type property for HDCP2.2 capable connectors.
Implements the update of content type from property and apply the restriction on HDCP version selection.
--- drivers/gpu/drm/i915/intel_ddi.c | 21 +++++++++++++++------ drivers/gpu/drm/i915/intel_drv.h | 2 +- drivers/gpu/drm/i915/intel_hdcp.c | 18 +++++++++++++++--- 3 files changed, 31 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/intel_ddi.c +15 -6
@@ -3499,7 +3499,8 @@ static void intel_enable_ddi(struct intel_encoder *encoder,/* Enable hdcp if it's desired */ if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_DESIRED ) -intel_hdcp_enable (to_intel_connector (conn_state->connector)); +intel_hdcp_enable (to_intel_connector (conn_state->connector), + (u8 )conn_state->cp_content_type); } static void intel_disable_ddi_dp(struct intel_encoder *encoder,
@@ -3562,21 +3563,29 @@ static void intel_ddi_update_pipe_dp(struct intel_encoder *encoder,intel_panel_update_backlight (encoder, crtc_state, conn_state); } -static void intel_ddi_update_pipe (struct intel_encoder *encoder, +static void intel_ddi_update_hdcp (struct intel_encoder *encoder,const struct intel_crtc_state *crtc_state,const struct drm_connector_state *conn_state) { -if (!intel_crtc_has_type (crtc_state,INTEL_OUTPUT_HDMI )) -intel_ddi_update_pipe_dp (encoder, crtc_state, conn_state); -if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_DESIRED ) -intel_hdcp_enable (to_intel_connector (conn_state->connector)); +intel_hdcp_enable (to_intel_connector (conn_state->connector), + (u8 )conn_state->cp_content_type);else if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_UNDESIRED )intel_hdcp_disable (to_intel_connector (conn_state->connector)); } +static void intel_ddi_update_pipe (struct intel_encoder *encoder, +const struct intel_crtc_state *crtc_state, +const struct drm_connector_state *conn_state) +{ +if (!intel_crtc_has_type (crtc_state,INTEL_OUTPUT_HDMI )) +intel_ddi_update_pipe_dp (encoder, crtc_state, conn_state); + +intel_ddi_update_hdcp (encoder, crtc_state, conn_state); +} +static void intel_ddi_set_fia_lane_count (struct intel_encoder *encoder,const struct intel_crtc_state *pipe_config,enum port port)
drivers/gpu/drm/i915/intel_drv.h +1 -1
@@ -2151,7 +2151,7 @@ void intel_hdcp_atomic_check(struct drm_connector *connector, struct drm_connector_state *new_state);int intel_hdcp_init (struct intel_connector *connector,const struct intel_hdcp_shim *hdcp_shim); -int intel_hdcp_enable (struct intel_connector *connector); +int intel_hdcp_enable (struct intel_connector *connector,u8 content_type);int intel_hdcp_disable (struct intel_connector *connector);bool is_hdcp_supported (struct drm_i915_private *dev_priv,enum port port);bool intel_hdcp_capable (struct intel_connector *connector);
drivers/gpu/drm/i915/intel_hdcp.c +15 -3
@@ -1782,6 +1782,12 @@ static void intel_hdcp2_init(struct intel_connector *connector)return ; } + ret =drm_connector_attach_cp_content_type_property (&connector->base); +if (ret) { +kfree (hdcp->port_data.streams); +return ; + } + hdcp->hdcp2_supported = true; }
@@ -1811,7 +1817,7 @@ int intel_hdcp_init(struct intel_connector *connector,return 0 ; } -int intel_hdcp_enable (struct intel_connector *connector) +int intel_hdcp_enable (struct intel_connector *connector,u8 content_type) {struct intel_hdcp *hdcp = &connector->hdcp;unsigned long check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ;
@@ -1823,6 +1829,8 @@ int intel_hdcp_enable(struct intel_connector *connector)mutex_lock (&hdcp->mutex);WARN_ON (hdcp->value ==DRM_MODE_CONTENT_PROTECTION_ENABLED ); + hdcp->content_type = content_type; +/* * Considering that HDCP2.2 is more secure than HDCP1.4, If the setup * is capable of HDCP2.2, it is preferred to use HDCP2.2.
@@ -1833,8 +1841,12 @@ int intel_hdcp_enable(struct intel_connector *connector) check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; } -/* When HDCP2.2 fails, HDCP1.4 will be attempted */ -if (ret &&intel_hdcp_capable (connector)) { +/* +* When HDCP2.2 fails and Content Type is not Type1, HDCP1.4 will +* be attempted. +*/ +if (ret &&intel_hdcp_capable (connector) && + hdcp->content_type !=DRM_MODE_CP_CONTENT_TYPE1 ) { ret =_intel_hdcp_enable (connector); }
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Maarten Lankhorst
maintainerRe: [Intel-gfx] [PATCH 02/10] drm/i915: Attach content type property
Op 26-02-2019 om 08:36 schreef Ramalingam C:
Quoted 11 lines
Attaches the content type property for HDCP2.2 capable connectors.
Implements the update of content type from property and apply the restriction on HDCP version selection.
Signed-off-by Ramalingam C <[email protected]>--- drivers/gpu/drm/i915/intel_ddi.c | 21 +++++++++++++++------ drivers/gpu/drm/i915/intel_drv.h | 2 +- drivers/gpu/drm/i915/intel_hdcp.c | 18 +++++++++++++++--- 3 files changed, 31 insertions(+), 10 deletions(-)
This should probably be the last patch, because we can only enable HDCP 2.2 with all patches merged?
Quoted 102 lines
drivers/gpu/drm/i915/intel_ddi.c +15
-6@@ -3499,7 +3499,8 @@ static void intel_enable_ddi(struct intel_encoder *encoder,/* Enable hdcp if it's desired */ if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_DESIRED ) -intel_hdcp_enable (to_intel_connector (conn_state->connector)); +intel_hdcp_enable (to_intel_connector (conn_state->connector), + (u8 )conn_state->cp_content_type); } static void intel_disable_ddi_dp(struct intel_encoder *encoder,@@ -3562,21 +3563,29 @@ static void intel_ddi_update_pipe_dp(struct intel_encoder *encoder,intel_panel_update_backlight (encoder, crtc_state, conn_state); } -static void intel_ddi_update_pipe (struct intel_encoder *encoder, +static void intel_ddi_update_hdcp (struct intel_encoder *encoder,const struct intel_crtc_state *crtc_state,const struct drm_connector_state *conn_state) { -if (!intel_crtc_has_type (crtc_state,INTEL_OUTPUT_HDMI )) -intel_ddi_update_pipe_dp (encoder, crtc_state, conn_state); -if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_DESIRED ) -intel_hdcp_enable (to_intel_connector (conn_state->connector)); +intel_hdcp_enable (to_intel_connector (conn_state->connector), + (u8 )conn_state->cp_content_type);else if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_UNDESIRED )intel_hdcp_disable (to_intel_connector (conn_state->connector)); } +static void intel_ddi_update_pipe (struct intel_encoder *encoder, +const struct intel_crtc_state *crtc_state, +const struct drm_connector_state *conn_state) +{ +if (!intel_crtc_has_type (crtc_state,INTEL_OUTPUT_HDMI )) +intel_ddi_update_pipe_dp (encoder, crtc_state, conn_state); + +intel_ddi_update_hdcp (encoder, crtc_state, conn_state); +} +static void intel_ddi_set_fia_lane_count (struct intel_encoder *encoder,const struct intel_crtc_state *pipe_config,enum port port)drivers/gpu/drm/i915/intel_drv.h +1
-1@@ -2151,7 +2151,7 @@ void intel_hdcp_atomic_check(struct drm_connector *connector, struct drm_connector_state *new_state);int intel_hdcp_init (struct intel_connector *connector,const struct intel_hdcp_shim *hdcp_shim); -int intel_hdcp_enable (struct intel_connector *connector); +int intel_hdcp_enable (struct intel_connector *connector,u8 content_type);int intel_hdcp_disable (struct intel_connector *connector);bool is_hdcp_supported (struct drm_i915_private *dev_priv,enum port port);bool intel_hdcp_capable (struct intel_connector *connector);drivers/gpu/drm/i915/intel_hdcp.c +9
-2@@ -1782,6 +1782,12 @@ static void intel_hdcp2_init(struct intel_connector *connector)return ; } + ret =drm_connector_attach_cp_content_type_property (&connector->base); +if (ret) { +kfree (hdcp->port_data.streams); +return ; + } + hdcp->hdcp2_supported = true; }@@ -1811,7 +1817,7 @@ int intel_hdcp_init(struct intel_connector *connector,return 0 ; } -int intel_hdcp_enable (struct intel_connector *connector) +int intel_hdcp_enable (struct intel_connector *connector,u8 content_type) {struct intel_hdcp *hdcp = &connector->hdcp;unsigned long check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ;@@ -1823,6 +1829,8 @@ int intel_hdcp_enable(struct intel_connector *connector)mutex_lock (&hdcp->mutex);WARN_ON (hdcp->value ==DRM_MODE_CONTENT_PROTECTION_ENABLED ); + hdcp->content_type = content_type; +/* * Considering that HDCP2.2 is more secure than HDCP1.4, If the setup * is capable of HDCP2.2, it is preferred to use HDCP2.2. @@ -1833,8 +1841,12 @@ int intel_hdcp_enable(struct intel_connector *connector) check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; } -/* When HDCP2.2 fails, HDCP1.4 will be attempted */
drivers/gpu/drm/i915/intel_hdcp.c int intel_hdcp_enable(struct intel_connector *connector) · line 1852
Quoted 10 lines
drivers/gpu/drm/i915/intel_hdcp.c +6
-1-if (ret &&intel_hdcp_capable (connector)) { +/* +* When HDCP2.2 fails and Content Type is not Type1, HDCP1.4 will +* be attempted. +*/ +if (ret &&intel_hdcp_capable (connector) && + hdcp->content_type !=DRM_MODE_CP_CONTENT_TYPE1 ) { ret =_intel_hdcp_enable (connector); }
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH 3/10 drm: Add CP System Renewability Msg Property
In reply to Ramalingam CThis patch adds a drm blob property to the selected connector. This property will be used to pass the SRM Blob ID from userspace to kernel.
Revocated ksv list from SRM Table will be used by the kernel in the HDCP authentication.
Kernel doesn't validate the incoming SRM table or store it in non-volatile storage. So it is expected that userspace will provide the latest valid SRM table on every power cycle before the HDCP authentication starts.
--- drivers/gpu/drm/drm_atomic_uapi.c | 10 ++++++++ drivers/gpu/drm/drm_connector.c | 52 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_connector.h | 13 ++++++++++ 3 files changed, 75 insertions(+)
drivers/gpu/drm/drm_atomic_uapi.c +10 -0
@@ -754,6 +754,14 @@ static int drm_atomic_connector_set_property(struct drm_connector *connector,return -EINVAL ; } state->cp_content_type = val; + }else if (property == connector->cp_srm_property) { +if (state->content_protection != +DRM_MODE_CONTENT_PROTECTION_UNDESIRED && + state->cp_srm_blob_id != val) { +DRM_DEBUG_KMS ("Disable CP, then change SRM Blob\n" ); +return -EINVAL ; + } + state->cp_srm_blob_id = val; }else if (property == connector->colorspace_property) { state->colorspace = val; }else if (property == config->writeback_fb_id_property) {
@@ -832,6 +840,8 @@ drm_atomic_connector_get_property(struct drm_connector *connector, *val = state->content_protection; }else if (property == connector->cp_content_type_property) { *val = state->cp_content_type; + }else if (property == connector->cp_srm_property) { + *val = state->cp_srm_blob_id; }else if (property == config->writeback_fb_id_property) {/* Writeback framebuffer is one-shot, write and forget */ *val =0 ;
drivers/gpu/drm/drm_connector.c +52 -0
64 lines not on this page · raw message
include/drm/drm_connector.h +13 -0
@@ -525,6 +525,12 @@ struct drm_connector_state {unsigned int cp_content_type;/** +* @cp_srm_blob_id: Connector property to pass the SRM table for content +* protection. This is most commonly used for HDCP. +*/ +unsigned int cp_srm_blob_id; + +/** * @scaling_mode: Connector property to control the * upscaling, mostly used for built-in panels. */
@@ -1048,6 +1054,12 @@ struct drm_connector {struct drm_property *cp_content_type_property;/** +* @cp_srm_property: DRM BLOB property for content +* protection SRM information. +*/ +struct drm_property *cp_srm_property; + +/** * @path_blob_ptr: * * DRM blob property data for the DP MST path property. This should only
@@ -1324,6 +1336,7 @@ int drm_connector_attach_content_protection_property( struct drm_connector *connector);int drm_connector_attach_cp_content_type_property (struct drm_connector *connector); +int drm_connector_attach_cp_srm_property (struct drm_connector *connector);int drm_mode_create_aspect_ratio_property (struct drm_device *dev);int drm_mode_create_colorspace_property (struct drm_connector *connector);int drm_mode_create_content_type_property (struct drm_device *dev);
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 4/10 drm/i915: Add HDCP SRM Blob parsing
In reply to Ramalingam CThis patch adds a drm blob property to selected connectors. And also adds capability to parse the new HDCP1.4 srm blob passed through cp_srm_property.
The revocated KSV list and their counts are stored in
the intel_hdcp. This list should be used for revocation check of BKSVs in first stage HDCP authentication and for revocation check of ksv_fifo in second stage authentication.
--- drivers/gpu/drm/i915/intel_ddi.c | 6 +- drivers/gpu/drm/i915/intel_drv.h | 8 ++- drivers/gpu/drm/i915/intel_hdcp.c | 147 +++++++++++++++++++++++++++++++++++++- include/drm/drm_hdcp.h | 14 ++++ 4 files changed, 170 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/intel_ddi.c +4 -2
@@ -3500,7 +3500,8 @@ static void intel_enable_ddi(struct intel_encoder *encoder,if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_DESIRED )intel_hdcp_enable (to_intel_connector (conn_state->connector), - (u8 )conn_state->cp_content_type); + (u8 )conn_state->cp_content_type, + conn_state->cp_srm_blob_id); } static void intel_disable_ddi_dp(struct intel_encoder *encoder,
@@ -3570,7 +3571,8 @@ static void intel_ddi_update_hdcp(struct intel_encoder *encoder,if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_DESIRED )intel_hdcp_enable (to_intel_connector (conn_state->connector), - (u8 )conn_state->cp_content_type); + (u8 )conn_state->cp_content_type, + conn_state->cp_srm_blob_id);else if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_UNDESIRED )intel_hdcp_disable (to_intel_connector (conn_state->connector));
drivers/gpu/drm/i915/intel_drv.h +7 -1
@@ -482,6 +482,11 @@ struct intel_hdcp {wait_queue_head_t cp_irq_queue;atomic_t cp_irq_count;int cp_irq_count_cached; + +/* list of Revocated KSVs and their count from SRM blob Parsing */ +unsigned int revocated_ksv_cnt; +u8 *revocated_ksv_list; +u32 srm_blob_id; };struct intel_connector {
@@ -2151,7 +2156,8 @@ void intel_hdcp_atomic_check(struct drm_connector *connector, struct drm_connector_state *new_state);int intel_hdcp_init (struct intel_connector *connector,const struct intel_hdcp_shim *hdcp_shim); -int intel_hdcp_enable (struct intel_connector *connector,u8 content_type); +int intel_hdcp_enable (struct intel_connector *connector,u8 content_type, +u32 srm_blob_id);int intel_hdcp_disable (struct intel_connector *connector);bool is_hdcp_supported (struct drm_i915_private *dev_priv,enum port port);bool intel_hdcp_capable (struct intel_connector *connector);
drivers/gpu/drm/i915/intel_hdcp.c +145 -2
167 lines not on this page · raw message
include/drm/drm_hdcp.h +14 -0
@@ -265,4 +265,18 @@ void drm_hdcp2_u32_to_seq_num(u8 seq_num[HDCP_2_2_SEQ_NUM_LEN], u32 val) seq_num[2] = val; } +#define DRM_HDCP_1_4_SRM_ID 0x8 +#define DRM_HDCP_1_4_VRL_LENGTH_SIZE 3 +#define DRM_HDCP_1_4_DCP_SIG_SIZE 40 + +struct hdcp_srm_header { +struct { +u8 reserved_hi:4 ; +u8 srm_id:4 ; +u8 reserved_lo; + } spec_indicator; +u16 srm_version; +u8 srm_gen_no; +} __packed; +#endif
Signature · 6 lines
2.7.4 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH 5/10 drm/i915: Add revocation check on HDCP1.4 Ksvs
In reply to Ramalingam CKSV list revocated by DCP LLC is provided as SRM Blob to kernel. Which is parsed and stored in intel_hdcp->revocated_ksv_list.
This patch adds the revocation check for BKSV and KSV_FIFO in HDCP1.4 authentication.
--- drivers/gpu/drm/i915/intel_hdcp.c | 67 ++++++++++++++++++++++++++++++++++----- 1 file changed, 59 insertions(+), 8 deletions(-)
drivers/gpu/drm/i915/intel_hdcp.c +59 -8
@@ -273,6 +273,45 @@ u32 intel_hdcp_get_repeater_ctl(struct intel_digital_port *intel_dig_port)return -EINVAL ; } +static inline void intel_hdcp_print_ksv (u8 *ksv) +{ +DRM_DEBUG_KMS ("\t%#04x, %#04x, %#04x, %#04x, %#04x\n" , *ksv, + *(ksv +1 ), *(ksv +2 ), *(ksv +3 ), *(ksv +4 )); +} + +/* Check if any of the KSV is revocated by DCP LLC through SRM table */ +static inline +bool intel_hdcp_ksvs_revocated (struct intel_hdcp *hdcp,u8 *ksvs,u32 ksv_count) +{ +u32 rev_ksv_cnt = hdcp->revocated_ksv_cnt; +u8 *rev_ksv_list = hdcp->revocated_ksv_list; +u32 cnt, i, j; + +/* If the Revocated ksv list is empty */ +if (!rev_ksv_cnt || !rev_ksv_list) +return false; + +for (cnt =0 ; cnt < ksv_count; cnt++) { + rev_ksv_list = hdcp->revocated_ksv_list; +for (i =0 ; i < rev_ksv_cnt; i++) { +for (j =0 ; j <DRM_HDCP_KSV_LEN ; j++) +if (*(ksvs + j) != *(rev_ksv_list + j)) { +break ; + }else if (j == (DRM_HDCP_KSV_LEN -1 )) { +DRM_DEBUG_KMS ("Revocated KSV is " ); +intel_hdcp_print_ksv (ksvs); +return true; + } +/* Move the offset to next KSV in the revocated list */ + rev_ksv_list +=DRM_HDCP_KSV_LEN ; + } + +/* Iterate to next ksv_offset */ + ksvs +=DRM_HDCP_KSV_LEN ; + } +return false; +} + static int intel_hdcp_validate_v_prime(struct intel_digital_port *intel_dig_port, const struct intel_hdcp_shim *shim,
@@ -490,9 +529,10 @@ int intel_hdcp_validate_v_prime(struct intel_digital_port *intel_dig_port,/* Implements Part 2 of the HDCP authorization procedure */ static -int intel_hdcp_auth_downstream (struct intel_digital_port *intel_dig_port, -const struct intel_hdcp_shim *shim) +int intel_hdcp_auth_downstream (struct intel_hdcp *hdcp, +struct intel_digital_port *intel_dig_port) { +const struct intel_hdcp_shim *shim = hdcp->shim;u8 bstatus[2 ], num_downstream, *ksv_fifo;int ret, i, tries =3 ;
@@ -531,6 +571,11 @@ int intel_hdcp_auth_downstream(struct intel_digital_port *intel_dig_port,if (ret) goto err; +if (intel_hdcp_ksvs_revocated (hdcp, ksv_fifo, num_downstream)) { +DRM_ERROR ("Revocated Ksv(s) in ksv_fifo\n" ); +return -EPERM ; + } +/* * When V prime mismatches, DP Spec mandates re-read of * V prime atleast twice.
@@ -557,9 +602,11 @@ int intel_hdcp_auth_downstream(struct intel_digital_port *intel_dig_port, }/* Implements Part 1 of the HDCP authorization procedure */ -static int intel_hdcp_auth (struct intel_digital_port *intel_dig_port, -const struct intel_hdcp_shim *shim) +static int intel_hdcp_auth (struct intel_connector *connector) { +struct intel_digital_port *intel_dig_port =conn_to_dig_port (connector); +struct intel_hdcp *hdcp = &connector->hdcp; +const struct intel_hdcp_shim *shim = hdcp->shim;struct drm_i915_private *dev_priv;enum port port;unsigned long r0_prime_gen_start;
@@ -625,6 +672,11 @@ static int intel_hdcp_auth(struct intel_digital_port *intel_dig_port,if (ret <0 )return ret; +if (intel_hdcp_ksvs_revocated (hdcp, bksv.shim,1 )) { +DRM_ERROR ("BKSV is revocated\n" ); +return -EPERM ; + } +I915_WRITE (PORT_HDCP_BKSVLO (port), bksv.reg[0 ]);I915_WRITE (PORT_HDCP_BKSVHI (port), bksv.reg[1 ]);
@@ -698,7 +750,7 @@ static int intel_hdcp_auth(struct intel_digital_port *intel_dig_port,*/ if (repeater_present) -return intel_hdcp_auth_downstream (intel_dig_port, shim); +return intel_hdcp_auth_downstream (hdcp, intel_dig_port);DRM_DEBUG_KMS ("HDCP is enabled (no repeater present)\n" );return 0 ;
@@ -735,7 +787,6 @@ static int _intel_hdcp_disable(struct intel_connector *connector)static int _intel_hdcp_enable (struct intel_connector *connector) { -struct intel_hdcp *hdcp = &connector->hdcp;struct drm_i915_private *dev_priv = connector->base.dev->dev_private;int i, ret, tries =3 ;
@@ -760,9 +811,9 @@ static int _intel_hdcp_enable(struct intel_connector *connector)/* Incase of authentication failures, HDCP spec expects reauth. */ for (i =0 ; i < tries; i++) { - ret =intel_hdcp_auth (conn_to_dig_port (connector), hdcp->shim); + ret =intel_hdcp_auth (connector);if (!ret) { - hdcp->hdcp_encrypted = true; + connector->hdcp.hdcp_encrypted = true;return 0 ; }
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 6/10 drm/i915: SRM parsing and revocation check for HDCP2
In reply to Ramalingam CSRM blob with hdcp2 id is parsed and parsed list of revoked ids is used in the authentication process to identify the compromised HDCP sinks.
--- drivers/gpu/drm/i915/intel_hdcp.c | 86 +++++++++++++++++++++++++++++++++++++-- include/drm/drm_hdcp.h | 20 +++++++++ 2 files changed, 103 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/intel_hdcp.c +83 -3
@@ -1244,6 +1244,12 @@ static int hdcp2_authentication_key_exchange(struct intel_connector *connector) hdcp->is_repeater =HDCP_2_2_RX_REPEATER (msgs.send_cert.rx_caps[2 ]); +if (intel_hdcp_ksvs_revocated (hdcp, + msgs.send_cert.cert_rx.receiver_id,1 )) { +DRM_ERROR ("Receiver ID is revocated\n" ); +return -EPERM ; + } +/* * Here msgs.no_stored_km will hold msgs corresponding to the km * stored also.
@@ -1402,7 +1408,7 @@ int hdcp2_authenticate_repeater_topology(struct intel_connector *connector) } msgs;const struct intel_hdcp_shim *shim = hdcp->shim;u8 *rx_info; -u32 seq_num_v; +u32 seq_num_v, device_cnt;int ret; ret = shim->read_2_2_msg(intel_dig_port, HDCP_2_2_REP_SEND_RECVID_LIST,
@@ -1427,6 +1433,14 @@ int hdcp2_authenticate_repeater_topology(struct intel_connector *connector)return -EINVAL ; } + device_cnt =HDCP_2_2_DEV_COUNT_HI (rx_info[0 ]) <<4 || +HDCP_2_2_DEV_COUNT_LO (rx_info[1 ]); +if (intel_hdcp_ksvs_revocated (hdcp, msgs.recvid_list.receiver_ids, + device_cnt)) { +DRM_ERROR ("Revoked receiver ID(s) is in list\n" ); +return -EPERM ; + } + ret =hdcp2_verify_rep_topology_prepare_ack (connector, &msgs.recvid_list, &msgs.rep_ack);
@@ -1982,12 +1996,72 @@ static int intel_hdcp_parse_srm(struct drm_connector *connector,return 0 ; } +static int intel_hdcp2_parse_srm (struct drm_connector *connector, +struct drm_property_blob *blob) +{ +struct intel_hdcp *hdcp = &(to_intel_connector (connector)->hdcp); +struct hdcp2_srm_header *header; +u32 vrl_length, ksv_count, ksv_sz; +u8 *buf; + +if (blob->length < (sizeof (struct hdcp2_srm_header ) + +DRM_HDCP_2_VRL_LENGTH_SIZE +DRM_HDCP_2_DCP_SIG_SIZE )) { +DRM_ERROR ("Invalid blob length\n" ); +return -EINVAL ; + } + + header = (struct hdcp2_srm_header *)blob->data; +DRM_DEBUG_KMS ("SRM ID: 0x%x, SRM Ver: 0x%x, SRM Gen No: 0x%x\n" , + header->spec_indicator.srm_id, +__swab16 (header->srm_version), header->srm_gen_no); +WARN_ON (header->spec_indicator.reserved); + buf = blob->data +sizeof (*header); + + vrl_length = (*buf <<16 | *(buf +1 ) <<8 | *(buf +2 )); +if (blob->length < (sizeof (struct hdcp2_srm_header ) + vrl_length) || + vrl_length < (DRM_HDCP_2_VRL_LENGTH_SIZE + +DRM_HDCP_2_DCP_SIG_SIZE )) { +DRM_ERROR ("Invalid blob length or vrl length\n" ); +return -EINVAL ; + } + +/* Length of the all vrls combined */ + vrl_length -= (DRM_HDCP_2_VRL_LENGTH_SIZE +DRM_HDCP_2_DCP_SIG_SIZE ); +if (!vrl_length) { +DRM_ERROR ("No vrl found\n" ); +return -EINVAL ; + } + + buf +=DRM_HDCP_2_VRL_LENGTH_SIZE ; + ksv_count = (*buf <<2 ) |DRM_HDCP_2_KSV_COUNT_2_LSBITS (*(buf +1 )); +if (!ksv_count) +return 0 ; + +kfree (hdcp->revocated_ksv_list); + hdcp->revocated_ksv_list =kzalloc (ksv_count *DRM_HDCP_KSV_LEN , +GFP_KERNEL ); +if (!hdcp->revocated_ksv_list) { +DRM_ERROR ("Out of Memory\n" ); +return -ENOMEM ; + } + + ksv_sz = ksv_count *DRM_HDCP_KSV_LEN ; + buf +=DRM_HDCP_2_NO_OF_DEV_PLUS_RESERVED_SZ ; + +DRM_DEBUG_KMS ("Revoked KSVs: %d\n" , ksv_count); +memcpy (hdcp->revocated_ksv_list, buf, ksv_sz); + hdcp->revocated_ksv_cnt = ksv_count; + +return 0 ; +} +static void intel_hdcp_update_srm (struct intel_connector *intel_connector,u32 srm_blob_id) {struct drm_connector *connector = &intel_connector->base;struct intel_hdcp *hdcp = &intel_connector->hdcp;struct drm_property_blob *blob; +u8 srm_id;DRM_DEBUG_KMS ("srm_blob_id %u\n" , srm_blob_id);
@@ -2002,8 +2076,14 @@ static void intel_hdcp_update_srm(struct intel_connector *intel_connector,if (!blob || !blob->data)return ; -if (!intel_hdcp_parse_srm (connector, blob)) - hdcp->srm_blob_id = srm_blob_id; + srm_id = *((u8 *)blob->data); +if (srm_id ==DRM_HDCP_SRM_ID ) { +if (!intel_hdcp_parse_srm (connector, blob)) + hdcp->srm_blob_id = srm_blob_id; + }else if (srm_id ==DRM_HDCP2_SRM_ID ) { +if (!intel_hdcp2_parse_srm (connector, blob)) + hdcp->srm_blob_id = srm_blob_id; + }drm_property_blob_put (blob); }
include/drm/drm_hdcp.h +20 -0
@@ -279,4 +279,24 @@ struct hdcp_srm_header { u8 srm_gen_no; } __packed; +#define DRM_HDCP_2_SRM_ID 0x9 +#define DRM_HDCP_2_INDICATOR 0x1 +#define DRM_HDCP_2_VRL_LENGTH_SIZE 3 +#define DRM_HDCP_2_DCP_SIG_SIZE 384 +#define DRM_HDCP_2_NO_OF_DEV_PLUS_RESERVED_SZ 4 + +#define DRM_HDCP_2_KSV_COUNT_2_LSBITS (byte) (((byte) & 0xC) >> 6) +#define DRM_HDCP_SRM_ID 0x80 +#define DRM_HDCP2_SRM_ID 0x91 + +struct hdcp2_srm_header { +struct { +u8 hdcp2_indicator:4 ; +u8 srm_id:4 ; +u8 reserved; + } spec_indicator; +u16 srm_version; +u8 srm_gen_no; +} __packed; +#endif
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 7/10 drm: Add CP downstream_info property
In reply to Ramalingam CThis patch adds CP downstream info blob property to the connectors. This enables the Userspace to read the information of HDCP authenticated downstream topology.
Driver will updated this blob with all downstream information at the end of the authentication.
Userspace need this informations to configure this platform as repeater, where KMD will be the downstream HDCP ports of the repeater and userspace implementation will act as upstream HDCP port.
--- drivers/gpu/drm/drm_atomic_uapi.c | 3 ++ drivers/gpu/drm/drm_connector.c | 88 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_connector.h | 12 ++++++ include/uapi/drm/drm_mode.h | 27 ++++++++++++ 4 files changed, 130 insertions(+)
drivers/gpu/drm/drm_atomic_uapi.c +3 -0
@@ -842,6 +842,9 @@ drm_atomic_connector_get_property(struct drm_connector *connector, *val = state->cp_content_type; }else if (property == connector->cp_srm_property) { *val = state->cp_srm_blob_id; + }else if (property == connector->cp_downstream_property) { + *val = connector->cp_downstream_blob_ptr ? + connector->cp_downstream_blob_ptr->base.id :0 ; }else if (property == config->writeback_fb_id_property) {/* Writeback framebuffer is one-shot, write and forget */ *val =0 ;
drivers/gpu/drm/drm_connector.c +88 -0
106 lines not on this page · raw message
include/drm/drm_connector.h +12 -0
@@ -1060,6 +1060,13 @@ struct drm_connector {struct drm_property *cp_srm_property;/** +* @cp_downstream_property: DRM BLOB property for content +* protection downstream information. +*/ +struct drm_property *cp_downstream_property; +struct drm_property_blob *cp_downstream_blob_ptr; + +/** * @path_blob_ptr: * * DRM blob property data for the DP MST path property. This should only
@@ -1337,6 +1344,11 @@ int drm_connector_attach_content_protection_property(int drm_connector_attach_cp_content_type_property (struct drm_connector *connector);int drm_connector_attach_cp_srm_property (struct drm_connector *connector); +int drm_connector_attach_cp_downstream_property ( +struct drm_connector *connector); +int drm_mode_connector_update_cp_downstream_property ( +struct drm_connector *connector, +const struct cp_downstream_info *info);int drm_mode_create_aspect_ratio_property (struct drm_device *dev);int drm_mode_create_colorspace_property (struct drm_connector *connector);int drm_mode_create_content_type_property (struct drm_device *dev);
include/uapi/drm/drm_mode.h +27 -0
@@ -214,6 +214,33 @@ extern "C" {#define DRM_MODE_CP_CONTENT_TYPE0 0#define DRM_MODE_CP_CONTENT_TYPE1 1 +#define DRM_MODE_HDCP_KSV_LEN 5 +#define DRM_MODE_HDCP_MAX_DEVICE_CNT 127 + +struct cp_downstream_info { +/* KSV of immediate HDCP Sink. In Little-Endian Format. */ +char bksv[DRM_MODE_HDCP_KSV_LEN ]; + +/* Whether Immediate HDCP sink is a repeater? */ +bool is_repeater; + +/* Depth received from immediate downstream repeater */ +__u8 depth; + +/* Device count received from immediate downstream repeater */ +__u32 device_count; + +/* +* Max buffer required to hold ksv list received from immediate +* repeater. In this array first device_count * DRM_MODE_HDCP_KSV_LEN +* will hold the valid ksv bytes. +* If authentication specification is +* HDCP1.4 - each KSV's Bytes will be in Little-Endian format. +* HDCP2.2 - each KSV's Bytes will be in Big-Endian format. +*/ +char ksv_list[DRM_MODE_HDCP_KSV_LEN *DRM_MODE_HDCP_MAX_DEVICE_CNT ]; +}; +struct drm_mode_modeinfo {__u32 clock;__u16 hdisplay;
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 8/10 drm/i915: Populate downstream info for HDCP1.4
In reply to Ramalingam CImplements drm blob property cp_downstream_info property on HDCP capable connectors.
Downstream topology info is gathered across authentication stages and stored in intel_hdcp. When HDCP authentication is complete, new blob with latest downstream topology information is updated to cp_downstream_info property.
--- drivers/gpu/drm/i915/intel_drv.h | 2 ++ drivers/gpu/drm/i915/intel_hdcp.c | 32 +++++++++++++++++++++++++++++++- include/drm/drm_hdcp.h | 1 + include/uapi/drm/drm_mode.h | 5 +++++ 4 files changed, 39 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_drv.h +2 -0
@@ -487,6 +487,8 @@ struct intel_hdcp {unsigned int revocated_ksv_cnt;u8 *revocated_ksv_list;u32 srm_blob_id; + +struct cp_downstream_info *downstream_info; };struct intel_connector {
drivers/gpu/drm/i915/intel_hdcp.c +31 -1
@@ -563,6 +563,9 @@ int intel_hdcp_auth_downstream(struct intel_hdcp *hdcp,if (num_downstream ==0 )return -EINVAL ; + hdcp->downstream_info->device_count = num_downstream; + hdcp->downstream_info->depth =DRM_HDCP_DEPTH (bstatus[1 ]); + ksv_fifo =kcalloc (DRM_HDCP_KSV_LEN , num_downstream,GFP_KERNEL );if (!ksv_fifo)return -ENOMEM ;
@@ -576,6 +579,8 @@ int intel_hdcp_auth_downstream(struct intel_hdcp *hdcp,return -EPERM ; } +memcpy (hdcp->downstream_info->ksv_list, ksv_fifo, + num_downstream *DRM_HDCP_KSV_LEN );/* * When V prime mismatches, DP Spec mandates re-read of * V prime atleast twice.
@@ -677,15 +682,20 @@ static int intel_hdcp_auth(struct intel_connector *connector)return -EPERM ; } + hdcp->downstream_info->ver_in_force =DRM_MODE_HDCP14_IN_FORCE ; +memcpy (hdcp->downstream_info->bksv, bksv.shim,DRM_MODE_HDCP_KSV_LEN ); +I915_WRITE (PORT_HDCP_BKSVLO (port), bksv.reg[0 ]);I915_WRITE (PORT_HDCP_BKSVHI (port), bksv.reg[1 ]); ret = shim->repeater_present (intel_dig_port, &repeater_present);if (ret)return ret; -if (repeater_present) +if (repeater_present) {I915_WRITE (HDCP_REP_CTL ,intel_hdcp_get_repeater_ctl (intel_dig_port)); + hdcp->downstream_info->is_repeater = true; + } ret = shim->toggle_signalling (intel_dig_port, true);if (ret)
@@ -781,6 +791,13 @@ static int _intel_hdcp_disable(struct intel_connector *connector)return ret; } +memset (hdcp->downstream_info,0 ,sizeof (struct cp_downstream_info )); + +if (drm_mode_connector_update_cp_downstream_property ( + &connector->base, + connector->hdcp.downstream_info)) +DRM_ERROR ("Downstream_info update failed.\n" ); +DRM_DEBUG_KMS ("HDCP is disabled\n" );return 0 ; }
@@ -814,6 +831,10 @@ static int _intel_hdcp_enable(struct intel_connector *connector) ret =intel_hdcp_auth (connector);if (!ret) { connector->hdcp.hdcp_encrypted = true; +if (drm_mode_connector_update_cp_downstream_property ( + &connector->base, + connector->hdcp.downstream_info)) +DRM_ERROR ("Downstream_info update failed.\n" );return 0 ; }
@@ -1874,6 +1895,15 @@ int intel_hdcp_init(struct intel_connector *connector,if (ret)return ret; + ret =drm_connector_attach_cp_downstream_property (&connector->base); +if (ret) +return ret; + + hdcp->downstream_info =kzalloc (sizeof (*hdcp->downstream_info), +GFP_KERNEL ); +if (!hdcp->downstream_info) +return -ENOMEM ; + hdcp->shim = shim;mutex_init (&hdcp->mutex);INIT_DELAYED_WORK (&hdcp->check_work, intel_hdcp_check_work);
include/drm/drm_hdcp.h +1 -0
@@ -23,6 +23,7 @@#define DRM_HDCP_V_PRIME_PART_LEN 4#define DRM_HDCP_V_PRIME_NUM_PARTS 5#define DRM_HDCP_NUM_DOWNSTREAM (x) (x & 0x7f) +#define DRM_HDCP_DEPTH (x) ((x) & 0x7)#define DRM_HDCP_MAX_CASCADE_EXCEEDED (x) (x & BIT(3))#define DRM_HDCP_MAX_DEVICE_EXCEEDED (x) (x & BIT(7))
include/uapi/drm/drm_mode.h +5 -0
@@ -216,8 +216,13 @@ extern "C" {#define DRM_MODE_HDCP_KSV_LEN 5#define DRM_MODE_HDCP_MAX_DEVICE_CNT 127 +#define DRM_MODE_HDCP14_IN_FORCE (1 << 0) +#define DRM_MODE_HDCP22_IN_FORCE (1 << 1)struct cp_downstream_info { +/* Version of HDCP authenticated (1.4/2.2) */ +__u32 ver_in_force; +/* KSV of immediate HDCP Sink. In Little-Endian Format. */ char bksv[DRM_MODE_HDCP_KSV_LEN ];
Signature · 6 lines
2.7.4 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH 9/10 drm/i915: Populate downstream info for HDCP2.2
In reply to Ramalingam CPopulates the downstream info for HDCP2.2 encryption also. On success of encryption Blob is updated.
Additional two variable are added to downstream info blob. Such as ver_in_force and content type.
--- drivers/gpu/drm/i915/intel_hdcp.c | 29 ++++++++++++++++++++++++++++- include/uapi/drm/drm_mode.h | 3 +++ 2 files changed, 31 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_hdcp.c +28 -1
@@ -1271,6 +1271,12 @@ static int hdcp2_authentication_key_exchange(struct intel_connector *connector)return -EPERM ; } + hdcp->downstream_info->ver_in_force =DRM_MODE_HDCP22_IN_FORCE ; + hdcp->downstream_info->content_type = hdcp->content_type; +memcpy (hdcp->downstream_info->bksv, msgs.send_cert.cert_rx.receiver_id, +HDCP_2_2_RECEIVER_ID_LEN ); + hdcp->downstream_info->is_repeater = hdcp->is_repeater; +/* * Here msgs.no_stored_km will hold msgs corresponding to the km * stored also.
@@ -1462,6 +1468,11 @@ int hdcp2_authenticate_repeater_topology(struct intel_connector *connector)return -EPERM ; } + hdcp->downstream_info->device_count = device_cnt; + hdcp->downstream_info->depth =HDCP_2_2_DEPTH (rx_info[0 ]); +memcpy (hdcp->downstream_info->ksv_list, msgs.recvid_list.receiver_ids, + device_cnt *HDCP_2_2_RECEIVER_ID_LEN ); + ret =hdcp2_verify_rep_topology_prepare_ack (connector, &msgs.recvid_list, &msgs.rep_ack);
@@ -1648,6 +1659,13 @@ static int _intel_hdcp2_enable(struct intel_connector *connector)if (ret) {DRM_DEBUG_KMS ("HDCP2 Type%d Enabling Failed. (%d)\n" , hdcp->content_type, ret); + +memset (hdcp->downstream_info,0 , +sizeof (struct cp_downstream_info )); +drm_mode_connector_update_cp_downstream_property ( + &connector->base, + hdcp->downstream_info); +return ret; }
@@ -1655,12 +1673,17 @@ static int _intel_hdcp2_enable(struct intel_connector *connector) connector->base.name, connector->base.base.id, hdcp->content_type); +drm_mode_connector_update_cp_downstream_property ( + &connector->base, + hdcp->downstream_info); hdcp->hdcp2_encrypted = true; +return 0 ; }static int _intel_hdcp2_disable (struct intel_connector *connector) { +struct intel_hdcp *hdcp = &connector->hdcp;int ret; DRM_DEBUG_KMS("[%s:%d] HDCP2.2 is being Disabled\n",
@@ -1671,8 +1694,12 @@ static int _intel_hdcp2_disable(struct intel_connector *connector)if (hdcp2_deauthenticate_port (connector) <0 )DRM_DEBUG_KMS ("Port deauth failed.\n" ); - connector->hdcp.hdcp2_encrypted = false; + hdcp->hdcp2_encrypted = false; +memset (hdcp->downstream_info,0 ,sizeof (struct cp_downstream_info )); +drm_mode_connector_update_cp_downstream_property ( + &connector->base, + hdcp->downstream_info);return ret; }
include/uapi/drm/drm_mode.h +3 -0
@@ -223,6 +223,9 @@ struct cp_downstream_info {/* Version of HDCP authenticated (1.4/2.2) */ __u32 ver_in_force; +/* Applicable only for HDCP2.2 */ +__u8 content_type; +/* KSV of immediate HDCP Sink. In Little-Endian Format. */ char bksv[DRM_MODE_HDCP_KSV_LEN ];
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 10/10 drm/i915: debugfs: HDCP2.2 capability read
In reply to Ramalingam CAdding the HDCP2.2 capability of HDCP src and sink info into debugfs entry "i915_hdcp_sink_capability"
This helps the userspace tests to skip the HDCP2.2 test on non HDCP2.2 sinks.
--- drivers/gpu/drm/i915/i915_debugfs.c | 13 +++++++++++-- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_hdcp.c | 2 +- 3 files changed, 13 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/i915_debugfs.c +11 -2
@@ -4762,6 +4762,7 @@ static int i915_hdcp_sink_capability_show(struct seq_file *m, void *data) {struct drm_connector *connector = m->private;struct intel_connector *intel_connector =to_intel_connector (connector); +bool hdcp_cap, hdcp2_cap;if (connector->status != connector_status_connected)return -ENODEV ;
@@ -4772,8 +4773,16 @@ static int i915_hdcp_sink_capability_show(struct seq_file *m, void *data)seq_printf (m,"%s:%d HDCP version: " , connector->name, connector->base.id); -seq_printf (m,"%s " , !intel_hdcp_capable (intel_connector) ? -"None" :"HDCP1.4" ); + hdcp_cap =intel_hdcp_capable (intel_connector); + hdcp2_cap =intel_hdcp2_capable (intel_connector); + +if (hdcp_cap) +seq_puts (m,"HDCP1.4 " ); +if (hdcp2_cap) +seq_puts (m,"HDCP2.2 " ); + +if (!hdcp_cap && !hdcp2_cap) +seq_puts (m,"None" );seq_puts (m,"\n" );return 0 ;
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -2163,6 +2163,7 @@ int intel_hdcp_enable(struct intel_connector *connector, u8 content_type,int intel_hdcp_disable (struct intel_connector *connector);bool is_hdcp_supported (struct drm_i915_private *dev_priv,enum port port);bool intel_hdcp_capable (struct intel_connector *connector); +bool intel_hdcp2_capable (struct intel_connector *connector);void intel_hdcp_component_init (struct drm_i915_private *dev_priv);void intel_hdcp_component_fini (struct drm_i915_private *dev_priv);void intel_hdcp_cleanup (struct intel_connector *connector);
drivers/gpu/drm/i915/intel_hdcp.c +1 -1
@@ -76,7 +76,7 @@ bool intel_hdcp_capable(struct intel_connector *connector) }/* Is HDCP2.2 capable on Platform and Sink */ -static bool intel_hdcp2_capable (struct intel_connector *connector) +bool intel_hdcp2_capable (struct intel_connector *connector) {struct drm_i915_private *dev_priv =to_i915 (connector->base.dev);struct intel_digital_port *intel_dig_port =conn_to_dig_port (connector);
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II
In reply to Ramalingam C== Series Details ==
== Series Details ==
Series: HDCP2.2 Phase II
URL : https://patchwork.freedesktop.org/series/57232/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d436a49061d8 drm: Add CP content type property
-:123: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#123: FILE: drivers/gpu/drm/drm_connector.c:1601:
+ ARRAY_SIZE(-:181: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #181: FILE: include/drm/drm_connector.h:1325:
+int drm_connector_attach_cp_content_type_property(
total: 0 errors, 0 warnings, 2 checks, 153 lines checked9637bf9bd9d9 drm/i915: Attach content type property112fc8797d7c drm: Add CP System Renewability Msg Propertyd3eae4abcd2b drm/i915: Add HDCP SRM Blob parsingc7cf67c7ec3e drm/i915: Add revocation check on HDCP1.4 Ksvs1ff0fb1cf24e drm/i915: SRM parsing and revocation check for HDCP2 c1068365cf3a drm: Add CP downstream_info property
-:13: WARNING:TYPO_SPELLING: 'informations' may be misspelled - perhaps 'information'? #13:
Userspace need this informations to configure this platform as repeater,
-:91: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #91: FILE: drivers/gpu/drm/drm_connector.c:1702:
+int drm_connector_attach_cp_downstream_property(
-:123: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #123: FILE: drivers/gpu/drm/drm_connector.c:1734:
+int drm_mode_connector_update_cp_downstream_property(
-:134: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #134: FILE: drivers/gpu/drm/drm_connector.c:1745:
+ ret = drm_property_replace_global_blob(dev,
+ &connector->cp_downstream_blob_ptr,
-:168: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #168: FILE: include/drm/drm_connector.h:1347:
+int drm_connector_attach_cp_downstream_property(
-:170: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #170: FILE: include/drm/drm_connector.h:1349:
+int drm_mode_connector_update_cp_downstream_property(
total: 0 errors, 1 warnings, 5 checks, 172 lines checked 0e9b016d27ad drm/i915: Populate downstream info for HDCP1.4 -:80: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #80: FILE: drivers/gpu/drm/i915/intel_hdcp.c:796:
+ if (drm_mode_connector_update_cp_downstream_property(
-:92: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #92: FILE: drivers/gpu/drm/i915/intel_hdcp.c:834:
+ if (drm_mode_connector_update_cp_downstream_property(
total: 0 errors, 0 warnings, 2 checks, 104 lines checked c1f5086d0622 drm/i915: Populate downstream info for HDCP2.2 -:50: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #50: FILE: drivers/gpu/drm/i915/intel_hdcp.c:1665:
+ drm_mode_connector_update_cp_downstream_property(
-:61: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #61: FILE: drivers/gpu/drm/i915/intel_hdcp.c:1676:
+ drm_mode_connector_update_cp_downstream_property(
-:83: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #83: FILE: drivers/gpu/drm/i915/intel_hdcp.c:1700:
+ drm_mode_connector_update_cp_downstream_property(
total: 0 errors, 0 warnings, 3 checks, 75 lines checked 89073ee51fc9 drm/i915: debugfs: HDCP2.2 capability read
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 5 lines · Ramalingam C
HDCP2.2 phase-II mojorly adds below features:
Addition of three connector properties
CP_Content_Type
CP_SRM
Not really clear why this is a connector property. Do we need different SRM for different connectors? My understanding of the spec is that we want one SRM globally (so not even per driver). I think a binary sysfs file in the drm class (in /sys/class/drm, not one of the subdirectories) would fit that. Plus make userspace simpler, since a cat srm_file > /sys/class/drm/cp_srm at boot-up is all we need.
Drivers can then just check with drm core for the latest srm file at the start of each hdcp transaction, and update it if there is one. Plus maybe a few functions to do sink filtering on the cpu - I think we need that for hdcp1.x on i915 too.
Other properties make sense on the connector I think. Also please spell out CP as content_protection in all the properties/interfaces, I think that would be good, in common lingo (see urban dictionary) cp has a different meaning.
-Daniel
Quoted 70 lines
CP_Downstream_Info
parsing for HDCP1.4 and 2.2 SRM Blobs
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_SRM:
This blob property is 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.Work in progress to add the SRM support in the weston HDCP stack. Yet to publish the patches in the #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_infosupport in the weston HDCP stack.Test-with: [email protected]
Ramalingam C (10):
drm: Add CP content type property
drm/i915: Attach content type property
drm: Add CP System Renewability Msg Property drm/i915: Add HDCP SRM Blob parsing drm/i915: Add revocation check on HDCP1.4 Ksvs drm/i915: SRM parsing and revocation check for HDCP2
drm: Add CPdownstream_infoproperty drm/i915: Populate downstream info for HDCP1.4 drm/i915: Populate downstream info for HDCP2.2 drm/i915: debugfs: HDCP2.2 capability readdrivers/gpu/drm/drm_atomic_uapi.c | 23 +++ drivers/gpu/drm/drm_connector.c | 204 ++++++++++++++++++++ drivers/gpu/drm/i915/i915_debugfs.c | 13 +- drivers/gpu/drm/i915/intel_ddi.c | 23 ++- drivers/gpu/drm/i915/intel_drv.h | 11 +- drivers/gpu/drm/i915/intel_hdcp.c | 373 ++++++++++++++++++++++++++++++++++-- include/drm/drm_connector.h | 40 ++++ include/drm/drm_hdcp.h | 35 ++++ include/uapi/drm/drm_mode.h | 39 ++++ 9 files changed, 737 insertions(+), 24 deletions(-)--
2.7.4
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.BAT: success for HDCP2.2 Phase II
In reply to Ramalingam C== Series Details ==
== Series Details ==
Series: HDCP2.2 Phase II
URL : https://patchwork.freedesktop.org/series/57232/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5659 -> Patchwork_12303
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/57232/revisions/1/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_12303:
### IGT changes ###
#### Possible regressions ####
* {igt@kms_content_protection@srm} (NEW):
- {fi-icl-y}: NOTRUN -> SKIP
New tests
---------
New tests have been introduced between CI_DRM_5659 and Patchwork_12303:
### New IGT tests (1) ###
* igt@kms_content_protection@srm:
- Statuses : 37 skip(s)
- Exec time: [0.0, 0.00] s
Known issues
------------
Here are the changes found in Patchwork_12303 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-n3050: PASS -> SKIP [fdo#109271]
* igt@i915_pm_rpm@basic-rte:
- fi-bsw-n3050: PASS -> FAIL [fdo#108800]
* igt@kms_content_protection@atomic:
- fi-skl-gvtdvm: NOTRUN -> FAIL [fdo#108597] / [fdo#108739] +1
- fi-ivb-3520m: NOTRUN -> SKIP [fdo#109271] +2
- fi-elk-e7500: NOTRUN -> SKIP [fdo#109271] +2
- fi-whl-u: NOTRUN -> SKIP [fdo#109271] +2
- fi-cfl-8700k: NOTRUN -> SKIP [fdo#109271] +2
- fi-pnv-d510: NOTRUN -> SKIP [fdo#109271] +2
- fi-snb-2520m: NOTRUN -> SKIP [fdo#109271] +2
- fi-skl-guc: NOTRUN -> SKIP [fdo#109271] +2
- fi-hsw-peppy: NOTRUN -> SKIP [fdo#109271] +2
- fi-apl-guc: NOTRUN -> FAIL [fdo#108597] / [fdo#108739] +1* igt@kms_content_protection@legacy:
- fi-cfl-guc: NOTRUN -> SKIP [fdo#109271] +2
- fi-bxt-j4205: NOTRUN -> SKIP [fdo#109271] +2
- fi-kbl-r: NOTRUN -> SKIP [fdo#109271] +2
- fi-cfl-8109u: NOTRUN -> FAIL [fdo#108739] +1
- fi-kbl-guc: NOTRUN -> SKIP [fdo#109271] +2
- fi-bdw-gvtdvm: NOTRUN -> SKIP [fdo#109271] +2
- fi-gdg-551: NOTRUN -> SKIP [fdo#109271] +2
- fi-bwr-2160: NOTRUN -> SKIP [fdo#109271] +2
- fi-hsw-4770: NOTRUN -> SKIP [fdo#109271] +2
- fi-ivb-3770: NOTRUN -> SKIP [fdo#109271] +2
- fi-kbl-8809g: NOTRUN -> SKIP [fdo#109271] +2* {igt@kms_content_protection@srm} (NEW):
- fi-ilk-650: NOTRUN -> SKIP [fdo#109271] +2
- fi-bsw-n3050: NOTRUN -> SKIP [fdo#109271] +2
- fi-bsw-kefka: NOTRUN -> SKIP [fdo#109271] +2
- fi-hsw-4770r: NOTRUN -> SKIP [fdo#109271] +2
- fi-cfl-8109u: NOTRUN -> SKIP [fdo#109271]
- fi-blb-e6850: NOTRUN -> SKIP [fdo#109271] +2
- fi-kbl-7500u: NOTRUN -> SKIP [fdo#109271]
- fi-bdw-5557u: NOTRUN -> SKIP [fdo#109271] +2
- fi-kbl-7567u: NOTRUN -> SKIP [fdo#109271]
- fi-skl-6600u: NOTRUN -> SKIP [fdo#109271] +2
- fi-kbl-7560u: NOTRUN -> SKIP [fdo#109271] +2
- fi-byt-j1900: NOTRUN -> SKIP [fdo#109271] +2
- fi-apl-guc: NOTRUN -> SKIP [fdo#109271]
- fi-byt-n2820: NOTRUN -> SKIP [fdo#109271] +2
- fi-skl-6700k2: NOTRUN -> SKIP [fdo#109271]
- fi-skl-6260u: NOTRUN -> SKIP [fdo#109271]
- fi-skl-gvtdvm: NOTRUN -> SKIP [fdo#109271]
- fi-kbl-x1275: NOTRUN -> SKIP [fdo#109271] * igt@kms_pipe_crc_basic@hang-read-crc-pipe-c:
- fi-cfl-8109u: PASS -> FAIL [fdo#109495]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#108597]: https://bugs.freedesktop.org/show_bug.cgi?id=108597
[fdo#108739]: https://bugs.freedesktop.org/show_bug.cgi?id=108739
[fdo#108800]: https://bugs.freedesktop.org/show_bug.cgi?id=108800
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109495]: https://bugs.freedesktop.org/show_bug.cgi?id=109495
[fdo#109527]: https://bugs.freedesktop.org/show_bug.cgi?id=109527
Participating hosts (44 -> 38)
------------------------------
Missing (6): fi-ilk-m540 fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-ctg-p8600 fi-icl-u3
Build changes
-------------
* IGT: IGT_4854 -> IGTPW_2521
* Linux: CI_DRM_5659 -> Patchwork_12303
CI_DRM_5659: bffea990c63087245e8501df82fd45f24ce6ad1f @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_2521: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2521/
IGT_4854: 06b0830fb948b9b632342cd26100342aa01cbc79 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12303: 89073ee51fc9833ef92d07adf075bea255011c7b @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
89073ee51fc9 drm/i915: debugfs: HDCP2.2 capability read c1f5086d0622 drm/i915: Populate downstream info for HDCP2.2 0e9b016d27ad drm/i915: Populate downstream info for HDCP1.4 c1068365cf3a drm: Add CP downstream_info property 1ff0fb1cf24e drm/i915: SRM parsing and revocation check for HDCP2 c7cf67c7ec3e drm/i915: Add revocation check on HDCP1.4 Ksvs d3eae4abcd2b drm/i915: Add HDCP SRM Blob parsing 112fc8797d7c drm: Add CP System Renewability Msg Property 9637bf9bd9d9 drm/i915: Attach content type property d436a49061d8 drm: Add CP content type property
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12303/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.IGT: success for HDCP2.2 Phase II
In reply to Ramalingam C== Series Details ==
== Series Details ==
Series: HDCP2.2 Phase II
URL : https://patchwork.freedesktop.org/series/57232/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5659_full -> Patchwork_12303_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_12303_full:
### IGT changes ###
#### Possible regressions ####
* {igt@kms_content_protection@type1} (NEW):
- shard-iclb: NOTRUN -> SKIP +2
New tests
---------
New tests have been introduced between CI_DRM_5659_full and Patchwork_12303_full:
### New IGT tests (3) ###
* igt@kms_content_protection@srm:
- Statuses : 6 skip(s)
- Exec time: [0.0] s
* igt@kms_content_protection@type1:
- Statuses : 6 skip(s)
- Exec time: [0.0] s
* igt@kms_content_protection@type1_mei_interface:
- Statuses : 6 skip(s)
- Exec time: [0.00, 0.02] s
Known issues
------------
Here are the changes found in Patchwork_12303_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_flink_basic@bad-open:
- shard-snb: PASS -> INCOMPLETE [fdo#105411] / [fdo#107469]
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-snb: NOTRUN -> SKIP [fdo#109271] +97
* igt@gem_mocs_settings@mocs-settings-vebox:
- shard-iclb: NOTRUN -> SKIP [fdo#109287] +2
* igt@gem_softpin@evict-snoop-interruptible:
- shard-iclb: NOTRUN -> SKIP [fdo#109312]
* igt@i915_pm_rpm@gem-mmap-gtt:
- shard-iclb: PASS -> DMESG-WARN [fdo#107724] +3
* igt@kms_atomic_transition@3x-modeset-transitions-nonblocking-fencing:
- shard-snb: NOTRUN -> SKIP [fdo#109271] / [fdo#109278] +7
* igt@kms_atomic_transition@5x-modeset-transitions-nonblocking:
- shard-glk: NOTRUN -> SKIP [fdo#109271] / [fdo#109278]
* igt@kms_busy@extended-modeset-hang-newfb-render-b:
- shard-snb: NOTRUN -> DMESG-WARN [fdo#107956]
* igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a:
- shard-hsw: PASS -> DMESG-WARN [fdo#107956]
* igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c:
- shard-glk: NOTRUN -> DMESG-WARN [fdo#107956]
* igt@kms_busy@extended-pageflip-hang-oldfb-render-d:
- shard-kbl: NOTRUN -> SKIP [fdo#109271] / [fdo#109278] +4
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic:
- shard-glk: PASS -> FAIL [fdo#108145]
* igt@kms_chamelium@hdmi-crc-single:
- shard-iclb: NOTRUN -> SKIP [fdo#109284]
* igt@kms_color@pipe-c-legacy-gamma:
- shard-glk: PASS -> FAIL [fdo#104782]
* {igt@kms_content_protection@srm} (NEW):
- shard-glk: NOTRUN -> SKIP [fdo#109271] +15
* {igt@kms_content_protection@type1} (NEW):
- shard-hsw: NOTRUN -> SKIP [fdo#109271] +2
* igt@kms_cursor_crc@cursor-128x128-random:
- shard-iclb: NOTRUN -> FAIL [fdo#103232]
* igt@kms_cursor_crc@cursor-64x21-random:
- shard-apl: PASS -> FAIL [fdo#103232] +3
- shard-kbl: PASS -> FAIL [fdo#103232]
* igt@kms_cursor_crc@cursor-alpha-opaque:
- shard-kbl: PASS -> FAIL [fdo#109350]
- shard-apl: PASS -> FAIL [fdo#109350]
- shard-glk: PASS -> FAIL [fdo#109350] * igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-ytiled:
- shard-glk: PASS -> FAIL [fdo#103184]
* igt@kms_fbcon_fbt@fbc:
- shard-iclb: PASS -> DMESG-WARN [fdo#109593]
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible:
- shard-iclb: NOTRUN -> SKIP [fdo#109274] +1
* igt@kms_flip@2x-modeset-vs-vblank-race-interruptible:
- shard-glk: PASS -> FAIL [fdo#103060]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-cpu:
- shard-apl: PASS -> FAIL [fdo#103167] +1
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen:
- shard-glk: PASS -> FAIL [fdo#103167] +2
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: PASS -> INCOMPLETE [fdo#103665]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-render:
- shard-kbl: NOTRUN -> SKIP [fdo#109271] +34
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen:
- shard-iclb: PASS -> FAIL [fdo#103167] +7
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-indfb-pgflip-blt:
- shard-iclb: NOTRUN -> SKIP [fdo#109280] +2
* igt@kms_invalid_dotclock:
- shard-iclb: NOTRUN -> SKIP [fdo#109310]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-iclb: PASS -> INCOMPLETE [fdo#107713]
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparant-fb:
- shard-apl: NOTRUN -> FAIL [fdo#108145]
- shard-kbl: NOTRUN -> FAIL [fdo#108145]
* igt@kms_plane_multiple@atomic-pipe-a-tiling-x:
- shard-apl: PASS -> FAIL [fdo#103166] +5
* igt@kms_plane_multiple@atomic-pipe-b-tiling-none:
- shard-glk: PASS -> FAIL [fdo#103166] +3
- shard-kbl: PASS -> FAIL [fdo#103166] +1
* igt@kms_plane_multiple@atomic-pipe-b-tiling-x:
- shard-iclb: PASS -> FAIL [fdo#103166] +3
* igt@kms_plane_scaling@pipe-a-scaler-with-rotation:
- shard-iclb: NOTRUN -> DMESG-WARN [fdo#107724]
* igt@kms_plane_scaling@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> SKIP [fdo#109271] / [fdo#109278] +3
* igt@kms_psr@psr2_sprite_render:
- shard-iclb: NOTRUN -> SKIP [fdo#109441]
* igt@kms_rotation_crc@multiplane-rotation-cropping-top:
- shard-kbl: PASS -> FAIL [fdo#109016]
* igt@kms_vblank@pipe-a-ts-continuation-dpms-rpm:
- shard-kbl: PASS -> FAIL [fdo#104894] +2
- shard-apl: PASS -> FAIL [fdo#104894] +2
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: NOTRUN -> SKIP [fdo#109276] +5
* igt@prime_vgem@fence-write-hang:
- shard-apl: NOTRUN -> SKIP [fdo#109271] +34
* igt@runner@aborted:
- shard-iclb: NOTRUN -> FAIL [fdo#109593]
* igt@v3d_get_param@get-bad-param:
- shard-iclb: NOTRUN -> SKIP [fdo#109315]
#### Possible fixes ####
* igt@i915_pm_rpm@gem-idle:
- shard-iclb: DMESG-WARN [fdo#107724] -> PASS +6
* igt@i915_pm_rpm@legacy-planes-dpms:
- shard-iclb: INCOMPLETE [fdo#108840] / [fdo#109369] -> PASS
* igt@i915_suspend@sysfs-reader:
- shard-iclb: INCOMPLETE [fdo#107713] -> PASS
* igt@kms_atomic_transition@plane-all-modeset-transition:
- shard-kbl: INCOMPLETE [fdo#103665] -> PASS +1
- shard-apl: INCOMPLETE [fdo#103927] -> PASS
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic:
- shard-apl: FAIL [fdo#106510] / [fdo#108145] -> PASS
* igt@kms_color@pipe-b-legacy-gamma:
- shard-apl: FAIL [fdo#104782] -> PASS
- shard-kbl: FAIL [fdo#104782] -> PASS
* igt@kms_cursor_crc@cursor-64x21-sliding:
- shard-apl: FAIL [fdo#103232] -> PASS +4
- shard-kbl: FAIL [fdo#103232] -> PASS
* igt@kms_cursor_crc@cursor-size-change:
- shard-glk: FAIL [fdo#103232] -> PASS
* igt@kms_flip@flip-vs-expired-vblank:
- shard-iclb: FAIL [fdo#105363] -> PASS
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-gtt:
- shard-apl: FAIL [fdo#103167] -> PASS +4
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move:
- shard-iclb: FAIL [fdo#103167] -> PASS +5
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-mmap-cpu:
- shard-glk: FAIL [fdo#103167] -> PASS +4
* igt@kms_plane@pixel-format-pipe-b-planes-source-clamping:
- shard-apl: FAIL [fdo#108948] -> PASS +1
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-glk: INCOMPLETE [fdo#103359] / [k.org#198133] -> PASS
* igt@kms_plane@plane-position-covered-pipe-c-planes:
- shard-glk: FAIL [fdo#103166] -> PASS +2
* igt@kms_plane@plane-position-hole-dpms-pipe-b-planes:
- shard-snb: SKIP [fdo#109271] -> PASS
* igt@kms_plane_multiple@atomic-pipe-a-tiling-none:
- shard-apl: FAIL [fdo#103166] -> PASS
* igt@kms_plane_multiple@atomic-pipe-a-tiling-y:
- shard-iclb: FAIL [fdo#103166] -> PASS +1
* igt@kms_rotation_crc@multiplane-rotation-cropping-bottom:
- shard-kbl: DMESG-FAIL [fdo#105763] -> PASS
* igt@prime_busy@hang-vebox:
- shard-hsw: FAIL [fdo#108807] -> PASS
#### Warnings ####
* igt@i915_pm_backlight@fade_with_suspend:
- shard-iclb: FAIL [fdo#107847] -> DMESG-FAIL [fdo#107724] / [fdo#107847]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103060]: https://bugs.freedesktop.org/show_bug.cgi?id=103060
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103184]: https://bugs.freedesktop.org/show_bug.cgi?id=103184
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#104782]: https://bugs.freedesktop.org/show_bug.cgi?id=104782
[fdo#104894]: https://bugs.freedesktop.org/show_bug.cgi?id=104894
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#106510]: https://bugs.freedesktop.org/show_bug.cgi?id=106510
[fdo#107469]: https://bugs.freedesktop.org/show_bug.cgi?id=107469
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#107847]: https://bugs.freedesktop.org/show_bug.cgi?id=107847
[fdo#107956]: https://bugs.freedesktop.org/show_bug.cgi?id=107956
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108807]: https://bugs.freedesktop.org/show_bug.cgi?id=108807
[fdo#108840]: https://bugs.freedesktop.org/show_bug.cgi?id=108840
[fdo#108948]: https://bugs.freedesktop.org/show_bug.cgi?id=108948
[fdo#109016]: https://bugs.freedesktop.org/show_bug.cgi?id=109016
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109287]: https://bugs.freedesktop.org/show_bug.cgi?id=109287
[fdo#109310]: https://bugs.freedesktop.org/show_bug.cgi?id=109310
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#109350]: https://bugs.freedesktop.org/show_bug.cgi?id=109350
[fdo#109369]: https://bugs.freedesktop.org/show_bug.cgi?id=109369
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109593]: https://bugs.freedesktop.org/show_bug.cgi?id=109593
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (7 -> 6)
------------------------------
Missing (1): shard-skl
Build changes
-------------
* IGT: IGT_4854 -> IGTPW_2521
* Linux: CI_DRM_5659 -> Patchwork_12303
CI_DRM_5659: bffea990c63087245e8501df82fd45f24ce6ad1f @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_2521: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2521/
IGT_4854: 06b0830fb948b9b632342cd26100342aa01cbc79 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12303: 89073ee51fc9833ef92d07adf075bea255011c7b @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12303/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx