drm/dp: DRM DP helper for reading Ignore MSA from DPCD
PATCH v5 1/3 drm/dp: DRM DP helper for reading Ignore MSA from DPCD
DP sink device sets the Ignore MSA bit in its DP_DOWNSTREAM_PORT_COUNT register to indicate its ability to ignore the MSA video timing parameters and its ability to support seamless video timing change over a range of timing exposed by DisplayID and EDID.
This is required for the sink to indicate that it is Adaptive sync capable.
v3:
* Fi the typo in commit message (Manasi)
v2:
* Rename to describe what the function does (Jani Nikula)
--- include/drm/drm_dp_helper.h | 8 ++++++++ 1 file changed, 8 insertions(+)
include/drm/drm_dp_helper.h +8 -0
@@ -1454,6 +1454,14 @@ drm_dp_alternate_scrambler_reset_cap(const u8 dpcd[DP_RECEIVER_CAP_SIZE])DP_ALTERNATE_SCRAMBLER_RESET_CAP ; } +/* Ignore MSA timing for Adaptive Sync support on DP 1.4 */ +static inline bool +drm_dp_sink_can_do_video_without_timing_msa (const u8 dpcd[DP_RECEIVER_CAP_SIZE ]) +{ +return dpcd[DP_DOWN_STREAM_PORT_COUNT ] & +DP_MSA_TIMING_PAR_IGNORED ; +} +/* * DisplayPort AUX channel */
Signature · 6 lines
2.19.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v5 2/3 drm/i915/dp: Attach and set drm connector VRR property
From: Aditya Swarup <[email protected]>
This function sets the VRR property for connector based on the platform support, EDID monitor range and DP sink DPCD capability of outputing video without msa timing information.
v5:
* Fix the vrr prop not being set in kernel (Manasi)
* Unset the prop on connector disconnect (Manasi)
v4:
* Rebase (Mansi)
v3:
* intel_dp_is_vrr_capable can be used for debugfs, make it non static (Manasi)
v2:
* Just set this in intel_dp_get_modes instead of new hook (Jani)
--- drivers/gpu/drm/i915/display/intel_dp.c | 27 +++++++++++++++++++++++++ drivers/gpu/drm/i915/display/intel_dp.h | 2 ++ 2 files changed, 29 insertions(+)
drivers/gpu/drm/i915/display/intel_dp.c +27 -0
@@ -6153,6 +6153,9 @@ intel_dp_detect(struct drm_connector *connector,if (status == connector_status_disconnected) {memset (&intel_dp->compliance,0 ,sizeof (intel_dp->compliance));memset (intel_dp->dsc_dpcd,0 ,sizeof (intel_dp->dsc_dpcd)); +/*Reset the immutable VRR Capable property */ +drm_connector_set_vrr_capable_property (connector, + false);if (intel_dp->is_mst) { drm_dbg_kms(&dev_priv->drm,
@@ -6260,6 +6263,23 @@ intel_dp_force(struct drm_connector *connector)intel_display_power_put (dev_priv, aux_domain, wakeref); } +bool intel_dp_is_vrr_capable (struct drm_connector *connector) +{ +struct intel_dp *intel_dp =intel_attached_dp (to_intel_connector (connector)); +const struct drm_display_info *info = &connector->display_info; +struct drm_i915_private *dev_priv =to_i915 (connector->dev); + +/* +* DP Sink is capable of Variable refresh video timings if +* Ignore MSA bit is set in DPCD. +* EDID monitor range also should be atleast 10 for reasonable +* Adaptive sync/ VRR end user experience. +*/ +return INTEL_GEN (dev_priv) >=12 && +drm_dp_sink_can_do_video_without_timing_msa (intel_dp->dpcd) && + info->monitor_range.max_vfreq - info->monitor_range.min_vfreq >10 ; +} +static int intel_dp_get_modes (struct drm_connector *connector) {struct intel_connector *intel_connector =to_intel_connector (connector);
@@ -6268,6 +6288,10 @@ static int intel_dp_get_modes(struct drm_connector *connector) edid = intel_connector->detect_edid;if (edid) {int ret =intel_connector_update_modes (connector, edid); + +if (intel_dp_is_vrr_capable (connector)) +drm_connector_set_vrr_capable_property (connector, + true);if (ret)return ret; }
@@ -7354,6 +7378,9 @@ intel_dp_add_properties(struct intel_dp *intel_dp, struct drm_connector *connect connector->state->scaling_mode =DRM_MODE_SCALE_ASPECT ; } + +if (INTEL_GEN (dev_priv) >=12 ) +drm_connector_attach_vrr_capable_property (connector); }static void intel_dp_init_panel_power_timestamps (struct intel_dp *intel_dp)
drivers/gpu/drm/i915/display/intel_dp.h +2 -0
@@ -14,6 +14,7 @@ enum pipe;enum port ;struct drm_connector_state ;struct drm_encoder ; +struct drm_connector ;struct drm_i915_private ;struct drm_modeset_acquire_ctx ;struct intel_connector ;
@@ -119,6 +120,7 @@ void intel_dp_set_infoframes(struct intel_encoder *encoder, bool enable, const struct drm_connector_state *conn_state);bool intel_digital_port_connected (struct intel_encoder *encoder);void intel_dp_process_phy_request (struct intel_dp *intel_dp); +bool intel_dp_is_vrr_capable (struct drm_connector *connector);static inline unsigned int intel_dp_unused_lane_mask (int lane_count) {
Signature · 6 lines
2.19.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v5 3/3 drm/i915/dp: Expose connector VRR info via debugfs
In reply to Manasi NavareFrom: Bhanuprakash Modem <[email protected]>
[Why]
It's useful to know the min and max vrr range for IGT testing.
[How]
Expose the min and max vfreq for the connector via a debugfs file on the connector, "i915_vrr_info".
Example usage: cat /sys/kernel/debug/dri/0/DP-1/i915_vrr_info
v5:
* Rename to vrr_range to match AMD debugfs
v4:
* Rebase
v3:
* Remove the unnecessary debug print (Manasi) v2:
* Fix the typo in max_vfreq (Manasi)
* Change the name of node to i915_vrr_info so we can add other vrr info for more debug info (Manasi)
* Change the VRR capable to display Yes or No (Manasi)
* Fix indentation checkpatch errors (Manasi)
--- .../drm/i915/display/intel_display_debugfs.c | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_display_debugfs.c +21 -1
@@ -2185,6 +2185,21 @@ static const struct file_operations i915_dsc_fec_support_fops = { .write = i915_dsc_fec_support_write }; +static int vrr_range_show (struct seq_file *m,void *data) +{ +struct drm_connector *connector = m->private; + +if (connector->status != connector_status_connected) +return -ENODEV ; + +seq_printf (m,"Vrr_capable: %s\n" ,yesno (intel_dp_is_vrr_capable (connector))); +seq_printf (m,"Min: %u\n" , (u8 )connector->display_info.monitor_range.min_vfreq); +seq_printf (m,"Max: %u\n" , (u8 )connector->display_info.monitor_range.max_vfreq); + +return 0 ; +} +DEFINE_SHOW_ATTRIBUTE (vrr_range); +/** * intel_connector_debugfs_add - add i915 specific connector debugfs files * @connector: pointer to a registered drm_connector
@@ -2219,10 +2234,15 @@ int intel_connector_debugfs_add(struct drm_connector *connector)if (INTEL_GEN (dev_priv) >=10 && (connector->connector_type == DRM_MODE_CONNECTOR_DisplayPort || - connector->connector_type == DRM_MODE_CONNECTOR_eDP)) + connector->connector_type == DRM_MODE_CONNECTOR_eDP)) {debugfs_create_file ("i915_dsc_fec_support" ,S_IRUGO , root, connector, &i915_dsc_fec_support_fops); +if (INTEL_GEN (dev_priv) >=12 ) +debugfs_create_file ("vrr_range" ,S_IRUGO , + root, connector, &vrr_range_fops); + } +/* Legacy panels doesn't lpsp on any platform */ if ((INTEL_GEN(dev_priv) >= 9 || IS_HASWELL(dev_priv) || IS_BROADWELL(dev_priv)) &&
Signature · 6 lines
2.19.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
RE: [PATCH v5 3/3] drm/i915/dp: Expose connector VRR info via debugfs
-----Original Message-----
From: Navare, Manasi D <[email protected]>
Sent: Wednesday, May 13, 2020 11:05 AM
To: [email protected]; [email protected]
Cc: Modem, Bhanuprakash <[email protected]>; Navare, Manasi D <[email protected]>; Jani Nikula <[email protected]>; Ville Syrjälä <[email protected]>
Subject: [PATCH v5 3/3] drm/i915/dp: Expose connector VRR info via debugfs
From: Bhanuprakash Modem <[email protected]>
[Why]
It's useful to know the min and max vrr range for IGT testing.
[How]
Expose the min and max vfreq for the connector via a debugfs file on the connector, "i915_vrr_info".
Example usage: cat /sys/kernel/debug/dri/0/DP-1/i915_vrr_info
[Bhanu]: Can you please fix the commit message? 's/i915_vrr_info/vrr_range/'
v5:
* Rename to vrr_range to match AMD debugfs
v4:
* Rebase
v3:
* Remove the unnecessary debug print (Manasi)
v2:
* Fix the typo in max_vfreq (Manasi)
* Change the name of node to i915_vrr_info so we can add other vrr info for more debug info (Manasi)
* Change the VRR capable to display Yes or No (Manasi)
* Fix indentation checkpatch errors (Manasi)
--- .../drm/i915/display/intel_display_debugfs.c | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_display_debugfs.c +7 -0
@@ -2185,6 +2185,21 @@ static const struct file_operations i915_dsc_fec_support_fops = { .write = i915_dsc_fec_support_write }; +static int vrr_range_show (struct seq_file *m,void *data) { +struct drm_connector *connector = m->private; + +if (connector->status != connector_status_connected) +return -ENODEV ; + +seq_printf (m,"Vrr_capable: %s\n" ,yesno (intel_dp_is_vrr_capable (connector)));
[Bhanu]: As we can read "vrr_capable" property from DRM_IOCTL_MODE_OBJ_GETPROPERTIES ioctl, I think we don't need to expose "vrr_capable" through debugfs.
+ seq_printf(m, "Min: %u\n", (u8)connector->display_info.monitor_range.min_vfreq);
+ seq_printf(m, "Max: %u\n",
+(u8)connector->display_info.monitor_range.max_vfreq);
+
+ return 0;
+}
+DEFINE_SHOW_ATTRIBUTE(vrr_range);
+
/**
* intel_connector_debugfs_add - add i915 specific connector debugfs files
* @connector: pointer to a registered drm_connector @@ -2219,10 +2234,15 @@ int intel_connector_debugfs_add(struct drm_connector *connector)
if (INTEL_GEN(dev_priv) >= 10 &&
(connector->connector_type == DRM_MODE_CONNECTOR_DisplayPort ||
- connector->connector_type == DRM_MODE_CONNECTOR_eDP))
+ connector->connector_type == DRM_MODE_CONNECTOR_eDP)) {
debugfs_create_file("i915_dsc_fec_support", S_IRUGO, root,
connector, &i915_dsc_fec_support_fops);
+ if (INTEL_GEN(dev_priv) >= 12)
+ debugfs_create_file("vrr_range", S_IRUGO,
+ root, connector, &vrr_range_fops);
+ }
+
/* Legacy panels doesn't lpsp on any platform */ if ((INTEL_GEN(dev_priv) >= 9 || IS_HASWELL(dev_priv) ||
IS_BROADWELL(dev_priv)) &&
--
2.19.1
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v5 3/3] drm/i915/dp: Expose connector VRR info via debugfs
Quoted 55 lines · Bhanuprakash
-----Original Message-----
From: Navare, Manasi D <[email protected]>
Sent: Wednesday, May 13, 2020 11:05 AM
To: [email protected]; [email protected]
Cc: Modem, Bhanuprakash <[email protected]>; Navare, Manasi D <[email protected]>; Jani Nikula <[email protected]>; Ville Syrjälä <[email protected]>
Subject: [PATCH v5 3/3] drm/i915/dp: Expose connector VRR info via debugfsFrom: Bhanuprakash Modem <[email protected]>
[Why]
It's useful to know the min and max vrr range for IGT testing.[How]
Expose the min and max vfreq for the connector via a debugfs file on the connector, "i915_vrr_info".Example usage: cat
/sys/kernel/debug/dri/0/DP-1/i915_vrr_info[Bhanu]: Can you please fix the commit message? 's/i915_vrr_info/vrr_range/'
v5:
* Rename tovrr_rangeto match AMD debugfs
v4:
* Rebase
v3:
* Remove the unnecessary debug print (Manasi)
v2:
* Fix the typo inmax_vfreq(Manasi)
* Change the name of node toi915_vrr_infoso we can add other vrr info for more debug info (Manasi)
* Change the VRR capable to display Yes or No (Manasi)
* Fix indentation checkpatch errors (Manasi)Signed-off-by Bhanuprakash Modem <[email protected]>Signed-off-by Manasi Navare <[email protected]>Cc Jani Nikula <[email protected]>Cc Ville Syrjälä <[email protected]>Tested-by Manasi Navare <[email protected]>--- .../drm/i915/display/intel_display_debugfs.c | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_display_debugfs.c +7
-0@@ -2185,6 +2185,21 @@ static const struct file_operations i915_dsc_fec_support_fops = { .write = i915_dsc_fec_support_write }; +static int vrr_range_show (struct seq_file *m,void *data) { +struct drm_connector *connector = m->private; + +if (connector->status != connector_status_connected) +return -ENODEV ; + +seq_printf (m,"Vrr_capable: %s\n" ,yesno (intel_dp_is_vrr_capable (connector)));
Quoted 1 line
[Bhanu]: As we can read "
vrr_capable" property fromDRM_IOCTL_MODE_OBJ_GETPROPERTIESioctl, I think we don't need to expose "vrr_capable" through debugfs.
Yes we can get it with the Get prop IOCTL, but having it in debugfs will still be a good debug info without needing to call the ioctl
Manasi
Quoted 28 lines
drivers/gpu/drm/i915/display/intel_display_debugfs.c +14
-2+seq_printf (m,"Min: %u\n" , (u8 )connector->display_info.monitor_range.min_vfreq); +seq_printf (m,"Max: %u\n" , +(u8 )connector->display_info.monitor_range.max_vfreq); + +return 0 ; +} +DEFINE_SHOW_ATTRIBUTE (vrr_range); +/** * intel_connector_debugfs_add - add i915 specific connector debugfs files * @connector: pointer to a registered drm_connector @@ -2219,10 +2234,15 @@ int intel_connector_debugfs_add(struct drm_connector *connector) if (INTEL_GEN(dev_priv) >= 10 && (connector->connector_type == DRM_MODE_CONNECTOR_DisplayPort || -connector->connector_type == DRM_MODE_CONNECTOR_eDP)) +connector->connector_type == DRM_MODE_CONNECTOR_eDP)) { debugfs_create_file("i915_dsc_fec_support", S_IRUGO, root, connector, &i915_dsc_fec_support_fops); +if (INTEL_GEN(dev_priv) >= 12) +debugfs_create_file("vrr_range", S_IRUGO, +root, connector, &vrr_range_fops); +} +/* Legacy panels doesn't lpsp on any platform */ if ((INTEL_GEN(dev_priv) >= 9 || IS_HASWELL(dev_priv) || IS_BROADWELL(dev_priv)) && --
Quoted 2 lines
2.19.1
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v5 3/3] drm/i915/dp: Expose connector VRR info via debugfs
In reply to Manasi Navare[Why]
It's useful to know the min and max vrr range for IGT testing.
[How]
Expose the min and max vfreq for the connector via a debugfs file on the connector, "vrr_range".
Example usage: cat /sys/kernel/debug/dri/0/DP-1/vrr_range
v5:
* Rename to vrr_range to match AMD debugfs
v4:
* Rebase
v3:
* Remove the unnecessary debug print (Manasi)
v2:
* Fix the typo in max_vfreq (Manasi)
* Change the name of node to i915_vrr_info so we can add other vrr info for more debug info (Manasi)
* Change the VRR capable to display Yes or No (Manasi)
* Fix indentation checkpatch errors (Manasi)
--- .../drm/i915/display/intel_display_debugfs.c | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_display_debugfs.c +15 -0
@@ -2185,6 +2185,21 @@ static const struct file_operations i915_dsc_fec_support_fops = { .write = i915_dsc_fec_support_write }; +static int vrr_range_show (struct seq_file *m,void *data) { +struct drm_connector *connector = m->private; + +if (connector->status != connector_status_connected) +return -ENODEV ; + +seq_printf (m,"Vrr_capable: %s\n" ,yesno (intel_dp_is_vrr_capable (connector))); +seq_printf (m,"Min: %u\n" , (u8 )connector->display_info.monitor_range.min_vfreq); +seq_printf (m,"Max: %u\n" , +(u8 )connector->display_info.monitor_range.max_vfreq); + +return 0 ; +} +DEFINE_SHOW_ATTRIBUTE (vrr_range); +/** * intel_connector_debugfs_add - add i915 specific connector debugfs files * @connector: pointer to a registered drm_connector @@ -2219,10 +2234,15 @@ int intel_connector_debugfs_add(struct drm_connector *connector)
if (INTEL_GEN(dev_priv) >= 10 &&
(connector->connector_type == DRM_MODE_CONNECTOR_DisplayPort ||
- connector->connector_type == DRM_MODE_CONNECTOR_eDP))
+ connector->connector_type == DRM_MODE_CONNECTOR_eDP)) {
debugfs_create_file("i915_dsc_fec_support", S_IRUGO, root,
connector, &i915_dsc_fec_support_fops);
+ if (INTEL_GEN(dev_priv) >= 12)
+ debugfs_create_file("vrr_range", S_IRUGO,
+ root, connector, &vrr_range_fops);
+ }
+
/* Legacy panels doesn't lpsp on any platform */ if ((INTEL_GEN(dev_priv) >= 9 || IS_HASWELL(dev_priv) ||
IS_BROADWELL(dev_priv)) &&
--
2.19.1
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD
In reply to Manasi Navare== Series Details ==
== Series Details ==
Series: series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD
URL : https://patchwork.freedesktop.org/series/77204/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f6ad5ff374c2 drm/dp: DRM DP helper for reading Ignore MSA from DPCD
2aca669eeacd drm/i915/dp: Attach and set drm connector VRR property
a2b5aa381b03 drm/i915/dp: Expose connector VRR info via debugfs
-:73: WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IRUGO' are not preferred. Consider using octal permissions '0444'.
#73: FILE: drivers/gpu/drm/i915/display/intel_display_debugfs.c:2242:
+ debugfs_create_file("vrr_range", S_IRUGO,total: 0 errors, 1 warnings, 0 checks, 37 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD
In reply to Manasi Navare== Series Details ==
== Series Details ==
Series: series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD
URL : https://patchwork.freedesktop.org/series/77204/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8471 -> Patchwork_17638
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17638 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17638, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17638/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17638:
### IGT changes ###
#### Possible regressions ####
* igt@kms_chamelium@dp-hpd-fast:
- fi-cml-u2: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8471/fi-cml-u2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17638/fi-cml-u2/igt@[email protected]
- fi-kbl-7500u: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8471/fi-kbl-7500u/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17638/fi-kbl-7500u/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17638 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@i915_selftest@live@objects:
- fi-bwr-2160: [INCOMPLETE][5] ([i915#489]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8471/fi-bwr-2160/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17638/fi-bwr-2160/igt@i915_selftest@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1803]: https://gitlab.freedesktop.org/drm/intel/issues/1803
[i915#489]: https://gitlab.freedesktop.org/drm/intel/issues/489
Participating hosts (49 -> 12)
------------------------------
ERROR: It appears as if the changes made in Patchwork_17638 prevented too many machines from booting.
Missing (37): fi-kbl-soraka fi-bdw-gvtdvm fi-icl-u2 fi-apl-guc fi-snb-2520m fi-icl-y fi-skl-lmem fi-byt-n2820 fi-icl-guc fi-icl-dsi fi-skl-6600u fi-snb-2600 fi-bxt-dsi fi-bdw-5557u fi-cml-s fi-bsw-n3050 fi-byt-j1900 fi-glk-dsi fi-hsw-4770 fi-ivb-3770 fi-elk-e7500 fi-bsw-nick fi-skl-6700k2 fi-kbl-r fi-ilk-m540 fi-ehl-1 fi-skl-guc fi-cfl-8700k fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-cfl-guc fi-kbl-guc fi-whl-u fi-kbl-x1275 fi-bsw-kefka fi-byt-clapper
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8471 -> Patchwork_17638
CI-20190529: 20190529
CI_DRM_8471: 3c84a88ed50e99b200fac400a9b817a23d399c01 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5651: e54e2642f1967ca3c488db32264607df670d1dfb @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17638: a2b5aa381b03ce6944ec2f184d8383ea1a942b04 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a2b5aa381b03 drm/i915/dp: Expose connector VRR info via debugfs 2aca669eeacd drm/i915/dp: Attach and set drm connector VRR property f6ad5ff374c2 drm/dp: DRM DP helper for reading Ignore MSA from DPCD
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17638/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD (rev2)
In reply to Manasi Navare== Series Details ==
== Series Details ==
Series: series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD (rev2)
URL : https://patchwork.freedesktop.org/series/77204/
State : failure
== Summary ==
Applying: drm/dp: DRM DP helper for reading Ignore MSA from DPCD
Applying: drm/i915/dp: Attach and set drm connector VRR property
Applying: drm/i915/dp: Expose connector VRR info via debugfs
error: corrupt patch at line 40
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch Patch failed at 0003 drm/i915/dp: Expose connector VRR info via debugfs When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD (rev3)
In reply to Manasi Navare== Series Details ==
== Series Details ==
Series: series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD (rev3)
URL : https://patchwork.freedesktop.org/series/77204/
State : failure
== Summary ==
Applying: drm/dp: DRM DP helper for reading Ignore MSA from DPCD
Applying: drm/i915/dp: Attach and set drm connector VRR property
Applying: drm/i915/dp: Expose connector VRR info via debugfs .git/rebase-apply/patch:40: trailing whitespace.
seq_printf(m, "Max: %u\n",
error: patch failed: drivers/gpu/drm/i915/display/intel_display_debugfs.c:2185
error: drivers/gpu/drm/i915/display/intel_display_debugfs.c: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
hint: Use 'git am --show-current-patch=diff' to see the failed patch Using index info to reconstruct a base tree...
Patch failed at 0003 drm/i915/dp: Expose connector VRR info via debugfs When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx