From: Raag Jadav <raag.jadav@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tursulin@ursulin.net, airlied@gmail.com,
daniel@ffwll.ch, linux@roeck-us.net,
andriy.shevchenko@linux.intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-hwmon@vger.kernel.org, linux-kernel@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 v5] drm/i915/hwmon: expose fan speed
Date: Tue, 13 Aug 2024 09:30:22 +0300 [thread overview]
Message-ID: <Zrr9fobk-zahLpIO@black.fi.intel.com> (raw)
In-Reply-To: <ZroTN3UudwvIJ7oR@ashyti-mobl2.lan>
On Mon, Aug 12, 2024 at 03:50:47PM +0200, Andi Shyti wrote:
> Hi Raag,
>
> > +static int
> > +hwm_fan_read(struct hwm_drvdata *ddat, u32 attr, long *val)
> > +{
> > + struct i915_hwmon *hwmon = ddat->hwmon;
> > + struct hwm_fan_info *fi = &ddat->fi;
> > + u64 rotations, time_now, time;
> > + intel_wakeref_t wakeref;
> > + u32 reg_val, pulses;
> > + int ret = 0;
> > +
> > + if (attr != hwmon_fan_input)
> > + return -EOPNOTSUPP;
> > +
> > + wakeref = intel_runtime_pm_get(ddat->uncore->rpm);
> > + mutex_lock(&hwmon->hwmon_lock);
> > +
> > + reg_val = intel_uncore_read(ddat->uncore, hwmon->rg.fan_speed);
> > + time_now = get_jiffies_64();
> > +
> > + /* Handle HW register overflow */
> > + if (reg_val >= fi->reg_val_prev)
> > + pulses = reg_val - fi->reg_val_prev;
> > + else
> > + pulses = UINT_MAX - fi->reg_val_prev + reg_val;
> > +
> > + /*
> > + * HW register value is accumulated count of pulses from
> > + * PWM fan with the scale of 2 pulses per rotation.
> > + */
> > + rotations = pulses / 2;
> > +
> > + time = jiffies_delta_to_msecs(time_now - fi->time_prev);
> > + if (unlikely(!time)) {
> > + ret = -EAGAIN;
> > + goto exit;
> > + }
>
> Can you please add a comment describing how you obtain the speed
> calculation?
That's what I initially tried but ended up dropping it in favour of RPM
formula below, which I found to be doing a better job of explaining than
a few lines of description.
> Basically at every read you store the values. Is it possible that
> we don't have reads for a long time and the register resets more
> than once?
Considering a fan continuously running at higher speeds (for example 4000 RPM
which is quite optimistic), with the scale of 2 pulses per rotation, a 32 bit
register will take around a year to overflow, which is more than most usecases
I could think of.
Raag
> > + /*
> > + * Convert to minutes for calculating RPM.
> > + * RPM = number of rotations * msecs per minute / time in msecs
> > + */
> > + *val = DIV_ROUND_UP(rotations * (MSEC_PER_SEC * 60), time);
> > +
> > + fi->reg_val_prev = reg_val;
> > + fi->time_prev = time_now;
> > +exit:
> > + mutex_unlock(&hwmon->hwmon_lock);
> > + intel_runtime_pm_put(ddat->uncore->rpm, wakeref);
> > + return ret;
> > +}
next prev parent reply other threads:[~2024-08-13 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:15 [PATCH v5] drm/i915/hwmon: expose fan speed Raag Jadav
2024-08-12 13:15 ` Andy Shevchenko
2024-08-13 5:45 ` Raag Jadav
2024-08-13 8:27 ` Andy Shevchenko
2024-08-13 10:03 ` Raag Jadav
2024-08-12 13:50 ` Andi Shyti
2024-08-13 6:30 ` Raag Jadav [this message]
2024-08-21 14:58 ` Andi Shyti
2024-08-12 21:36 ` kernel test robot
2024-08-13 0:38 ` kernel test robot
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=Zrr9fobk-zahLpIO@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=airlied@gmail.com \
--cc=andi.shyti@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=badal.nilawar@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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