Enable HDR on MCA LSPCON based Gen9 devices
Subsystems (3)
v12 cover Enable HDR on MCA LSPCON based Gen9 devices
Gen9 hardware supports HDMI2.0 through LSPCON chips. Extending HDR support for MCA and Parade LSPCON based GEN9 devices.
SOC will drive LSPCON as DP and send HDR metadata as standard DP SDP packets. LSPCON will be set to operate in PCON mode, will receive the metadata and create Dynamic Range and Mastering Infoframe (DRM packets) and send it to HDR capable HDMI sink devices.
v2: Fixed Ville's review comments. Suppressed some warnings. Patch 8 of the series is marked "Not for Merge" and is just for reference to userspace people to incorporate in order to support 10bit content with 4K@60 resolutions.
v3: Added Infoframe readout support for DRM infoframes. Addressed Jani Nikula's review comments.
v4: Addressed Ville's review comments and added proper bitmask for enabled infoframes. Series also incorporates Ville's patch for stopping infoframes to be sent to DVI sinks. Extended the same for DRM as well.
v5: Created separate helper function for lspcon_infoframes_enabled as per Ville's suggestion.
v6: Rebase
v7: Addressed Ville's review comments.
v8: Addressed Ville's review comments. Fixed the colorspace handling for Pcon and property attachment logic based on new lspcon detetction changes.
v9: Rebase
v10: Fixed one patch for detection
v11: Addressed Ville's review comments and added RB in the respective patches.
v12: Addressed Ville's review comments, re-order the changes. With Ville's help fixed the lingering colorspace handling for lspcon.
Thanks Ville for all the suggestions and inputs.
Note: Patch 15 of the series is for reference to userspace, not to be merged to driver.
Uma Shankar (14):
drm/i915/display: Add HDR Capability detection for LSPCON drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon drm/i915/display: Attach HDR property for capable Gen9 devices drm/i915/display: Fixes quantization range for YCbCr output drm/i915/display: Add a WARN for invalid output range and format drm/i915/display: Attach content type property for LSPCON drm/i915/display: Enable colorspace programming for LSPCON devices drm/i915/display: Nuke bogus lspcon check drm/i915/display: Enable HDR for Parade based lspcon drm/i915/lspcon: Create separate infoframe_enabled helper drm/i915/display: Implement infoframes readback for LSPCON drm/i915/display: Implement DRM infoframe read for LSPCON drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks drm/i915/display: [NOT FOR MERGE] Reduce blanking to support
4k60@10bpp for LSPCON
Ville Syrjälä (1):
drm/i915: Split intel_attach_colorspace_property() into HDMI vs. DP
variants
.../gpu/drm/i915/display/intel_connector.c | 29 ++-- .../gpu/drm/i915/display/intel_connector.h | 3 +- drivers/gpu/drm/i915/display/intel_ddi.c | 20 ++- .../drm/i915/display/intel_display_types.h | 1 + drivers/gpu/drm/i915/display/intel_dp.c | 38 +++- drivers/gpu/drm/i915/display/intel_hdmi.c | 26 +-- drivers/gpu/drm/i915/display/intel_lspcon.c | 162 +++++++++++++++--- drivers/gpu/drm/i915/display/intel_lspcon.h | 12 ++ 8 files changed, 226 insertions(+), 65 deletions(-)
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 1/15 drm/i915/display: Add HDR Capability detection for LSPCON
LSPCON firmware exposes HDR capability through LPCON_CAPABILITIES DPCD register. LSPCON implementations capable of supporting HDR set HDR_CAPABILITY bit in LSPCON_CAPABILITIES to 1. This patch reads the same, detects the HDR capability and adds this to intel_lspcon struct.
v2: Addressed Jani Nikula's review comment and fixed the HDR
capability detection logic
v3: Deferred HDR detection from lspcon_init (Ville)
v4: Addressed Ville's minor review comments, added his RB.
--- .../drm/i915/display/intel_display_types.h | 1 + drivers/gpu/drm/i915/display/intel_lspcon.c | 27 +++++++++++++++++++ drivers/gpu/drm/i915/display/intel_lspcon.h | 1 + 3 files changed, 29 insertions(+)
drivers/gpu/drm/i915/display/intel_display_types.h +1 -0
@@ -1450,6 +1450,7 @@ enum lspcon_vendor {struct intel_lspcon {bool active; +bool hdr_supported;enum drm_lspcon_mode mode;enum lspcon_vendor vendor; };
drivers/gpu/drm/i915/display/intel_lspcon.c +27 -0
@@ -35,6 +35,8 @@#define LSPCON_VENDOR_PARADE_OUI 0x001CF8#define LSPCON_VENDOR_MCA_OUI 0x0060AD +#define DPCD_MCA_LSPCON_HDR_STATUS 0x70003 +/* AUX addresses to write MCA AVI IF */ #define LSPCON_MCA_AVI_IF_WRITE_OFFSET 0x5C0#define LSPCON_MCA_AVI_IF_CTRL 0x5DF
@@ -104,6 +106,31 @@ static bool lspcon_detect_vendor(struct intel_lspcon *lspcon)return true; } +void lspcon_detect_hdr_capability (struct intel_lspcon *lspcon) +{ +struct intel_digital_port *dig_port = + container_of(lspcon, struct intel_digital_port, lspcon); +struct drm_device *dev = dig_port->base.base.dev; +struct intel_dp *dp =lspcon_to_intel_dp (lspcon); +u8 hdr_caps; +int ret; + +/* Enable HDR for MCA based LSPCON devices */ +if (lspcon->vendor ==LSPCON_VENDOR_MCA ) + ret =drm_dp_dpcd_read (&dp->aux,DPCD_MCA_LSPCON_HDR_STATUS , + &hdr_caps,1 ); +else +return ; + +if (ret <0 ) { +drm_dbg_kms (dev,"HDR capability detection failed\n" ); + lspcon->hdr_supported = false; + }else if (hdr_caps &0x1 ) { +drm_dbg_kms (dev,"LSPCON capable of HDR\n" ); + lspcon->hdr_supported = true; + } +} +static enum drm_lspcon_mode lspcon_get_current_mode (struct intel_lspcon *lspcon) {enum drm_lspcon_mode current_mode;
drivers/gpu/drm/i915/display/intel_lspcon.h +1 -0
@@ -15,6 +15,7 @@ struct intel_digital_port;struct intel_encoder ;struct intel_lspcon ; +void lspcon_detect_hdr_capability (struct intel_lspcon *lspcon);void lspcon_resume (struct intel_digital_port *dig_port);void lspcon_wait_pcon_mode (struct intel_lspcon *lspcon); void lspcon_write_infoframe(struct intel_encoder *encoder,
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 2/15 drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon
In reply to Uma ShankarGen9 hardware supports HDMI2.0 through LSPCON chips. Extending HDR support for MCA LSPCON based GEN9 devices.
SOC will drive LSPCON as DP and send HDR metadata as standard DP SDP packets. LSPCON will be set to operate in PCON mode, will receive the metadata and create Dynamic Range and Mastering Infoframe (DRM packets) and send it to HDR capable HDMI sink devices.
v2: Re-used hsw infoframe write implementation for HDR metadata for LSPCON as per Ville's suggestion.
v3: Addressed Jani Nikula's review comments.
v4: Addressed Ville's review comments, removed redundant wrapper and checks, passed arguments instead of hardcodings.
--- drivers/gpu/drm/i915/display/intel_hdmi.c | 8 +++--- drivers/gpu/drm/i915/display/intel_lspcon.c | 31 ++++++++++++--------- drivers/gpu/drm/i915/display/intel_lspcon.h | 4 +++ 3 files changed, 26 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/display/intel_hdmi.c +4 -4
@@ -518,10 +518,10 @@ static u32 vlv_infoframes_enabled(struct intel_encoder *encoder, VIDEO_DIP_ENABLE_SPD | VIDEO_DIP_ENABLE_GCP); } -static void hsw_write_infoframe (struct intel_encoder *encoder, -const struct intel_crtc_state *crtc_state, -unsigned int type, -const void *frame,ssize_t len) +void hsw_write_infoframe (struct intel_encoder *encoder, +const struct intel_crtc_state *crtc_state, +unsigned int type, +const void *frame,ssize_t len) {const u32 *data = frame;struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);
drivers/gpu/drm/i915/display/intel_lspcon.c +18 -13
@@ -445,27 +445,32 @@ void lspcon_write_infoframe(struct intel_encoder *encoder,unsigned int type, const void *frame, ssize_t len) { - bool ret; + bool ret = true;struct intel_dp *intel_dp =enc_to_intel_dp (encoder);struct intel_lspcon *lspcon =enc_to_intel_lspcon (encoder); -/* LSPCON only needs AVI IF */ -if (type !=HDMI_INFOFRAME_TYPE_AVI ) +switch (type) { +case HDMI_INFOFRAME_TYPE_AVI : +if (lspcon->vendor ==LSPCON_VENDOR_MCA ) + ret =_lspcon_write_avi_infoframe_mca (&intel_dp->aux, + frame, len); +else + ret =_lspcon_write_avi_infoframe_parade (&intel_dp->aux, + frame, len); +break ; +case HDMI_PACKET_TYPE_GAMUT_METADATA : +drm_dbg_kms (encoder->base.dev,"Update HDR metadata for lspcon\n" ); +/* It uses the legacy hsw implementation for the same */ +hsw_write_infoframe (encoder, crtc_state, type, frame, len); +break ; +default :return ; - -if (lspcon->vendor ==LSPCON_VENDOR_MCA ) - ret =_lspcon_write_avi_infoframe_mca (&intel_dp->aux, - frame, len); -else - ret =_lspcon_write_avi_infoframe_parade (&intel_dp->aux, - frame, len); + }if (!ret) { -DRM_ERROR ("Failed to write AVI infoframes\n" ); +DRM_ERROR ("Failed to write infoframes\n" );return ; } - -DRM_DEBUG_DRIVER ("AVI infoframes updated successfully\n" ); } void lspcon_read_infoframe(struct intel_encoder *encoder,
drivers/gpu/drm/i915/display/intel_lspcon.h +4 -0
@@ -32,5 +32,9 @@ void lspcon_set_infoframes(struct intel_encoder *encoder, const struct drm_connector_state *conn_state);u32 lspcon_infoframes_enabled (struct intel_encoder *encoder,const struct intel_crtc_state *pipe_config); +void hsw_write_infoframe (struct intel_encoder *encoder, +const struct intel_crtc_state *crtc_state, +unsigned int type, +const void *frame,ssize_t len);#endif /* __INTEL_LSPCON_H__ */
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 3/15 drm/i915/display: Attach HDR property for capable Gen9 devices
In reply to Uma ShankarAttach HDR property for Gen9 devices with MCA LSPCON chips.
v2: Cleaned HDR property attachment logic based on capability as per Jani Nikula's suggestion.
v3: Fixed the HDR property attachment logic as per the new changes by Kai-Feng to align with lspcon detection failure on some devices.
v4: Add HDR proprty in late_register to handle lspcon detection, as suggested by Ville.
v5: Init Lspcon only if advertized from BIOS.
v6: Added a Todo to plan a cleanup later, added Ville's RB.
--- drivers/gpu/drm/i915/display/intel_dp.c | 18 ++++++++++++++++++ drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +- drivers/gpu/drm/i915/display/intel_lspcon.h | 1 + 3 files changed, 20 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_dp.c +18 -0
@@ -6774,6 +6774,8 @@ intel_dp_connector_register(struct drm_connector *connector) {struct drm_i915_private *i915 =to_i915 (connector->dev);struct intel_dp *intel_dp =intel_attached_dp (to_intel_connector (connector)); +struct intel_digital_port *dig_port =dp_to_dig_port (intel_dp); +struct intel_lspcon *lspcon = &dig_port->lspcon;int ret; ret =intel_connector_register (connector);
@@ -6787,6 +6789,22 @@ intel_dp_connector_register(struct drm_connector *connector) ret =drm_dp_aux_register (&intel_dp->aux);if (!ret)drm_dp_cec_register_connector (&intel_dp->aux, connector); + +if (!intel_bios_is_lspcon_present (i915, dig_port->base.port)) +return ret; + +/* +* ToDo: Clean this up to handle lspcon init and resume more +* efficiently and streamlined. +*/ +if (lspcon_init (dig_port)) { +lspcon_detect_hdr_capability (lspcon); +if (lspcon->hdr_supported) +drm_object_attach_property (&connector->base, + connector->dev->mode_config.hdr_output_metadata_property, +0 ); + } +return ret; }
drivers/gpu/drm/i915/display/intel_lspcon.c +1 -1
@@ -552,7 +552,7 @@ void lspcon_wait_pcon_mode(struct intel_lspcon *lspcon)lspcon_wait_mode (lspcon,DRM_LSPCON_MODE_PCON ); } -static bool lspcon_init (struct intel_digital_port *dig_port) +bool lspcon_init (struct intel_digital_port *dig_port) {struct intel_dp *dp = &dig_port->dp;struct intel_lspcon *lspcon = &dig_port->lspcon;
drivers/gpu/drm/i915/display/intel_lspcon.h +1 -0
@@ -15,6 +15,7 @@ struct intel_digital_port;struct intel_encoder ;struct intel_lspcon ; +bool lspcon_init (struct intel_digital_port *dig_port);void lspcon_detect_hdr_capability (struct intel_lspcon *lspcon);void lspcon_resume (struct intel_digital_port *dig_port);void lspcon_wait_pcon_mode (struct intel_lspcon *lspcon);
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 4/15 drm/i915/display: Fixes quantization range for YCbCr output
In reply to Uma ShankarThis patch fixes the quantization range for YCbCr output on Lspcon based devices.
v2: Re-phrased the description and added Ville's Rb.
--- drivers/gpu/drm/i915/display/intel_lspcon.c | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/display/intel_lspcon.c +11 -6
@@ -523,12 +523,17 @@ void lspcon_set_infoframes(struct intel_encoder *encoder,else frame.avi.colorspace =HDMI_COLORSPACE_RGB ; -drm_hdmi_avi_infoframe_quant_range (&frame.avi, - conn_state->connector, - adjusted_mode, - crtc_state->limited_color_range ? -HDMI_QUANTIZATION_RANGE_LIMITED : -HDMI_QUANTIZATION_RANGE_FULL ); +if (crtc_state->output_format ==INTEL_OUTPUT_FORMAT_RGB ) { +drm_hdmi_avi_infoframe_quant_range (&frame.avi, + conn_state->connector, + adjusted_mode, + crtc_state->limited_color_range ? +HDMI_QUANTIZATION_RANGE_LIMITED : +HDMI_QUANTIZATION_RANGE_FULL ); + }else { + frame.avi.quantization_range =HDMI_QUANTIZATION_RANGE_DEFAULT ; + frame.avi.ycc_quantization_range =HDMI_YCC_QUANTIZATION_RANGE_LIMITED ; + } ret =hdmi_infoframe_pack (&frame, buf,sizeof (buf));if (ret <0 ) {
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 5/15 drm/i915/display: Add a WARN for invalid output range and format
In reply to Uma ShankarAdd a WARN to rule out an invalid output range and format combination. This is to align the lspcon code with compute_avi_infoframes.
--- drivers/gpu/drm/i915/display/intel_lspcon.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/gpu/drm/i915/display/intel_lspcon.c +4 -0
@@ -523,6 +523,10 @@ void lspcon_set_infoframes(struct intel_encoder *encoder,else frame.avi.colorspace =HDMI_COLORSPACE_RGB ; +/* nonsense combination */ +drm_WARN_ON (encoder->base.dev, crtc_state->limited_color_range && + crtc_state->output_format !=INTEL_OUTPUT_FORMAT_RGB ); +if (crtc_state->output_format ==INTEL_OUTPUT_FORMAT_RGB ) { drm_hdmi_avi_infoframe_quant_range(&frame.avi, conn_state->connector,
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 6/15 drm/i915/display: Attach content type property for LSPCON
In reply to Uma ShankarContent type is supported on HDMI sink devices. Attached the property for the same for LSPCON based devices.
v2: Added the content type programming when we are attaching the property to connector, as suggested by Ville.
--- drivers/gpu/drm/i915/display/intel_dp.c | 1 + drivers/gpu/drm/i915/display/intel_lspcon.c | 2 ++ 2 files changed, 3 insertions(+)
drivers/gpu/drm/i915/display/intel_dp.c +1 -0
@@ -6803,6 +6803,7 @@ intel_dp_connector_register(struct drm_connector *connector)drm_object_attach_property (&connector->base, connector->dev->mode_config.hdr_output_metadata_property,0 ); +drm_connector_attach_content_type_property (connector); }return ret;
drivers/gpu/drm/i915/display/intel_lspcon.c +2 -0
@@ -539,6 +539,8 @@ void lspcon_set_infoframes(struct intel_encoder *encoder, frame.avi.ycc_quantization_range =HDMI_YCC_QUANTIZATION_RANGE_LIMITED ; } +drm_hdmi_avi_infoframe_content_type (&frame.avi, conn_state); + ret =hdmi_infoframe_pack (&frame, buf,sizeof (buf));if (ret <0 ) {DRM_ERROR ("Failed to pack AVI IF\n" );
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v13 6/15 drm/i915/display: Attach content type property for LSPCON
Content type is supported on HDMI sink devices. Attached the property for the same for LSPCON based devices.
v2: Added the content type programming when we are attaching the property to connector, as suggested by Ville.
v3: Need to attach content type on intel_dp_add_properties as creating of new properties is not possible at late_register.
--- drivers/gpu/drm/i915/display/intel_dp.c | 3 +++ drivers/gpu/drm/i915/display/intel_lspcon.c | 2 ++ 2 files changed, 5 insertions(+)
drivers/gpu/drm/i915/display/intel_dp.c +3 -0
@@ -7195,6 +7195,9 @@ intel_dp_add_properties(struct intel_dp *intel_dp, struct drm_connector *connectintel_attach_colorspace_property (connector); +if (intel_bios_is_lspcon_present (dev_priv, port)) +drm_connector_attach_content_type_property (connector); +if (IS_GEMINILAKE (dev_priv) ||INTEL_GEN (dev_priv) >=11 ) drm_object_attach_property(&connector->base, connector->dev->mode_config.hdr_output_metadata_property,
drivers/gpu/drm/i915/display/intel_lspcon.c +2 -0
@@ -539,6 +539,8 @@ void lspcon_set_infoframes(struct intel_encoder *encoder, frame.avi.ycc_quantization_range =HDMI_YCC_QUANTIZATION_RANGE_LIMITED ; } +drm_hdmi_avi_infoframe_content_type (&frame.avi, conn_state); + ret =hdmi_infoframe_pack (&frame, buf,sizeof (buf));if (ret <0 ) {DRM_ERROR ("Failed to pack AVI IF\n" );
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 7/15 drm/i915: Split intel_attach_colorspace_property() into HDMI vs. DP variants
In reply to Uma ShankarFrom: Ville Syrjälä <[email protected]>
With LSPCON we use the AVI infoframe to convey the colorimetry information (as opposed to DP MSA/SDP), so the property we expose should match the values we can stuff into the infoframe. Ie. we must use the HDMI variant of the property, even though we drive LSPCON in PCON mode. To that end just split intel_attach_colorspace_property() into HDMI and DP variants and let the caller worry about which one it wants to use.
--- .../gpu/drm/i915/display/intel_connector.c | 29 +++++++------------ .../gpu/drm/i915/display/intel_connector.h | 3 +- drivers/gpu/drm/i915/display/intel_dp.c | 2 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 2 +- 4 files changed, 15 insertions(+), 21 deletions(-)
drivers/gpu/drm/i915/display/intel_connector.c +11 -18
@@ -279,24 +279,17 @@ intel_attach_aspect_ratio_property(struct drm_connector *connector) }void -intel_attach_colorspace_property (struct drm_connector *connector) +intel_attach_hdmi_colorspace_property (struct drm_connector *connector) { -switch (connector->connector_type) { -case DRM_MODE_CONNECTOR_HDMIA : -case DRM_MODE_CONNECTOR_HDMIB : -if (drm_mode_create_hdmi_colorspace_property (connector)) -return ; -break ; -case DRM_MODE_CONNECTOR_DisplayPort: -case DRM_MODE_CONNECTOR_eDP: -if (drm_mode_create_dp_colorspace_property (connector)) -return ; -break ; -default : -MISSING_CASE (connector->connector_type); -return ; - } +if (!drm_mode_create_hdmi_colorspace_property (connector)) +drm_object_attach_property (&connector->base, + connector->colorspace_property,0 ); +} -drm_object_attach_property (&connector->base, - connector->colorspace_property,0 ); +void +intel_attach_dp_colorspace_property (struct drm_connector *connector) +{ +if (!drm_mode_create_dp_colorspace_property (connector)) +drm_object_attach_property (&connector->base, + connector->colorspace_property,0 ); }
drivers/gpu/drm/i915/display/intel_connector.h +2 -1
@@ -30,6 +30,7 @@ int intel_ddc_get_modes(struct drm_connector *c, struct i2c_adapter *adapter);void intel_attach_force_audio_property (struct drm_connector *connector);void intel_attach_broadcast_rgb_property (struct drm_connector *connector);void intel_attach_aspect_ratio_property (struct drm_connector *connector); -void intel_attach_colorspace_property (struct drm_connector *connector); +void intel_attach_hdmi_colorspace_property (struct drm_connector *connector); +void intel_attach_dp_colorspace_property (struct drm_connector *connector);#endif /* __INTEL_CONNECTOR_H__ */
drivers/gpu/drm/i915/display/intel_dp.c +1 -1
@@ -7194,7 +7194,7 @@ intel_dp_add_properties(struct intel_dp *intel_dp, struct drm_connector *connectelse if (INTEL_GEN (dev_priv) >=5 )drm_connector_attach_max_bpc_property (connector,6 ,12 ); -intel_attach_colorspace_property (connector); +intel_attach_dp_colorspace_property (connector);if (IS_GEMINILAKE (dev_priv) ||INTEL_GEN (dev_priv) >=11 ) drm_object_attach_property(&connector->base,
drivers/gpu/drm/i915/display/intel_hdmi.c +1 -1
@@ -2963,7 +2963,7 @@ intel_hdmi_add_properties(struct intel_hdmi *intel_hdmi, struct drm_connector *c* as well. Will be implemented separately. */ if (!dig_port->lspcon.active) -intel_attach_colorspace_property (connector); +intel_attach_hdmi_colorspace_property (connector);drm_connector_attach_content_type_property (connector);
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 8/15 drm/i915/display: Enable colorspace programming for LSPCON devices
In reply to Uma ShankarEnable HDMI Colorspace for LSPCON based devices. Sending Colorimetry data for HDR using AVI infoframe. LSPCON firmware expects this and though SOC drives DP, for HDMI panel AVI infoframe is sent to the LSPCON device which transfers the same to HDMI sink.
v2: Dropped state managed in drm core as per Jani Nikula's suggestion.
v3: Aligned colorimetry handling for lspcon as per compute_avi_infoframes, as suggested by Ville.
v4: Finally fixed this with Ville's help, re-phrased the commit header and description.
Credits-to: Ville Syrjälä <[email protected]>
--- drivers/gpu/drm/i915/display/intel_lspcon.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/i915/display/intel_lspcon.c +3 -0
@@ -523,6 +523,9 @@ void lspcon_set_infoframes(struct intel_encoder *encoder,else frame.avi.colorspace =HDMI_COLORSPACE_RGB ; +/* Set the Colorspace as per the HDMI spec */ +drm_hdmi_avi_infoframe_colorspace (&frame.avi, conn_state); +/* nonsense combination */ drm_WARN_ON (encoder->base.dev, crtc_state->limited_color_range && crtc_state->output_format !=INTEL_OUTPUT_FORMAT_RGB );
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 08/15] drm/i915/display: Enable colorspace programming for LSPCON devices
Quoted 5 lines · Uma Shankar
Enable HDMI Colorspace for LSPCON based devices. Sending Colorimetry data for HDR using AVI infoframe. LSPCON firmware expects this and though SOC drives DP, for HDMI panel AVI infoframe is sent to the LSPCON device which transfers the same to HDMI sink.
Quoted 7 lines
v2: Dropped state managed in drm core as per Jani Nikula's suggestion.
v3: Aligned colorimetry handling for lspcon as per
compute_avi_infoframes, as suggested by Ville.v4: Finally fixed this with Ville's help, re-phrased the commit header and description.
Still missing the "expose the hdmi variant of the prop on lspcon" part. I didn't include that in my patch since we didn't use drm_hdmi_avi_infoframe_colorspace() yes on lspcon. Although maybe I should have just done that change anyway since we were already registering the prop anyway even if we didn't actually put the data into the infoframe.
Quoted 23 lines
Credits-to: Ville Syrjälä <[email protected]>
Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_lspcon.c | 3 +++ 1 file changed, 3 insertions(+)drivers/gpu/drm/i915/display/intel_lspcon.c +3
-0@@ -523,6 +523,9 @@ void lspcon_set_infoframes(struct intel_encoder *encoder,else frame.avi.colorspace =HDMI_COLORSPACE_RGB ; +/* Set the Colorspace as per the HDMI spec */ +drm_hdmi_avi_infoframe_colorspace (&frame.avi, conn_state); +/* nonsense combination */ drm_WARN_ON (encoder->base.dev, crtc_state->limited_color_range && crtc_state->output_format !=INTEL_OUTPUT_FORMAT_RGB );Signature · 1 line
2.26.2
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 08/15] drm/i915/display: Enable colorspace programming for LSPCON devices
Quoted 21 lines
-----Original Message-----
From: Ville Syrjälä <[email protected]>
Sent: Friday, November 27, 2020 7:15 PM
To: Shankar, Uma <[email protected]>
Cc: [email protected]
Subject: Re: [v12 08/15] drm/i915/display: Enable colorspace programming for LSPCON devicesQuoted 10 lines · Uma Shankar
Enable HDMI Colorspace for LSPCON based devices. Sending Colorimetry data for HDR using AVI infoframe. LSPCON firmware expects this and though SOC drives DP, for HDMI panel AVI infoframe is sent to the LSPCON device which transfers the same to HDMI sink.
v2: Dropped state managed in drm core as per Jani Nikula's suggestion.
v3: Aligned colorimetry handling for lspcon as per
compute_avi_infoframes, as suggested by Ville.
Quoted 8 lines
Quoted 2 lines
v4: Finally fixed this with Ville's help, re-phrased the commit header and description.
Still missing the "expose the hdmi variant of the prop on lspcon" part. I didn't include that in my patch since we didn't use
drm_hdmi_avi_infoframe_colorspace()yes on lspcon. Although maybe I should have just done that change anyway since we were already registering the prop anyway even if we didn't actually put the data into the infoframe.
Yeah just sent the fix for that Ville. We had to create the properties early so moved the checks to intel_dp_add_properties. Just see if the new version looks ok
Regards,
Uma Shankar
Quoted 17 lines
drivers/gpu/drm/i915/display/intel_lspcon.c void lspcon_set_infoframes(struct intel_encoder
Quoted 13 lines
Credits-to: Ville Syrjälä <[email protected]>
Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_lspcon.c | 3 +++ 1 file changed, 3 insertions(+)drivers/gpu/drm/i915/display/intel_lspcon.c +0
-0@@ -523,6 +523,9 @@ void lspcon_set_infoframes(struct intel_encoder*encoder,
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_lspcon.c +0
-0else frame.avi.colorspace =HDMI_COLORSPACE_RGB ;
Quoted 12 lines
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_lspcon.c +3
-1+/* Set the Colorspace as per the HDMI spec */ +drm_hdmi_avi_infoframe_colorspace (&frame.avi, conn_state); +/* nonsense combination */ drm_WARN_ON (encoder->base.dev, crtc_state->limited_color_range && crtc_state->output_format !=INTEL_OUTPUT_FORMAT_RGB ); --2.26.2
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v13 8/15 drm/i915/display: Enable colorspace programming for LSPCON devices
In reply to Uma ShankarEnable HDMI Colorspace for LSPCON based devices. Sending Colorimetry data for HDR using AVI infoframe. LSPCON firmware expects this and though SOC drives DP, for HDMI panel AVI infoframe is sent to the LSPCON device which transfers the same to HDMI sink.
v2: Dropped state managed in drm core as per Jani Nikula's suggestion.
v3: Aligned colorimetry handling for lspcon as per compute_avi_infoframes, as suggested by Ville.
v4: Finally fixed this with Ville's help, re-phrased the commit header and description.
v5: Register HDMI colorspace for lspcon and move this to intel_dp_add_properties as we can't create property at late_register.
Credits-to: Ville Syrjälä <[email protected]>
--- drivers/gpu/drm/i915/display/intel_dp.c | 9 ++++++--- drivers/gpu/drm/i915/display/intel_lspcon.c | 3 +++ 2 files changed, 9 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_dp.c +6 -3
@@ -7193,10 +7193,13 @@ intel_dp_add_properties(struct intel_dp *intel_dp, struct drm_connector *connectelse if (INTEL_GEN (dev_priv) >=5 )drm_connector_attach_max_bpc_property (connector,6 ,12 ); -intel_attach_dp_colorspace_property (connector); - -if (intel_bios_is_lspcon_present (dev_priv, port)) +/* Register HDMI colorspace for case of lspcon */ +if (intel_bios_is_lspcon_present (dev_priv, port)) {drm_connector_attach_content_type_property (connector); +intel_attach_hdmi_colorspace_property (connector); + }else { +intel_attach_dp_colorspace_property (connector); + }if (IS_GEMINILAKE (dev_priv) ||INTEL_GEN (dev_priv) >=11 ) drm_object_attach_property(&connector->base,
drivers/gpu/drm/i915/display/intel_lspcon.c +3 -0
@@ -523,6 +523,9 @@ void lspcon_set_infoframes(struct intel_encoder *encoder,else frame.avi.colorspace =HDMI_COLORSPACE_RGB ; +/* Set the Colorspace as per the HDMI spec */ +drm_hdmi_avi_infoframe_colorspace (&frame.avi, conn_state); +/* nonsense combination */ drm_WARN_ON (encoder->base.dev, crtc_state->limited_color_range && crtc_state->output_format !=INTEL_OUTPUT_FORMAT_RGB );
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v13 08/15] drm/i915/display: Enable colorspace programming for LSPCON devices
Quoted 10 lines · Uma Shankar
Enable HDMI Colorspace for LSPCON based devices. Sending Colorimetry data for HDR using AVI infoframe. LSPCON firmware expects this and though SOC drives DP, for HDMI panel AVI infoframe is sent to the LSPCON device which transfers the same to HDMI sink.
v2: Dropped state managed in drm core as per Jani Nikula's suggestion.
v3: Aligned colorimetry handling for lspcon as per
compute_avi_infoframes, as suggested by Ville.
Quoted 8 lines
v4: Finally fixed this with Ville's help, re-phrased the commit header and description.
v5: Register HDMI colorspace for lspcon and move this to
intel_dp_add_propertiesas we can't create property atlate_register.Credits-to: Ville Syrjälä <[email protected]>
Signed-off-by Uma Shankar <[email protected]>
Quoted 42 lines
--- drivers/gpu/drm/i915/display/intel_dp.c | 9 ++++++--- drivers/gpu/drm/i915/display/intel_lspcon.c | 3 +++ 2 files changed, 9 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/display/intel_dp.c +6
-3@@ -7193,10 +7193,13 @@ intel_dp_add_properties(struct intel_dp *intel_dp, struct drm_connector *connectelse if (INTEL_GEN (dev_priv) >=5 )drm_connector_attach_max_bpc_property (connector,6 ,12 ); -intel_attach_dp_colorspace_property (connector); - -if (intel_bios_is_lspcon_present (dev_priv, port)) +/* Register HDMI colorspace for case of lspcon */ +if (intel_bios_is_lspcon_present (dev_priv, port)) {drm_connector_attach_content_type_property (connector); +intel_attach_hdmi_colorspace_property (connector); + }else { +intel_attach_dp_colorspace_property (connector); + }if (IS_GEMINILAKE (dev_priv) ||INTEL_GEN (dev_priv) >=11 ) drm_object_attach_property(&connector->base,drivers/gpu/drm/i915/display/intel_lspcon.c +3
-0@@ -523,6 +523,9 @@ void lspcon_set_infoframes(struct intel_encoder *encoder,else frame.avi.colorspace =HDMI_COLORSPACE_RGB ; +/* Set the Colorspace as per the HDMI spec */ +drm_hdmi_avi_infoframe_colorspace (&frame.avi, conn_state); +/* nonsense combination */ drm_WARN_ON (encoder->base.dev, crtc_state->limited_color_range && crtc_state->output_format !=INTEL_OUTPUT_FORMAT_RGB );Signature · 1 line
2.26.2
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v13 08/15] drm/i915/display: Enable colorspace programming for LSPCON devices
Quoted 24 lines
-----Original Message-----
From: Ville Syrjälä <[email protected]>
Sent: Tuesday, December 1, 2020 1:21 AM
To: Shankar, Uma <[email protected]>
Cc: [email protected]
Subject: Re: [v13 08/15] drm/i915/display: Enable colorspace programming for LSPCON devicesQuoted 13 lines · Uma Shankar
Enable HDMI Colorspace for LSPCON based devices. Sending Colorimetry data for HDR using AVI infoframe. LSPCON firmware expects this and though SOC drives DP, for HDMI panel AVI infoframe is sent to the LSPCON device which transfers the same to HDMI sink.
v2: Dropped state managed in drm core as per Jani Nikula's suggestion.
v3: Aligned colorimetry handling for lspcon as per
compute_avi_infoframes, as suggested by Ville.v4: Finally fixed this with Ville's help, re-phrased the commit header and description.
Quoted 7 lines
Quoted 5 lines
v5: Register HDMI colorspace for lspcon and move this to
intel_dp_add_propertiesas we can't create property atlate_register.Credits-to: Ville Syrjälä <[email protected]>
Signed-off-by Uma Shankar <[email protected]>Reviewed-by Ville Syrjälä <[email protected]>
Thanks a lot Ville for all your support, review and useful suggestions. I have sent out a final version with all your RB's and conditional comments addressed.
This series is now ready for merge.
Thanks & Regards,
Uma Shankar
Quoted 38 lines
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_add_properties(struct intel_dp *intel_dp,
Quoted 11 lines
--- drivers/gpu/drm/i915/display/intel_dp.c | 9 ++++++--- drivers/gpu/drm/i915/display/intel_lspcon.c | 3 +++ 2 files changed, 9 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/display/intel_dp.c +0
-0@@ -7193,10 +7193,13 @@ intel_dp_add_properties(struct intel_dp *intel_dp,struct
drm_connector*connectdrivers/gpu/drm/i915/display/intel_lspcon.c void lspcon_set_infoframes(struct intel_encoder
Quoted 22 lines
drivers/gpu/drm/i915/display/intel_dp.c +6
-3else if (INTEL_GEN (dev_priv) >=5 )drm_connector_attach_max_bpc_property (connector,6 ,12 ); -intel_attach_dp_colorspace_property (connector); - -if (intel_bios_is_lspcon_present (dev_priv, port)) +/* Register HDMI colorspace for case of lspcon */ +if (intel_bios_is_lspcon_present (dev_priv, port)) {drm_connector_attach_content_type_property (connector); +intel_attach_hdmi_colorspace_property (connector); + }else { +intel_attach_dp_colorspace_property (connector); + }if (IS_GEMINILAKE (dev_priv) ||INTEL_GEN (dev_priv) >=11 ) drm_object_attach_property(&connector->base,drivers/gpu/drm/i915/display/intel_lspcon.c +0
-0@@ -523,6 +523,9 @@ void lspcon_set_infoframes(struct intel_encoder*encoder,
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_lspcon.c +0
-0else frame.avi.colorspace =HDMI_COLORSPACE_RGB ;
Quoted 12 lines
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_lspcon.c +3
-1+/* Set the Colorspace as per the HDMI spec */ +drm_hdmi_avi_infoframe_colorspace (&frame.avi, conn_state); +/* nonsense combination */ drm_WARN_ON (encoder->base.dev, crtc_state->limited_color_range && crtc_state->output_format !=INTEL_OUTPUT_FORMAT_RGB ); --2.26.2
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 9/15 drm/i915/display: Nuke bogus lspcon check
In reply to Uma ShankarDropped a irrelevant lspcon check from intel_hdmi_add_properties function.
--- drivers/gpu/drm/i915/display/intel_hdmi.c | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-)
drivers/gpu/drm/i915/display/intel_hdmi.c +1 -10
@@ -2950,21 +2950,12 @@ static void intel_hdmi_add_properties(struct intel_hdmi *intel_hdmi, struct drm_connector *connector) { struct drm_i915_private *dev_priv = to_i915(connector->dev); -struct intel_digital_port *dig_port = -hdmi_to_dig_port (intel_hdmi);intel_attach_force_audio_property (connector);intel_attach_broadcast_rgb_property (connector);intel_attach_aspect_ratio_property (connector); -/* -* Attach Colorspace property for Non LSPCON based device -* ToDo: This needs to be extended for LSPCON implementation -* as well. Will be implemented separately. -*/ -if (!dig_port->lspcon.active) -intel_attach_hdmi_colorspace_property (connector); - +intel_attach_hdmi_colorspace_property (connector);drm_connector_attach_content_type_property (connector);if (INTEL_GEN (dev_priv) >=10 ||IS_GEMINILAKE (dev_priv))
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 10/15 drm/i915/display: Enable HDR for Parade based lspcon
In reply to Uma ShankarEnable HDR for LSPCON based on Parade along with MCA.
v2: Added a helper for status reg as suggested by Ville.
v3: Removed a redundant variable, added Ville's RB.
--- drivers/gpu/drm/i915/display/intel_lspcon.c | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/display/intel_lspcon.c +11 -6
@@ -36,6 +36,7 @@#define LSPCON_VENDOR_MCA_OUI 0x0060AD#define DPCD_MCA_LSPCON_HDR_STATUS 0x70003 +#define DPCD_PARADE_LSPCON_HDR_STATUS 0x00511/* AUX addresses to write MCA AVI IF */ #define LSPCON_MCA_AVI_IF_WRITE_OFFSET 0x5C0
@@ -106,6 +107,14 @@ static bool lspcon_detect_vendor(struct intel_lspcon *lspcon)return true; } +static u32 get_hdr_status_reg (struct intel_lspcon *lspcon) +{ +if (lspcon->vendor ==LSPCON_VENDOR_MCA ) +return DPCD_MCA_LSPCON_HDR_STATUS ; +else +return DPCD_PARADE_LSPCON_HDR_STATUS ; +} +void lspcon_detect_hdr_capability (struct intel_lspcon *lspcon) { struct intel_digital_port *dig_port =
@@ -115,12 +124,8 @@ void lspcon_detect_hdr_capability(struct intel_lspcon *lspcon)u8 hdr_caps;int ret; -/* Enable HDR for MCA based LSPCON devices */ -if (lspcon->vendor ==LSPCON_VENDOR_MCA ) - ret =drm_dp_dpcd_read (&dp->aux,DPCD_MCA_LSPCON_HDR_STATUS , - &hdr_caps,1 ); -else -return ; + ret =drm_dp_dpcd_read (&dp->aux,get_hdr_status_reg (lspcon), + &hdr_caps,1 );if (ret <0 ) {drm_dbg_kms (dev,"HDR capability detection failed\n" );
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 11/15 drm/i915/lspcon: Create separate infoframe_enabled helper
In reply to Uma ShankarLspcon has Infoframes as well as DIP for HDR metadata(DRM Infoframe). Create a separate mechanism for lspcon compared to HDMI in order to address the same and ensure future scalability.
v2: Streamlined this as per Ville's suggestions, making sure that HDMI infoframe versions are directly returned instead of a redundant and confusing DIP overhead.
--- drivers/gpu/drm/i915/display/intel_ddi.c | 10 +++++++--- drivers/gpu/drm/i915/display/intel_lspcon.c | 9 +++++++++ drivers/gpu/drm/i915/display/intel_lspcon.h | 2 ++ 3 files changed, 18 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_ddi.c +7 -3
@@ -4583,6 +4583,7 @@ static void intel_ddi_read_func_ctl(struct intel_encoder *encoder,struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);struct intel_crtc *intel_crtc =to_intel_crtc (pipe_config->uapi.crtc);enum transcoder cpu_transcoder = pipe_config->cpu_transcoder; +struct intel_digital_port *dig_port =enc_to_dig_port (encoder);u32 temp, flags =0 ; temp =intel_de_read (dev_priv,TRANS_DDI_FUNC_CTL (cpu_transcoder));
@@ -4657,9 +4658,12 @@ static void intel_ddi_read_func_ctl(struct intel_encoder *encoder, pipe_config->fec_enable); } - pipe_config->infoframes.enable |= -intel_hdmi_infoframes_enabled (encoder, pipe_config); - +if (dig_port->lspcon.active && dig_port->dp.has_hdmi_sink) + pipe_config->infoframes.enable |= +intel_lspcon_infoframes_enabled (encoder, pipe_config); +else + pipe_config->infoframes.enable |= +intel_hdmi_infoframes_enabled (encoder, pipe_config);break ;case TRANS_DDI_MODE_SELECT_DP_MST : pipe_config->output_types |=BIT (INTEL_OUTPUT_DP_MST );
drivers/gpu/drm/i915/display/intel_lspcon.c +9 -0
@@ -30,6 +30,7 @@#include "intel_display_types.h" #include "intel_dp.h" #include "intel_lspcon.h" +#include "intel_hdmi.h" /* LSPCON OUI Vendor ID(signatures) */ #define LSPCON_VENDOR_PARADE_OUI 0x001CF8
@@ -601,6 +602,14 @@ bool lspcon_init(struct intel_digital_port *dig_port)return true; } +u32 intel_lspcon_infoframes_enabled (struct intel_encoder *encoder, +const struct intel_crtc_state *pipe_config) +{ +struct intel_digital_port *dig_port =enc_to_dig_port (encoder); + +return dig_port->infoframes_enabled (encoder, pipe_config); +} +void lspcon_resume (struct intel_digital_port *dig_port) {struct intel_lspcon *lspcon = &dig_port->lspcon;
drivers/gpu/drm/i915/display/intel_lspcon.h +2 -0
@@ -33,6 +33,8 @@ void lspcon_set_infoframes(struct intel_encoder *encoder, const struct drm_connector_state *conn_state);u32 lspcon_infoframes_enabled (struct intel_encoder *encoder,const struct intel_crtc_state *pipe_config); +u32 intel_lspcon_infoframes_enabled (struct intel_encoder *encoder, +const struct intel_crtc_state *pipe_config); void hsw_write_infoframe(struct intel_encoder *encoder, const struct intel_crtc_state *crtc_state, unsigned int type,
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 11/15] drm/i915/lspcon: Create separate infoframe_enabled helper
Quoted 49 lines · Uma Shankar
Lspcon has Infoframes as well as DIP for HDR metadata(DRM Infoframe). Create a separate mechanism for lspcon compared to HDMI in order to address the same and ensure future scalability.
v2: Streamlined this as per Ville's suggestions, making sure that HDMI infoframe versions are directly returned instead of a redundant and confusing DIP overhead.
Suggested-by Ville Syrjälä <[email protected]>Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_ddi.c | 10 +++++++--- drivers/gpu/drm/i915/display/intel_lspcon.c | 9 +++++++++ drivers/gpu/drm/i915/display/intel_lspcon.h | 2 ++ 3 files changed, 18 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/display/intel_ddi.c +7
-3@@ -4583,6 +4583,7 @@ static void intel_ddi_read_func_ctl(struct intel_encoder *encoder,struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);struct intel_crtc *intel_crtc =to_intel_crtc (pipe_config->uapi.crtc);enum transcoder cpu_transcoder = pipe_config->cpu_transcoder; +struct intel_digital_port *dig_port =enc_to_dig_port (encoder);u32 temp, flags =0 ; temp =intel_de_read (dev_priv,TRANS_DDI_FUNC_CTL (cpu_transcoder));@@ -4657,9 +4658,12 @@ static void intel_ddi_read_func_ctl(struct intel_encoder *encoder, pipe_config->fec_enable); } - pipe_config->infoframes.enable |= -intel_hdmi_infoframes_enabled (encoder, pipe_config); - +if (dig_port->lspcon.active && dig_port->dp.has_hdmi_sink) + pipe_config->infoframes.enable |= +intel_lspcon_infoframes_enabled (encoder, pipe_config); +else + pipe_config->infoframes.enable |= +intel_hdmi_infoframes_enabled (encoder, pipe_config);break ;case TRANS_DDI_MODE_SELECT_DP_MST : pipe_config->output_types |=BIT (INTEL_OUTPUT_DP_MST );drivers/gpu/drm/i915/display/intel_lspcon.c +0
-0
drivers/gpu/drm/i915/display/intel_lspcon.c line 33
Quoted 4 lines
drivers/gpu/drm/i915/display/intel_lspcon.c +1
-0@@ -30,6 +30,7 @@#include "intel_display_types.h" #include "intel_dp.h" #include "intel_lspcon.h" +#include "intel_hdmi.h"
Why do you need that header?
With that potentially removed if it's not needed.
Quoted 33 lines
drivers/gpu/drm/i915/display/intel_lspcon.c +8
-0/* LSPCON OUI Vendor ID(signatures) */ #define LSPCON_VENDOR_PARADE_OUI 0x001CF8@@ -601,6 +602,14 @@ bool lspcon_init(struct intel_digital_port *dig_port)return true; } +u32 intel_lspcon_infoframes_enabled (struct intel_encoder *encoder, +const struct intel_crtc_state *pipe_config) +{ +struct intel_digital_port *dig_port =enc_to_dig_port (encoder); + +return dig_port->infoframes_enabled (encoder, pipe_config); +} +void lspcon_resume (struct intel_digital_port *dig_port) {struct intel_lspcon *lspcon = &dig_port->lspcon;drivers/gpu/drm/i915/display/intel_lspcon.h +2
-0@@ -33,6 +33,8 @@ void lspcon_set_infoframes(struct intel_encoder *encoder, const struct drm_connector_state *conn_state);u32 lspcon_infoframes_enabled (struct intel_encoder *encoder,const struct intel_crtc_state *pipe_config); +u32 intel_lspcon_infoframes_enabled (struct intel_encoder *encoder, +const struct intel_crtc_state *pipe_config); void hsw_write_infoframe(struct intel_encoder *encoder, const struct intel_crtc_state *crtc_state, unsigned int type,Signature · 1 line
2.26.2
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 11/15] drm/i915/lspcon: Create separate infoframe_enabled helper
Quoted 61 lines
-----Original Message-----
From: Ville Syrjälä <[email protected]>
Sent: Friday, November 27, 2020 8:25 PM
To: Shankar, Uma <[email protected]>
Cc: [email protected]
Subject: Re: [v12 11/15] drm/i915/lspcon: Create separateinfoframe_enabledhelperdrivers/gpu/drm/i915/display/intel_ddi.c static void intel_ddi_read_func_ctl(struct
Quoted 22 lines · Uma Shankar
Lspcon has Infoframes as well as DIP for HDR metadata(DRM Infoframe). Create a separate mechanism for lspcon compared to HDMI in order to address the same and ensure future scalability.
v2: Streamlined this as per Ville's suggestions, making sure that HDMI infoframe versions are directly returned instead of a redundant and confusing DIP overhead.
Suggested-by Ville Syrjälä <[email protected]>Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_ddi.c | 10 +++++++--- drivers/gpu/drm/i915/display/intel_lspcon.c | 9 +++++++++ drivers/gpu/drm/i915/display/intel_lspcon.h | 2 ++ 3 files changed, 18 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/display/intel_ddi.c +0
-0@@ -4583,6 +4583,7 @@ static void intel_ddi_read_func_ctl(struct
intel_encoder*encoder,drivers/gpu/drm/i915/display/intel_ddi.c static void intel_ddi_read_func_ctl(struct
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_ddi.c +1
-0struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);struct intel_crtc *intel_crtc =to_intel_crtc (pipe_config->uapi.crtc);enum transcoder cpu_transcoder = pipe_config->cpu_transcoder; +struct intel_digital_port *dig_port =enc_to_dig_port (encoder);u32 temp, flags =0 ; temp =intel_de_read (dev_priv,TRANS_DDI_FUNC_CTL (cpu_transcoder));@@ -4657,9 +4658,12 @@ static void intel_ddi_read_func_ctl(struct
intel_encoder*encoder,drivers/gpu/drm/i915/display/intel_ddi.c static void intel_ddi_read_func_ctl(struct intel_encoder *encoder,
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_ddi.c +3
-3pipe_config->fec_enable); } - pipe_config->infoframes.enable |= -intel_hdmi_infoframes_enabled (encoder, pipe_config); - +if (dig_port->lspcon.active && dig_port->dp.has_hdmi_sink) + pipe_config->infoframes.enable |= + intel_lspcon_infoframes_enabled(encoder,
pipe_config);drivers/gpu/drm/i915/display/intel_ddi.c static void intel_ddi_read_func_ctl(struct intel_encoder *encoder,
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_ddi.c +3
-0+else + pipe_config->infoframes.enable |= + intel_hdmi_infoframes_enabled(encoder,
pipe_config);drivers/gpu/drm/i915/display/intel_ddi.c static void intel_ddi_read_func_ctl(struct intel_encoder *encoder,
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_ddi.c +0
-0break ;case TRANS_DDI_MODE_SELECT_DP_MST : pipe_config->output_types |= BIT(INTEL_OUTPUT_DP_MST); diff --git
Quoted 12 lines
drivers/gpu/drm/i915/display/intel_lspcon.c line 33
Quoted 10 lines
a/drivers/gpu/drm/i915/display/intel_lspcon.cb/drivers/gpu/drm/i915/display/intel_lspcon.c
index592c19deba00..303f23d35020100644drivers/gpu/drm/i915/display/intel_lspcon.c +1
-0@@ -30,6 +30,7 @@#include "intel_display_types.h" #include "intel_dp.h" #include "intel_lspcon.h" +#include "intel_hdmi.h" Why do you need that header?
intel_hdmi_infoframe_enabled is coming from that, hence we need that. Thanks Ville for the review and RB.
Regards,
Uma Shankar
Quoted 25 lines
With that potentially removed if it's not needed.
Reviewed-by Ville Syrjälä <[email protected]>drivers/gpu/drm/i915/display/intel_lspcon.h void lspcon_set_infoframes(struct intel_encoder
Quoted 21 lines
drivers/gpu/drm/i915/display/intel_lspcon.c +0
-0/* LSPCON OUI Vendor ID(signatures) */ #define
LSPCON_VENDOR_PARADE_OUI0x001CF8@@ -601,6 +602,14 @@ boollspcon_init(struct intel_digital_port *dig_port)drivers/gpu/drm/i915/display/intel_lspcon.c +6
-0return true; } +u32 intel_lspcon_infoframes_enabled (struct intel_encoder *encoder, +const struct intel_crtc_state *pipe_config) { +struct intel_digital_port *dig_port =enc_to_dig_port (encoder); + +return dig_port->infoframes_enabled (encoder, pipe_config); } +void lspcon_resume (struct intel_digital_port *dig_port) { struct intel_lspcon *lspcon = &dig_port->lspcon; diff --git
a/drivers/gpu/drm/i915/display/intel_lspcon.hb/drivers/gpu/drm/i915/display/intel_lspcon.h
index42ccb21c908f..44aa6bc38512100644drivers/gpu/drm/i915/display/intel_lspcon.h +0
-0@@ -33,6 +33,8 @@ void lspcon_set_infoframes(struct intel_encoder*encoder,
Quoted 14 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_lspcon.h +2
-1const struct drm_connector_state *conn_state);u32 lspcon_infoframes_enabled (struct intel_encoder *encoder,const struct intel_crtc_state *pipe_config); +u32 intel_lspcon_infoframes_enabled (struct intel_encoder *encoder, +const struct intel_crtc_state *pipe_config); void hsw_write_infoframe(struct intel_encoder *encoder, const struct intel_crtc_state *crtc_state, unsigned int type, --2.26.2
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 12/15 drm/i915/display: Implement infoframes readback for LSPCON
In reply to Uma ShankarImplemented Infoframes enabled readback for LSPCON devices. This will help align the implementation with state readback infrastructure.
v2: Added proper bitmask of enabled infoframes as per Ville's recommendation.
v3: Added pcon specific infoframe types instead of using the HSW one's, as recommended by Ville.
v4: Addressed Ville's review comment by adding HDMI infoframe versions directly instead of DIP wrappers.
v5: Re-ordered the patches to avoid potential break in usage, as suggested by Ville.
--- drivers/gpu/drm/i915/display/intel_lspcon.c | 57 ++++++++++++++++++++- 1 file changed, 55 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/display/intel_lspcon.c +55 -2
@@ -560,11 +560,64 @@ void lspcon_set_infoframes(struct intel_encoder *encoder, buf, ret); } +static bool _lspcon_read_avi_infoframe_enabled_mca (struct drm_dp_aux *aux) +{ +int ret; +u32 val =0 ; +u16 reg =LSPCON_MCA_AVI_IF_CTRL ; + + ret =drm_dp_dpcd_read (aux, reg, &val,1 ); +if (ret <0 ) { +DRM_ERROR ("DPCD read failed, address 0x%x\n" , reg); +return false; + } + +return val &LSPCON_MCA_AVI_IF_KICKOFF ; +} + +static bool _lspcon_read_avi_infoframe_enabled_parade (struct drm_dp_aux *aux) +{ +int ret; +u32 val =0 ; +u16 reg =LSPCON_PARADE_AVI_IF_CTRL ; + + ret =drm_dp_dpcd_read (aux, reg, &val,1 ); +if (ret <0 ) { +DRM_ERROR ("DPCD read failed, address 0x%x\n" , reg); +return false; + } + +return val &LSPCON_PARADE_AVI_IF_KICKOFF ; +} +u32 lspcon_infoframes_enabled (struct intel_encoder *encoder,const struct intel_crtc_state *pipe_config) { -/* FIXME actually read this from the hw */ -return 0 ; +struct intel_dp *intel_dp =enc_to_intel_dp (encoder); +struct intel_lspcon *lspcon =enc_to_intel_lspcon (encoder); +struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev); +bool infoframes_enabled; +u32 val =0 ; +u32 mask, tmp; + +if (lspcon->vendor ==LSPCON_VENDOR_MCA ) + infoframes_enabled =_lspcon_read_avi_infoframe_enabled_mca (&intel_dp->aux); +else + infoframes_enabled =_lspcon_read_avi_infoframe_enabled_parade (&intel_dp->aux); + +if (infoframes_enabled) + val |=intel_hdmi_infoframe_enable (HDMI_INFOFRAME_TYPE_AVI ); + +if (lspcon->hdr_supported) { + tmp =intel_de_read (dev_priv, +HSW_TVIDEO_DIP_CTL (pipe_config->cpu_transcoder)); + mask =VIDEO_DIP_ENABLE_GMP_HSW ; + +if (tmp & mask) + val |=intel_hdmi_infoframe_enable (HDMI_PACKET_TYPE_GAMUT_METADATA ); + } + +return val; }void lspcon_wait_pcon_mode (struct intel_lspcon *lspcon)
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 13/15 drm/i915/display: Implement DRM infoframe read for LSPCON
In reply to Uma ShankarImplement Read back of HDR metadata infoframes i.e Dynamic Range and Mastering Infoframe for LSPCON devices.
v2: Added proper bitmask of enabled infoframes as per Ville's recommendation.
v3: Dropped a redundant wrapper as per Ville's comment.
v4: Dropped a redundant print, added Ville's RB.
--- drivers/gpu/drm/i915/display/intel_hdmi.c | 7 +++---- drivers/gpu/drm/i915/display/intel_lspcon.c | 5 ++++- drivers/gpu/drm/i915/display/intel_lspcon.h | 4 ++++ 3 files changed, 11 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/display/intel_hdmi.c +3 -4
@@ -555,10 +555,9 @@ void hsw_write_infoframe(struct intel_encoder *encoder,intel_de_posting_read (dev_priv, ctl_reg); } -static void hsw_read_infoframe (struct intel_encoder *encoder, -const struct intel_crtc_state *crtc_state, -unsigned int type, -void *frame,ssize_t len) +void hsw_read_infoframe (struct intel_encoder *encoder, +const struct intel_crtc_state *crtc_state, +unsigned int type,void *frame,ssize_t len) {struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);enum transcoder cpu_transcoder = crtc_state->cpu_transcoder;
drivers/gpu/drm/i915/display/intel_lspcon.c +4 -1
@@ -484,7 +484,10 @@ void lspcon_read_infoframe(struct intel_encoder *encoder,unsigned int type, void *frame, ssize_t len) { - /* FIXME implement this */ + /* FIXME implement for AVI Infoframe as well */ + if (type == HDMI_PACKET_TYPE_GAMUT_METADATA) + hsw_read_infoframe(encoder, crtc_state, type, + frame, len); } void lspcon_set_infoframes(struct intel_encoder *encoder,
drivers/gpu/drm/i915/display/intel_lspcon.h +4 -0
@@ -39,5 +39,9 @@ void hsw_write_infoframe(struct intel_encoder *encoder,const struct intel_crtc_state *crtc_state, unsigned int type, const void *frame, ssize_t len); +void hsw_read_infoframe (struct intel_encoder *encoder, +const struct intel_crtc_state *crtc_state, +unsigned int type, +void *frame,ssize_t len);#endif /* __INTEL_LSPCON_H__ */
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 14/15 drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks
In reply to Uma ShankarNon-HDMI sinks shouldn't be sent Dynamic Range and Mastering infoframes. Check for that when using LSPCON.
--- drivers/gpu/drm/i915/display/intel_ddi.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_ddi.c +9 -1
@@ -4118,6 +4118,7 @@ static void intel_enable_ddi_dp(struct intel_atomic_state *state, {struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);struct intel_dp *intel_dp =enc_to_intel_dp (encoder); +struct intel_digital_port *dig_port =enc_to_dig_port (encoder);enum port port = encoder->port;if (port ==PORT_A &&INTEL_GEN (dev_priv) <9 )
@@ -4125,7 +4126,14 @@ static void intel_enable_ddi_dp(struct intel_atomic_state *state,intel_edp_backlight_on (crtc_state, conn_state);intel_psr_enable (intel_dp, crtc_state, conn_state); -intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + +if (dig_port->lspcon.active) { +if (dig_port->dp.has_hdmi_sink) +intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + }else { +intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + } +intel_edp_drrs_enable (intel_dp, crtc_state);if (crtc_state->has_audio)
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 14/15] drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks
Quoted 22 lines · Uma Shankar
Non-HDMI sinks shouldn't be sent Dynamic Range and Mastering infoframes. Check for that when using LSPCON.
Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_ddi.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_ddi.c +1
-0@@ -4118,6 +4118,7 @@ static void intel_enable_ddi_dp(struct intel_atomic_state *state, {struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);struct intel_dp *intel_dp =enc_to_intel_dp (encoder); +struct intel_digital_port *dig_port =enc_to_dig_port (encoder);enum port port = encoder->port;if (port ==PORT_A &&INTEL_GEN (dev_priv) <9 )@@ -4125,7 +4126,14 @@ static void intel_enable_ddi_dp(struct intel_atomic_state *state,
drivers/gpu/drm/i915/display/intel_ddi.c static void intel_enable_ddi_dp(struct intel_atomic_state *state, · line 4135
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_ddi.c +7
-1intel_edp_backlight_on (crtc_state, conn_state);intel_psr_enable (intel_dp, crtc_state, conn_state); -intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + +if (dig_port->lspcon.active) { +if (dig_port->dp.has_hdmi_sink) +intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + }else { +intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + }
Simplify to
if (!lspcon || has_hdmi_sink)
intel_dp_set_infoframes()
?
Some time ago I was pondering if we should start to use crtc_state->has_hdmi_sink for DP too, but since we have no way to do readout for it I'm not sure it can be done in a sane way. I guess in the meantime I guess we need something like this.
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_ddi.c +1
-0+intel_edp_drrs_enable (intel_dp, crtc_state);if (crtc_state->has_audio)Signature · 1 line
2.26.2
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 14/15] drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks
Quoted 42 lines
-----Original Message-----
From: Ville Syrjälä <[email protected]>
Sent: Friday, November 27, 2020 8:22 PM
To: Shankar, Uma <[email protected]>
Cc: [email protected]
Subject: Re: [v12 14/15] drm/i915/lspcon: Do not send DRM infoframes to non- HDMI sinksQuoted 23 lines · Uma Shankar
Non-HDMI sinks shouldn't be sent Dynamic Range and Mastering infoframes. Check for that when using LSPCON.
Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_ddi.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_ddi.c +1
-0@@ -4118,6 +4118,7 @@ static void intel_enable_ddi_dp(struct intel_atomic_state *state, {struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev);struct intel_dp *intel_dp =enc_to_intel_dp (encoder); +struct intel_digital_port *dig_port =enc_to_dig_port (encoder);enum port port = encoder->port; if (port == PORT_A && INTEL_GEN(dev_priv) < 9) @@ -4125,7 +4126,14@@ static void intel_enable_ddi_dp(struct
intel_atomic_state*state,drivers/gpu/drm/i915/display/intel_ddi.c static void intel_enable_ddi_dp(struct intel_atomic_state *state,
Quoted 7 lines
drivers/gpu/drm/i915/display/intel_ddi.c +4
-1intel_edp_backlight_on (crtc_state, conn_state);intel_psr_enable (intel_dp, crtc_state, conn_state); -intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + +if (dig_port->lspcon.active) { +if (dig_port->dp.has_hdmi_sink) + intel_dp_set_infoframes(encoder, true, crtc_state,
conn_state);
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_ddi.c static void intel_enable_ddi_dp(struct intel_atomic_state *state, · line 4135
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_ddi.c +3
-0+ }else { +intel_dp_set_infoframes (encoder, true, crtc_state, conn_state); + }Simplify to
if (!lspcon ||has_hdmi_sink)
intel_dp_set_infoframes()
?
Sure, will update this.
Quoted 3 lines
Some time ago I was pondering if we should start to use crtc_state-
Quoted 1 line
has_hdmi_sinkfor DP too, but since we have no way to do readout for it I'mnot sure it can be done in a sane way.
Yeah this is a bit convoluted to fit both.
Can you please check 1 last remaining patch as well
https://patchwork.freedesktop.org/patch/404605/?series=68081&rev=14
With that the series would be ready for merge,
Thanks & Regards,
Uma Shankar
Quoted 7 lines
I guess in the meantime I guess we need something like this.
Reviewed-by Ville Syrjälä <[email protected]>Quoted 3 lines
drivers/gpu/drm/i915/display/intel_ddi.c +1
-0+intel_edp_drrs_enable (intel_dp, crtc_state);
Quoted 7 lines
Quoted 3 lines
if (
crtc_state->has_audio)
--
2.26.2--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v12 15/15 drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON
In reply to Uma ShankarBlanking needs to be reduced to incorporate DP and HDMI timing/link bandwidth limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will cause mode to blank out. Reduced Htotal by shortening the back porch and front porch within permissible limits.
Note: This is for reference for userspace, not to be merged in kernel.
v2: This is marked as Not for merge and the responsibilty to program these custom timings will be on userspace. This patch is just for reference purposes. This is based on Ville's recommendation.
v3: updated commit message.
--- drivers/gpu/drm/i915/display/intel_dp.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
drivers/gpu/drm/i915/display/intel_dp.c +17 -0
@@ -741,8 +741,10 @@ intel_dp_mode_valid(struct drm_connector *connector, {struct intel_dp *intel_dp =intel_attached_dp (to_intel_connector (connector));struct intel_connector *intel_connector =to_intel_connector (connector); +struct intel_encoder *intel_encoder =intel_attached_encoder (intel_connector);struct drm_display_mode *fixed_mode = intel_connector->panel.fixed_mode;struct drm_i915_private *dev_priv =to_i915 (connector->dev); +struct intel_lspcon *lspcon =enc_to_intel_lspcon (intel_encoder);int target_clock = mode->clock;int max_rate, mode_rate, max_lanes, max_link_clock;int max_dotclk = dev_priv->max_dotclk_freq;
@@ -778,6 +780,21 @@ intel_dp_mode_valid(struct drm_connector *connector,if (target_clock > max_dotclk)return MODE_CLOCK_HIGH ; +/* +* Reducing Blanking to incorporate DP and HDMI timing/link bandwidth +* limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs +* while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will +* cause mode to blank out. Reduced Htotal by shortening the back porch +* and front porch within permissible limits. +*/ +if (lspcon->active && lspcon->hdr_supported && + mode->clock >570000 ) { + mode->clock =570000 ; + mode->htotal -=180 ; + mode->hsync_start -=72 ; + mode->hsync_end -=72 ; + } + max_link_clock =intel_dp_max_link_rate (intel_dp); max_lanes =intel_dp_max_lane_count (intel_dp);
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 15/15] drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON
Hello Uma,
This expectations from user-space of having to adjust the timings of video mode doesn't seem like a good idea to me.
This seems more like a quirk, and it should be better kept in I915 layer itself.
Else, it will enforce user space to write a lot of vendor specific code, like:
- Is it Intel device ?
- Is it GEN9 ?
- Is it Gen9 + LSPCON ?
- Are we planning for a HDR playback ?
which is not what most of the compositors developers would be interested in.
I was talking to some of the Kodi folks and they also seem to think that it should go in driver.
Any reason why can't we add this code in encoder->compute_config() or mode_fixup() ?
compute_config() will have all the information above required, as this might be required for future LSPCON based devices as well.
Regards
Shashank
Quoted 46 lines · Uma Shankar
Blanking needs to be reduced to incorporate DP and HDMI timing/link bandwidth limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will cause mode to blank out. Reduced Htotal by shortening the back porch and front porch within permissible limits.
Note: This is for reference for userspace, not to be merged in kernel.
v2: This is marked as Not for merge and the responsibilty to program these custom timings will be on userspace. This patch is just for reference purposes. This is based on Ville's recommendation.
v3: updated commit message.
Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)drivers/gpu/drm/i915/display/intel_dp.c +10
-0@@ -741,8 +741,10 @@ intel_dp_mode_valid(struct drm_connector *connector, {struct intel_dp *intel_dp =intel_attached_dp (to_intel_connector (connector));struct intel_connector *intel_connector =to_intel_connector (connector); +struct intel_encoder *intel_encoder =intel_attached_encoder (intel_connector);struct drm_display_mode *fixed_mode = intel_connector->panel.fixed_mode;struct drm_i915_private *dev_priv =to_i915 (connector->dev); +struct intel_lspcon *lspcon =enc_to_intel_lspcon (intel_encoder);int target_clock = mode->clock;int max_rate, mode_rate, max_lanes, max_link_clock;int max_dotclk = dev_priv->max_dotclk_freq;@@ -778,6 +780,21 @@ intel_dp_mode_valid(struct drm_connector *connector,if (target_clock > max_dotclk)return MODE_CLOCK_HIGH ; +/* +* Reducing Blanking to incorporate DP and HDMI timing/link bandwidth +* limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs +* while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will +* cause mode to blank out. Reduced Htotal by shortening the back porch +* and front porch within permissible limits. +*/ + if (lspcon->active && lspcon->hdr_supported &&
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector *connector, · line 800
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_dp.c +7
-0+ mode->clock > 570000) { + mode->clock =570000 ; + mode->htotal -=180 ; + mode->hsync_start -=72 ; + mode->hsync_end -=72 ; + } + max_link_clock =intel_dp_max_link_rate (intel_dp); max_lanes =intel_dp_max_lane_count (intel_dp);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [v12 15/15] drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON
Quoted 31 lines
-----Original Message-----
From: Intel-gfx <[email protected]> On Behalf Of Shashank Sharma
Sent: Monday, November 30, 2020 4:43 PM
To: [email protected]
Subject: Re: [Intel-gfx] [v12 15/15] drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCONHello Uma,
This expectations from user-space of having to adjust the timings of video mode doesn't seem like a good idea to me.
This seems more like a quirk, and it should be better kept in I915 layer itself.
Else, it will enforce user space to write a lot of vendor specific code, like:
- Is it Intel device ?
- Is it GEN9 ?
- Is it Gen9 + LSPCON ?
- Are we planning for a HDR playback ?
which is not what most of the compositors developers would be interested in.
Quoted 8 lines
I was talking to some of the Kodi folks and they also seem to think that it should go in driver.
Any reason why can't we add this code in
encoder->compute_config()ormode_fixup()?
compute_config()will have all the information above required, as this might be required for future LSPCON based devices as well.
Hi Shashank,
My initial idea was to have it inside kernel itself. But this actually tweaks the display timing from the standard one what sink has given, so Ville's suggestion was to keep this out from kernel, and let userspace components force the adjusted timings.
This is more of a limitation coming from DP spec wrt HBR2 bandwidths.
@[email protected] What do you suggest. I have merged the changes leaving this patch out as of now.
Based on recommendation, I can re-work this and merge if we all are aligned on this one.
Thanks & Regards,
Uma Shankar
Quoted 64 lines
Regards
Shashank
Quoted 25 lines · Uma Shankar
Blanking needs to be reduced to incorporate DP and HDMI timing/link bandwidth limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will cause mode to blank out. Reduced Htotal by shortening the back porch and front porch within permissible limits.
Note: This is for reference for userspace, not to be merged in kernel.
v2: This is marked as Not for merge and the responsibilty to program these custom timings will be on userspace. This patch is just for reference purposes. This is based on Ville's recommendation.
v3: updated commit message.
Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)drivers/gpu/drm/i915/display/intel_dp.c +0
-0drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector · line 742
Quoted 2 lines
drivers/gpu/drm/i915/display/intel_dp.c +0
-0@@ -741,8 +741,10 @@ intel_dp_mode_valid(struct drm_connector *connector, { struct intel_dp *intel_dp =intel_attached_dp(to_intel_connector(connector));
Quoted 12 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-0struct intel_connector *intel_connector =to_intel_connector (connector); +struct intel_encoder *intel_encoder = +intel_attached_encoder (intel_connector);struct drm_display_mode *fixed_mode = intel_connector- panel.fixed_mode;struct drm_i915_private *dev_priv =to_i915 (connector->dev); +struct intel_lspcon *lspcon =enc_to_intel_lspcon (intel_encoder);int target_clock = mode->clock;int max_rate, mode_rate, max_lanes, max_link_clock; int max_dotclk = dev_priv->max_dotclk_freq; @@ -778,6 +780,21 @@intel_dp_mode_valid(struct
drm_connector*connector,drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector *connector,
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp.c +5
-0if (target_clock > max_dotclk)return MODE_CLOCK_HIGH ; +/* +* Reducing Blanking to incorporate DP and HDMI timing/link bandwidth +* limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs +* while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will +* cause mode to blank out. Reduced Htotal by shortening the back porch
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_dp.c +9
-0+* and front porch within permissible limits. +*/ +if (lspcon->active && lspcon->hdr_supported && + mode->clock >570000 ) { + mode->clock =570000 ; + mode->htotal -=180 ; + mode->hsync_start -=72 ; + mode->hsync_end -=72 ; + }
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector *connector, · line 799
Quoted 4 lines
drivers/gpu/drm/i915/display/intel_dp.c +1
-0+ max_link_clock =intel_dp_max_link_rate (intel_dp); max_lanes =intel_dp_max_lane_count (intel_dp);_______________________________________________
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
Re: [Intel-gfx] [v12 15/15] drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON
Quoted 36 lines · Uma
Quoted 36 lines
-----Original Message-----
From: Intel-gfx <[email protected]> On Behalf Of Shashank Sharma
Sent: Monday, November 30, 2020 4:43 PM
To: [email protected]
Subject: Re: [Intel-gfx] [v12 15/15] drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCONHello Uma,
This expectations from user-space of having to adjust the timings of video mode doesn't seem like a good idea to me.
This seems more like a quirk, and it should be better kept in I915 layer itself.
Else, it will enforce user space to write a lot of vendor specific code, like:
- Is it Intel device ?
- Is it GEN9 ?
- Is it Gen9 + LSPCON ?
- Are we planning for a HDR playback ?
which is not what most of the compositors developers would be interested in.
I was talking to some of the Kodi folks and they also seem to think that it should go in driver.
Any reason why can't we add this code in
encoder->compute_config()ormode_fixup()?
Quoted 6 lines
Quoted 2 lines
compute_config()will have all the information above required, as this might be required for future LSPCON based devices as well.Hi Shashank,
My initial idea was to have it inside kernel itself. But this actually tweaks the display timing from the standard one what sink has given, so Ville's suggestion was to keep this out from kernel, and let userspace components force the adjusted timings.
IIRC, we can handle this situation something like this:
- Allow the mode to be in modelist
- On GEN9 + LSPCON during normal modeset
- Never pick 10-bit depth for 4k@60 modes (I think no changes required here)
- On GEN9 + LSPCON during HDR playback (check HDR metadata)
- produce the required timing and save it as "adjusted_mode" during the encoder->compute_config()
Regards
Shashank
Quoted 82 lines
This is more of a limitation coming from DP spec wrt HBR2 bandwidths.
@[email protected] What do you suggest. I have merged the changes leaving this patch out as of now.
Based on recommendation, I can re-work this and merge if we all are aligned on this one.
Thanks & Regards,
Uma ShankarQuoted 71 lines
Regards
Shashank
Quoted 25 lines · Uma Shankar
Blanking needs to be reduced to incorporate DP and HDMI timing/link bandwidth limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will cause mode to blank out. Reduced Htotal by shortening the back porch and front porch within permissible limits.
Note: This is for reference for userspace, not to be merged in kernel.
v2: This is marked as Not for merge and the responsibilty to program these custom timings will be on userspace. This patch is just for reference purposes. This is based on Ville's recommendation.
v3: updated commit message.
Signed-off-by Uma Shankar <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)drivers/gpu/drm/i915/display/intel_dp.c +0
-0drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector · line 742
Quoted 2 lines
drivers/gpu/drm/i915/display/intel_dp.c +0
-0@@ -741,8 +741,10 @@ intel_dp_mode_valid(struct drm_connector *connector, { struct intel_dp *intel_dp =intel_attached_dp(to_intel_connector(connector));
Quoted 12 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-0struct intel_connector *intel_connector =to_intel_connector (connector); +struct intel_encoder *intel_encoder = +intel_attached_encoder (intel_connector);struct drm_display_mode *fixed_mode = intel_connector- panel.fixed_mode;struct drm_i915_private *dev_priv =to_i915 (connector->dev); +struct intel_lspcon *lspcon =enc_to_intel_lspcon (intel_encoder);int target_clock = mode->clock;int max_rate, mode_rate, max_lanes, max_link_clock; int max_dotclk = dev_priv->max_dotclk_freq; @@ -778,6 +780,21 @@intel_dp_mode_valid(struct
drm_connector*connector,drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector *connector,
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp.c +5
-0if (target_clock > max_dotclk)return MODE_CLOCK_HIGH ; +/* +* Reducing Blanking to incorporate DP and HDMI timing/link bandwidth +* limitations for CEA modes (4k@60 at 10 bpp). DP can drive 17.28Gbs +* while 4k modes (VIC97 etc) at 10 bpp required 17.8 Gbps. This will +* cause mode to blank out. Reduced Htotal by shortening the back porch
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector *connector, · line 799
Quoted 13 lines
drivers/gpu/drm/i915/display/intel_dp.c +10
-0+* and front porch within permissible limits. +*/ +if (lspcon->active && lspcon->hdr_supported && + mode->clock >570000 ) { + mode->clock =570000 ; + mode->htotal -=180 ; + mode->hsync_start -=72 ; + mode->hsync_end -=72 ; + } + max_link_clock =intel_dp_max_link_rate (intel_dp); max_lanes =intel_dp_max_lane_count (intel_dp);_______________________________________________
Intel-gfx mailing list
[email protected]
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fintel-gfx&data=04%7C01%7Cshashank.sharma%40amd.com%7C47cefaeaa67e40bfe21108d8963a5b14%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637424524669551722%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=0uxRP3Ih1HwnqJglJVF%2FL34D4KmmDZC2MOyPO7%2BE1ow%3D&reserved=0
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enable HDR on MCA LSPCON based Gen9 devices (rev12)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev12)
URL : https://patchwork.freedesktop.org/series/68081/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 07f151724145 drm/i915/display: Add HDR Capability detection for LSPCON 015b28ecdd00 drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon 566633074760 drm/i915/display: Attach HDR property for capable Gen9 devices -:58: WARNING:LONG_LINE: line length of 108 exceeds 100 columns #58: FILE: drivers/gpu/drm/i915/display/intel_dp.c:6804: + connector->dev->mode_config.hdr_output_metadata_property,
total: 0 errors, 1 warnings, 0 checks, 45 lines checked819a38caa76a drm/i915/display: Fixes quantization range for YCbCr output caa7a05c57aa drm/i915/display: Add a WARN for invalid output range and format 19e480392aa1 drm/i915/display: Attach content type property for LSPCON 5904fa4c5259 drm/i915: Split intel_attach_colorspace_property() into HDMI vs. DP variants 9e4c990a2a21 drm/i915/display: Enable colorspace programming for LSPCON devices 589d8106afd0 drm/i915/display: Nuke bogus lspcon check82c84c1a78fa drm/i915/display: Enable HDR for Parade based lspcon1a2451b47ea0 drm/i915/lspcon: Create separate infoframe_enabled helper 76e7ab963acd drm/i915/display: Implement infoframes readback for LSPCON e9838030d807 drm/i915/display: Implement DRM infoframe read for LSPCON b992e94961f3 drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks 1702176c40ec drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Enable HDR on MCA LSPCON based Gen9 devices (rev12)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev12)
URL : https://patchwork.freedesktop.org/series/68081/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. - +drivers/gpu/drm/i915/gt/intel_reset.c:1312:5: warning: context imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block +drivers/gpu/drm/i915/gt/selftest_reset.c:100:20: expected void *in +drivers/gpu/drm/i915/gt/selftest_reset.c:100:20: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:100:20: warning: incorrect type in assignment (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:101:46: expected void const *src +drivers/gpu/drm/i915/gt/selftest_reset.c:101:46: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:101:46: warning: incorrect type in argument 2 (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:136:20: expected void *in +drivers/gpu/drm/i915/gt/selftest_reset.c:136:20: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:136:20: warning: incorrect type in assignment (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:137:46: expected void const *src +drivers/gpu/drm/i915/gt/selftest_reset.c:137:46: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:137:46: warning: incorrect type in argument 2 (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:98:34: expected unsigned int [usertype] *s +drivers/gpu/drm/i915/gt/selftest_reset.c:98:34: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:98:34: warning: incorrect type in argument 1 (different address spaces) +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write8' - different lock contexts for basic block
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Enable HDR on MCA LSPCON based Gen9 devices (rev12)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev12)
URL : https://patchwork.freedesktop.org/series/68081/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9395 -> Patchwork_18993
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/index.html
New tests
---------
New tests have been introduced between CI_DRM_9395 and Patchwork_18993:
### New CI tests (1) ###
* boot:
- Statuses : 40 pass(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_18993 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@debugfs_test@read_all_entries:
- fi-bsw-nick: [PASS][1] -> [INCOMPLETE][2] ([i915#1250] / [i915#1436])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-bsw-nick/igt@debugfs_test@read_all_entries.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-bsw-nick/igt@debugfs_test@read_all_entries.html
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-byt-j1900: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-byt-j1900/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-byt-j1900/igt@[email protected]
* igt@i915_selftest@live@active:
- fi-bsw-kefka: [PASS][5] -> [DMESG-FAIL][6] ([i915#2675] / [i915#541])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-bsw-kefka/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-bsw-kefka/igt@i915_selftest@[email protected]
* igt@kms_busy@basic@flip:
- fi-tgl-y: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-tgl-y/igt@kms_busy@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-tgl-y/igt@kms_busy@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-bsw-kefka: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-bsw-kefka/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-bsw-kefka/igt@[email protected]
* igt@prime_self_import@basic-with_one_bo_two_files:
- fi-tgl-y: [PASS][11] -> [DMESG-WARN][12] ([i915#402]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
#### Possible fixes ####
* igt@core_hotunplug@unbind-rebind:
- fi-tgl-u2: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-tgl-u2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-tgl-u2/igt@[email protected]
- fi-icl-u2: [DMESG-WARN][15] ([i915#1982]) -> [PASS][16] +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-icl-u2/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-icl-u2/igt@[email protected]
- fi-kbl-7500u: [DMESG-WARN][17] -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-kbl-7500u/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-kbl-7500u/igt@[email protected]
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [DMESG-WARN][19] ([i915#1982]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-bsw-kefka/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-bsw-kefka/igt@[email protected]
* igt@kms_chamelium@hdmi-edid-read:
- fi-kbl-7500u: [DMESG-FAIL][21] ([i915#165]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-kbl-7500u/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-kbl-7500u/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-byt-j1900: [DMESG-WARN][23] ([i915#1982]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-byt-j1900/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-byt-j1900/igt@[email protected]
* igt@vgem_basic@create:
- fi-tgl-y: [DMESG-WARN][25] ([i915#402]) -> [PASS][26] +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-tgl-y/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-tgl-y/igt@[email protected]
#### Warnings ####
* igt@gem_exec_parallel@engines@fds:
- fi-bwr-2160: [SKIP][27] ([fdo#109271] / [i915#2295]) -> [SKIP][28] ([fdo#109271])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-bwr-2160/igt@gem_exec_parallel@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-bwr-2160/igt@gem_exec_parallel@[email protected]
- fi-pnv-d510: [SKIP][29] ([fdo#109271] / [i915#2295]) -> [SKIP][30] ([fdo#109271])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-pnv-d510/igt@gem_exec_parallel@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-pnv-d510/igt@gem_exec_parallel@[email protected]
- fi-ilk-650: [SKIP][31] ([fdo#109271] / [i915#2295]) -> [SKIP][32] ([fdo#109271])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-ilk-650/igt@gem_exec_parallel@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-ilk-650/igt@gem_exec_parallel@[email protected]
- fi-blb-e6850: [SKIP][33] ([fdo#109271] / [i915#2295]) -> [SKIP][34] ([fdo#109271])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-blb-e6850/igt@gem_exec_parallel@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-blb-e6850/igt@gem_exec_parallel@[email protected]
- fi-elk-e7500: [SKIP][35] ([fdo#109271] / [i915#2295]) -> [SKIP][36] ([fdo#109271])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-elk-e7500/igt@gem_exec_parallel@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-elk-e7500/igt@gem_exec_parallel@[email protected]
* igt@runner@aborted:
- fi-kbl-8809g: [FAIL][37] ([i915#1186] / [i915#2426]) -> [FAIL][38] ([i915#1186] / [i915#2426] / [i915#2722])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/fi-kbl-8809g/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/fi-kbl-8809g/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1186]: https://gitlab.freedesktop.org/drm/intel/issues/1186
[i915#1250]: https://gitlab.freedesktop.org/drm/intel/issues/1250
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2292]: https://gitlab.freedesktop.org/drm/intel/issues/2292
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#2675]: https://gitlab.freedesktop.org/drm/intel/issues/2675
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541
[k.org#204565]: https://bugzilla.kernel.org/show_bug.cgi?id=204565
Participating hosts (44 -> 40)
------------------------------
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u
Build changes
-------------
* Linux: CI_DRM_9395 -> Patchwork_18993
CI-20190529: 20190529
CI_DRM_9395: 83729b962cacdce11fe05033ad2493da61536ebf @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5871: ff519fd84618558c550bec07e7cc4b2c682f86ff @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18993: 1702176c40ec84b4ae74690055dcfb850ee47256 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
1702176c40ec drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON b992e94961f3 drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks e9838030d807 drm/i915/display: Implement DRM infoframe read for LSPCON 76e7ab963acd drm/i915/display: Implement infoframes readback for LSPCON 1a2451b47ea0 drm/i915/lspcon: Create separate infoframe_enabled helper 82c84c1a78fa drm/i915/display: Enable HDR for Parade based lspcon589d8106afd0 drm/i915/display: Nuke bogus lspcon check9e4c990a2a21 drm/i915/display: Enable colorspace programming for LSPCON devices 5904fa4c5259 drm/i915: Split intel_attach_colorspace_property() into HDMI vs. DP variants 19e480392aa1 drm/i915/display: Attach content type property for LSPCON caa7a05c57aa drm/i915/display: Add a WARN for invalid output range and format 819a38caa76a drm/i915/display: Fixes quantization range for YCbCr output 566633074760 drm/i915/display: Attach HDR property for capable Gen9 devices 015b28ecdd00 drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon 07f151724145 drm/i915/display: Add HDR Capability detection for LSPCON
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for Enable HDR on MCA LSPCON based Gen9 devices (rev12)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev12)
URL : https://patchwork.freedesktop.org/series/68081/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9395_full -> Patchwork_18993_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_18993_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_18993_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_18993_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_frontbuffer_tracking@psr-1p-rte:
- shard-skl: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl5/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl7/igt@[email protected]
* igt@syncobj_timeline@wait-all-snapshot:
- shard-glk: [PASS][3] -> [FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk4/igt@[email protected]
New tests
---------
New tests have been introduced between CI_DRM_9395_full and Patchwork_18993_full:
### New CI tests (1) ###
* boot:
- Statuses : 200 pass(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_18993_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-normal-all:
- shard-glk: [PASS][5] -> [DMESG-WARN][6] ([i915#118] / [i915#95])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk4/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk3/igt@[email protected]
* igt@i915_pm_rpm@system-suspend:
- shard-skl: [PASS][7] -> [INCOMPLETE][8] ([i915#151])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl1/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl9/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x42-offscreen:
- shard-skl: [PASS][9] -> [FAIL][10] ([i915#54])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl9/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl4/igt@[email protected]
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic:
- shard-glk: [PASS][11] -> [FAIL][12] ([i915#72])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk8/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk8/igt@[email protected]
* igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions:
- shard-kbl: [PASS][13] -> [DMESG-WARN][14] ([i915#1982])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-kbl2/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-kbl2/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions.html
* igt@kms_draw_crc@draw-method-rgb565-pwrite-ytiled:
- shard-glk: [PASS][15] -> [DMESG-WARN][16] ([i915#1982]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk1/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk7/igt@[email protected]
* igt@kms_flip@2x-flip-vs-dpms@ab-vga1-hdmi-a1:
- shard-hsw: [PASS][17] -> [DMESG-WARN][18] ([i915#1982])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-hsw2/igt@kms_flip@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-hsw6/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-tglb: [PASS][19] -> [FAIL][20] ([i915#2598])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb7/igt@kms_flip@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb7/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-fb-recreate@b-edp1:
- shard-skl: [PASS][21] -> [FAIL][22] ([i915#2122]) +2 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl5/igt@kms_flip@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-indfb-msflip-blt:
- shard-tglb: [PASS][23] -> [DMESG-WARN][24] ([i915#1982]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb7/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb7/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen:
- shard-skl: [PASS][25] -> [DMESG-WARN][26] ([i915#1982]) +6 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl10/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl1/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt:
- shard-skl: [PASS][27] -> [FAIL][28] ([i915#49]) +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl4/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl7/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [PASS][29] -> [FAIL][30] ([i915#1188])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl10/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [PASS][31] -> [FAIL][32] ([fdo#108145] / [i915#265]) +2 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl7/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl2/igt@[email protected]
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441]) +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-iclb6/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@perf@blocking:
- shard-skl: [PASS][35] -> [FAIL][36] ([i915#1542]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl2/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl10/igt@[email protected]
* igt@sysfs_heartbeat_interval@mixed@vecs0:
- shard-skl: [PASS][37] -> [FAIL][38] ([i915#1731])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl4/igt@sysfs_heartbeat_interval@[email protected]
#### Possible fixes ####
* igt@gem_exec_whisper@basic-contexts-forked:
- shard-glk: [DMESG-WARN][39] ([i915#118] / [i915#95]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk8/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk6/igt@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-skl: [INCOMPLETE][41] ([i915#198] / [i915#2405]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl3/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl8/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][43] ([i915#1436] / [i915#716]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl8/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl1/igt@[email protected]
* igt@i915_module_load@reload:
- shard-skl: [DMESG-WARN][45] ([i915#1982]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl4/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl4/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-256x85-random:
- shard-skl: [FAIL][47] ([i915#54]) -> [PASS][48] +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl10/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl8/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-b-256x256-left-edge:
- shard-glk: [DMESG-WARN][49] ([i915#1982]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk6/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk1/igt@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][51] ([i915#2122]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk1/igt@kms_flip@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk7/igt@kms_flip@[email protected]
* igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1:
- shard-kbl: [DMESG-WARN][53] ([i915#1982]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-kbl4/igt@kms_flip@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-kbl7/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1:
- shard-glk: [FAIL][55] ([i915#79]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk4/igt@kms_flip@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk3/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-badstride:
- shard-iclb: [DMESG-WARN][57] ([i915#1982]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-iclb7/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-iclb4/igt@[email protected]
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [SKIP][59] ([fdo#109441]) -> [PASS][60] +2 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-iclb8/igt@kms_psr@psr2_sprite_mmap_gtt.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
* igt@kms_universal_plane@disable-primary-vs-flip-pipe-c:
- shard-tglb: [DMESG-WARN][61] ([i915#1982]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb1/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb8/igt@[email protected]
* igt@prime_vgem@sync@rcs0:
- shard-snb: [INCOMPLETE][63] -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-snb6/igt@prime_vgem@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-snb5/igt@prime_vgem@[email protected]
#### Warnings ####
* igt@gem_exec_schedule@semaphore-power:
- shard-snb: [SKIP][65] ([fdo#109271] / [i915#2295]) -> [SKIP][66] ([fdo#109271]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-snb6/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-snb4/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-tglb: [WARN][67] ([i915#2681]) -> [WARN][68] ([i915#2681] / [i915#2684])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb2/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb5/igt@[email protected]
- shard-iclb: [WARN][69] ([i915#1804]) -> [WARN][70] ([i915#2684])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-iclb3/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-iclb2/igt@[email protected]
* igt@kms_cursor_legacy@cursor-vs-flip-atomic:
- shard-skl: [DMESG-WARN][71] ([i915#1982] / [i915#2295]) -> [DMESG-WARN][72] ([i915#1982])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl4/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max:
- shard-glk: [FAIL][73] ([fdo#108145] / [i915#2295] / [i915#265]) -> [FAIL][74] ([fdo#108145] / [i915#265])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk4/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk3/igt@[email protected]
- shard-skl: [FAIL][75] ([fdo#108145] / [i915#2295] / [i915#265]) -> [FAIL][76] ([fdo#108145] / [i915#265])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl1/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl9/igt@[email protected]
- shard-hsw: [SKIP][77] ([fdo#109271] / [i915#2295]) -> [SKIP][78] ([fdo#109271]) +1 similar issue
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-hsw4/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-hsw2/igt@[email protected]
- shard-kbl: [FAIL][79] ([fdo#108145] / [i915#2295] / [i915#265]) -> [FAIL][80] ([fdo#108145] / [i915#265])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-kbl1/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-kbl7/igt@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- shard-tglb: [INCOMPLETE][81] ([i915#1436] / [i915#1602] / [i915#1887] / [i915#2411] / [i915#456]) -> [DMESG-WARN][82] ([i915#1436] / [i915#1602] / [i915#1887] / [i915#2411])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb6/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb3/igt@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-tglb: [DMESG-WARN][83] ([i915#2295] / [i915#2411]) -> [DMESG-WARN][84] ([i915#2411]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb7/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb7/igt@[email protected]
* igt@runner@aborted:
- shard-kbl: [FAIL][85] ([i915#2295]) -> [FAIL][86] ([i915#2295] / [i915#2722])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-kbl7/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-kbl7/igt@[email protected]
- shard-iclb: ([FAIL][87], [FAIL][88]) ([i915#1814] / [i915#2295] / [i915#483]) -> ([FAIL][89], [FAIL][90]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-iclb3/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-iclb5/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-iclb1/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-iclb4/igt@[email protected]
- shard-apl: ([FAIL][91], [FAIL][92]) ([i915#1814] / [i915#2295]) -> ([FAIL][93], [FAIL][94], [FAIL][95], [FAIL][96], [FAIL][97], [FAIL][98], [FAIL][99], [FAIL][100], [FAIL][101], [FAIL][102], [FAIL][103], [FAIL][104], [FAIL][105], [FAIL][106], [FAIL][107], [FAIL][108], [FAIL][109], [FAIL][110], [FAIL][111], [FAIL][112], [FAIL][113], [FAIL][114], [FAIL][115], [FAIL][116], [FAIL][117]) ([i915#1610] / [i915#2295] / [i915#2722])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-apl3/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-apl7/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl2/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl1/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl8/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl3/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl4/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl4/igt@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl1/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl7/igt@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl3/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl1/igt@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl2/igt@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl1/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl8/igt@[email protected]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl7/igt@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl6/igt@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl4/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl8/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl6/igt@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl6/igt@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl8/igt@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl6/igt@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl3/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl3/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl2/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-apl7/igt@[email protected]
- shard-glk: ([FAIL][118], [FAIL][119], [FAIL][120]) ([i915#1814] / [i915#2295] / [i915#483] / [k.org#202321]) -> ([FAIL][121], [FAIL][122]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [k.org#202321])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk8/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk4/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-glk7/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk3/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-glk5/igt@[email protected]
- shard-tglb: ([FAIL][123], [FAIL][124]) ([i915#1602] / [i915#2295]) -> ([FAIL][125], [FAIL][126]) ([i915#1602] / [i915#2295] / [i915#2722])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb2/igt@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-tglb6/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb5/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-tglb3/igt@[email protected]
- shard-skl: ([FAIL][127], [FAIL][128]) ([i915#1436] / [i915#2295]) -> [FAIL][129] ([i915#2295] / [i915#2722])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl4/igt@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9395/shard-skl8/igt@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18993/shard-skl8/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#151]: https://gitlab.freedesktop.org/drm/intel/issues/151
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#1731]: https://gitlab.freedesktop.org/drm/intel/issues/1731
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1887]: https://gitlab.freedesktop.org/drm/intel/issues/1887
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2405]: https://gitlab.freedesktop.org/drm/intel/issues/2405
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2598]: https://gitlab.freedesktop.org/drm/intel/issues/2598
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#483]: https://gitlab.freedesktop.org/drm/intel/issues/483
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_9395 -> Patchwork_18993
CI-20190529: 20190529
CI_DRM_9395: 83729b962cacdce11fe05033ad2493da61536ebf @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5871: ff519fd84618558c550bec07e7cc4b2c682f86ff @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18993: 1702176c40ec84b4ae74690055dcfb850ee47256 @ 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_18993/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enable HDR on MCA LSPCON based Gen9 devices (rev14)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev14)
URL : https://patchwork.freedesktop.org/series/68081/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 7f90737a12fb drm/i915/display: Add HDR Capability detection for LSPCON a44d7eb6654e drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon 1319993255f3 drm/i915/display: Attach HDR property for capable Gen9 devices -:58: WARNING:LONG_LINE: line length of 108 exceeds 100 columns #58: FILE: drivers/gpu/drm/i915/display/intel_dp.c:6804: + connector->dev->mode_config.hdr_output_metadata_property,
total: 0 errors, 1 warnings, 0 checks, 45 lines checked36eb79c62329 drm/i915/display: Fixes quantization range for YCbCr output 5518242f17cc drm/i915/display: Add a WARN for invalid output range and format 8c6662304756 drm/i915/display: Attach content type property for LSPCON 953887a7e7fa drm/i915: Split intel_attach_colorspace_property() into HDMI vs. DP variants 952e986183d7 drm/i915/display: Enable colorspace programming for LSPCON devices 0d908347d855 drm/i915/display: Nuke bogus lspcon checka62b61152c33 drm/i915/display: Enable HDR for Parade based lspcon2897d74df2af drm/i915/lspcon: Create separate infoframe_enabled helper 617df78a8179 drm/i915/display: Implement infoframes readback for LSPCON 0fc199846536 drm/i915/display: Implement DRM infoframe read for LSPCON 9d54f5aa21a3 drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks de26a0b2bb4b drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Enable HDR on MCA LSPCON based Gen9 devices (rev14)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev14)
URL : https://patchwork.freedesktop.org/series/68081/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. - +drivers/gpu/drm/i915/gt/intel_reset.c:1312:5: warning: context imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block +drivers/gpu/drm/i915/gt/selftest_reset.c:100:20: expected void *in +drivers/gpu/drm/i915/gt/selftest_reset.c:100:20: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:100:20: warning: incorrect type in assignment (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:101:46: expected void const *src +drivers/gpu/drm/i915/gt/selftest_reset.c:101:46: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:101:46: warning: incorrect type in argument 2 (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:136:20: expected void *in +drivers/gpu/drm/i915/gt/selftest_reset.c:136:20: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:136:20: warning: incorrect type in assignment (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:137:46: expected void const *src +drivers/gpu/drm/i915/gt/selftest_reset.c:137:46: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:137:46: warning: incorrect type in argument 2 (different address spaces) +drivers/gpu/drm/i915/gt/selftest_reset.c:98:34: expected unsigned int [usertype] *s +drivers/gpu/drm/i915/gt/selftest_reset.c:98:34: got void [noderef] __iomem *[assigned] s +drivers/gpu/drm/i915/gt/selftest_reset.c:98:34: warning: incorrect type in argument 1 (different address spaces) +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read64' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write8' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write16' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write32' - different lock contexts for basic block +./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write8' - different lock contexts for basic block
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Enable HDR on MCA LSPCON based Gen9 devices (rev14)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev14)
URL : https://patchwork.freedesktop.org/series/68081/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9399 -> Patchwork_19001
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/index.html
New tests
---------
New tests have been introduced between CI_DRM_9399 and Patchwork_19001:
### New CI tests (1) ###
* boot:
- Statuses : 40 pass(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_19001 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_module_load@reload:
- fi-byt-j1900: [PASS][1] -> [DMESG-WARN][2] ([i915#1982]) +2 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/fi-byt-j1900/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/fi-byt-j1900/igt@[email protected]
* igt@vgem_basic@setversion:
- fi-tgl-y: [PASS][3] -> [DMESG-WARN][4] ([i915#402]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/fi-tgl-y/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/fi-tgl-y/igt@[email protected]
#### Possible fixes ####
* igt@debugfs_test@read_all_entries:
- fi-tgl-y: [DMESG-WARN][5] ([i915#402]) -> [PASS][6] +2 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/fi-tgl-y/igt@debugfs_test@read_all_entries.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/fi-tgl-y/igt@debugfs_test@read_all_entries.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-kbl-soraka: [DMESG-FAIL][7] ([i915#541]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html
* igt@kms_busy@basic@flip:
- fi-kbl-soraka: [DMESG-WARN][9] ([i915#1982]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/fi-kbl-soraka/igt@kms_busy@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/fi-kbl-soraka/igt@kms_busy@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-icl-u2: [DMESG-WARN][11] ([i915#1982]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/fi-icl-u2/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/fi-icl-u2/igt@[email protected]
#### Warnings ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-tgl-y: [DMESG-WARN][13] ([i915#2411]) -> [DMESG-WARN][14] ([i915#1982] / [i915#2411])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/fi-tgl-y/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/fi-tgl-y/igt@[email protected]
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541
Participating hosts (45 -> 40)
------------------------------
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9399 -> Patchwork_19001
CI-20190529: 20190529
CI_DRM_9399: b3d976d7d7851bcfcd64b5d6c29672a9e2462442 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5873: b6321b58dcaa41ba1d28aced42d6b15dc3d49ca2 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19001: de26a0b2bb4bae9572b9a722768ea8af4cb8c9df @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
de26a0b2bb4b drm/i915/display: [NOT FOR MERGE] Reduce blanking to support 4k60@10bpp for LSPCON 9d54f5aa21a3 drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks 0fc199846536 drm/i915/display: Implement DRM infoframe read for LSPCON 617df78a8179 drm/i915/display: Implement infoframes readback for LSPCON 2897d74df2af drm/i915/lspcon: Create separate infoframe_enabled helper a62b61152c33 drm/i915/display: Enable HDR for Parade based lspcon0d908347d855 drm/i915/display: Nuke bogus lspcon check952e986183d7 drm/i915/display: Enable colorspace programming for LSPCON devices 953887a7e7fa drm/i915: Split intel_attach_colorspace_property() into HDMI vs. DP variants 8c6662304756 drm/i915/display: Attach content type property for LSPCON 5518242f17cc drm/i915/display: Add a WARN for invalid output range and format 36eb79c62329 drm/i915/display: Fixes quantization range for YCbCr output 1319993255f3 drm/i915/display: Attach HDR property for capable Gen9 devices a44d7eb6654e drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon 7f90737a12fb drm/i915/display: Add HDR Capability detection for LSPCON
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/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 Enable HDR on MCA LSPCON based Gen9 devices (rev14)
In reply to Uma Shankar== Series Details ==
== Series Details ==
Series: Enable HDR on MCA LSPCON based Gen9 devices (rev14)
URL : https://patchwork.freedesktop.org/series/68081/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9399_full -> Patchwork_19001_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
New tests
---------
New tests have been introduced between CI_DRM_9399_full and Patchwork_19001_full:
### New CI tests (1) ###
* boot:
- Statuses : 200 pass(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_19001_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@psr2:
- shard-iclb: [PASS][1] -> [SKIP][2] ([i915#658])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-iclb2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-iclb4/igt@[email protected]
* igt@gem_exec_whisper@basic-fds-priority:
- shard-glk: [PASS][3] -> [DMESG-WARN][4] ([i915#118] / [i915#95])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-glk3/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-glk7/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][5] -> [SKIP][6] ([i915#2190])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-tglb5/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-tglb6/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x128-offscreen:
- shard-skl: [PASS][7] -> [FAIL][8] ([i915#54])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl1/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl2/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-c-128x128-top-edge:
- shard-hsw: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-hsw6/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-hsw8/igt@[email protected]
* igt@kms_cursor_legacy@basic-flip-before-cursor-atomic:
- shard-apl: [PASS][11] -> [DMESG-WARN][12] ([i915#1982]) +5 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-apl7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-apl3/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-dp1:
- shard-apl: [PASS][13] -> [FAIL][14] ([i915#79])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-apl7/igt@kms_flip@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-apl1/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
- shard-skl: [PASS][15] -> [FAIL][16] ([i915#2122])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl3/igt@kms_flip@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl6/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-render:
- shard-tglb: [PASS][17] -> [DMESG-WARN][18] ([i915#1982]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-render.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-tglb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt:
- shard-skl: [PASS][19] -> [DMESG-WARN][20] ([i915#1982]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl6/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl4/igt@[email protected]
* igt@kms_plane_lowres@pipe-a-tiling-yf:
- shard-kbl: [PASS][21] -> [DMESG-WARN][22] ([i915#165] / [i915#180] / [i915#78])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-kbl7/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-kbl2/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][23] -> [SKIP][24] ([fdo#109441]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-iclb7/igt@kms_psr@psr2_no_drrs.html
* igt@kms_sysfs_edid_timing:
- shard-hsw: [PASS][25] -> [FAIL][26] ([IGT#2])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-hsw8/igt@kms_sysfs_edid_timing.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-hsw6/igt@kms_sysfs_edid_timing.html
* igt@perf_pmu@module-unload:
- shard-tglb: [PASS][27] -> [DMESG-WARN][28] ([i915#1982] / [i915#262])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-tglb5/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-tglb6/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_gttfill@engines@rcs0:
- shard-glk: [DMESG-WARN][29] ([i915#118] / [i915#95]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-glk9/igt@gem_exec_gttfill@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-glk4/igt@gem_exec_gttfill@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-64x21-offscreen:
- shard-skl: [FAIL][31] ([i915#54]) -> [PASS][32] +5 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl5/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl8/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-c-256x256-bottom-edge:
- shard-tglb: [DMESG-WARN][33] ([i915#1982]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-tglb8/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-tglb3/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [FAIL][35] ([i915#2346]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl6/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_draw_crc@draw-method-xrgb8888-mmap-wc-xtiled:
- shard-skl: [FAIL][37] ([i915#52] / [i915#54]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl7/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl4/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-render:
- shard-apl: [DMESG-WARN][39] ([i915#1982]) -> [PASS][40] +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-apl6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-render.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-apl8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-gtt:
- shard-skl: [DMESG-WARN][41] ([i915#1982]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl10/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl1/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][43] ([i915#1188]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl7/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [FAIL][45] ([fdo#108145] / [i915#265]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl10/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl7/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][47] ([fdo#109642] / [fdo#111068]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-iclb1/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-iclb2/igt@[email protected]
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][49] ([fdo#109441]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-iclb1/igt@kms_psr@psr2_cursor_mmap_cpu.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][51] ([i915#1804] / [i915#2684]) -> [WARN][52] ([i915#2681] / [i915#2684]) +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-iclb7/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-iclb8/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: [DMESG-WARN][53] ([i915#1982]) -> [DMESG-FAIL][54] ([i915#1982])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl6/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl4/igt@[email protected]
* igt@runner@aborted:
- shard-glk: ([FAIL][55], [FAIL][56]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [k.org#202321]) -> ([FAIL][57], [FAIL][58]) ([i915#1814] / [i915#2295] / [i915#2722] / [k.org#202321])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-glk2/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-glk3/igt@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-glk8/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-glk6/igt@[email protected]
- shard-skl: [FAIL][59] ([i915#2295] / [i915#2722] / [i915#483]) -> [FAIL][60] ([i915#2295] / [i915#2722])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9399/shard-skl7/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19001/shard-skl4/igt@[email protected]
[IGT#2]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/2
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#483]: https://gitlab.freedesktop.org/drm/intel/issues/483
[i915#52]: https://gitlab.freedesktop.org/drm/intel/issues/52
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#78]: https://gitlab.freedesktop.org/drm/intel/issues/78
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_9399 -> Patchwork_19001
CI-20190529: 20190529
CI_DRM_9399: b3d976d7d7851bcfcd64b5d6c29672a9e2462442 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5873: b6321b58dcaa41ba1d28aced42d6b15dc3d49ca2 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19001: de26a0b2bb4bae9572b9a722768ea8af4cb8c9df @ 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_19001/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx