Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5009467imu; Tue, 29 Jan 2019 11:11:10 -0800 (PST) X-Google-Smtp-Source: ALg8bN4sVPj7UU2Jbgt9JbGzQoJ6yCxGqW7g0oMrkUCUH9PRlkemmTmBjdrJ88lfvW/XX36iYKKm X-Received: by 2002:a65:6491:: with SMTP id e17mr24566345pgv.418.1548789070529; Tue, 29 Jan 2019 11:11:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548789070; cv=none; d=google.com; s=arc-20160816; b=t3d8rSRKHneWDQ65RBK+LuXB/01xqxu5nIvO4xD/cgIyA7M7nHxr35eb/u6C60aaqz x9/dOrdUY0rs9ybXMmbxpNsoQk4NfOwi3Jpprcoq+0v9WKoUuubux+9pPPOIHsxH8yhz rNBcGyar0BjWLTqaYmaLE+8XTZb7XwVwO28GPJkBvO8pfGp9RWuUZAIc8FCiwIWQwNYv QDT6R/PZqh966fTCej8DTYSrKj/ZvuvGI/ZDCCpq6JE7HDWu0HB9JlFvOBsDRPXc9vYe Hr1Ti48xNj0mpIh4i77S5lZ542JWSZ9qJTk6RF5udfVcymGednp+SdkxE9b66Qc3XHiW ykdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=COoMg9zJF24SpHxDywcz/dGYmsq3jtUltUcbj+S+HpI=; b=zoQpQ2Xf2c7/idoUCndznpgECsG1QidHCS9DC6F4Uk7C69F73mxL5vY81cvtKRANSw iRFMd8wThU8aBOFSKa6LA2ij8pEG9FlnYD8UhdpPrOxL6iab5vwgrnQ3WCnQSth7KvXM MYIbRHcMIAtIzIdgTlK0zx+4FbR65Mb/VuIHb+ybmELpMqCy4kF4JswMklje6YgBXQwR y/wEYX8UzQtUHc3mh8e5e9RJ9S4XVcswwrTbdI1QTwUNs7pQmMpd2DpDZfHB5JHndB67 ybBisv58HKDLroaUQTjR7A059sxsM3FgwTq9ujW0zBcc37Y/hlHnW/FcXgLuVhF1o0Bx N6lw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 133si30662398pfc.61.2019.01.29.11.10.55; Tue, 29 Jan 2019 11:11:10 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729391AbfA2TKZ (ORCPT + 99 others); Tue, 29 Jan 2019 14:10:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46662 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729132AbfA2TKY (ORCPT ); Tue, 29 Jan 2019 14:10:24 -0500 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C333E2D805; Tue, 29 Jan 2019 19:10:23 +0000 (UTC) Received: from malachite.bss.redhat.com (dhcp-10-20-1-11.bss.redhat.com [10.20.1.11]) by smtp.corp.redhat.com (Postfix) with ESMTP id A946917157; Tue, 29 Jan 2019 19:10:22 +0000 (UTC) From: Lyude Paul To: intel-gfx@lists.freedesktop.org Cc: Chris Wilson , Imre Deak , Daniel Vetter , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 2/3] drm/i915: Don't send MST hotplugs during resume Date: Tue, 29 Jan 2019 14:10:00 -0500 Message-Id: <20190129191001.442-3-lyude@redhat.com> In-Reply-To: <20190129191001.442-1-lyude@redhat.com> References: <20190129191001.442-1-lyude@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Tue, 29 Jan 2019 19:10:24 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We have a bad habit of calling drm_fb_helper_hotplug_event() far more then we actually need to. MST appears to be one of these cases, where we call drm_fb_helper_hotplug_event() if we fail to resume a connected MST topology in intel_dp_mst_resume(). We don't actually need to do this at all though since hotplug events are already sent from drm_dp_connector_destroy_work() every time connectors are unregistered from userspace's PoV. Additionally, extra calls to drm_fb_helper_hotplug_event() also just mean more of a chance of doing a connector probe somewhere we shouldn't. So, don't send any hotplug events during resume if the MST topology fails to come up. Just rely on the DP MST helpers to send them for us. Signed-off-by: Lyude Paul Cc: Imre Deak Cc: Daniel Vetter --- drivers/gpu/drm/i915/intel_dp.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c index 681e88405ada..c2399acf177b 100644 --- a/drivers/gpu/drm/i915/intel_dp.c +++ b/drivers/gpu/drm/i915/intel_dp.c @@ -7096,7 +7096,10 @@ void intel_dp_mst_resume(struct drm_i915_private *dev_priv) continue; ret = drm_dp_mst_topology_mgr_resume(&intel_dp->mst_mgr); - if (ret) - intel_dp_check_mst_status(intel_dp); + if (ret) { + intel_dp->is_mst = false; + drm_dp_mst_topology_mgr_set_mst(&intel_dp->mst_mgr, + false); + } } } -- 2.20.1