From: Raag Jadav <raag.jadav@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
matthew.d.roper@intel.com, intel-xe@lists.freedesktop.org,
anshuman.gupta@intel.com, riana.tauro@intel.com,
badal.nilawar@intel.com, karthik.poosa@intel.com
Subject: Re: [PATCH v2] drm/xe/hwmon: expose package and vram temperature
Date: Wed, 5 Feb 2025 19:50:38 +0200 [thread overview]
Message-ID: <Z6Ok7v0cubcdf2t3@black.fi.intel.com> (raw)
In-Reply-To: <Z5zRn9tijHkPxrhy@ashyti-mobl2.lan>
On Fri, Jan 31, 2025 at 02:35:27PM +0100, Andi Shyti wrote:
> Hi Raag,
>
> ...
>
> > diff --git a/drivers/gpu/drm/xe/regs/xe_mchbar_regs.h b/drivers/gpu/drm/xe/regs/xe_mchbar_regs.h
> > index 519dd1067a19..f5e5234857c1 100644
> > --- a/drivers/gpu/drm/xe/regs/xe_mchbar_regs.h
> > +++ b/drivers/gpu/drm/xe/regs/xe_mchbar_regs.h
> > @@ -34,6 +34,9 @@
> >
> > #define PCU_CR_PACKAGE_ENERGY_STATUS XE_REG(MCHBAR_MIRROR_BASE_SNB + 0x593c)
> >
> > +#define PCU_CR_PACKAGE_TEMPERATURE XE_REG(MCHBAR_MIRROR_BASE_SNB + 0x5978)
> > +#define TEMP_MASK REG_GENMASK(7, 0)
>
> is it called TEMP also in the docs? It can somehow be confused
> with "temporary".
Doc just calls it DATA, but I went with GENMASK() macro convention here.
And since it'll be used by temperature functions, the room for confusion is
less likely.
> In any case:
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
I don't believe we allow duplicate tags (context: it's already in the patch),
but at some point we might want to allow it for (re-)assurance :D
Thank you (x2).
Raag
next prev parent reply other threads:[~2025-02-05 17:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 5:45 [PATCH v2] drm/xe/hwmon: expose package and vram temperature Raag Jadav
2025-01-31 6:29 ` ✓ CI.Patch_applied: success for drm/xe/hwmon: expose package and vram temperature (rev2) Patchwork
2025-01-31 6:30 ` ✓ CI.checkpatch: " Patchwork
2025-01-31 6:31 ` ✓ CI.KUnit: " Patchwork
2025-01-31 6:47 ` ✓ CI.Build: " Patchwork
2025-01-31 6:49 ` ✓ CI.Hooks: " Patchwork
2025-01-31 6:51 ` ✓ CI.checksparse: " Patchwork
2025-01-31 7:22 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-31 10:04 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-31 13:35 ` [PATCH v2] drm/xe/hwmon: expose package and vram temperature Andi Shyti
2025-02-05 17:50 ` Raag Jadav [this message]
2025-02-06 10:48 ` Andi Shyti
2025-01-31 13:54 ` Nilawar, Badal
2025-01-31 14:43 ` Poosa, Karthik
2025-02-01 6:37 ` Raag Jadav
2025-02-03 6:27 ` Riana Tauro
2025-02-04 23:45 ` Rodrigo Vivi
2025-02-05 7:10 ` Riana Tauro
2025-02-05 12:02 ` Raag Jadav
2025-02-05 13:51 ` Rodrigo Vivi
2025-02-05 15:31 ` Lucas De Marchi
2025-02-05 17:29 ` Raag Jadav
2025-02-06 15:32 ` Vivi, Rodrigo
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=Z6Ok7v0cubcdf2t3@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=riana.tauro@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