summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTorsten Duwe <torsten@lst.de>2013-03-23 15:39:34 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2013-03-23 10:46:10 -0700
commitc19b3b0f6eed552952845e4ad908dba2113d67b4 (patch)
tree37505f56235e5d9286c47d492f3809dfdede788a
parent16dad1d743d31a104a849c8944e6b9eb479f6cd7 (diff)
downloadop-kernel-dev-c19b3b0f6eed552952845e4ad908dba2113d67b4.zip
op-kernel-dev-c19b3b0f6eed552952845e4ad908dba2113d67b4.tar.gz
KMS: fix EDID detailed timing frame rate
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 <duwe@lst.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--drivers/gpu/drm/drm_edid.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 0dcbb63..e2acfdb 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drivers/gpu/drm/drm_edid.c
@@ -1715,6 +1715,7 @@ set_size:
}
mode->type = DRM_MODE_TYPE_DRIVER;
+ mode->vrefresh = drm_mode_vrefresh(mode);
drm_mode_set_name(mode);
return mode;
OpenPOWER on IntegriCloud