Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/1] drm/i915: Handle the DG2 max bw properly
Date: Mon, 28 Mar 2022 19:37:28 +0300	[thread overview]
Message-ID: <YkHkSC+6JtZd8he/@intel.com> (raw)
In-Reply-To: <20220328161025.175993-2-vinod.govindapillai@intel.com>

On Mon, Mar 28, 2022 at 07:10:25PM +0300, Vinod Govindapillai wrote:
> DG2 has a constant bandwidth regardless of the number of planes
> enabled. Handle the DG2 bw separately.
> 
> cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> 
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_bw.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> index ac11ff19e47d..8955f9f8476a 100644
> --- a/drivers/gpu/drm/i915/display/intel_bw.c
> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> @@ -1003,7 +1003,9 @@ int intel_bw_atomic_check(struct intel_atomic_state *state)
>  	for (i = 0; i < num_qgv_points; i++) {
>  		unsigned int max_data_rate;
>  
> -		if (DISPLAY_VER(dev_priv) > 11)
> +		if (IS_DG2(dev_priv))
> +			max_data_rate = dev_priv->max_bw[0].deratedbw[0];

Are you saying tgl_max_bw() doesn't actually work for dg2?

> +		else if (DISPLAY_VER(dev_priv) > 11)
>  			max_data_rate = tgl_max_bw(dev_priv, num_active_planes, i);
>  		else
>  			max_data_rate = icl_max_bw(dev_priv, num_active_planes, i);
> -- 
> 2.25.1

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-03-28 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 16:10 [Intel-gfx] [PATCH v2 0/1] Handle the DG2 max bw properly Vinod Govindapillai
2022-03-28 16:10 ` [Intel-gfx] [PATCH v2 1/1] drm/i915: " Vinod Govindapillai
2022-03-28 16:37   ` Ville Syrjälä [this message]
2022-03-28 23:17 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for Handle the DG2 max bw properly (rev2) Patchwork
2022-03-28 23:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-29  1:52 ` [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=YkHkSC+6JtZd8he/@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox