From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 6/9] drm/i915/gen9: fix plane_blocks_per_line on watermarks calculations
Date: Tue, 27 Sep 2016 08:20:10 +0100 [thread overview]
Message-ID: <3719f30a-0d51-a4f7-629a-ee7b16763042@linux.intel.com> (raw)
In-Reply-To: <1474578035-424-7-git-send-email-paulo.r.zanoni@intel.com>
On 22/09/2016 22:00, Paulo Zanoni wrote:
> The confusing thing is that plane_blocks_per_line is listed as part of
> the method 2 calculation but is also used for other things. We
> calculated it in two different places and different ways: one inside
> skl_wm_method2() and the other inside skl_compute_plane_wm(). The
> skl_wm_method2() implementation is the one that matches the
> specification.
>
> With this patch we fix the skl_compute_plane_wm() calculation and just
> pass it as a parameter to skl_wm_method2(). We also take care to not
> modify the value of plane_bytes_per_line since we're going to rely on
> it having a correct value in later patches.
>
> This should affect the watermarks for Linear and Y-tiled.
>
> From my analysis, it looks like the two plane_blocks_per_line
> variables got out of sync on 0fda65680e92, but we can't really say
> that commit was a regression, it looks like just an incomplete fix.
> There's always the possibility that 0fda65680e92 matched our
> specification at that time, and then later the specification changed.
Yes, it wouldn't be a regression since before that commit changing
tiling with page flips did not work at all.
Whether or not calculation was fully correct at the time I am not sure.
The formulas changed at least twice after the initial implementation so
both are possible.
Regards,
Tvrtko
> v2: Try to add a "Fixes" tag (Maarten).
>
> Fixes: 0fda65680e92 ("drm/i915/skl: Update watermarks for Y tiling")
> Cc: stable@vger.kernel.org
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Reviewed-by: Lyude <cpaul@redhat.com>
> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> ---
> drivers/gpu/drm/i915/intel_pm.c | 39 +++++++++++++++------------------------
> 1 file changed, 15 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index a7f5f7f..a6ae7b7 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -3494,30 +3494,14 @@ static uint32_t skl_wm_method1(uint32_t pixel_rate, uint8_t cpp, uint32_t latenc
> }
>
> static uint32_t skl_wm_method2(uint32_t pixel_rate, uint32_t pipe_htotal,
> - uint32_t horiz_pixels, uint8_t cpp,
> - uint64_t tiling, uint32_t latency,
> - uint32_t y_min_scanlines)
> + uint32_t latency, uint32_t plane_blocks_per_line)
> {
> uint32_t ret;
> - uint32_t plane_bytes_per_line, plane_blocks_per_line;
> uint32_t wm_intermediate_val;
>
> if (latency == 0)
> return UINT_MAX;
>
> - plane_bytes_per_line = horiz_pixels * cpp;
> -
> - if (tiling == I915_FORMAT_MOD_Y_TILED ||
> - tiling == I915_FORMAT_MOD_Yf_TILED) {
> - plane_bytes_per_line *= y_min_scanlines;
> - plane_blocks_per_line = DIV_ROUND_UP(plane_bytes_per_line, 512);
> - plane_blocks_per_line /= y_min_scanlines;
> - } else if (tiling == DRM_FORMAT_MOD_NONE) {
> - plane_blocks_per_line = DIV_ROUND_UP(plane_bytes_per_line, 512) + 1;
> - } else {
> - plane_blocks_per_line = DIV_ROUND_UP(plane_bytes_per_line, 512);
> - }
> -
> wm_intermediate_val = latency * pixel_rate;
> ret = DIV_ROUND_UP(wm_intermediate_val, pipe_htotal * 1000) *
> plane_blocks_per_line;
> @@ -3606,17 +3590,24 @@ static int skl_compute_plane_wm(const struct drm_i915_private *dev_priv,
> y_min_scanlines = 4;
> }
>
> + plane_bytes_per_line = width * cpp;
> + if (fb->modifier[0] == I915_FORMAT_MOD_Y_TILED ||
> + fb->modifier[0] == I915_FORMAT_MOD_Yf_TILED) {
> + plane_blocks_per_line =
> + DIV_ROUND_UP(plane_bytes_per_line * y_min_scanlines, 512);
> + plane_blocks_per_line /= y_min_scanlines;
> + } else if (fb->modifier[0] == DRM_FORMAT_MOD_NONE) {
> + plane_blocks_per_line = DIV_ROUND_UP(plane_bytes_per_line, 512)
> + + 1;
> + } else {
> + plane_blocks_per_line = DIV_ROUND_UP(plane_bytes_per_line, 512);
> + }
> +
> method1 = skl_wm_method1(plane_pixel_rate, cpp, latency);
> method2 = skl_wm_method2(plane_pixel_rate,
> cstate->base.adjusted_mode.crtc_htotal,
> - width,
> - cpp,
> - fb->modifier[0],
> latency,
> - y_min_scanlines);
> -
> - plane_bytes_per_line = width * cpp;
> - plane_blocks_per_line = DIV_ROUND_UP(plane_bytes_per_line, 512);
> + plane_blocks_per_line);
>
> if (fb->modifier[0] == I915_FORMAT_MOD_Y_TILED ||
> fb->modifier[0] == I915_FORMAT_MOD_Yf_TILED) {
next prev parent reply other threads:[~2016-09-27 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1474578035-424-1-git-send-email-paulo.r.zanoni@intel.com>
2016-09-22 21:00 ` [PATCH 1/9] drm/i915: SAGV is not SKL-only, so rename a few things Paulo Zanoni
2016-09-22 21:00 ` [PATCH 2/9] drm/i915: introduce intel_has_sagv() Paulo Zanoni
2016-09-22 21:00 ` [PATCH 3/9] drm/i915/kbl: KBL also needs to run the SAGV code Paulo Zanoni
2016-09-22 21:00 ` [PATCH 4/9] drm/i915/gen9: fix the WaWmMemoryReadLatency implementation Paulo Zanoni
2016-09-22 21:00 ` [PATCH 5/9] drm/i915/gen9: minimum scanlines for Y tile is not always 4 Paulo Zanoni
2016-09-27 7:06 ` [Intel-gfx] " Tvrtko Ursulin
2016-09-22 21:00 ` [PATCH 6/9] drm/i915/gen9: fix plane_blocks_per_line on watermarks calculations Paulo Zanoni
2016-09-27 7:20 ` Tvrtko Ursulin [this message]
2016-09-22 21:00 ` [PATCH 7/9] drm/i915/gen9: fix the watermark res_blocks value Paulo Zanoni
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=3719f30a-0d51-a4f7-629a-ee7b16763042@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).