All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe/mtl: Use 16.67 Mhz freq scale factor to get rpX
Date: Wed, 01 Nov 2023 08:23:15 -0700	[thread overview]
Message-ID: <87il6la464.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20231101151756.1617408-1-badal.nilawar@intel.com>

On Wed, 01 Nov 2023 08:17:56 -0700, Badal Nilawar wrote:
>

Hi Badal,

> For mtl and above 16.67 Mhz is the scale factor to calculate
> rpX frequencies.
>
> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_guc_pc.c | 25 ++++++++++++++-----------
>  1 file changed, 14 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c b/drivers/gpu/drm/xe/xe_guc_pc.c
> index 74247e0d3674..90e3e1b56c27 100644
> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
> @@ -306,14 +306,15 @@ static int pc_set_max_freq(struct xe_guc_pc *pc, u32 freq)
>  static void mtl_update_rpe_value(struct xe_guc_pc *pc)
>  {
>	struct xe_gt *gt = pc_to_gt(pc);
> -	u32 reg;
> +	u32 freq;
>
>	if (xe_gt_is_media_type(gt))
> -		reg = xe_mmio_read32(gt, MTL_MPE_FREQUENCY);
> +		freq = xe_mmio_read32(gt, MTL_MPE_FREQUENCY);
>	else
> -		reg = xe_mmio_read32(gt, MTL_GT_RPE_FREQUENCY);
> +		freq = xe_mmio_read32(gt, MTL_GT_RPE_FREQUENCY);

Generally I think we should avoid making these kind of variable name
changes, if only to keep the patch small and reduce the review
effort.

In this case, isn't 'reg' more appropriate anyway? If we retained reg this
would be a single line change in this function.

>
> -	pc->rpe_freq = REG_FIELD_GET(MTL_RPE_MASK, reg) * GT_FREQUENCY_MULTIPLIER;
> +	freq = REG_FIELD_GET(MTL_RPE_MASK, freq);
> +	pc->rpe_freq = decode_freq(freq);
>  }
>
>  static void tgl_update_rpe_value(struct xe_guc_pc *pc)
> @@ -645,18 +646,20 @@ static const struct attribute *pc_attrs[] = {
>  static void mtl_init_fused_rp_values(struct xe_guc_pc *pc)
>  {
>	struct xe_gt *gt = pc_to_gt(pc);
> -	u32 reg;
> +	u32 freq;
>
>	xe_device_assert_mem_access(pc_to_xe(pc));
>
>	if (xe_gt_is_media_type(gt))
> -		reg = xe_mmio_read32(gt, MTL_MEDIAP_STATE_CAP);
> +		freq = xe_mmio_read32(gt, MTL_MEDIAP_STATE_CAP);
>	else
> -		reg = xe_mmio_read32(gt, MTL_RP_STATE_CAP);
> -	pc->rp0_freq = REG_FIELD_GET(MTL_RP0_CAP_MASK, reg) *
> -		GT_FREQUENCY_MULTIPLIER;
> -	pc->rpn_freq = REG_FIELD_GET(MTL_RPN_CAP_MASK, reg) *
> -		GT_FREQUENCY_MULTIPLIER;
> +		freq = xe_mmio_read32(gt, MTL_RP_STATE_CAP);
> +
> +	freq = REG_FIELD_GET(MTL_RP0_CAP_MASK, freq);
> +	pc->rp0_freq = decode_freq(freq);
> +
> +	freq = REG_FIELD_GET(MTL_RPN_CAP_MASK, freq);
> +	pc->rpn_freq = decode_freq(freq);

Similar comments here too.

>  }
>
>  static void tgl_init_fused_rp_values(struct xe_guc_pc *pc)
> --
> 2.25.1
>

Thanks.
--
Ashutosh

  parent reply	other threads:[~2023-11-01 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 15:17 [Intel-xe] [PATCH] drm/xe/mtl: Use 16.67 Mhz freq scale factor to get rpX Badal Nilawar
2023-11-01 15:12 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-11-01 15:12 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-11-01 15:13 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-11-01 15:21 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-01 15:21 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-01 15:22 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-11-01 15:23 ` Dixit, Ashutosh [this message]
2023-11-01 15:58   ` [Intel-xe] [PATCH] " Nilawar, Badal
2023-11-01 15:55 ` [Intel-xe] ✓ CI.BAT: success for " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-11-01 16:32 [Intel-xe] [PATCH] " Badal Nilawar
2023-11-01 16:28 ` Dixit, Ashutosh

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=87il6la464.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.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 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.