[Bug 72334] [BYT Regression]igt/drv_suspend/fence-restore-tiled2untiled fails

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Dec 10 01:19:59 PST 2013


https://bugs.freedesktop.org/show_bug.cgi?id=72334

lu hua <huax.lu at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #3 from lu hua <huax.lu at intel.com> ---
Bisect shows:f69e515699d8e9b1c25dcfe1c4c6f435087495d2 is the first bad commit
commit f69e515699d8e9b1c25dcfe1c4c6f435087495d2
Author: Duncan Laurie <dlaurie at chromium.org>
Date:   Wed Nov 13 17:59:43 2013 -0800

    i915: Use 120MHz LVDS SSC clock for gen5/gen6/gen7

    We had been using a DMI table workaround to select the right
    frequency for devices, but this is fragile and must be updated
    with every new platform.

    Instead the default case when VBT is missing is changed to use
    120MHz clock for LVDS SSC for these generations.

    The docs for 2010-Core, SandyBridge, and IvyBridge all indicate
    that the reference frequency for LVDS is 120MHz:

    "2010 Core"
    http://intellinuxgraphics.org/IHD_OS_Vol3_Part3r2.pdf
    page 38
    Reference Frequency: 120MHz for CRT and LVDS.  100MHz for the FDI.

    "2011 SandyBridge"
    http://intellinuxgraphics.org/documentation/SNB/IHD_OS_Vol3_Part3.pdf
    page 33
    Reference Frequency: 120MHz for CRT, HDMI, LVDS.  100MHz for the FDI.

    "2012 IvyBridge"
    http://intellinuxgraphics.org/documentation/IVB/IHD_OS_Vol3_Part4.pdf
    page 27
    Reference Frequency: 120 MHz for CRT, HDMI, LVDS, 100MHz for the FDI.

    Signed-off-by: Duncan Laurie <dlaurie at chromium.org>
    [olof: Fixup for recent base, switched from if/else to single call]
    Signed-off-by: Olof Johansson <olof at lixom.net>
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi at gmail.com>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20131210/92c1dff2/attachment.html>


More information about the intel-gfx-bugs mailing list