From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<badal.nilawar@intel.com>, <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v5 1/4] drm/xe/hwmon: Expose temperature limits
Date: Mon, 12 Jan 2026 12:20:26 +0530 [thread overview]
Message-ID: <8dd53b1d-69b9-44ef-b90e-2f083ab18bf0@intel.com> (raw)
In-Reply-To: <aWIldD6hKFt_Sle9@black.igk.intel.com>
On 10-01-2026 15:39, Raag Jadav wrote:
> On Sat, Jan 10, 2026 at 01:46:41AM +0530, Karthik Poosa wrote:
>> Read temperature limits using pcode mailbox and expose shutdown
>> temperature limit as tempX_emergency, critical temperature limit as
>> tempX_crit and GPU max temperature limit as temp2_max.
>>
>> Update Xe hwmon documentation for these entries.
> ...
>
>> @@ -808,6 +871,37 @@ xe_hwmon_temp_read(struct xe_hwmon *hwmon, u32 attr, int channel, long *val)
>> /* HW register value is in degrees Celsius, convert to millidegrees. */
>> *val = REG_FIELD_GET(TEMP_MASK, reg_val) * MILLIDEGREE_PER_DEGREE;
>> return 0;
>> + case hwmon_temp_emergency:
>> + switch (channel) {
>> + case CHANNEL_PKG:
>> + *val = hwmon->temp.limit[TEMP_LIMIT_PKG_SHUTDOWN] * MILLIDEGREE_PER_DEGREE;
>> + return 0;
>> + case CHANNEL_VRAM:
>> + *val = hwmon->temp.limit[TEMP_LIMIT_MEM_SHUTDOWN] * MILLIDEGREE_PER_DEGREE;
>> + return 0;
>> + default:
>> + return -EOPNOTSUPP;
>> + }
>> + case hwmon_temp_crit:
>> + switch (channel) {
>> + case CHANNEL_PKG:
>> + *val = hwmon->temp.limit[TEMP_LIMIT_PKG_CRIT] * MILLIDEGREE_PER_DEGREE;
>> + return 0;
>> + case CHANNEL_VRAM:
>> + *val = hwmon->temp.limit[TEMP_LIMIT_MEM_CRIT] * MILLIDEGREE_PER_DEGREE;
>> + return 0;
>> + default:
>> + return -EOPNOTSUPP;
>> + }
>> + break;
> Missed an instance, please drop it ;)
okay
>
>> + case hwmon_temp_max:
>> + switch (channel) {
>> + case CHANNEL_PKG:
>> + *val = hwmon->temp.limit[TEMP_LIMIT_PKG_MAX] * MILLIDEGREE_PER_DEGREE;
>> + return 0;
>> + default:
>> + return -EOPNOTSUPP;
>> + }
>> default:
>> return -EOPNOTSUPP;
>> }
>> @@ -1263,6 +1357,9 @@ xe_hwmon_get_preregistration_info(struct xe_hwmon *hwmon)
>> for (channel = 0; channel < FAN_MAX; channel++)
>> if (xe_hwmon_is_visible(hwmon, hwmon_fan, hwmon_fan_input, channel))
>> xe_hwmon_fan_input_read(hwmon, channel, &fan_speed);
>> +
>> + if (hwmon->xe->info.has_mbx_thermal_info && xe_hwmon_pcode_read_thermal_info(hwmon))
>> + drm_dbg(&hwmon->xe->drm, "Thermal mailbox not supported by card firmware\n");
> I think this should be drm_warn() but I'll let you all make the final call.
Yes, drm_warn should be fine.
>
> Reviewed-by: Raag Jadav <raag.jadav@intel.com>
next prev parent reply other threads:[~2026-01-12 6:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 20:16 [PATCH v5 0/4] drm/xe/hwmon: Expose new temperature attributes Karthik Poosa
2026-01-09 20:16 ` [PATCH v5 1/4] drm/xe/hwmon: Expose temperature limits Karthik Poosa
2026-01-10 10:09 ` Raag Jadav
2026-01-12 6:50 ` Poosa, Karthik [this message]
2026-01-09 20:16 ` [PATCH v5 2/4] drm/xe/hwmon: Expose memory controller temperature Karthik Poosa
2026-01-10 10:42 ` Raag Jadav
2026-01-12 6:56 ` Poosa, Karthik
2026-01-09 20:16 ` [PATCH v5 3/4] drm/xe/hwmon: Expose GPU pcie temperature Karthik Poosa
2026-01-10 11:13 ` Raag Jadav
2026-01-12 7:05 ` Poosa, Karthik
2026-01-09 20:16 ` [PATCH v5 4/4] drm/xe/hwmon: Expose individual vram channel temperature Karthik Poosa
2026-01-10 16:23 ` Raag Jadav
2026-01-10 19:22 ` Poosa, Karthik
2026-01-12 8:11 ` Raag Jadav
2026-01-12 11:45 ` Poosa, Karthik
2026-01-12 17:23 ` Rodrigo Vivi
2026-01-09 20:17 ` ✓ CI.KUnit: success for drm/xe/hwmon: Expose new temperature attributes (rev7) Patchwork
2026-01-09 21:25 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-10 2:06 ` ✓ 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=8dd53b1d-69b9-44ef-b90e-2f083ab18bf0@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