Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E06A6C3DA4A for ; Thu, 22 Aug 2024 10:07:15 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 678BB10E84B; Thu, 22 Aug 2024 10:07:15 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="bc2LMyDR"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.18]) by gabe.freedesktop.org (Postfix) with ESMTPS id BE39610E86A for ; Thu, 22 Aug 2024 10:07:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1724321235; x=1755857235; h=date:from:to:cc:subject:message-id:reply-to:references: mime-version:in-reply-to; bh=+YzNmkCSDdvYV0aOWfn2Y0H4WGiF6rt+KiKLzIruPhI=; b=bc2LMyDRTZ7fnRVEc4Rfi98B/DyYBP5bvai3Kt1Mt2A0gPmLZiRsdOS6 xoz4RDmIuR1ZJtccEEZtnVXGCGT1Z4B8gP8XVQbX+sIalHoFqUigUl9GM 69S+BwGg+E8CufrRTOGN6oBB7FkkIA+iqdTLToc1h912b4TzVOFZs1B/W peaaD47KKg3C0cK6ZeFcYwGoBCJtm8XN3ybpppLLt8LTF3AH9IFdjWuky UBRofrj2nzxf0IlL0zwmVOZKX56LKrXcgel86k6t9j/xK81rjXOVwrWQY rjSJo7+wydU5aWZQwBGzsQPL8LlR2+IGh9EE+eQG1NQ1xGPI9VyKKYUNn g==; X-CSE-ConnectionGUID: o519chCuQs29qwn6GSHmmg== X-CSE-MsgGUID: Ob3rAmgPQcKiOksOgaFgPw== X-IronPort-AV: E=McAfee;i="6700,10204,11171"; a="22877985" X-IronPort-AV: E=Sophos;i="6.10,166,1719903600"; d="scan'208";a="22877985" Received: from fmviesa001.fm.intel.com ([10.60.135.141]) by orvoesa110.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Aug 2024 03:07:15 -0700 X-CSE-ConnectionGUID: sEYPn8iZTl24o9Fc+V4rNg== X-CSE-MsgGUID: oofTQ4FdTi2HasNvgvM9mQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.10,166,1719903600"; d="scan'208";a="92187383" Received: from ideak-desk.fi.intel.com ([10.237.72.78]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Aug 2024 03:07:13 -0700 Date: Thu, 22 Aug 2024 13:07:33 +0300 From: Imre Deak To: Jani Nikula Cc: intel-gfx@lists.freedesktop.org Subject: Re: [PATCH] drm/i915/dp_mst: Fix MST state after a sink reset Message-ID: References: <20240724161223.2291853-1-imre.deak@intel.com> <87ttfe3qn4.fsf@intel.com> <87frqw513w.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87frqw513w.fsf@intel.com> X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: imre.deak@intel.com Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Thu, Aug 22, 2024 at 01:00:03PM +0300, Jani Nikula wrote: > On Wed, 21 Aug 2024, Imre Deak wrote: > > On Wed, Aug 21, 2024 at 05:19:11PM +0300, Jani Nikula wrote: > >> On Wed, 24 Jul 2024, Imre Deak wrote: > >> > In some cases the sink can reset itself after it was configured into MST > >> > mode, without the driver noticing the disconnected state. For instance > >> > the reset may happen in the middle of a modeset, or the (long) HPD pulse > >> > generated may be not long enough for the encoder detect handler to > >> > observe the HPD's deasserted state. In this case the sink's DPCD > >> > register programmed to enable MST will be reset, while the driver still > >> > assumes MST is still enabled. Detect this condition, which will tear > >> > down and recreate/re-enable the MST topology. > >> > > >> > Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11195 > >> > Signed-off-by: Imre Deak > >> > --- > >> > drivers/gpu/drm/i915/display/intel_dp.c | 3 +++ > >> > drivers/gpu/drm/i915/display/intel_dp_mst.c | 30 +++++++++++++++++++++ > >> > drivers/gpu/drm/i915/display/intel_dp_mst.h | 1 + > >> > 3 files changed, 34 insertions(+) > >> > > >> > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c > >> > index 1e43e32e05199..c621f6daf8235 100644 > >> > --- a/drivers/gpu/drm/i915/display/intel_dp.c > >> > +++ b/drivers/gpu/drm/i915/display/intel_dp.c > >> > @@ -5878,6 +5878,9 @@ intel_dp_detect(struct drm_connector *connector, > >> > else > >> > status = connector_status_disconnected; > >> > > >> > + if (!intel_dp_mst_verify_dpcd_state(intel_dp)) > >> > + status = connector_status_disconnected; > >> > + > >> > >> So I still don't understand. We've got a detect which we've determined > >> is connected. But then we disconnect because the sink state has changed. > >> > >> How do we get another connect? > > > > The detect in this case will be retried with a 1 sec delay, since the > > mode changes back to SST and the connector state stays disconnected. > > What exactly triggers the retry? I don't see this triggering the > INTEL_HOTPLUG_RETRY case. drm_connector::status is connector_status_disconnected before the detect (as always for an MST root connector) and it stays connector_status_disconnected. The connector's mode will also change to SST (intel_dp::is_mst from true to false). This condition will lead to the detect getting retried. A detect will actually happen in any case, since removing the MST connectors results in a (global) hotplug uevent being sent, to which userspace should respond with re-probing all connectors. > I'm just trying to understand, please bear with me. > > BR, > Jani. > > > > > >> BR, > >> Jani. > >> > >> > >> > if (status == connector_status_disconnected) { > >> > memset(&intel_dp->compliance, 0, sizeof(intel_dp->compliance)); > >> > memset(intel_connector->dp.dsc_dpcd, 0, sizeof(intel_connector->dp.dsc_dpcd)); > >> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c > >> > index 27ce5c3f5951e..89b147e37b400 100644 > >> > --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c > >> > +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c > >> > @@ -1998,3 +1998,33 @@ bool intel_dp_mst_crtc_needs_modeset(struct intel_atomic_state *state, > >> > > >> > return false; > >> > } > >> > + > >> > +/** > >> > + * intel_dp_mst_verify_dpcd_state - verify the MST SW enabled state wrt. the DPCD > >> > + * @intel_dp: DP port object > >> > + * > >> > + * Verify if @intel_dp's MST enabled SW state matches the corresponding DPCD > >> > + * state. A long HPD pulse -not long enough to be detected as a disconnected > >> > + * state - could've reset the DPCD state, which requires tearing > >> > + * down/recreating the MST topology. > >> > + * > >> > + * Returns %true if the SW MST enabled and DPCD states match, %false > >> > + * otherwise. > >> > + */ > >> > +bool intel_dp_mst_verify_dpcd_state(struct intel_dp *intel_dp) > >> > +{ > >> > + int ret; > >> > + u8 val; > >> > + > >> > + if (!intel_dp->is_mst) > >> > + return true; > >> > + > >> > + ret = drm_dp_dpcd_readb(intel_dp->mst_mgr.aux, DP_MSTM_CTRL, &val); > >> > + if (ret < 0) > >> > + return false; > >> > + > >> > + if (val != (DP_MST_EN | DP_UP_REQ_EN | DP_UPSTREAM_IS_SRC)) > >> > + return false; > >> > + > >> > + return true; > >> > +} > >> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.h b/drivers/gpu/drm/i915/display/intel_dp_mst.h > >> > index 8ca1d599091c6..9e4c7679f1c3a 100644 > >> > --- a/drivers/gpu/drm/i915/display/intel_dp_mst.h > >> > +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.h > >> > @@ -27,5 +27,6 @@ int intel_dp_mst_atomic_check_link(struct intel_atomic_state *state, > >> > struct intel_link_bw_limits *limits); > >> > bool intel_dp_mst_crtc_needs_modeset(struct intel_atomic_state *state, > >> > struct intel_crtc *crtc); > >> > +bool intel_dp_mst_verify_dpcd_state(struct intel_dp *intel_dp); > >> > > >> > #endif /* __INTEL_DP_MST_H__ */ > >> > >> -- > >> Jani Nikula, Intel > > -- > Jani Nikula, Intel