[Bug 105887] [GLK] no signal after switch resolution from 1080p at 23.98
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jun 29 21:32:31 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105887
--- Comment #109 from Clinton Taylor <clinton.a.taylor at intel.com> ---
> Maybe the connector check causes the
> initial issue here?
Daniel,
Using the v3 patch could you apply the following diff?
Thanks,-Clint
diff --git a/drivers/gpu/drm/i915/intel_ddi.c
b/drivers/gpu/drm/i915/intel_ddi.c
index 89bb5ce..b2ff394 100644
--- a/drivers/gpu/drm/i915/intel_ddi.c
+++ b/drivers/gpu/drm/i915/intel_ddi.c
@@ -1818,15 +1818,16 @@ void intel_ddi_disable_transcoder_func(const struct
inte
i915_reg_t reg = TRANS_DDI_FUNC_CTL(cpu_transcoder);
uint32_t val = I915_READ(reg);
-
val &= ~(TRANS_DDI_FUNC_ENABLE | TRANS_DDI_PORT_MASK |
TRANS_DDI_DP_VC_P
val |= TRANS_DDI_PORT_NONE;
I915_WRITE(reg, val);
+ DRM_ERROR(" *** connector type = %d\n", crtc_state->output_types);
if (dev_priv->quirks & QUIRK_INCREASE_DDI_DISABLED_TIME &&
- intel_crtc_has_type(crtc_state, INTEL_OUTPUT_HDMI)) {
- msleep(DDI_DISABLED_QUIRK_TIME);
+ (intel_crtc_has_type(crtc_state, INTEL_OUTPUT_HDMI) ||
+ intel_crtc_has_type(crtc_state, INTEL_OUTPUT_UNUSED))) {
DRM_DEBUG_KMS("Quirk Increase DDI disabled time\n");
+ msleep(DDI_DISABLED_QUIRK_TIME);
}
}
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_d
index ff42268..d3ad9c1 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -14956,7 +14956,6 @@ static int intel_dmi_reverse_brightness(const struct
dmi
/* ASRock ITX*/
{ 0x3185, 0x1849, 0x2212, quirk_increase_ddi_disabled_time },
{ 0x3184, 0x1849, 0x2212, quirk_increase_ddi_disabled_time },
-
};
static void intel_init_quirks(struct drm_device *dev)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180629/334f2c57/attachment.html>
More information about the intel-gfx-bugs
mailing list