[Bug 97971] Reading EDID on valleyview(device id: 0x0f31) fails

[bugzilla-daemon at freedesktop.org]

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

--- Comment #5 from Jani Nikula <jani.nikula at intel.com> ---
杨波, can you get /sys/kernel/debug/dri/0/i915_vbt or
/sys/kernel/debug/dri/0/i915_opregion from the original reporter?

Ville, any idea if we should be looking at some other ddc pin in the VBT, or is
the IS_VALLEYVIEW() thing all right? Are there any machines that would have
both VGA and DVI connectors, or does having DVI always mean that the VGA is
routed to DVI-I?

The original commit adding the retry on DVI-I ddc pin isn't too helpful:

commit 8e4d36b993898b344f9176147f1dfeca583f81fd
Author: ling.ma at intel.com <ling.ma at intel.com>
Date:   Tue Jun 30 11:35:34 2009 +0800

    drm/i915: crt fetch EDID by DVI-I converter on G4x platform

    Usually crt mainly get modes via GPIOA ports.
    However on G4X platform we need to probe possible
    ports for DVI-I, which could be wired to GPIOD,
    then fetch our desired EDID, i.e on DG45ID platform
    we successfully fetch EDID by GPIOD port.

    It fixed freedesktop.org bug #21084

    Signed-off-by: Ma Ling <ling.ma at intel.com>
    Signed-off-by: Eric Anholt <eric at anholt.net>

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