From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-Id: <20130411202553.365379721@goodmis.org> Date: Thu, 11 Apr 2013 16:25:47 -0400 From: Steven Rostedt To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Torsten Duwe Subject: [ 044/171 ] KMS: fix EDID detailed timing frame rate References: <20130411202503.783159048@goodmis.org> Content-Disposition: inline; filename=0044-KMS-fix-EDID-detailed-timing-frame-rate.patch Sender: linux-kernel-owner@vger.kernel.org List-ID: 3.6.11.2 stable review patch. If anyone has any objections, please let me know. ------------------ From: Torsten Duwe [ Upstream commit c19b3b0f6eed552952845e4ad908dba2113d67b4 ] When KMS has parsed an EDID "detailed timing", it leaves the frame rate zeroed. Consecutive (debug-) output of that mode thus yields 0 for vsync. This simple fix also speeds up future invocations of drm_mode_vrefresh(). While it is debatable whether this qualifies as a -stable fix I'd apply it for consistency's sake; drm_helper_probe_single_connector_modes() does the same thing already for all probed modes. Cc: stable@vger.kernel.org Signed-off-by: Torsten Duwe Signed-off-by: Linus Torvalds Signed-off-by: Steven Rostedt --- drivers/gpu/drm/drm_edid.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c index fafd5a1..24763fa 100644 --- a/drivers/gpu/drm/drm_edid.c +++ b/drivers/gpu/drm/drm_edid.c @@ -960,6 +960,7 @@ set_size: } mode->type = DRM_MODE_TYPE_DRIVER; + mode->vrefresh = drm_mode_vrefresh(mode); drm_mode_set_name(mode); return mode; -- 1.7.10.4