All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915/dg2: Bump up CDCLK for DG2
Date: Tue, 5 Jul 2022 06:52:52 +0000	[thread overview]
Message-ID: <dcb344303a224c71ad2ddb9a45f88cdd@intel.com> (raw)
In-Reply-To: <20220614123049.16183-2-stanislav.lisovskiy@intel.com>



> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Stanislav
> Lisovskiy
> Sent: Tuesday, June 14, 2022 6:01 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH 1/1] drm/i915/dg2: Bump up CDCLK for DG2
> 
> We seem to need this W/A same way as for TGL, in order to fix some of the
> underruns, which we currently have and those not related to PSR.

We need to dig deeper on the real root causes and try to identify scenarios restricted by
hardware bandwidth limits and operate at optimum CD clock.

This should be kept under investigation with some open JIRA ticket while we can get the
tree stabilized with this stop gap solution.

With above agreed, this is:
Reviewed-by: Uma Shankar <uma.shankar@intel.com>

> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_cdclk.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c
> b/drivers/gpu/drm/i915/display/intel_cdclk.c
> index 6e80162632dd..86a22c3766e5 100644
> --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
> +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
> @@ -2300,7 +2300,7 @@ int intel_crtc_compute_min_cdclk(const struct
> intel_crtc_state *crtc_state)
>  		min_cdclk = max(min_cdclk, (int)crtc_state->pixel_rate);
> 
>  	/*
> -	 * HACK. Currently for TGL platforms we calculate
> +	 * HACK. Currently for TGL/DG2 platforms we calculate
>  	 * min_cdclk initially based on pixel_rate divided
>  	 * by 2, accounting for also plane requirements,
>  	 * however in some cases the lowest possible CDCLK @@ -2308,7 +2308,7
> @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)
>  	 * Explicitly stating here that this seems to be currently
>  	 * rather a Hack, than final solution.
>  	 */
> -	if (IS_TIGERLAKE(dev_priv)) {
> +	if (IS_TIGERLAKE(dev_priv) || IS_DG2(dev_priv)) {
>  		/*
>  		 * Clamp to max_cdclk_freq in case pixel rate is higher,
>  		 * in order not to break an 8K, but still leave W/A at place.
> --
> 2.24.1.485.gad05a3d8e5


  reply	other threads:[~2022-07-05 11:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 12:30 [Intel-gfx] [PATCH 0/1] Bump up CDCLK for DG2 Stanislav Lisovskiy
2022-06-14 12:30 ` [Intel-gfx] [PATCH 1/1] drm/i915/dg2: " Stanislav Lisovskiy
2022-07-05  6:52   ` Shankar, Uma [this message]
2022-06-14 17:14 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-06-15 12:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Bump up CDCLK for DG2 (rev2) Patchwork
2022-06-15 18:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=dcb344303a224c71ad2ddb9a45f88cdd@intel.com \
    --to=uma.shankar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stanislav.lisovskiy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.