Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/i915: Use the the correct pixel rate to compute wm line time
Date: Wed, 1 Oct 2025 14:34:42 +0300	[thread overview]
Message-ID: <aN0R0ggZESnWZMrv@intel.com> (raw)
In-Reply-To: <b98101c43bb40a1affab97d5c8bf3e3997ed92a0.camel@intel.com>

On Wed, Oct 01, 2025 at 10:27:44AM +0000, Govindapillai, Vinod wrote:
> On Fri, 2025-09-19 at 21:08 +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > The line time used for the watermark calculations is supposed to
> > based on the plane's adjusted pixel rate, not the pipe's adjusted
> > pixel rate. The current code will give incorrect answers if plane
> > downscaling is used.
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/skl_watermark.c | 9 ++++-----
> >  1 file changed, 4 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/skl_watermark.c
> > b/drivers/gpu/drm/i915/display/skl_watermark.c
> > index d74cbb43ae6f..bdd005c6cc2d 100644
> > --- a/drivers/gpu/drm/i915/display/skl_watermark.c
> > +++ b/drivers/gpu/drm/i915/display/skl_watermark.c
> > @@ -1637,18 +1637,16 @@ skl_wm_method2(u32 pixel_rate, u32 pipe_htotal, u32 latency,
> >  }
> >  
> >  static uint_fixed_16_16_t
> > -intel_get_linetime_us(const struct intel_crtc_state *crtc_state)
> > +intel_get_linetime_us(const struct intel_crtc_state *crtc_state,
> > +		      int pixel_rate)
> >  {
> >  	struct intel_display *display = to_intel_display(crtc_state);
> > -	u32 pixel_rate;
> >  	u32 crtc_htotal;
> >  	uint_fixed_16_16_t linetime_us;
> >  
> >  	if (!crtc_state->hw.active)
> >  		return u32_to_fixed16(0);
> >  
> > -	pixel_rate = crtc_state->pixel_rate;
> > -
> >  	if (drm_WARN_ON(display->drm, pixel_rate == 0))
> >  		return u32_to_fixed16(0);
> >  
> > @@ -1743,7 +1741,8 @@ skl_compute_wm_params(const struct intel_crtc_state *crtc_state,
> >  	wp->y_tile_minimum = mul_u32_fixed16(wp->y_min_scanlines,
> >  					     wp->plane_blocks_per_line);
> >  
> > -	wp->linetime_us = fixed16_to_u32_round_up(intel_get_linetime_us(crtc_state));
> > +	wp->linetime_us = fixed16_to_u32_round_up(intel_get_linetime_us(crtc_state,
> > +									plane_pixel_rate));
> 
> Hi Ville,
> 
> As per the bspec 49325 the starting point is,
> 
> Adjusted pipe pixel rate = pixel rate for the screen resolution
> if (pipe scale enabled)
> 	adjusted pipe pixel rate = adjusted pipe pixel rate * pipe down scale amoun
> 
> adjusted plane pixel rate = adjusted pipe pixel rate
> if (plane scale enabled)
> 	adjusted plane pixel rate = adjusted plane pixel rate * plane down scale 
> 
> and
> line time microseconds = pipe horizontal total pixels/adjusted plane pixel rate MHz
> 
> Our Method1, Method2 and line time calculations are based on plane_pixel_rate vs. adjusted plane
> pixel rate in bspec. So I wonder if we differ from the bspec in these wm calculations?

plane_pixel_rate is what the spec calls "adjusted plane pixel rate"

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2025-10-01 11:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 18:08 [PATCH 0/3] drm/i915: Fix skl+ watermark linetime stuff Ville Syrjala
2025-09-19 18:08 ` [PATCH 1/3] drm/i915: Use the the correct pixel rate to compute wm line time Ville Syrjala
2025-10-01 10:27   ` Govindapillai, Vinod
2025-10-01 11:34     ` Ville Syrjälä [this message]
2025-10-01 12:06       ` Govindapillai, Vinod
2025-09-19 18:08 ` [PATCH 2/3] drm/i915: Deobfuscate wm linetime calculation Ville Syrjala
2025-10-01 12:06   ` Govindapillai, Vinod
2025-09-19 18:08 ` [PATCH 3/3] drm/i915: s/intel_get_linetime_us()/skl_wm_linetime_us()/ Ville Syrjala
2025-10-01 12:07   ` Govindapillai, Vinod
2025-09-19 19:06 ` ✗ i915.CI.BAT: failure for drm/i915: Fix skl+ watermark linetime stuff Patchwork
2025-09-20 17:45 ` ✓ i915.CI.BAT: success for drm/i915: Fix skl+ watermark linetime stuff (rev2) Patchwork
2025-09-20 21:18 ` ✗ i915.CI.Full: 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=aN0R0ggZESnWZMrv@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@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