public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: LM Sensors <sensors@stimpy.netroedge.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Dynamic fan clock divider changes (long)
Date: Thu, 20 May 2004 12:20:30 +0100	[thread overview]
Message-ID: <40AC947E.2050706@grupopie.com> (raw)
In-Reply-To: <20040516222809.2c3d1ea2.khali@linux-fr.org>

Jean Delvare wrote:
> The user still doesn't have to care, which is fine, but if the user has
> a fan speed between 2000 and 5000 RPM, with low limit set to 1500 RPM,
> he/she will have a "bad" accuracy at 5000 RPM (+/- 104 RPM). I see this
> as the low limit "nailing" the divider ;)

This doesn't sound so bad at all. And this seems to be the simplest approach.

> This is what I implemented in my new pc87360 driver (after trying #1). I
> use 85 and 224 as the arbitrary limits for changing dividers.

This confused me a bit. It seems that a direct consequence of implementation #2 
is that the divider will be set in a way that the low limit will be between 128 
and 255, and that there is no point in changing the divider, because it will 
only get worse. This leads directly to implementation #4. Am I missing something?

Anyway, if the user is really concerned about accuracy an average of several 
measurements should increase precision in this kind of problem. See the 
following ascii art:

clock:
     ___     ___     ___     ___     ___     ___     ___     ___
___|   |___|   |___|   |___|   |___|   |___|   |___|   |___|   |__

fan complete turn pulse:

____________________|_____________________|_____________________|

So the first measurement is 3 (assuming rising edge counting), but some of the 
period will slip into the second measurement giving a count of only 2, and so 
on. So the jitter on the counts is actually correlated with the fan speed.

Just my 2 cents,

-- 
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"

  parent reply	other threads:[~2004-05-20 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 20:28 [RFC] Dynamic fan clock divider changes (long) Jean Delvare
2004-05-16 21:36 ` Rutger Nijlunsing
2004-05-19 21:28   ` Jean Delvare
     [not found] ` <20040518021540.GB11012@earth.solarsys.private>
2004-05-20  9:03   ` Jean Delvare
2004-05-20 11:20 ` Paulo Marques [this message]
2004-05-22 14:46   ` Jean Delvare

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=40AC947E.2050706@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.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