HDCP 2.2 Comp fixes
Subsystems (3)
v3 cover HDCP 2.2 Comp fixes
Adding ram's RB on patch1 and a new patch to fix DP HDCP Auth.
Anshuman Gupta (2):
drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg drm/i915/hdcp: Return 0 on config_stream_type() +ve return
drivers/gpu/drm/i915/display/intel_hdcp.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
Signature · 6 lines
2.24.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 1/2 drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg
HDCP Repeater initializes seq_num_V to 0 at the beginning of hdcp Session i.e. after AKE_init received, refer HDCP 2.2 Spec HDMI PAGE 19, DP PAGE 20.
HDCP 2.2 Comp specs 1B-06 test verifies that whether DUT considers failure of authentication if the repeater provides a non-zero value in seq_num_V in the first, RepeaterAuth_Send_ReceiverID_List message.
Make sure that HDCP repeater initializes seq_num_V to zero at beginning of session i.e. after AKE_Init, fail the Auth if there is non zero seq_num_V.
v2:
- Used existing hdcp2_encrypted flag instead of
declaring new flag. [Ram]
--- drivers/gpu/drm/i915/display/intel_hdcp.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/gpu/drm/i915/display/intel_hdcp.c +6 -0
@@ -1462,6 +1462,12 @@ int hdcp2_authenticate_repeater_topology(struct intel_connector *connector) seq_num_v =drm_hdcp_be24_to_cpu ((const u8 *)msgs.recvid_list.seq_num_v); +if (!hdcp->hdcp2_encrypted && seq_num_v) { +drm_dbg_kms (&dev_priv->drm, +"Non zero Seq_num_v at first RecvId_List msg\n" ); +return -EINVAL ; + } +if (seq_num_v < hdcp->seq_num_v) {/* Roll over of the seq_num_v from repeater. Reauthenticate. */ DRM_DEBUG_KMS ("Seq_num_v roll over.\n" );
Signature · 6 lines
2.24.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 2/2 drm/i915/hdcp: Return 0 on config_stream_type() +ve return
In reply to Anshuman GuptaAs DP shim's config_stream_type returns size of message to be written in case of success therefore on config_stream_type success return a zero success value in order to succeed the HDCP auth.
--- drivers/gpu/drm/i915/display/intel_hdcp.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_hdcp.c +3 -1
@@ -1538,7 +1538,9 @@ static int hdcp2_authenticate_sink(struct intel_connector *connector) ret = shim->config_stream_type (intel_dig_port, hdcp->is_repeater, hdcp->content_type); -if (ret <0 ) +if (ret >=0 ) + ret =0 ; +else return ret; }
Signature · 6 lines
2.24.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/hdcp: Return 0 on config_stream_type() +ve return
Quoted 16 lines · Anshuman Gupta
As DP shim's
config_stream_typereturns size of message to be written in case of success therefore onconfig_stream_typesuccess return a zero success value in order to succeed the HDCP auth.CC Ramalingam C <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/display/intel_hdcp.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_hdcp.c +0
-0
drivers/gpu/drm/i915/display/intel_hdcp.c static int hdcp2_authenticate_sink(struct intel_connector *connector) · line 1543
Quoted 7 lines
drivers/gpu/drm/i915/display/intel_hdcp.c +3
-1@@ -1538,7 +1538,9 @@ static int hdcp2_authenticate_sink(struct intel_connector *connector) ret = shim->config_stream_type (intel_dig_port, hdcp->is_repeater, hdcp->content_type); -if (ret <0 ) +if (ret >=0 ) + ret =0 ; +else
Anshuman, could we convert the return value of intel_dp_hdcp2_config_stream_type to return the 0 or -ve, as the functions is for configuring thr stream_type? Returning the bytes written is not useful for the caller.
-Ram.
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_hdcp.c +0
-0return ret; }Signature · 1 line
2.24.0
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v4 2/2 drm/i915/hdcp: Fix config_stream_type() ret value
In reply to Anshuman GuptaDP shim's config_stream_type considered to be succeeded when return value of intel_dp_hdcp2_write_msg() equals to size of message to be written, it makes config_stream_type to return a zero success value in order to succeed the HDCP auth.
v2:
- config_stream_type() returns 0 on success. [Ram]
--- drivers/gpu/drm/i915/display/intel_dp.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_dp.c +7 -1
@@ -6448,6 +6448,7 @@ staticint intel_dp_hdcp2_config_stream_type (struct intel_digital_port *intel_dig_port,bool is_repeater,u8 content_type) { +int ret;struct hdcp2_dp_errata_stream_type stream_type_msg;if (is_repeater)
@@ -6463,8 +6464,13 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, stream_type_msg.msg_id =HDCP_2_2_ERRATA_DP_STREAM_TYPE ; stream_type_msg.stream_type = content_type; -return intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg, + ret =intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg,sizeof (stream_type_msg)); + +if (ret ==sizeof (stream_type_msg)) +return 0 ; +else +return ret; } static
Signature · 6 lines
2.25.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v4 2/2] drm/i915/hdcp: Fix config_stream_type() ret value
Quoted 27 lines · Anshuman Gupta
DP shim's
config_stream_typeconsidered to be succeeded when return value ofintel_dp_hdcp2_write_msg()equals to size of message to be written, it makesconfig_stream_typeto return a zero success value in order to succeed the HDCP auth.v2:
-config_stream_type()returns 0 on success. [Ram]CC Ramalingam C <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_dp.c +1
-0@@ -6448,6 +6448,7 @@ staticint intel_dp_hdcp2_config_stream_type (struct intel_digital_port *intel_dig_port,bool is_repeater,u8 content_type) { +int ret;struct hdcp2_dp_errata_stream_type stream_type_msg;if (is_repeater)
drivers/gpu/drm/i915/display/intel_dp.c int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, · line 6470
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-1@@ -6463,8 +6464,13 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, stream_type_msg.msg_id =HDCP_2_2_ERRATA_DP_STREAM_TYPE ; stream_type_msg.stream_type = content_type; -return intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg, + ret =intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg,sizeof (stream_type_msg)); + +if (ret ==sizeof (stream_type_msg))
return ret < 0 ? ret : 0;
Above statement will be sufficient here?
-Ram
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-0+return 0 ; + else + return ret; } staticSignature · 1 line
2.25.1
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v4 2/2] drm/i915/hdcp: Fix config_stream_type() ret value
Quoted 31 lines · Ramalingam C
Quoted 30 lines · Anshuman Gupta
DP shim's
config_stream_typeconsidered to be succeeded when return value ofintel_dp_hdcp2_write_msg()equals to size of message to be written, it makesconfig_stream_typeto return a zero success value in order to succeed the HDCP auth.v2:
-config_stream_type()returns 0 on success. [Ram]CC Ramalingam C <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_dp.c +1
-0@@ -6448,6 +6448,7 @@ staticint intel_dp_hdcp2_config_stream_type (struct intel_digital_port *intel_dig_port,bool is_repeater,u8 content_type) { +int ret;struct hdcp2_dp_errata_stream_type stream_type_msg;if (is_repeater)@@ -6463,8 +6464,13 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, stream_type_msg.msg_id =HDCP_2_2_ERRATA_DP_STREAM_TYPE ; stream_type_msg.stream_type = content_type;
Quoted 7 lines
drivers/gpu/drm/i915/display/intel_dp.c int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, · line 6470
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-1-return intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg, + ret =intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg,sizeof (stream_type_msg)); + +if (ret ==sizeof (stream_type_msg))return ret < 0 ? ret : 0;
Above statement will be sufficient here?
IMHO if intel_dp_hdcp2_write_msg() is being abstracted, it should return success only when its return value is equals to size to be written.
yes, return ret == sizeof(stream_type_msg) ? 0 : ret would make sense to reduced line of code.
I can change that.
Thanks,
Anshuman.
Quoted 11 lines
-Ram
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-0+return 0 ; + else + return ret; } staticSignature · 1 line
2.25.1
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v4 2/2] drm/i915/hdcp: Fix config_stream_type() ret value
Quoted 39 lines · Anshuman Gupta
Quoted 31 lines · Ramalingam C
Quoted 30 lines · Anshuman Gupta
DP shim's
config_stream_typeconsidered to be succeeded when return value ofintel_dp_hdcp2_write_msg()equals to size of message to be written, it makesconfig_stream_typeto return a zero success value in order to succeed the HDCP auth.v2:
-config_stream_type()returns 0 on success. [Ram]CC Ramalingam C <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_dp.c +1
-0@@ -6448,6 +6448,7 @@ staticint intel_dp_hdcp2_config_stream_type (struct intel_digital_port *intel_dig_port,bool is_repeater,u8 content_type) { +int ret;struct hdcp2_dp_errata_stream_type stream_type_msg;if (is_repeater)@@ -6463,8 +6464,13 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, stream_type_msg.msg_id =HDCP_2_2_ERRATA_DP_STREAM_TYPE ; stream_type_msg.stream_type = content_type;Quoted 7 lines
drivers/gpu/drm/i915/display/intel_dp.c int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, · line 6470
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-1-return intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg, + ret =intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg,sizeof (stream_type_msg)); + +if (ret ==sizeof (stream_type_msg))return ret < 0 ? ret : 0;
Above statement will be sufficient here?
Quoted 6 lines
IMHO if
intel_dp_hdcp2_write_msg()is being abstracted, it should return success only when its return value is equals to size to be written.
yes, return ret ==sizeof(stream_type_msg)? 0 : ret would make sense to reduced line of code.
I can change that.
intel_dp_hdcp2_write_msg can't return >0 and != sizeof(stream_type_msg) because that is error scenario hence return will be <0. So check for the size of msg size is not compulsary
I am fine with this too.
-Ram
Quoted 10 lines
Thanks,
Anshuman.Quoted 7 lines
-Ram
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-0+return 0 ; + else + return ret; }
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
drivers/gpu/drm/i915/display/intel_dp.c +0
-0staticSignature · 1 line
2.25.1
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v4 2/2 drm/i915/hdcp: Fix config_stream_type() ret value
In reply to Anshuman GuptaDP shim's config_stream_type considered to be succeeded when return value of intel_dp_hdcp2_write_msg() equals to size of message to be written, it makes config_stream_type to return a zero success value in order to succeed the HDCP auth.
v2:
- config_stream_type() returns 0 on success. [Ram]
--- drivers/gpu/drm/i915/display/intel_dp.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_dp.c +5 -1
@@ -6448,6 +6448,7 @@ staticint intel_dp_hdcp2_config_stream_type (struct intel_digital_port *intel_dig_port,bool is_repeater,u8 content_type) { +int ret;struct hdcp2_dp_errata_stream_type stream_type_msg;if (is_repeater)
@@ -6463,8 +6464,11 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, stream_type_msg.msg_id =HDCP_2_2_ERRATA_DP_STREAM_TYPE ; stream_type_msg.stream_type = content_type; -return intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg, + ret =intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg,sizeof (stream_type_msg)); + +return ret <0 ? ret :0 ; + } static
Signature · 6 lines
2.25.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v4 2/2] drm/i915/hdcp: Fix config_stream_type() ret value
Quoted 19 lines · Anshuman Gupta
DP shim's
config_stream_typeconsidered to be succeeded when return value ofintel_dp_hdcp2_write_msg()equals to size of message to be written, it makesconfig_stream_typeto return a zero success value in order to succeed the HDCP auth.v2:
-config_stream_type()returns 0 on success. [Ram]CC Ramalingam C <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_dp.c +0
-0
drivers/gpu/drm/i915/display/intel_dp.c static · line 6451
Quoted 4 lines
drivers/gpu/drm/i915/display/intel_dp.c +1
-0@@ -6448,6 +6448,7 @@ staticint intel_dp_hdcp2_config_stream_type (struct intel_digital_port *intel_dig_port,bool is_repeater,u8 content_type) { +int ret;
Order it as per the length of the declations. long->short...
drivers/gpu/drm/i915/display/intel_dp.c int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, · line 6471
Quoted 13 lines
drivers/gpu/drm/i915/display/intel_dp.c +4
-1struct hdcp2_dp_errata_stream_type stream_type_msg;if (is_repeater)@@ -6463,8 +6464,11 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, stream_type_msg.msg_id =HDCP_2_2_ERRATA_DP_STREAM_TYPE ; stream_type_msg.stream_type = content_type; -return intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg, + ret =intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg,sizeof (stream_type_msg)); + +return ret <0 ? ret :0 ; +
With that fixed, Looks Good to me.
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_dp.c +0
-0} staticSignature · 1 line
2.25.1
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v4 2/2 drm/i915/hdcp: Fix config_stream_type() ret value
In reply to Anshuman GuptaDP shim's config_stream_type considered to be succeeded when return value of intel_dp_hdcp2_write_msg() equals to size of message to be written, it makes config_stream_type to return a zero success value in order to succeed the HDCP auth.
v2:
- config_stream_type() returns 0 on success. [Ram]
--- drivers/gpu/drm/i915/display/intel_dp.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_dp.c +5 -1
@@ -6449,6 +6449,7 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, bool is_repeater, u8 content_type) {struct hdcp2_dp_errata_stream_type stream_type_msg; +int ret;if (is_repeater)return 0 ;
@@ -6463,8 +6464,11 @@ int intel_dp_hdcp2_config_stream_type(struct intel_digital_port *intel_dig_port, stream_type_msg.msg_id =HDCP_2_2_ERRATA_DP_STREAM_TYPE ; stream_type_msg.stream_type = content_type; -return intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg, + ret =intel_dp_hdcp2_write_msg (intel_dig_port, &stream_type_msg,sizeof (stream_type_msg)); + +return ret <0 ? ret :0 ; + } static
Signature · 6 lines
2.25.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for HDCP 2.2 Comp fixes
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: HDCP 2.2 Comp fixes
URL : https://patchwork.freedesktop.org/series/73708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7975 -> Patchwork_16646
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/index.html
Known issues
------------
Here are the changes found in Patchwork_16646 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_close_race@basic-threads:
- fi-hsw-peppy: [PASS][1] -> [INCOMPLETE][2] ([i915#694] / [i915#816])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-hsw-peppy/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-hsw-peppy/igt@[email protected]
* igt@gem_flink_basic@double-flink:
- fi-tgl-y: [PASS][3] -> [DMESG-WARN][4] ([CI#94] / [i915#402])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-tgl-y/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-tgl-y/igt@[email protected]
#### Possible fixes ####
* igt@gem_close_race@basic-threads:
- fi-hsw-4770r: [TIMEOUT][5] ([fdo#112271] / [i915#1084]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-hsw-4770r/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-hsw-4770r/igt@[email protected]
* igt@gem_exec_suspend@basic-s4-devices:
- fi-tgl-y: [FAIL][7] ([CI#94]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-tgl-y/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-tgl-y/igt@[email protected]
* igt@gem_mmap@basic:
- fi-tgl-y: [DMESG-WARN][9] ([CI#94] / [i915#402]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-tgl-y/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-tgl-y/igt@[email protected]
* igt@i915_selftest@live_execlists:
- fi-tgl-y: [INCOMPLETE][11] ([CI#94] / [i915#647]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-tgl-y/igt@i915_selftest@live_execlists.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-tgl-y/igt@i915_selftest@live_execlists.html
- fi-icl-y: [DMESG-FAIL][13] ([fdo#108569]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-icl-y/igt@i915_selftest@live_execlists.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-icl-y/igt@i915_selftest@live_execlists.html
* igt@i915_selftest@live_sanitycheck:
- fi-icl-u3: [DMESG-WARN][15] ([i915#585]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-icl-u3/igt@i915_selftest@live_sanitycheck.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-icl-u3/igt@i915_selftest@live_sanitycheck.html
* igt@kms_chamelium@dp-crc-fast:
- fi-cml-u2: [FAIL][17] ([i915#262]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-cml-u2/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-cml-u2/igt@[email protected]
#### Warnings ####
* igt@amdgpu/amd_prime@amd-to-i915:
- fi-icl-u3: [SKIP][19] ([fdo#109315]) -> [SKIP][20] ([fdo#109315] / [i915#585])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-icl-u3/igt@amdgpu/[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-icl-u3/igt@amdgpu/[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][21] ([fdo#111096] / [i915#323]) -> [FAIL][22] ([fdo#111407])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/fi-kbl-7500u/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/fi-kbl-7500u/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[CI#94]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/94
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
[i915#1084]: https://gitlab.freedesktop.org/drm/intel/issues/1084
[i915#1233]: https://gitlab.freedesktop.org/drm/intel/issues/1233
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#585]: https://gitlab.freedesktop.org/drm/intel/issues/585
[i915#647]: https://gitlab.freedesktop.org/drm/intel/issues/647
[i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694
[i915#816]: https://gitlab.freedesktop.org/drm/intel/issues/816
Participating hosts (47 -> 43)
------------------------------
Additional (5): fi-tgl-dsi fi-glk-dsi fi-bwr-2160 fi-snb-2520m fi-kbl-r
Missing (9): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-ilk-650 fi-ctg-p8600 fi-gdg-551 fi-byt-clapper fi-bsw-nick fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7975 -> Patchwork_16646
CI-20190529: 20190529
CI_DRM_7975: f66891f7bdc3c60bb6f06fd6bc0718a0bd975896 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5453: cae9a5881ed2c5be2c2518a255740b612a927f9a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16646: 6c7853420838966ea74464c65ff3f0e05b30b319 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
6c7853420838 drm/i915/hdcp: Return 0 on config_stream_type() +ve return 731c2227fe99 drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for HDCP 2.2 Comp fixes
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: HDCP 2.2 Comp fixes
URL : https://patchwork.freedesktop.org/series/73708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7975_full -> Patchwork_16646_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_16646_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@gem_ctx_persistence@close-replace-race}:
- shard-skl: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl7/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl3/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_16646_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_caching@read-writes:
- shard-hsw: [PASS][3] -> [FAIL][4] ([i915#694]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-hsw2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-hsw1/igt@[email protected]
* igt@gem_exec_schedule@pi-common-bsd:
- shard-iclb: [PASS][5] -> [SKIP][6] ([i915#677]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb5/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#112146]) +4 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb7/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb4/igt@[email protected]
* igt@gem_tiled_blits@interruptible:
- shard-hsw: [PASS][9] -> [FAIL][10] ([i915#818])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-hsw5/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-hsw1/igt@[email protected]
* igt@i915_pm_rps@waitboost:
- shard-iclb: [PASS][11] -> [FAIL][12] ([i915#413])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb3/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-skl: [PASS][13] -> [INCOMPLETE][14] ([i915#221])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl7/igt@[email protected]
* igt@kms_plane_multiple@atomic-pipe-b-tiling-y:
- shard-skl: [PASS][15] -> [DMESG-WARN][16] ([IGT#6])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl9/igt@[email protected]
* igt@kms_psr@psr2_sprite_blt:
- shard-iclb: [PASS][17] -> [SKIP][18] ([fdo#109441]) +2 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb2/igt@kms_psr@psr2_sprite_blt.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb1/igt@kms_psr@psr2_sprite_blt.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [PASS][19] -> [DMESG-WARN][20] ([i915#180]) +4 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-kbl2/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-kbl2/igt@[email protected]
* igt@perf_pmu@busy-vcs1:
- shard-iclb: [PASS][21] -> [SKIP][22] ([fdo#112080]) +13 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb8/igt@[email protected]
* igt@prime_mmap_coherency@ioctl-errors:
- shard-hsw: [PASS][23] -> [FAIL][24] ([i915#831])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-hsw2/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-hsw5/igt@[email protected]
* igt@prime_mmap_coherency@read:
- shard-hsw: [PASS][25] -> [FAIL][26] ([i915#914])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-hsw1/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-hsw7/igt@[email protected]
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: [PASS][27] -> [SKIP][28] ([fdo#109276]) +25 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb2/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb6/igt@[email protected]
#### Possible fixes ####
* igt@gem_busy@busy-vcs1:
- shard-iclb: [SKIP][29] ([fdo#112080]) -> [PASS][30] +14 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb8/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb1/igt@[email protected]
* {igt@gem_exec_schedule@implicit-write-read-bsd2}:
- shard-iclb: [SKIP][31] ([fdo#109276] / [i915#677]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb5/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb2/igt@[email protected]
* igt@gem_exec_schedule@pi-distinct-iova-bsd:
- shard-iclb: [SKIP][33] ([i915#677]) -> [PASS][34] +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb4/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb8/igt@[email protected]
* igt@gem_exec_schedule@preemptive-hang-bsd:
- shard-iclb: [SKIP][35] ([fdo#112146]) -> [PASS][36] +7 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb1/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb7/igt@[email protected]
* {igt@gem_exec_whisper@basic-queues-forked}:
- shard-iclb: [INCOMPLETE][37] ([i915#1120]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb6/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb5/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [FAIL][39] ([i915#644]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-glk8/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-glk9/igt@[email protected]
- shard-kbl: [FAIL][41] ([i915#644]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-kbl2/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-kbl2/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][43] ([i915#454]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb3/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb7/igt@[email protected]
* igt@i915_selftest@mock_buddy:
- shard-apl: [TIMEOUT][45] ([fdo#112271]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-apl6/igt@i915_selftest@mock_buddy.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-apl3/igt@i915_selftest@mock_buddy.html
* igt@i915_suspend@debugfs-reader:
- shard-kbl: [DMESG-WARN][47] ([i915#180]) -> [PASS][48] +2 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-kbl3/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-kbl2/igt@[email protected]
* igt@kms_color@pipe-a-ctm-blue-to-red:
- shard-skl: [FAIL][49] ([i915#129]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl1/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl2/igt@[email protected]
* igt@kms_color@pipe-a-gamma:
- shard-skl: [FAIL][51] ([i915#71]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl10/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl1/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-skl: [INCOMPLETE][53] ([i915#300]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl3/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl2/igt@[email protected]
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
- shard-glk: [FAIL][55] ([i915#72]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-glk8/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-glk9/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [FAIL][57] ([i915#79]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl5/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl10/igt@[email protected]
* igt@kms_flip@flip-vs-suspend:
- shard-apl: [DMESG-WARN][59] ([i915#180]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-apl1/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-apl2/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-indfb-fliptrack:
- shard-glk: [FAIL][61] ([i915#49]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-glk5/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-glk4/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-slowdraw:
- shard-tglb: [SKIP][63] ([i915#668]) -> [PASS][64] +5 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-tglb5/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-tglb5/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [FAIL][65] ([fdo#108145]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl10/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][67] ([fdo#108145] / [i915#265]) -> [PASS][68] +1 similar issue
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl3/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl2/igt@[email protected]
* igt@kms_psr@psr2_sprite_render:
- shard-iclb: [SKIP][69] ([fdo#109441]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb3/igt@kms_psr@psr2_sprite_render.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb2/igt@kms_psr@psr2_sprite_render.html
* igt@prime_busy@hang-bsd2:
- shard-iclb: [SKIP][71] ([fdo#109276]) -> [PASS][72] +18 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-iclb5/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-iclb2/igt@[email protected]
#### Warnings ####
* igt@i915_pm_dc@dc6-dpms:
- shard-tglb: [FAIL][73] ([i915#454]) -> [SKIP][74] ([i915#468])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-tglb7/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-tglb2/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-kbl: [TIMEOUT][75] ([fdo#112271] / [i915#727]) -> [TIMEOUT][76] ([fdo#112271]) +1 similar issue
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-kbl3/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-kbl1/igt@[email protected]
* igt@kms_rotation_crc@primary-rotation-90:
- shard-skl: [TIMEOUT][77] ([fdo#112271]) -> [TIMEOUT][78] ([fdo#112271] / [i915#727])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7975/shard-skl9/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16646/shard-skl9/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
[i915#1120]: https://gitlab.freedesktop.org/drm/intel/issues/1120
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#129]: https://gitlab.freedesktop.org/drm/intel/issues/129
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#221]: https://gitlab.freedesktop.org/drm/intel/issues/221
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#300]: https://gitlab.freedesktop.org/drm/intel/issues/300
[i915#413]: https://gitlab.freedesktop.org/drm/intel/issues/413
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#468]: https://gitlab.freedesktop.org/drm/intel/issues/468
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#668]: https://gitlab.freedesktop.org/drm/intel/issues/668
[i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677
[i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694
[i915#71]: https://gitlab.freedesktop.org/drm/intel/issues/71
[i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72
[i915#727]: https://gitlab.freedesktop.org/drm/intel/issues/727
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#818]: https://gitlab.freedesktop.org/drm/intel/issues/818
[i915#831]: https://gitlab.freedesktop.org/drm/intel/issues/831
[i915#914]: https://gitlab.freedesktop.org/drm/intel/issues/914
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7975 -> Patchwork_16646
CI-20190529: 20190529
CI_DRM_7975: f66891f7bdc3c60bb6f06fd6bc0718a0bd975896 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5453: cae9a5881ed2c5be2c2518a255740b612a927f9a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16646: 6c7853420838966ea74464c65ff3f0e05b30b319 @ 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_16646/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.DOCS: warning for HDCP 2.2 Comp fixes (rev2)
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: HDCP 2.2 Comp fixes (rev2)
URL : https://patchwork.freedesktop.org/series/73708/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915 Error: Cannot open file ./drivers/gpu/drm/i915/intel_csr.c Error: Cannot open file ./drivers/gpu/drm/i915/intel_csr.c Error: Cannot open file ./drivers/gpu/drm/i915/intel_csr.c ./drivers/gpu/drm/i915/display/intel_dpll_mgr.h:285: warning: Function parameter or member 'get_freq' not described in 'intel_shared_dpll_funcs' ./drivers/gpu/drm/i915/i915_vma.h:1: warning: 'Virtual Memory Address' not found ./drivers/gpu/drm/i915/i915_gem_gtt.c:1: warning: 'Global GTT views' not found WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function csr support for dmc ./drivers/gpu/drm/i915/intel_csr.c' failed with return code 1 WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/i915/intel_csr.c' failed with return code 2
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for HDCP 2.2 Comp fixes (rev2)
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: HDCP 2.2 Comp fixes (rev2)
URL : https://patchwork.freedesktop.org/series/73708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8050 -> Patchwork_16791
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16791/index.html
Known issues
------------
Here are the changes found in Patchwork_16791 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_wait@basic-await-all:
- fi-tgl-y: [PASS][1] -> [DMESG-WARN][2] ([CI#94] / [i915#402]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-tgl-y/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16791/fi-tgl-y/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-icl-y: [DMESG-FAIL][3] ([fdo#108569]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-icl-y/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16791/fi-icl-y/igt@i915_selftest@[email protected]
* igt@prime_self_import@basic-with_fd_dup:
- fi-tgl-y: [DMESG-WARN][5] ([CI#94] / [i915#402]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-tgl-y/igt@prime_self_import@basic-with_fd_dup.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16791/fi-tgl-y/igt@prime_self_import@basic-with_fd_dup.html
[CI#94]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/94
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (46 -> 38)
------------------------------
Additional (2): fi-kbl-7560u fi-snb-2520m
Missing (10): fi-bdw-samus fi-hsw-4200u fi-hsw-peppy fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-skl-lmem fi-blb-e6850 fi-byt-clapper fi-skl-6700k2
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8050 -> Patchwork_16791
CI-20190529: 20190529
CI_DRM_8050: 422d76f5669ce8b7cd0c579f60628877159cbe7c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5484: 91b36b61e76901a2bd09fe93ac7bf7b8a60f258c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16791: 920a726f54f6aa58476a58513d840591b8763f9c @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
920a726f54f6 drm/i915/hdcp: Fix config_stream_type() ret value f9be7f7e53c5 drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16791/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.DOCS: warning for HDCP 2.2 Comp fixes (rev3)
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: HDCP 2.2 Comp fixes (rev3)
URL : https://patchwork.freedesktop.org/series/73708/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915 Error: Cannot open file ./drivers/gpu/drm/i915/intel_csr.c Error: Cannot open file ./drivers/gpu/drm/i915/intel_csr.c Error: Cannot open file ./drivers/gpu/drm/i915/intel_csr.c ./drivers/gpu/drm/i915/display/intel_dpll_mgr.h:285: warning: Function parameter or member 'get_freq' not described in 'intel_shared_dpll_funcs' ./drivers/gpu/drm/i915/i915_vma.h:1: warning: 'Virtual Memory Address' not found ./drivers/gpu/drm/i915/i915_gem_gtt.c:1: warning: 'Global GTT views' not found WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function csr support for dmc ./drivers/gpu/drm/i915/intel_csr.c' failed with return code 1 WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/i915/intel_csr.c' failed with return code 2
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for HDCP 2.2 Comp fixes (rev3)
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: HDCP 2.2 Comp fixes (rev3)
URL : https://patchwork.freedesktop.org/series/73708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8050 -> Patchwork_16792
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/index.html
Known issues
------------
Here are the changes found in Patchwork_16792 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@gem_contexts:
- fi-cfl-8700k: [PASS][1] -> [INCOMPLETE][2] ([i915#424])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-cfl-8700k/igt@i915_selftest@live@gem_contexts.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/fi-cfl-8700k/igt@i915_selftest@live@gem_contexts.html
- fi-cml-s: [PASS][3] -> [DMESG-FAIL][4] ([i915#877])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-cml-s/igt@i915_selftest@live@gem_contexts.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/fi-cml-s/igt@i915_selftest@live@gem_contexts.html
* igt@kms_addfb_basic@too-wide:
- fi-tgl-y: [PASS][5] -> [DMESG-WARN][6] ([CI#94] / [i915#402])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-tgl-y/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/fi-tgl-y/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-icl-y: [DMESG-FAIL][7] ([fdo#108569]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-icl-y/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/fi-icl-y/igt@i915_selftest@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][9] ([fdo#111096] / [i915#323]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-kbl-7500u/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/fi-kbl-7500u/igt@[email protected]
* igt@prime_self_import@basic-with_fd_dup:
- fi-tgl-y: [DMESG-WARN][11] ([CI#94] / [i915#402]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/fi-tgl-y/igt@prime_self_import@basic-with_fd_dup.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/fi-tgl-y/igt@prime_self_import@basic-with_fd_dup.html
[CI#94]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/94
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#424]: https://gitlab.freedesktop.org/drm/intel/issues/424
[i915#877]: https://gitlab.freedesktop.org/drm/intel/issues/877
Participating hosts (46 -> 37)
------------------------------
Additional (3): fi-gdg-551 fi-snb-2520m fi-elk-e7500
Missing (12): fi-hsw-4200u fi-glk-dsi fi-byt-squawks fi-bwr-2160 fi-ilk-650 fi-bsw-cyan fi-ctg-p8600 fi-ivb-3770 fi-blb-e6850 fi-byt-clapper fi-bdw-samus fi-snb-2600
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8050 -> Patchwork_16792
CI-20190529: 20190529
CI_DRM_8050: 422d76f5669ce8b7cd0c579f60628877159cbe7c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5484: 91b36b61e76901a2bd09fe93ac7bf7b8a60f258c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16792: 1c652492ce24706a22705cc827866ec8388fb25c @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
1c652492ce24 drm/i915/hdcp: Fix config_stream_type() ret value 9bcf6e3a8502 drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for HDCP 2.2 Comp fixes (rev3)
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: HDCP 2.2 Comp fixes (rev3)
URL : https://patchwork.freedesktop.org/series/73708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8050_full -> Patchwork_16792_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_16792_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@legacy-engines-mixed-process@vebox:
- shard-apl: [PASS][1] -> [FAIL][2] ([i915#679])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-apl4/igt@gem_ctx_persistence@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-apl1/igt@gem_ctx_persistence@[email protected]
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#110841])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb6/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@implicit-both-bsd:
- shard-iclb: [PASS][5] -> [SKIP][6] ([i915#677]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb6/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@implicit-both-bsd2:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#109276] / [i915#677])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb2/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb6/igt@[email protected]
* igt@gem_exec_schedule@pi-common-bsd1:
- shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#109276]) +20 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb1/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb6/igt@[email protected]
* igt@gem_exec_schedule@promotion-bsd:
- shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#112146]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb6/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb1/igt@[email protected]
* igt@gem_workarounds@suspend-resume-context:
- shard-skl: [PASS][13] -> [INCOMPLETE][14] ([i915#69])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl7/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl1/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [PASS][15] -> [INCOMPLETE][16] ([i915#716])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl1/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl9/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-64x21-onscreen:
- shard-skl: [PASS][17] -> [FAIL][18] ([i915#54])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl5/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl9/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][19] -> [DMESG-WARN][20] ([i915#180]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-kbl1/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-kbl7/igt@[email protected]
* igt@kms_flip@2x-plain-flip-fb-recreate-interruptible:
- shard-glk: [PASS][21] -> [FAIL][22] ([i915#34])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-glk5/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-glk4/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [PASS][23] -> [FAIL][24] ([i915#79])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl1/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl8/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-apl: [PASS][25] -> [DMESG-WARN][26] ([i915#180]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-apl6/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-apl6/igt@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible:
- shard-skl: [PASS][27] -> [FAIL][28] ([i915#34])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl8/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl2/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu:
- shard-skl: [PASS][29] -> [FAIL][30] ([i915#49])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl1/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu.html
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][31] -> [FAIL][32] ([fdo#108145])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl7/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [PASS][33] -> [FAIL][34] ([fdo#108145] / [i915#265])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl5/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl9/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][35] -> [SKIP][36] ([fdo#109441])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb8/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_setmode@basic:
- shard-apl: [PASS][37] -> [FAIL][38] ([i915#31])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-apl7/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-apl2/igt@[email protected]
* igt@perf_pmu@busy-check-all-vcs1:
- shard-iclb: [PASS][39] -> [SKIP][40] ([fdo#112080]) +15 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb1/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb6/igt@[email protected]
#### Possible fixes ####
* igt@gem_ctx_persistence@legacy-engines-mixed-process@bsd:
- shard-skl: [INCOMPLETE][41] ([i915#1197] / [i915#1239]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl1/igt@gem_ctx_persistence@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl7/igt@gem_ctx_persistence@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed-process@render:
- shard-skl: [FAIL][43] ([i915#679]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl1/igt@gem_ctx_persistence@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl7/igt@gem_ctx_persistence@[email protected]
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][45] ([fdo#110854]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb6/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@fifo-bsd1:
- shard-iclb: [SKIP][47] ([fdo#109276]) -> [PASS][48] +13 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb5/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb4/igt@[email protected]
* igt@gem_exec_schedule@implicit-write-read-bsd2:
- shard-iclb: [SKIP][49] ([fdo#109276] / [i915#677]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb7/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [SKIP][51] ([fdo#112146]) -> [PASS][52] +5 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb1/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb8/igt@[email protected]
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-apl: [DMESG-WARN][53] ([i915#180]) -> [PASS][54] +2 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-apl4/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-apl3/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-kbl: [DMESG-WARN][55] ([i915#180]) -> [PASS][56] +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-kbl1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-kbl3/igt@[email protected]
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-glk: [FAIL][57] ([i915#899]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-glk3/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-glk7/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][59] ([fdo#109441]) -> [PASS][60] +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb4/igt@kms_psr@psr2_primary_mmap_cpu.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_universal_plane@cursor-fb-leak-pipe-a:
- shard-snb: [SKIP][61] ([fdo#109271]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-snb5/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-snb4/igt@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- shard-skl: [INCOMPLETE][63] ([i915#69]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-skl8/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-skl2/igt@[email protected]
* igt@perf_pmu@busy-vcs1:
- shard-iclb: [SKIP][65] ([fdo#112080]) -> [PASS][66] +12 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8050/shard-iclb7/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16792/shard-iclb1/igt@[email protected]
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[i915#1197]: https://gitlab.freedesktop.org/drm/intel/issues/1197
[i915#1239]: https://gitlab.freedesktop.org/drm/intel/issues/1239
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#34]: https://gitlab.freedesktop.org/drm/intel/issues/34
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677
[i915#679]: https://gitlab.freedesktop.org/drm/intel/issues/679
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#899]: https://gitlab.freedesktop.org/drm/intel/issues/899
Participating hosts (9 -> 10)
------------------------------
Additional (1): pig-skl-6260u
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8050 -> Patchwork_16792
CI-20190529: 20190529
CI_DRM_8050: 422d76f5669ce8b7cd0c579f60628877159cbe7c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5484: 91b36b61e76901a2bd09fe93ac7bf7b8a60f258c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16792: 1c652492ce24706a22705cc827866ec8388fb25c @ 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_16792/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 5 lines · Anshuman Gupta
Adding ram's RB on patch1 and a new patch to fix DP HDCP Auth.
Anshuman Gupta (2):
drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg drm/i915/hdcp: Return 0 onconfig_stream_type()+ve return
Thanks for the patches. Submitted them to dinq.
-Ram
Quoted 11 lines
drivers/gpu/drm/i915/display/intel_hdcp.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)Signature · 6 lines
2.24.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx