Curently after resume we reset all connector status to unknown and then try to tell userspace about the probable changes (e.g. a laptop being unplugged from one dock and plugged into another). However, we call drm_helper_hpd_irq_event() to send the hotplug event to userspace which first does a check of connector->status before deciding if userspace needs to know about the event. This will filter out the above scenario of one output being replaced because it only checks the status and not whether the output is the same. Always send the hotplug uevent to userspace upon resume, and force it to reprobe. Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> --- drivers/gpu/drm/i915/i915_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c index 4df75e63cf22..da944ca4298f 100644 --- a/drivers/gpu/drm/i915/i915_drv.c +++ b/drivers/gpu/drm/i915/i915_drv.c @@ -1606,7 +1606,7 @@ static int i915_drm_resume(struct drm_device *dev) * */ intel_hpd_init(dev_priv); /* Config may have changed between suspend and resume */ - drm_helper_hpd_irq_event(dev); + drm_kms_helper_hotplug_event(dev, NULL); intel_opregion_register(dev_priv); -- 2.9.3 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
