Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: Karthik Poosa <karthik.poosa@intel.com>,
	<intel-xe@lists.freedesktop.org>,  <anshuman.gupta@intel.com>,
	<badal.nilawar@intel.com>, <riana.tauro@intel.com>,
	<sk.anirban@intel.com>, <mallesh.koujalagi@intel.com>,
	<soham.purkait@intel.com>
Subject: Re: [PATCH 2/3] drm/xe/hwmon: Use VRAM temperature sensor count from thermal config on CRI
Date: Wed, 26 Aug 2026 16:10:43 -0400	[thread overview]
Message-ID: <ao9IQ3KnnwsIeZQ-@intel.com> (raw)
In-Reply-To: <ao8uP1ykIgCjkUvF@black.igk.intel.com>

On Wed, Aug 26, 2026 at 08:19:43PM +0200, Raag Jadav wrote:
> On Tue, Aug 25, 2026 at 12:11:32AM +0530, Karthik Poosa wrote:
> > Read the number of VRAM temperature sensor channels from the second byte
> > of READ_THERMAL_CONFIG on CRI platforms. Use the reported count to avoid
> > exposing hwmon attributes for unavailable VRAM temperature sensors, while
> > retaining the maximum supported channel count on non-CRI platforms.
> > 
> > Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_hwmon.c     | 35 ++++++++++++++++++++++++++-----
> >  drivers/gpu/drm/xe/xe_pcode_api.h |  1 +
> >  2 files changed, 31 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> > index 2c4eba4b8f8f..6e7cb250e628 100644
> > --- a/drivers/gpu/drm/xe/xe_hwmon.c
> > +++ b/drivers/gpu/drm/xe/xe_hwmon.c
> > @@ -39,7 +39,8 @@ enum xe_hwmon_reg_operation {
> >  	REG_READ64,
> >  };
> >  
> > -#define MAX_VRAM_CHANNELS      (16)
> > +/* Maximum number of VRAM channels supported by Xe */
> > +#define MAX_VRAM_CHANNELS      (80)
> 
> Why?

it is used below.

But it should simply be something like this:

#define MAX_VRAM_CHANNELS	16
#define CRI_MAX_VRAM_CHANNELS	80

and both gets used below

> 
> >  enum xe_hwmon_channel {
> >  	CHANNEL_CARD,
> > @@ -48,6 +49,7 @@ enum xe_hwmon_channel {
> >  	CHANNEL_MCTRL,
> >  	CHANNEL_PCIE,
> >  	CHANNEL_VRAM_N,
> > +	/* Compile-time upper bound; actual channel count is hwmon->temp.vram_count */
> >  	CHANNEL_VRAM_N_MAX = CHANNEL_VRAM_N + MAX_VRAM_CHANNELS - 1,
> >  	CHANNEL_MAX,
> >  };
> > @@ -144,10 +146,12 @@ struct xe_hwmon_thermal_info {
> >  	};
> >  	/** @count: no of temperature sensors available for the platform */
> 
> So now this can be "total number of temperature sensors"?
> 
> >  	u8 count;
> > +	/** @vram_count: number of VRAM temperature sensors available for the platform */
> > +	u8 vram_count;
> >  	/** @value: signed value from each sensor */
> >  	s8 value[U8_MAX];
> > -	/** @vram_label: vram label names */
> > -	char vram_label[MAX_VRAM_CHANNELS][MAX_LABEL_SIZE];
> > +	/** @vram_label: vram label names, dynamically allocated based on vram_count */
> > +	char (*vram_label)[MAX_LABEL_SIZE];
> >  };
> >  
> >  /**
> > @@ -271,7 +275,7 @@ static struct xe_reg xe_hwmon_get_reg(struct xe_hwmon *hwmon, enum xe_hwmon_reg
> >  				return BMG_PACKAGE_TEMPERATURE;
> >  			else if (channel == CHANNEL_VRAM)
> >  				return BMG_VRAM_TEMPERATURE;
> > -			else if (in_range(channel, CHANNEL_VRAM_N, MAX_VRAM_CHANNELS))
> > +			else if (in_range(channel, CHANNEL_VRAM_N, hwmon->temp.vram_count))
> >  				return BMG_VRAM_TEMPERATURE_N(channel - CHANNEL_VRAM_N);
> >  		} else if (xe->info.platform == XE_DG2) {
> >  			if (channel == CHANNEL_PKG)
> > @@ -810,6 +814,17 @@ static int xe_hwmon_pcode_read_thermal_info(struct xe_hwmon *hwmon)
> >  	drm_dbg(&hwmon->xe->drm, "thermal config count 0x%x\n", config);
> >  	hwmon->temp.count = REG_FIELD_GET(TEMP_MASK, config);
> >  
> > +	if (hwmon->xe->info.platform >= XE_CRESCENTISLAND) {
> 
> Same as last patch. Don't solve problems that don't exist.
> 
> > +		hwmon->temp.vram_count = REG_FIELD_GET(VRAM_COUNT_MASK, config);
> > +		if (hwmon->temp.vram_count > MAX_VRAM_CHANNELS && hwmon->temp.vram_count) {
> 
> Isn't the first condition sufficient? What am I missing?
> 
> > +			drm_warn(&hwmon->xe->drm, "VRAM channel count %d exceeds max %d, clamping\n",
> 
> Can this be invalid? i.e. 0xff? And should we clamp it in that case?
> 
> > +				 hwmon->temp.vram_count, MAX_VRAM_CHANNELS);
> > +			hwmon->temp.vram_count = MAX_VRAM_CHANNELS;

hwmon->temp.vram_count = CRI_MAX_VRAM_CHANNELS;

> 
> So perhaps CRI_MAX_VRAM_CHANNELS?
> 
> > +		}
> > +	} else {
> > +		hwmon->temp.vram_count = 16; /* For older platforms, max is 16 VRAM channels */
> 
> BMG_MAX_VRAM_CHANNELS?

hwmon->temp.vram_count = MAX_VRAM_CHANNELS;

do not necessarily need to add a prefix to the old one...
just a prefix for the new one...
But if someone's OCD is asking for symmetry then

XE_MAX_VRAM_CHANNELS
or
BMG_MAX_VRAM_CHANNELS

are both accepted options...

> 
> > +	}
> > +
> >  	return ret;
> >  }
> >  
> > @@ -988,6 +1003,9 @@ static inline bool is_vram_ch_available(struct xe_hwmon *hwmon, int channel)
> >  	u32 reg_val;
> >  	u8 temp;
> >  
> > +	if (vram_id >= hwmon->temp.vram_count)
> > +		return false;
> > +
> >  	vram_reg = xe_hwmon_get_reg(hwmon, REG_TEMP, channel);
> >  	if (!xe_reg_is_valid(vram_reg))
> >  		return false;
> > @@ -1516,7 +1534,7 @@ static int xe_hwmon_read_label(struct device *dev,
> >  			*str = "mctrl";
> >  		else if (channel == CHANNEL_PCIE)
> >  			*str = "pcie";
> > -		else if (in_range(channel, CHANNEL_VRAM_N, MAX_VRAM_CHANNELS))
> > +		else if (in_range(channel, CHANNEL_VRAM_N, hwmon->temp.vram_count))
> >  			*str = hwmon->temp.vram_label[channel - CHANNEL_VRAM_N];
> >  		return 0;
> >  	case hwmon_power:
> > @@ -1645,6 +1663,13 @@ int xe_hwmon_register(struct xe_device *xe)
> >  
> >  	xe_hwmon_get_preregistration_info(hwmon);
> >  
> > +	hwmon->temp.vram_label = devm_kcalloc(dev, hwmon->temp.vram_count,
> 
> What if vram_count is 0?

then we probably already skipped on the vram_id >= check above no?!
But better to check indeed...

> 
> Raag
> 
> > +					      MAX_LABEL_SIZE, GFP_KERNEL);
> > +	if (!hwmon->temp.vram_label) {
> > +		xe->hwmon = NULL;
> > +		return -ENOMEM;
> > +	}
> > +
> >  	drm_dbg(&xe->drm, "Register xe hwmon interface\n");
> >  
> >  	/*  hwmon_dev points to device hwmon<i> */
> > diff --git a/drivers/gpu/drm/xe/xe_pcode_api.h b/drivers/gpu/drm/xe/xe_pcode_api.h
> > index 94575c476e3d..e1079eff72c6 100644
> > --- a/drivers/gpu/drm/xe/xe_pcode_api.h
> > +++ b/drivers/gpu/drm/xe/xe_pcode_api.h
> > @@ -57,6 +57,7 @@
> >  #define   PCODE_THERMAL_INFO			0x25
> >  #define     READ_THERMAL_LIMITS			0x0
> >  #define     READ_THERMAL_CONFIG			0x1
> > +#define       VRAM_COUNT_MASK			REG_GENMASK(15, 8)
> >  #define     READ_THERMAL_DATA			0x2
> >  #define       PCIE_SENSOR_GROUP_ID		0x2
> >  #define       PCIE_SENSOR_MASK			REG_GENMASK(31, 16)
> > -- 
> > 2.25.1
> > 

  reply	other threads:[~2026-08-26 20:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 18:41 [PATCH 0/3] drm/xe/hwmon: Update hwmon thermal mailbox handling Karthik Poosa
2026-08-24 18:41 ` [PATCH 1/3] drm/xe/hwmon: Detect unavailable temperature sensors Karthik Poosa
2026-08-24 18:59   ` sashiko-bot
2026-08-25  6:45     ` Poosa, Karthik
2026-08-26 11:50   ` Nilawar, Badal
2026-08-27  5:16     ` Poosa, Karthik
2026-08-26 14:27   ` Raag Jadav
2026-08-26 20:20     ` Rodrigo Vivi
2026-08-24 18:41 ` [PATCH 2/3] drm/xe/hwmon: Use VRAM temperature sensor count from thermal config on CRI Karthik Poosa
2026-08-24 18:57   ` sashiko-bot
2026-08-25  7:22     ` Poosa, Karthik
2026-08-26 12:31   ` Nilawar, Badal
2026-08-26 18:19   ` Raag Jadav
2026-08-26 20:10     ` Rodrigo Vivi [this message]
2026-08-24 18:41 ` [PATCH 3/3] drm/xe/hwmon: Correct group selection for memory controller temperature Karthik Poosa
2026-08-24 18:54   ` sashiko-bot
2026-08-25  7:42     ` Poosa, Karthik
2026-08-24 18:41 ` [PATCH 0/3] drm/xe/hwmon: Update hwmon thermal mailbox handling Karthik Poosa
2026-08-24 18:41 ` [PATCH 1/3] drm/xe/hwmon: Detect unavailable temperature sensors Karthik Poosa
2026-08-24 18:58   ` sashiko-bot
2026-08-24 18:41 ` [PATCH 2/3] drm/xe/hwmon: Use VRAM temperature sensor count from thermal config on CRI Karthik Poosa
2026-08-24 18:56   ` sashiko-bot
2026-08-24 18:41 ` [PATCH 3/3] drm/xe/hwmon: Correct group selection for memory controller temperature Karthik Poosa
2026-08-24 18:57   ` sashiko-bot
2026-08-24 23:02 ` ✓ CI.KUnit: success for drm/xe/hwmon: Update hwmon thermal mailbox handling Patchwork
2026-08-24 23:59 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-08-25  3:10 ` ✓ Xe.CI.FULL: success " 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=ao9IQ3KnnwsIeZQ-@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=karthik.poosa@intel.com \
    --cc=mallesh.koujalagi@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=riana.tauro@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