| commit | c19b3b0f6eed552952845e4ad908dba2113d67b4 | |
| author | Torsten Duwe <torsten@lst.de> | |
| Sat, 23 Mar 2013 14:39:34 +0000 (23 15:39 +0100) | ||
| committer | Linus Torvalds <torvalds@linux-foundation.org> | |
| Sat, 23 Mar 2013 17:46:10 +0000 (23 10:46 -0700) | ||
| tree | 37505f56235e5d9286c47d492f3809dfdede788a | treesnapshot (tar.gz zip) |
| parent | 16dad1d743d31a104a849c8944e6b9eb479f6cd7 | commitdiff |
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>
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>
| drivers/gpu/drm/drm_edid.c | diffblobblamehistory |