[Bug 106291] drm.edid_firmware override does not work

[bugzilla-daemon at freedesktop.org]

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

--- Comment #26 from Ville Syrjala <ville.syrjala at linux.intel.com> ---
(In reply to Ville Syrjala from comment #25)
> (In reply to Wolfgang Haupt from comment #24)
> > Created attachment 139321 [details]
> > dpcd dump
> > 
> > Please note:
> > I have done this using ubuntu with drm-tip mainline kernel from 2.5.2018, as
> > my other system is a LibreELEC linux which has no packetmanager, dd didn't
> > work and I have no ddrescue there.
> > Hope it doesn't matter, both are quite recent drm-tip kernels.
> 
> 00000000  12 14 c4 01 01 15 01 81  00 00 04 00 0f 00 04 00 
> |................|
> 
> So it does in fact advertize 5.4Gbps link rate.
> 
> So it seems the the problem is due to the driver not reading/parsing the
> DPCD when we force the connector state. Not and impossible thing to do, but
> would certainly require shuffling a bunch of code around.

Actually, it just occurred to me that maybe the best option would be to change
the connector force to simply ignore the SINK_COUNT for DP, and otherwise work
exactly the same way as the normal detect path. That way the status could only
be forced in cases where there is an actual DP device we can talk to but
there's nothing plugged into its downstream ports.

Looks like we'd have to redo the locking scheme for the ->force() hook to match
how we handle the detect hook. Might be a good idea to do that anyway, since
the current scheme is rather inconsistent.

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