Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3899754imu; Mon, 28 Jan 2019 12:57:48 -0800 (PST) X-Google-Smtp-Source: ALg8bN5osxVXDTDyAi+NkktMar9HY4Xo8gYeFaPYZuTOE8eXmZCyARRQydOJCAcpB2g7xVRRETY+ X-Received: by 2002:a63:5761:: with SMTP id h33mr21137407pgm.283.1548709068743; Mon, 28 Jan 2019 12:57:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548709068; cv=none; d=google.com; s=arc-20160816; b=KkjTk2M4Ql9gD1PIn1hasHac88tpASh5q2tp8GEBha1r6trhhcZD+A6PkrFjRPjiOg MqwRr15TB4srEBgYWolbRB/nD+Pf50PUcrclUhprFJiwUoILWZKXWl2AHp/RVYfZY+Y+ rYcY8qKaevdrOPJj/SahrWaz0fesDWXmkkgHz7Le3ryIHpP0OA7LJRzcQuaV8cBsPuZG mi7QdZwijlTmQkJjN+Z8NaEvEYTOZWfRzY8gJOL70LFHzMrf/ke6z3DYFmrj05VHEO2S O4fBgeOfe03xBYdL6jzff1XsJ4qQJw5zaRIw4tjRwcNNl3TqkA9ukhZbj//pZsOPgUbH UQQg== 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=luBSHfMmAdGyaVHLfdyYNVzjfSPo/QWbu4sv1n8j6/hnfdOHU6Wd7g3wFCOv9wp8aX DfPlg7wcSwx2ibaW3T0T7CmgJLYr0djluVO/9BUs8OlhwbQr0n+MlS2ivfEZ5Er2UezM Uh5STCqYtKZ433lrt6GWJmFX4HpsgIfoJD9rOdC0scvUz3nBO4x4bQEdk8X/EiFkmoUC efckdODXGBjNVZ0a8qmCvbQdkaiDvRlV1Z+iqdLjoE/P2EU1HAwXTJOLlOUYQZYeIcce 9Xsa/9ZcEB+2imieAVObId5cc3FPNYUhEs1VRZhTHFpTxueu++8SG7RsiZ2VtFRla8Nr iwfQ== 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 p23si4505478plo.7.2019.01.28.12.57.33; Mon, 28 Jan 2019 12:57:48 -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 S1728396AbfA1U4V (ORCPT + 99 others); Mon, 28 Jan 2019 15:56:21 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52179 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728368AbfA1U4T (ORCPT ); Mon, 28 Jan 2019 15:56:19 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3D73AC0BFBA1; Mon, 28 Jan 2019 20:56:19 +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 2EDEE747D4; Mon, 28 Jan 2019 20:56:18 +0000 (UTC) From: Lyude Paul To: intel-gfx@lists.freedesktop.org Cc: Imre Deak , Daniel Vetter , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 2/3] drm/i915: Don't send MST hotplugs during resume Date: Mon, 28 Jan 2019 15:56:02 -0500 Message-Id: <20190128205603.16372-3-lyude@redhat.com> In-Reply-To: <20190128205603.16372-1-lyude@redhat.com> References: <20190128205603.16372-1-lyude@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Mon, 28 Jan 2019 20:56:19 +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