All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>
Cc: intel-gfx@lists.freedesktop.org, ville.syrjala@intel.com
Subject: Re: [Intel-gfx] [PATCH v5 3/8] drm/i915: store the peak bw per QGV point
Date: Mon, 22 May 2023 18:18:35 +0300	[thread overview]
Message-ID: <ZGuHy+V+FSC5LX7t@intel.com> (raw)
In-Reply-To: <20230511231750.313467-4-vinod.govindapillai@intel.com>

On Fri, May 12, 2023 at 02:17:45AM +0300, Vinod Govindapillai wrote:
> In MTL onwards, pcode locks the GV point based on the peak BW
> of a QGV point. So store the peak BW of all the QGV points.
> 
> v2: use DIV_ROUND_CLOSEST() for the peakBW calculation
> 
> Bspec: 64636
> 
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>

Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>

> ---
>  drivers/gpu/drm/i915/display/intel_bw.c           | 8 ++++++--
>  drivers/gpu/drm/i915/display/intel_display_core.h | 2 ++
>  2 files changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> index c8075a37c3ab..db117638d23b 100644
> --- a/drivers/gpu/drm/i915/display/intel_bw.c
> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> @@ -534,10 +534,14 @@ static int tgl_get_bw_info(struct drm_i915_private *dev_priv, const struct intel
>  
>  			bi->deratedbw[j] = min(maxdebw,
>  					       bw * (100 - sa->derating) / 100);
> +			bi->peakbw[j] = DIV_ROUND_CLOSEST(sp->dclk *
> +							  num_channels *
> +							  qi.channel_width, 8);
>  
>  			drm_dbg_kms(&dev_priv->drm,
> -				    "BW%d / QGV %d: num_planes=%d deratedbw=%u\n",
> -				    i, j, bi->num_planes, bi->deratedbw[j]);
> +				    "BW%d / QGV %d: num_planes=%d deratedbw=%u peakbw: %u\n",
> +				    i, j, bi->num_planes, bi->deratedbw[j],
> +				    bi->peakbw[j]);
>  		}
>  
>  		for (j = 0; j < qi.num_psf_points; j++) {
> diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
> index e36f88a39b86..9f66d734edf6 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_core.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_core.h
> @@ -314,6 +314,8 @@ struct intel_display {
>  			unsigned int deratedbw[I915_NUM_QGV_POINTS];
>  			/* for each PSF GV point */
>  			unsigned int psf_bw[I915_NUM_PSF_GV_POINTS];
> +			/* Peak BW for each QGV point */
> +			unsigned int peakbw[I915_NUM_QGV_POINTS];
>  			u8 num_qgv_points;
>  			u8 num_psf_gv_points;
>  			u8 num_planes;
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-05-22 15:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 23:17 [Intel-gfx] [PATCH v5 0/8] mtl: add support for pmdemand Vinod Govindapillai
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 1/8] drm/i915: fix the derating percentage for MTL Vinod Govindapillai
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 2/8] drm/i915: update the QGV point frequency calculations Vinod Govindapillai
2023-05-22 15:17   ` Lisovskiy, Stanislav
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 3/8] drm/i915: store the peak bw per QGV point Vinod Govindapillai
2023-05-22 15:18   ` Lisovskiy, Stanislav [this message]
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 4/8] drm/i915: extract intel_bw_check_qgv_points() Vinod Govindapillai
2023-05-22 15:23   ` Lisovskiy, Stanislav
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 5/8] drm/i915: modify max_bw to return index to intel_bw_info Vinod Govindapillai
2023-05-22 15:20   ` Lisovskiy, Stanislav
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 6/8] drm/i915/mtl: find the best QGV point for the SAGV configuration Vinod Govindapillai
2023-05-22 15:22   ` Lisovskiy, Stanislav
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 7/8] drm/i915/mtl: Add support for PM DEMAND Vinod Govindapillai
2023-05-16 19:59   ` Gustavo Sousa
2023-05-22 15:21   ` Lisovskiy, Stanislav
2023-05-11 23:17 ` [Intel-gfx] [PATCH v5 8/8] drm/i915/display: provision to suppress drm_warn in intel_get_crtc_new_encoder Vinod Govindapillai
2023-05-22 15:24   ` Lisovskiy, Stanislav
2023-05-23 11:48     ` Jani Nikula
2023-05-23 12:29       ` Saarinen, Jani
2023-05-12  0:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for mtl: add support for pmdemand (rev5) Patchwork
2023-05-12  0:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-05-12  0:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-12  6:40 ` [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=ZGuHy+V+FSC5LX7t@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@intel.com \
    --cc=vinod.govindapillai@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.