Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: <rodrigo.vivi@intel.com>, <anshuman.gupta@intel.com>,
	<badal.nilawar@intel.com>, <raag.jadav@intel.com>,
	<riana.tauro@intel.com>, <sk.anirban@intel.com>,
	<mallesh.koujalagi@intel.com>, <soham.purkait@intel.com>
Subject: Re: [PATCH v3 0/5] drm/xe/hwmon: Update hwmon thermal mailbox handling
Date: Thu, 24 Sep 2026 16:46:21 +0530	[thread overview]
Message-ID: <3e281317-1b9c-4ceb-8e64-21be3160ea4d@intel.com> (raw)
In-Reply-To: <20260910182756.638830-1-karthik.poosa@intel.com>


On 10-09-2026 23:57, Karthik Poosa wrote:
> This series adds CRI-specific temperature sensor handling to the Xe
> hwmon implementation.
>
> CRI platforms may report unavailable temperature sensors and support
> a variable number of VRAM temperature channels depending on platform
> configuration. This series adds the required sensor presence checks and
> uses platform-reported thermal configuration data to expose only valid
> temperature-related hwmon attributes.
>
> The series also corrects the telemetry group selection used for memory
> controller temperature reporting.
>
> v2:
>   - Address review comments from Sashiko, Badal and Raag.
>   - Enable IEEE 754 temperature decoding for MMIO temperature registers.
>    - Split sensor validity check into mailbox vs MMIO handling; add
>      is_temp_available() / is_temp_is_visible().
>   - Temporarily disable memory controller and PCIe temperatures on CRI.
>
> v3:
>    - Detect unavailable temperature sensors: rephrase a debug log.
>    - Use VRAM temperature sensor count from thermal config on CRI: address
>      review comments from sashiko-bot@kernel.org and Rodrigo.
>    - Decode CRI temperature registers as IEEE-754: reject temperatures that
>      overflow long on 32-bit systems.
>
> Karthik Poosa (5):
>    drm/xe/hwmon: Detect unavailable temperature sensors
>    drm/xe/hwmon: Use VRAM temperature sensor count from thermal config on
>      CRI
>    drm/xe/hwmon: Fix memory controller thermal data handling
>    drm/xe/hwmon: Decode CRI temperature registers as IEEE-754
>    drm/xe/hwmon: Disable memory controller and PCIe temperatures on CRI
>
>   drivers/gpu/drm/xe/xe_device_types.h |   4 +
>   drivers/gpu/drm/xe/xe_hwmon.c        | 322 ++++++++++++++++++++++-----
>   drivers/gpu/drm/xe/xe_pci.c          |   2 +
>   drivers/gpu/drm/xe/xe_pci_types.h    |   1 +
>   drivers/gpu/drm/xe/xe_pcode_api.h    |   1 +
>   5 files changed, 273 insertions(+), 57 deletions(-)

Next version of this patch series is at 
https://patchwork.freedesktop.org/series/174898/#rev2


      parent reply	other threads:[~2026-09-24 11:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 18:27 [PATCH v3 0/5] drm/xe/hwmon: Update hwmon thermal mailbox handling Karthik Poosa
2026-09-10 18:27 ` [PATCH v3 1/5] drm/xe/hwmon: Detect unavailable temperature sensors Karthik Poosa
2026-09-10 18:42   ` sashiko-bot
2026-09-17 11:02     ` Poosa, Karthik
2026-09-18  9:40   ` Rodrigo Vivi
2026-09-23 15:49     ` Poosa, Karthik
2026-09-10 18:27 ` [PATCH v3 2/5] drm/xe/hwmon: Use VRAM temperature sensor count from thermal config on CRI Karthik Poosa
2026-09-10 18:47   ` sashiko-bot
2026-09-18  9:50   ` Rodrigo Vivi
2026-09-10 18:27 ` [PATCH v3 3/5] drm/xe/hwmon: Fix memory controller thermal data handling Karthik Poosa
2026-09-18 10:00   ` Rodrigo Vivi
2026-09-10 18:27 ` [PATCH v3 4/5] drm/xe/hwmon: Decode CRI temperature registers as IEEE-754 Karthik Poosa
2026-09-18 10:13   ` Rodrigo Vivi
2026-09-24  6:54     ` Poosa, Karthik
2026-09-10 18:27 ` [PATCH v3 5/5] drm/xe/hwmon: Disable memory controller and PCIe temperatures on CRI Karthik Poosa
2026-09-18 10:20   ` Rodrigo Vivi
2026-09-23 18:37     ` Poosa, Karthik
2026-09-10 18:47 ` ✓ CI.KUnit: success for drm/xe/hwmon: Update hwmon thermal mailbox handling (rev3) Patchwork
2026-09-10 19:52 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-11  4:49 ` ✓ Xe.CI.FULL: " Patchwork
2026-09-24 11:16 ` 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=3e281317-1b9c-4ceb-8e64-21be3160ea4d@intel.com \
    --to=karthik.poosa@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mallesh.koujalagi@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sk.anirban@intel.com \
    --cc=soham.purkait@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