Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Navare, Manasi" <manasi.d.navare@intel.com>
To: Vandita Kulkarni <vandita.kulkarni@intel.com>
Cc: intel-gfx@lists.freedesktop.org, uma.shankar@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Update small joiner ram size
Date: Thu, 5 Aug 2021 11:42:34 -0700	[thread overview]
Message-ID: <20210805184234.GA16497@labuser-Z97X-UD5H> (raw)
In-Reply-To: <20210805101937.14664-1-vandita.kulkarni@intel.com>

On Thu, Aug 05, 2021 at 03:49:37PM +0530, Vandita Kulkarni wrote:
> Xelpd supports larger small joiner ram.
> 
> Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 75d4ebc66941..d174f0d6e7cd 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -461,7 +461,9 @@ u32 intel_dp_mode_to_fec_clock(u32 mode_clock)
>  static int
>  small_joiner_ram_size_bits(struct drm_i915_private *i915)
>  {
> -	if (DISPLAY_VER(i915) >= 11)
> +	if (DISPLAY_VER(i915) >= 13)
> +		return 17280 * 8;

Verified from the Bspec, looks good to me.

Reviewed-by: Manasi Navare <manasi.d.navare@intel.com>

Manasi

> +	else if (DISPLAY_VER(i915) >= 11)
>  		return 7680 * 8;
>  	else
>  		return 6144 * 8;
> -- 
> 2.32.0
> 

  parent reply	other threads:[~2021-08-05 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 10:19 [Intel-gfx] [PATCH] drm/i915: Update small joiner ram size Vandita Kulkarni
2021-08-05 12:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-08-05 18:42 ` Navare, Manasi [this message]
2021-09-01  7:45   ` [Intel-gfx] [PATCH] " Kulkarni, Vandita
2021-08-06  2:18 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=20210805184234.GA16497@labuser-Z97X-UD5H \
    --to=manasi.d.navare@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=uma.shankar@intel.com \
    --cc=vandita.kulkarni@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