Summary: | [v4.9 PATCH] DisplayPort Monitor Doesn't Come Back From Sleep | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Palmer Dabbelt <palmer> | ||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Status: | CLOSED FIXED | QA Contact: | Luis Botello <luis.botello.ortega> | ||||||
Severity: | blocker | ||||||||
Priority: | highest | CC: | intel-gfx-bugs, manasi.d.navare, ricardo.vega | ||||||
Version: | XOrg git | Keywords: | bisected, regression | ||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | ALL | i915 features: | display/DP | ||||||
Attachments: |
|
Description
Palmer Dabbelt
2017-02-10 21:16:11 UTC
Can you add a signed-off-by for your patch (See Developer's Certificate of Origin 1.1 in Documentation/process/submitting-patches.rst) and send it to intel-gfx@lists.freedesktop.org? Or just add an s-o-b here and I'll send it on. I sent the patch Created attachment 129515 [details] [review] drm/i915: Fix DisplayPort Hotplug I don't see my message in the intel-gfx mailing list archive so I'm worried it got lost somehow. I've attached the patch I sent out here, just in case. I'm experiencing the same issue on a PA328Q connected via DisplayPort. It must be doing something weird with the HPD line. When the monitor comes out of standby it is not detected by my stock GNOME 3 environemnt. I have to manually turn if off and on again to use it properly. Seems like all newer ASUS monitor seem to be affected by this behaviour. I'm on drm-intel-nightly which is currently based on 4.11-rc5. Ville has patch: https://patchwork.freedesktop.org/series/19601/ commit 1a36147bb93921651f7fbd7a6e522da6c349081b Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Wed Apr 12 22:30:17 2017 +0300 drm/i915: Perform link quality check unconditionally during long pulse |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.