Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 3/4] drm/xe/hwmon: Expose GPU pcie temperature
Date: Mon, 12 Jan 2026 12:35:16 +0530	[thread overview]
Message-ID: <40fb0473-719d-4258-a976-9de376255799@intel.com> (raw)
In-Reply-To: <aWI0YuShzGJ5nfmu@black.igk.intel.com>


On 10-01-2026 16:43, Raag Jadav wrote:
> On Sat, Jan 10, 2026 at 01:46:43AM +0530, Karthik Poosa wrote:
>> Expose GPU PCIe average temperature and its limits via hwmon sysfs entry
> Please also use 'PCIe' with correct upper/lower case in patch subject.
>
> ...
PCIe is the right usage, changing it wherever needed.
>
>>   /* Index of memory controller in READ_THERMAL_DATA output */
>> -#define TEMP_INDEX_MCTRL	(2)
>> +#define TEMP_INDEX_MCTRL	2
> Unneeded churn. If you don't want braces, don't even introduce it in
> earlier patch.
Removing the parentheses in previous patch
>
>> +#define PCIE_SENSOR_GROUP_ID	0x2
> This is used as part of mailbox command ...
>
>> +#define PCIE_SENSOR_MASK	REG_GENMASK(31, 16)
> ... and these are output bitfields, so both should be in xe_pcode_api.h.
>
> ...
okay
>
>> +static int get_pcie_temp(struct xe_hwmon *hwmon, long *val)
>> +{
>> +	struct xe_tile *root_tile = xe_device_get_root_tile(hwmon->xe);
>> +	int ret;
>> +	u32 data = 0;
> Use reverse xmas tree order.
ok
>
>> +	ret = xe_pcode_read(root_tile, PCODE_MBOX(PCODE_THERMAL_INFO, READ_THERMAL_DATA,
>> +						  PCIE_SENSOR_GROUP_ID), &data, NULL);
>> +	if (ret)
>> +		return ret;
>> +
>> +	/* Sensor offset is different for G21 */
>> +	if (hwmon->xe->info.subplatform != XE_SUBPLATFORM_BATTLEMAGE_G21)
>> +		data = REG_FIELD_GET(PCIE_SENSOR_MASK, data);
>> +
>> +	data &= TEMP_MASK;
> Use REG_FIELD_GET() for consistency.
ok
>
>> +	*val = (s8)data * MILLIDEGREE_PER_DEGREE;
>> +
>> +	return 0;
>> +}
> Reviewed-by: Raag Jadav <raag.jadav@intel.com>

  reply	other threads:[~2026-01-12  7:05 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
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 [this message]
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=40fb0473-719d-4258-a976-9de376255799@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