KMS: fix EDID detailed timing frame rate
authorTorsten Duwe <torsten@lst.de>
Sat, 23 Mar 2013 14:39:34 +0000 (15:39 +0100)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 27 Mar 2013 02:41:24 +0000 (02:41 +0000)
commitb5393b0f83a0ea21bb6002ca5c8015931b49fc8c
tree4be355a0811fb34b9f0382328cb0c9fb1a400da3
parent1b5ee14aafbdee09fc04d1a66162378f65652651
KMS: fix EDID detailed timing frame rate

commit c19b3b0f6eed552952845e4ad908dba2113d67b4 upstream.

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.

Signed-off-by: Torsten Duwe <duwe@lst.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/gpu/drm/drm_edid.c