Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
Cc: "Vivekanandan, Balasubramani" <balasubramani.vivekanandan@intel.com>
Subject: Re: [PATCH v3] drm/xe: Fix a bug in pc_adjust_freq_bounds()
Date: Tue, 11 Aug 2026 19:55:18 +0000	[thread overview]
Message-ID: <1f809ee1978cfa9fb9f9906cc85ca8bdf2681278.camel@intel.com> (raw)
In-Reply-To: <20260805234649.2076384-1-vinay.belgaumkar@intel.com>

On Wed, 2026-08-05 at 16:46 -0700, Vinay Belgaumkar wrote:
> In cases where min frequency was actually greater than BMG_MIN_FREQ,
> we were not using the updated min frequency as there was a missing
> call to pc_action_query_task_state() between the two settings of
> min frequency. Since we know what min_freq was last set, use that
> cached value while comparing to BMG_MIN_FREQ to fix this issue.
> 
> v2: pc->freq_ready is not set until after pc_adjust_freq_bounds().
> Stay
> with pc_action_query_task_state() instead.
> 
> v3: Update commit message (Stuart)
> 
> Fixes: bdde16c9ac5c ("drm/xe/bmg: Update Wa_14022085890")
> Signed-off-by: Balasubramani Vivekanandan
> <balasubramani.vivekanandan@intel.com>
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>

Reviewed-by: Stuart Summers <stuart.summers@intel.com>

Thanks for the change here!

> ---
>  drivers/gpu/drm/xe/xe_guc_pc.c | 13 ++++++++++---
>  1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c
> b/drivers/gpu/drm/xe/xe_guc_pc.c
> index 59f2fa79ad42..7cf8f4858598 100644
> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
> @@ -911,6 +911,7 @@ static bool pc_needs_min_freq_change(struct
> xe_guc_pc *pc)
>  static int pc_adjust_freq_bounds(struct xe_guc_pc *pc)
>  {
>         int ret;
> +       u32 min_freq;
>  
>         lockdep_assert_held(&pc->freq_lock);
>  
> @@ -933,8 +934,14 @@ static int pc_adjust_freq_bounds(struct
> xe_guc_pc *pc)
>          * Same thing happens for Server platforms where min is
> listed as
>          * RPMax
>          */
> -       if (pc_get_min_freq(pc) > pc->rp0_freq)
> +       min_freq = pc_get_min_freq(pc);
> +       if (min_freq > pc->rp0_freq) {
>                 ret = pc_set_min_freq(pc, pc->rp0_freq);
> +               if (ret)
> +                       goto out;
> +
> +               min_freq = pc->rp0_freq;
> +       }
>  
>         /*
>          * Setting GT RP min frequency to 1.2GHz by default for
> @@ -947,8 +954,8 @@ static int pc_adjust_freq_bounds(struct xe_guc_pc
> *pc)
>          * we aren't expecting high power output across board
>          *
>          */
> -       if (pc_needs_min_freq_change(pc))
> -               ret = pc_set_min_freq(pc, max(BMG_MIN_FREQ,
> pc_get_min_freq(pc)));
> +       if (pc_needs_min_freq_change(pc) && min_freq < BMG_MIN_FREQ)
> +               ret = pc_set_min_freq(pc, BMG_MIN_FREQ);
>  
>  out:
>         return ret;


      parent reply	other threads:[~2026-08-11 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 23:46 [PATCH v3] drm/xe: Fix a bug in pc_adjust_freq_bounds() Vinay Belgaumkar
2026-08-06  1:19 ` ✓ CI.KUnit: success for drm/xe: Fix a bug in pc_adjust_freq_bounds() (rev3) Patchwork
2026-08-06  2:07 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-06 12:45 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-08-11 19:55 ` Summers, Stuart [this message]

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=1f809ee1978cfa9fb9f9906cc85ca8bdf2681278.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=vinay.belgaumkar@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