From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DE2EAC433E1 for ; Tue, 16 Jun 2020 15:39:37 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id C295D21531 for ; Tue, 16 Jun 2020 15:39:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C295D21531 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=intel-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 4D76C6E8CD; Tue, 16 Jun 2020 15:39:37 +0000 (UTC) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by gabe.freedesktop.org (Postfix) with ESMTPS id 4A74D6E8CD for ; Tue, 16 Jun 2020 15:39:36 +0000 (UTC) IronPort-SDR: 8XJCnj2Z6PJfchGoH9vPs9niqMVF3y74922H9sNlqGtpXxJDCGDuBktSlFpJL1zlyQMfTp6OR5 eIEU7q26GU0A== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Jun 2020 08:39:34 -0700 IronPort-SDR: Ygor1tGRJIAFJvLBXiYi5VjkFHAkkNxe5MglND9J2eVJd1r+z+kU75q1CD2H2PxLZ6zC/Ls93/ Zr339zhn7XLQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,518,1583222400"; d="scan'208";a="309151188" Received: from stinkbox.fi.intel.com (HELO stinkbox) ([10.237.72.174]) by fmsmga002.fm.intel.com with SMTP; 16 Jun 2020 08:39:31 -0700 Received: by stinkbox (sSMTP sendmail emulation); Tue, 16 Jun 2020 18:39:30 +0300 Date: Tue, 16 Jun 2020 18:39:30 +0300 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Imre Deak Message-ID: <20200616153930.GX6112@intel.com> References: <20200616141855.746-1-imre.deak@intel.com> <20200616141855.746-2-imre.deak@intel.com> <20200616152251.GW6112@intel.com> <20200616153055.GA21389@ideak-desk.fi.intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200616153055.GA21389@ideak-desk.fi.intel.com> X-Patchwork-Hint: comment User-Agent: Mutt/1.10.1 (2018-07-13) Subject: Re: [Intel-gfx] [PATCH 2/6] drm/i915/dp_mst: Disable link training fallback on MST links 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: , Cc: intel-gfx@lists.freedesktop.org Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Tue, Jun 16, 2020 at 06:30:55PM +0300, Imre Deak wrote: > On Tue, Jun 16, 2020 at 06:22:51PM +0300, Ville Syrj=E4l=E4 wrote: > > On Tue, Jun 16, 2020 at 05:18:51PM +0300, Imre Deak wrote: > > > We calculate the MST available bandwidth using the link's maximum rate > > > and lane count. This bandwidth won't be recalculated in response to a > > = > > Thw wording here is a bit ambiguousr as to who "we" is, and what exactly > > "link's maximum rate and lane count". I would try to clarify a bit that > > it's drm_dp_mst_topology.c who is mostly in error here by directly > > interpreting the max data rate/lanes from the DPCD. > > = > > Althoguh the i915 code is not wihtout faults, as it lacks any logic > > to modeset all the MST streams for this link when the link params > > change (except on tgl+ where the master/slave stuff should force > > all streams to do a modeset anyway). > > = > > > link training error and fallback setting, so modesets following a link > > > training error will calculate incorrect timing parameters (like the > > > transcoder's data M/N params or the number of MST TUs). > > > = > > > Prevent the above problem by disabling the link training fallback on = MST > > > links for now, until the MST compute config can deal with changing li= nk > > > parameters. > > > = > > > The misconfigured timing lead at least to a > > > 'Timed out waiting for DP idle patterns' > > > error. > > > = > > > Cc: Ville Syrj=E4l=E4 > > > Cc: Manasi Navare > > > Signed-off-by: Imre Deak > > > --- > > > drivers/gpu/drm/i915/display/intel_dp.c | 25 ++++++++++++++++++-----= -- > > > 1 file changed, 18 insertions(+), 7 deletions(-) > > > = > > > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/dr= m/i915/display/intel_dp.c > > > index 42589cae766d..c585b002783a 100644 > > > --- a/drivers/gpu/drm/i915/display/intel_dp.c > > > +++ b/drivers/gpu/drm/i915/display/intel_dp.c > > > @@ -468,6 +468,13 @@ int intel_dp_get_link_train_fallback_values(stru= ct intel_dp *intel_dp, > > > struct drm_i915_private *i915 =3D dp_to_i915(intel_dp); > > > int index; > > > = > > > + /* > > > + * TODO: Enable fallback on MST links once MST link compute can han= dle > > > + * the fallback params. > > > + */ > > > + if (intel_dp->is_mst) > > > + return -1; > > = > > Should we duplicate the drm_error() from the other path here maybe? > = > Yes, will add it. > = > > = > > > + > > > index =3D intel_dp_rate_index(intel_dp->common_rates, > > > intel_dp->num_common_rates, > > > link_rate); > > > @@ -6163,7 +6170,17 @@ intel_dp_detect(struct drm_connector *connecto= r, > > > goto out; > > > } > > > = > > > - if (intel_dp->reset_link_params) { > > > + /* Read DP Sink DSC Cap DPCD regs for DP v1.4 */ > > > + if (INTEL_GEN(dev_priv) >=3D 11) > > > + intel_dp_get_dsc_sink_cap(intel_dp); > > > + > > > + intel_dp_configure_mst(intel_dp); > > > + > > > + /* > > > + * TODO: Reset link params when switching to MST mode, until MST > > > + * supports link training fallback params. > > > + */ > > > + if (intel_dp->reset_link_params || intel_dp->is_mst) { > > = > > /me confused. Why do we need to touch this code? > = > It's possible to switch to MST mode after the link rate/lane count got > reduced by a link training error in SST mode. But then we should have a long hpd and reset_link_params should be set anyway no? > = > > > /* Initial max link lane count */ > > > intel_dp->max_link_lane_count =3D intel_dp_max_common_lane_count(i= ntel_dp); > > > = > > > @@ -6175,12 +6192,6 @@ intel_dp_detect(struct drm_connector *connecto= r, > > > = > > > intel_dp_print_rates(intel_dp); > > > = > > > - /* Read DP Sink DSC Cap DPCD regs for DP v1.4 */ > > > - if (INTEL_GEN(dev_priv) >=3D 11) > > > - intel_dp_get_dsc_sink_cap(intel_dp); > > > - > > > - intel_dp_configure_mst(intel_dp); > > > - > > > if (intel_dp->is_mst) { > > > /* > > > * If we are in MST mode then this connector > > > -- = > > > 2.23.1 > > = > > -- = > > Ville Syrj=E4l=E4 > > Intel -- = Ville Syrj=E4l=E4 Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx