From: "Kumar G, Naresh" <naresh.kumar.g@intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "thomas.hellstrom@linux.intel.com" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH v3 1/1] drm/xe: Set GT rp min frequency as 1.2GHz default for BMG/CRI
Date: Wed, 25 Mar 2026 11:50:28 +0530 [thread overview]
Message-ID: <ebf0564f-410f-4968-b554-8b03c2463402@intel.com> (raw)
In-Reply-To: <41a25e7636ae6262818c51974cd2e602178cdb21.camel@intel.com>
On 25-03-2026 02:45, Summers, Stuart wrote:
> On Tue, 2026-03-24 at 23:51 +0530, Nareshkumar Gollakoti wrote:
>> While previously applied only to both tiles GT0(Graphics) and
>> Media(GT1)
>> the BMG G21(Battle image) platform via workaround Wa_14022085890,
>> this 1.2 GHz minimum is now the default for GT0(Graphics) tile
>> of BMG and CRI platforms.
>>
>> Setting this frequency floor(1.2GHz) default is critical in multi
>> GPU
>> environment for supporting effective Peer-to-Peer(P2P) transactions.
>>
>> v2:
>> - Fix Indentation(Thomas)
>> - Add comment about power impact(Stuart)
>>
>> v3:(Thomas/Ankur/Matt Roper)
>> - Add setting frequency to only GT0(Graphics) Tile of BMG/CRI
>>
>> Signed-off-by: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_guc_pc.c | 29 ++++++++++++++++++++++++++++-
>> 1 file changed, 28 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c
>> b/drivers/gpu/drm/xe/xe_guc_pc.c
>> index 5e5495a39a3c..2abfc2fff083 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
>> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
>> @@ -856,6 +856,21 @@ void xe_guc_pc_init_early(struct xe_guc_pc *pc)
>> pc_init_fused_rp_values(pc);
>> }
>>
>> +static bool pc_needs_min_freq_change(struct xe_guc_pc *pc)
>> +{
>> + struct xe_device *xe = pc_to_xe(pc);
>> + struct xe_gt *gt = pc_to_gt(pc);
>> +
>> + if (xe_gt_is_media_type(gt))
>> + return false;
>> +
>> + if (xe->info.platform == XE_BATTLEMAGE ||
>> + xe->info.platform == XE_CRESCENTISLAND)
>> + return true;
>> +
>> + return false;
>> +}
>> +
>> static int pc_adjust_freq_bounds(struct xe_guc_pc *pc)
>> {
>> struct xe_tile *tile = gt_to_tile(pc_to_gt(pc));
>> @@ -885,7 +900,19 @@ static int pc_adjust_freq_bounds(struct
>> xe_guc_pc *pc)
>> if (pc_get_min_freq(pc) > pc->rp0_freq)
>> ret = pc_set_min_freq(pc, pc->rp0_freq);
>>
>> - if (XE_DEVICE_WA(tile_to_xe(tile), 14022085890))
>> + /*
>> + * Setting GT RP min frequency to 1.2GHz by default for
>> + * GT0(Graphics) Tile of BMG and CRI.
>> + *
>> + * While BMG G21 WA will apply min freqeuncy for
>
> /s/freqeuncy/frequency/
Noted
>
>> + * both GT0(Graphics) and GT1(Media) Tile.
>> + *
>> + * This is an active frequency, so if the device is idle
>> + * we aren't expecting high power output across board
>
> If you post another series, you might add this last sentance also to
> the cover letter. I think it's important for customers to know that it
> only applies while they are running workloads.
Noted
>
>> + *
>> + */
>> + if (XE_DEVICE_WA(tile_to_xe(tile), 14022085890) ||
>
> Is there a reason not to move this bug ID check up to
> pc_needs_min_freq_change() also so we just check everything in one
> place?
>
There wont be any problem, can be moved inside the function and
just return true at first if WA is applicable otherwise only go further.
Thanks,
Naresh
> Thanks,
> Stuart
>
>> + pc_needs_min_freq_change(pc))
>> ret = pc_set_min_freq(pc, max(BMG_MIN_FREQ,
>> pc_get_min_freq(pc)));
>>
>> out:
>
next prev parent reply other threads:[~2026-03-25 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 18:21 [PATCH v3 0/1] drm/xe: Set GT rp min frequency as 1.2GHz default for BMG/CRI Nareshkumar Gollakoti
2026-03-24 18:21 ` [PATCH v3 1/1] " Nareshkumar Gollakoti
2026-03-24 21:15 ` Summers, Stuart
2026-03-25 6:20 ` Kumar G, Naresh [this message]
2026-03-24 18:35 ` ✓ CI.KUnit: success for drm/xe: Set GT rp min frequency as 1.2GHz default for BMG/CRI (rev3) Patchwork
2026-03-24 19:38 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-25 9:24 ` ✓ Xe.CI.FULL: " 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=ebf0564f-410f-4968-b554-8b03c2463402@intel.com \
--to=naresh.kumar.g@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=stuart.summers@intel.com \
--cc=thomas.hellstrom@linux.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