From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tursulin@ursulin.net, linux@roeck-us.net,
andi.shyti@linux.intel.com, intel-gfx@lists.freedesktop.org,
linux-hwmon@vger.kernel.org, anshuman.gupta@intel.com,
badal.nilawar@intel.com, riana.tauro@intel.com,
ashutosh.dixit@intel.com, karthik.poosa@intel.com
Subject: Re: [PATCH v1] drm/i915/hwmon: expose package temperature
Date: Wed, 28 Aug 2024 16:59:00 +0300 [thread overview]
Message-ID: <Zs8tJNV8ATILvmmA@smile.fi.intel.com> (raw)
In-Reply-To: <20240828044512.2710381-1-raag.jadav@intel.com>
On Wed, Aug 28, 2024 at 10:15:12AM +0530, Raag Jadav wrote:
> Add hwmon support for temp1_input attribute, which will expose package
> temperature in millidegree Celsius. With this in place we can monitor
> package temperature using lm-sensors tool.
>
> $ sensors
> i915-pci-0300
> Adapter: PCI adapter
> in0: 990.00 mV
> fan1: 1260 RPM
> temp1: +45.0°C
> power1: N/A (max = 35.00 W)
> energy1: 12.62 kJ
...
> +static umode_t
> +hwm_temp_is_visible(const struct hwm_drvdata *ddat, u32 attr)
> +{
> + struct i915_hwmon *hwmon = ddat->hwmon;
> +
> + if (attr == hwmon_temp_input && i915_mmio_reg_valid(hwmon->rg.pkg_temp))
> + return 0444;
> +
> + return 0;
Just a question (I'm fine with this implementation): is the style in this file
to check for correct cases first and return an err/etc at the end?
> +}
> +
> +static int
> +hwm_temp_read(struct hwm_drvdata *ddat, u32 attr, long *val)
> +{
> + struct i915_hwmon *hwmon = ddat->hwmon;
> + intel_wakeref_t wakeref;
> + u32 reg_val;
> +
> + if (attr == hwmon_temp_input) {
> + with_intel_runtime_pm(ddat->uncore->rpm, wakeref)
> + reg_val = intel_uncore_read(ddat->uncore, hwmon->rg.pkg_temp);
> +
> + /* HW register value is in degrees, convert to millidegrees. */
> + *val = REG_FIELD_GET(TEMP_MASK, reg_val) * MILLIDEGREE_PER_DEGREE;
> + return 0;
> + }
...because here we may drop an indentation level by doing it opposite
if (x != y)
return -E...;
...
> + return -EOPNOTSUPP;
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-08-28 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 4:45 [PATCH v1] drm/i915/hwmon: expose package temperature Raag Jadav
2024-08-28 4:34 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2024-08-28 13:59 ` Andy Shevchenko [this message]
2024-08-29 7:50 ` [PATCH v1] " Raag Jadav
2024-09-03 20:03 ` ✗ Fi.CI.BAT: failure for drm/i915/hwmon: expose package temperature (rev2) Patchwork
2024-09-05 6:26 ` [PATCH v1] drm/i915/hwmon: expose package temperature Nilawar, Badal
2024-09-05 8:55 ` Raag Jadav
2024-09-05 14:09 ` Anshuman Gupta
2024-09-05 19:18 ` Raag Jadav
2024-09-06 6:26 ` Anshuman Gupta
2024-09-06 11:03 ` Nilawar, Badal
2024-09-07 11:18 ` Raag Jadav
2024-09-10 4:33 ` Nilawar, Badal
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=Zs8tJNV8ATILvmmA@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=karthik.poosa@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
/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