Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Karthik Poosa <karthik.poosa@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <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>,
	<ravi.kishore.koppuravuri@intel.com>
Subject: Re: [PATCH v2 2/2] drm/xe/hwmon: Use shared pcode default timeout for power limit write
Date: Thu, 10 Sep 2026 17:59:28 -0400	[thread overview]
Message-ID: <aqMoQI5vySekKZ1D@intel.com> (raw)
In-Reply-To: <20260907083520.192418-3-karthik.poosa@intel.com>

On Mon, Sep 07, 2026 at 02:05:20PM +0530, Karthik Poosa wrote:
> Drop the local PL_WRITE_MBX_TIMEOUT_MS macro and use the common
> PCODE_DEFAULT_TIMEOUT_MS for the power limit write mailbox command.
> This removes a duplicate timeout definition and keeps hwmon in sync with
> the pcode default (now 10ms).
> 
> Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_hwmon.c | 7 +------
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> index 5284cab6703d..5edeac961ec3 100644
> --- a/drivers/gpu/drm/xe/xe_hwmon.c
> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
> @@ -101,11 +101,6 @@ enum sensor_attr_power {
>  
>  #define PWR_ATTR_TO_STR(attr)	(((attr) == hwmon_power_max) ? "PL1" : "PL2")
>  
> -/*
> - * Timeout for power limit write mailbox command.
> - */
> -#define PL_WRITE_MBX_TIMEOUT_MS	(1)
> -
>  /* Index of memory controller in READ_THERMAL_DATA output */
>  #define TEMP_INDEX_MCTRL	2
>  
> @@ -252,7 +247,7 @@ static int xe_hwmon_pcode_rmw_power_limit(const struct xe_hwmon *hwmon, u32 attr
>  							     (channel == CHANNEL_CARD) ?
>  							     WRITE_PSYSGPU_POWER_LIMIT :
>  							     WRITE_PACKAGE_POWER_LIMIT, 0),
> -							     val0, val1, PL_WRITE_MBX_TIMEOUT_MS);
> +							     val0, val1, PCODE_DEFAULT_TIMEOUT_MS);
>  	if (ret)
>  		drm_dbg(&hwmon->xe->drm, "write failed ch %d val0 0x%08x, val1 0x%08x, ret %d\n",
>  			channel, val0, val1, ret);
> -- 
> 2.25.1
> 

  parent reply	other threads:[~2026-09-10 21:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  8:35 [PATCH v2 0/2] drm/xe/pcode: Increase default mailbox timeout Karthik Poosa
2026-09-07  8:35 ` [PATCH v2 1/2] drm/xe/pcode: Increase default pcode mailbox timeout to 10ms Karthik Poosa
2026-09-10 21:59   ` Rodrigo Vivi
2026-09-07  8:35 ` [PATCH v2 2/2] drm/xe/hwmon: Use shared pcode default timeout for power limit write Karthik Poosa
2026-09-07  8:44   ` sashiko-bot
2026-09-08  6:06     ` Poosa, Karthik
2026-09-10 21:59   ` Rodrigo Vivi [this message]
2026-09-07  8:44 ` ✓ CI.KUnit: success for drm/xe/pcode: Increase default mailbox timeout Patchwork
2026-09-07  9:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-07 10:59 ` ✗ Xe.CI.FULL: failure " 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=aqMoQI5vySekKZ1D@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=ravi.kishore.koppuravuri@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