From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98352] [ctg bat] igt@kms_flip@basic-flip-vs-wf_vblank
Date: Mon, 24 Oct 2016 10:03:33 +0000 [thread overview]
Message-ID: <bug-98352-502-lG3MoNQn38@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98352-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 790 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98352
--- Comment #2 from Ville Syrjala <ville.syrjala@linux.intel.com> ---
The problem on this machine seems to be that the clock is about .6% off,
whereas the test will accept a deviation up to .5%.
I also have a VLV machine with DSI that suffers from a similar problem. I think
for internal panels the best solution might be for the kernel to fix up the
reported clock for the fixed mode. Not sure what we'd do about the EDID though,
assuming the the panel has one and the difference in the clocks would be large
enough to be visible in the EDID timings. And of course not all modes coming
from the EDID even have actual detailed timing descriptors.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1592 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-24 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-98352-502@http.bugs.freedesktop.org/>
2016-10-21 9:37 ` [Bug 98352] [ctg bat] igt@kms_flip@basic-flip-vs-wf_vblank bugzilla-daemon
2016-10-24 10:03 ` bugzilla-daemon [this message]
2016-10-24 10:14 ` bugzilla-daemon
2016-10-25 11:07 ` bugzilla-daemon
2017-09-14 21:58 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98352-502-lG3MoNQn38@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox