Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: "Nilawar, Badal" <badal.nilawar@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <rodrigo.vivi@intel.com>,
	<raag.jadav@intel.com>
Subject: Re: [PATCH] drm/xe/hwmon: Read accepted power limit for CRI
Date: Fri, 20 Mar 2026 18:19:13 +0530	[thread overview]
Message-ID: <51b1b6d2-5f40-4f2e-b2f4-8890e364a7b2@intel.com> (raw)
In-Reply-To: <4d6348b7-de39-4cf1-8281-dbd12ec37938@intel.com>


On 12-03-2026 15:58, Nilawar, Badal wrote:
>
> On 18-02-2026 17:17, Karthik Poosa wrote:
>> Update xe_hwmon_pcode_read_power_limit to read the accepted
> accepted by pcode firmware?
>> power limit using the new mailbox param introduced from CRI.
>>
>> Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_hwmon.c     | 5 +++--
>>   drivers/gpu/drm/xe/xe_pcode_api.h | 3 ++-
>>   2 files changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c 
>> b/drivers/gpu/drm/xe/xe_hwmon.c
>> index baf277955b33..8e1cbf7afed0 100644
>> --- a/drivers/gpu/drm/xe/xe_hwmon.c
>> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
>> @@ -192,8 +192,9 @@ static int xe_hwmon_pcode_read_power_limit(const 
>> struct xe_hwmon *hwmon, u32 att
>>                             READ_PSYSGPU_POWER_LIMIT :
>>                             READ_PACKAGE_POWER_LIMIT,
>>                             hwmon->boot_power_limit_read ?
>> -                          READ_PL_FROM_PCODE : READ_PL_FROM_FW),
>> -                          &val0, &val1);
>> +                          (hwmon->xe->info.platform >= 
>> XE_CRESCENTISLAND ?
>> +                           READ_PL_RESOLVED : READ_PL_FROM_PCODE) :
>
> I think this handling is needed in xe_hwmon_pcode_rmw_power_limit() as 
> well, especially when writing PWR_LIM_TIME.
>
> Thanks,
> Badal

Yes, adding this in next revision.

Also, adding an API to prepare param2 for power limits below.

+static inline int prepare_power_limit_param2(const struct xe_hwmon *hwmon)
+{
+       if (hwmon->boot_power_limit_read) {
+               if (hwmon->xe->info.platform >= XE_CRESCENTISLAND)
+                       return READ_PL_RESOLVED;
+               else
+                       return READ_PL_FROM_PCODE;
+       } else {
+               return READ_PL_FROM_FW;
+       }
+}

>> + READ_PL_FROM_FW), &val0, &val1);
>>         if (ret) {
>>           drm_dbg(&hwmon->xe->drm, "read failed ch %d val0 0x%08x, 
>> val1 0x%08x, ret %d\n",
>> diff --git a/drivers/gpu/drm/xe/xe_pcode_api.h 
>> b/drivers/gpu/drm/xe/xe_pcode_api.h
>> index 85cc7478b787..636b9dfb11da 100644
>> --- a/drivers/gpu/drm/xe/xe_pcode_api.h
>> +++ b/drivers/gpu/drm/xe/xe_pcode_api.h
>> @@ -47,8 +47,9 @@
>>   #define    WRITE_PSYSGPU_POWER_LIMIT        0x7
>>   #define    READ_PACKAGE_POWER_LIMIT        0x8
>>   #define    WRITE_PACKAGE_POWER_LIMIT        0x9
>> -#define    READ_PL_FROM_FW                0x1
>>   #define    READ_PL_FROM_PCODE            0x0
>> +#define    READ_PL_FROM_FW                0x1
>> +#define    READ_PL_RESOLVED            0x2
>>     #define   PCODE_THERMAL_INFO            0x25
>>   #define     READ_THERMAL_LIMITS            0x0

      reply	other threads:[~2026-03-20 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18 11:47 [PATCH] drm/xe/hwmon: Read accepted power limit for CRI Karthik Poosa
2026-02-18 15:38 ` ✓ CI.KUnit: success for " Patchwork
2026-02-18 16:14 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-18 17:20 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-12 10:28 ` [PATCH] " Nilawar, Badal
2026-03-20 12:49   ` Poosa, Karthik [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=51b1b6d2-5f40-4f2e-b2f4-8890e364a7b2@intel.com \
    --to=karthik.poosa@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=raag.jadav@intel.com \
    --cc=rodrigo.vivi@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