From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: ville.syrjala@intel.com
Subject: Re: [Intel-gfx] [PATCH v6 2/7] drm/i915: update the QGV point frequency calculations
Date: Tue, 23 May 2023 12:01:46 +0300 [thread overview]
Message-ID: <87fs7nmnet.fsf@intel.com> (raw)
In-Reply-To: <20230522230759.153112-3-vinod.govindapillai@intel.com>
On Tue, 23 May 2023, Vinod Govindapillai <vinod.govindapillai@intel.com> wrote:
> From MTL onwwards, pcode locks the QGV point based on peak BW of
> the intended QGV point passed by the driver. So the peak BW
> calculation must match the value expected by the pcode. Update
> the calculations as per the Bspec.
>
> v2: use DIV_ROUND_* macro for the calculations (Ville)
>
> 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 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> index ab405c48ca3a..c8075a37c3ab 100644
> --- a/drivers/gpu/drm/i915/display/intel_bw.c
> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> @@ -182,7 +182,7 @@ static int mtl_read_qgv_point_info(struct drm_i915_private *dev_priv,
> val2 = intel_uncore_read(&dev_priv->uncore,
> MTL_MEM_SS_INFO_QGV_POINT_HIGH(point));
> dclk = REG_FIELD_GET(MTL_DCLK_MASK, val);
> - sp->dclk = DIV_ROUND_UP((16667 * dclk), 1000);
> + sp->dclk = DIV_ROUND_CLOSEST(16667 * dclk + 500, 1000);
What's with the +500 there?
BR,
Jani.
> sp->t_rp = REG_FIELD_GET(MTL_TRP_MASK, val);
> sp->t_rcd = REG_FIELD_GET(MTL_TRCD_MASK, val);
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-05-23 9:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 23:07 [Intel-gfx] [PATCH v6 0/7] mtl: add support for pmdemand Vinod Govindapillai
2023-05-22 23:07 ` [Intel-gfx] [PATCH v6 1/7] drm/i915: fix the derating percentage for MTL Vinod Govindapillai
2023-05-22 23:07 ` [Intel-gfx] [PATCH v6 2/7] drm/i915: update the QGV point frequency calculations Vinod Govindapillai
2023-05-23 9:01 ` Jani Nikula [this message]
2023-05-23 12:32 ` Govindapillai, Vinod
2023-05-23 13:14 ` Jani Nikula
2023-05-24 6:42 ` Govindapillai, Vinod
2023-05-22 23:07 ` [Intel-gfx] [PATCH v6 3/7] drm/i915: store the peak bw per QGV point Vinod Govindapillai
2023-05-22 23:07 ` [Intel-gfx] [PATCH v6 4/7] drm/i915: extract intel_bw_check_qgv_points() Vinod Govindapillai
2023-05-23 9:05 ` Jani Nikula
2023-05-23 13:03 ` Govindapillai, Vinod
2023-05-22 23:07 ` [Intel-gfx] [PATCH v6 5/7] drm/i915: modify max_bw to return index to intel_bw_info Vinod Govindapillai
2023-05-22 23:07 ` [Intel-gfx] [PATCH v6 6/7] drm/i915/mtl: find the best QGV point for the SAGV configuration Vinod Govindapillai
2023-05-22 23:07 ` [Intel-gfx] [PATCH v6 7/7] drm/i915/mtl: Add support for PM DEMAND Vinod Govindapillai
2023-05-23 15:09 ` Gustavo Sousa
2023-05-22 23:18 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for mtl: add support for pmdemand (rev6) 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=87fs7nmnet.fsf@intel.com \
--to=jani.nikula@linux.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.