From: Raag Jadav <raag.jadav@intel.com>
To: Karthik Poosa <karthik.poosa@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
badal.nilawar@intel.com, rodrigo.vivi@intel.com
Subject: Re: [PATCH v5 2/4] drm/xe/hwmon: Expose memory controller temperature
Date: Sat, 10 Jan 2026 11:42:30 +0100 [thread overview]
Message-ID: <aWItFl5qz85fwjA6@black.igk.intel.com> (raw)
In-Reply-To: <20260109201644.736483-3-karthik.poosa@intel.com>
On Sat, Jan 10, 2026 at 01:46:42AM +0530, Karthik Poosa wrote:
> Expose GPU memory controller average temperature and its limits under
> temp4_xxx.
> Update Xe hwmon documentation for this.
...
> @@ -718,15 +727,50 @@ static int xe_hwmon_pcode_read_thermal_info(struct xe_hwmon *hwmon)
> {
> struct xe_tile *root_tile = xe_device_get_root_tile(hwmon->xe);
> int ret;
> + u32 config = 0;
Use reverse xmas tree order.
> ret = xe_pcode_read(root_tile, PCODE_MBOX(PCODE_THERMAL_INFO, READ_THERMAL_LIMITS, 0),
> &hwmon->temp.data[0], &hwmon->temp.data[1]);
> + if (ret)
> + return ret;
> +
> drm_dbg(&hwmon->xe->drm, "thermal info read val 0x%x val1 0x%x\n",
> hwmon->temp.data[0], hwmon->temp.data[1]);
>
> + ret = xe_pcode_read(root_tile, PCODE_MBOX(PCODE_THERMAL_INFO, READ_THERMAL_CONFIG, 0),
> + &config, NULL);
> + if (ret)
> + return ret;
> +
> + drm_dbg(&hwmon->xe->drm, "thermal config count %d\n", config);
If you want decimal value then I think you should print after[*] you mask
it, but if you want raw value then I think 0x%x would be more useful for
debugging.
> + hwmon->temp.count = config & TEMP_MASK;
Use REG_FIELD_GET() for consistency.
[*]
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
next prev parent reply other threads:[~2026-01-10 10:42 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
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 [this message]
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=aWItFl5qz85fwjA6@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@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