Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Taylor, Clinton A" <clinton.a.taylor@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>,
	"Kahola, Mika" <mika.kahola@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 07/12] drm/i915/cx0: Remove bus reset after every c10 transaction
Date: Thu, 24 Oct 2024 22:15:11 +0000	[thread overview]
Message-ID: <fc292e32fac2e9f36a474d9c2b3f2bb009a40f73.camel@intel.com> (raw)
In-Reply-To: <20241024191854.GM5725@mdroper-desk1.amr.corp.intel.com>

On Thu, 2024-10-24 at 12:18 -0700, Matt Roper wrote:
> On Thu, Oct 24, 2024 at 06:08:46AM +0000, Kahola, Mika wrote:
> > > -----Original Message-----
> > > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Clint
> > > Taylor
> > > Sent: Thursday, 24 October 2024 0.47
> > > To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
> > > Subject: [PATCH v2 07/12] drm/i915/cx0: Remove bus reset after every c10
> > > transaction
> > > 
> > > C10 phy timeouts occur on xe3lpd if the c10 bus is reset every transaction.
> > > Starting with xe3lpd this is bus reset not necessary
> > > 
> > 
> > This C10/C20 bus reset was originally placed as a workaround to prevent bus timeouts.
> > These timeouts were fixed elsewhere and therefore these are unnecessary lines.
> 
> I'm a bit confused by the patch / explanation here.  Before this patch
> we did the reset on all platforms, unconditionally.  The code change
> below is removing the reset from the existing platforms (MTL/ARL and
> Xe2) but keeping it only on the new Xe3 platforms.
> 
> If the timeout mystery was solved and these resets are no longer needed,
> shouldn't we be removing the line completely rather than making it
> conditional to the new platforms?  Or do we have now have new,
> unexplained failures specifically on Xe3 that requires that we bring
> back this hack at the same time we're removing it from the older
> platforms?
> 
I reversed the conditional when splitting the c10 patches. Will correct and send a new
series.

-Clint

> 
> Matt
> 
> > Reviewed-by: Mika Kahola <mika.kahola@intel.com>
> > 
> > > Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/display/intel_cx0_phy.c | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/display/intel_cx0_phy.c
> > > b/drivers/gpu/drm/i915/display/intel_cx0_phy.c
> > > index c1357bdb8a3b..a8966a7a9927 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_cx0_phy.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_cx0_phy.c
> > > @@ -224,7 +224,8 @@ static int __intel_cx0_read_once(struct intel_encoder
> > > *encoder,
> > >  	 * down and let the message bus to end up
> > >  	 * in a known state
> > >  	 */
> > > -	intel_cx0_bus_reset(encoder, lane);
> > > +	if ((DISPLAY_VER(i915) >= 30))
> > > +		intel_cx0_bus_reset(encoder, lane);
> > > 
> > >  	return REG_FIELD_GET(XELPDP_PORT_P2M_DATA_MASK, val);  } @@ -
> > > 313,7 +314,8 @@ static int __intel_cx0_write_once(struct intel_encoder
> > > *encoder,
> > >  	 * down and let the message bus to end up
> > >  	 * in a known state
> > >  	 */
> > > -	intel_cx0_bus_reset(encoder, lane);
> > > +	if ((DISPLAY_VER(i915) >= 30))
> > > +		intel_cx0_bus_reset(encoder, lane);
> > > 
> > >  	return 0;
> > >  }
> > > --
> > > 2.25.1

  reply	other threads:[~2024-10-24 22:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 21:46 [PATCH v2 00/12] drm/i915/xe3lpd: ptl display patches Clint Taylor
2024-10-23 21:46 ` [PATCH v2 01/12] drm/i915/xe3lpd: Update pmdemand programming Clint Taylor
2024-10-23 22:16   ` Gustavo Sousa
2024-10-23 21:46 ` [PATCH v2 02/12] drm/i915/xe3lpd: Disable HDCP Line Rekeying for Xe3 Clint Taylor
2024-10-24 19:04   ` Matt Roper
2024-10-23 21:46 ` [PATCH v2 03/12] drm/i915/xe3lpd: Add check to see if edp over type c is allowed Clint Taylor
2024-10-24  8:19   ` Jani Nikula
2024-10-23 21:46 ` [PATCH v2 04/12] drm/i915/display/ptl: Fill VRR crtc_state timings before other transcoder timings Clint Taylor
2024-10-24 10:52   ` Golani, Mitulkumar Ajitkumar
2024-10-23 21:46 ` [PATCH v2 05/12] drm/i915/ptl: Define IS_PANTHERLAKE macro Clint Taylor
2024-10-23 21:46 ` [PATCH v2 06/12] drm/i915/cx0: Extend C10 check to PTL Clint Taylor
2024-10-23 21:46 ` [PATCH v2 07/12] drm/i915/cx0: Remove bus reset after every c10 transaction Clint Taylor
2024-10-24  6:08   ` Kahola, Mika
2024-10-24  8:20     ` Jani Nikula
2024-10-24 19:18     ` Matt Roper
2024-10-24 22:15       ` Taylor, Clinton A [this message]
2024-10-24 22:21         ` Matt Roper
2024-10-25  6:44           ` Kahola, Mika
2024-10-24  8:20   ` Jani Nikula
2024-10-23 21:46 ` [PATCH v2 08/12] drm/i915/xe3lpd: Move async flip bit to PLANE_SURF register Clint Taylor
2024-10-24  6:14   ` Chauhan, Shekhar
2024-10-23 21:46 ` [PATCH v2 09/12] drm/i915/xe3: Underrun recovery does not exist post Xe2 Clint Taylor
2024-10-24  8:55   ` Pottumuttu, Sai Teja
2024-10-23 21:46 ` [PATCH v2 10/12] drm/i915/display/xe3: disable x-tiled framebuffers Clint Taylor
2024-10-23 22:24   ` Gustavo Sousa
2024-10-23 21:47 ` [PATCH v2 11/12] drm/i915/xe3lpd: Skip disabling VRR during modeset disable Clint Taylor
2024-10-24 17:24   ` Golani, Mitulkumar Ajitkumar
2024-10-23 21:47 ` [PATCH v2 12/12] drm/i915/xe3lpd: Power request asserting/deasserting Clint Taylor
2024-10-23 22:21   ` Gustavo Sousa
2024-10-24  8:49 ` ✓ Fi.CI.BAT: success for drm/i915/xe3lpd: ptl display patches (rev2) Patchwork
2024-10-24  8:50 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-10-24 10:38 ` ✗ Fi.CI.IGT: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fc292e32fac2e9f36a474d9c2b3f2bb009a40f73.camel@intel.com \
    --to=clinton.a.taylor@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=mika.kahola@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox