From: Jean Delvare <jdelvare@suse.de>
To: Laszlo Papp <lpapp@kde.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
lm-sensors@lm-sensors.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: Tachometer speed returned rather than absolute fan speed?
Date: Fri, 7 Mar 2014 16:37:17 +0100 [thread overview]
Message-ID: <20140307163717.336873f5@endymion.delvare> (raw)
In-Reply-To: <CAOMwXhOB=1HA57jwKCx3-hU8A_ypjrm0J3R9huO25xa4B_gw8w@mail.gmail.com>
On Fri, 7 Mar 2014 15:31:44 +0000, Laszlo Papp wrote:
> On Fri, Mar 7, 2014 at 3:25 PM, Jean Delvare <jdelvare@suse.de> wrote:
> > Hi Laszlo,
> >
> > On Fri, 7 Mar 2014 14:48:01 +0000, Laszlo Papp wrote:
> >> In medias res, I find this interface cumbersome:
> >> http://lxr.free-electrons.com/source/Documentation/hwmon/max6650#L31
> >>
> >> It returns tachometer speed rather than actual fan speed when you deal
> >> with the fan1_target interface. That would be way more convenient for
> >> end users like me.
> >>
> >> Is there any reason for not returning absolute fan speed? I guess,
> >> this would break the behavior now. However, that would be a really
> >> useful convenient feature. Is it possible to add a new interface for
> >> that?
> >
> > I'm quite confused. While I admit that the term "tachometer speed" is
> > awkward, the max6650 driver is reporting fan speeds in RPM as every
> > other hwmon driver. So I really have no idea what you think is wrong.
> > What did you think "tachometer speed" was, if not the fan speed? Does
> > the max6650 driver not return correct fan speeds for you?
>
> I was just writing a patch to improve the documentation. Tachometer
> value is not equal to the fan speed, and using the terms together is
> confusing. It should probably read as follows:
>
> "absolute fan speed in RPM based on the corresponding tachometer
> value" or something similar. I just did not get the meaning of two
> different values together, and I think that confused me, especially
> since get_fan and get_target are doing slightly different
> computations, so it took me a while to figure this out from the
> datasheet.
>
> Better wording would have definitely helped in here. Fwiw, I asked
> another kernel hacker person who also got confused telling me that he
> would not know without reading the source code. I think that it is an
> indication to improve the documentation. There might be better
> alternatives than the one I am proposing, but at least that one clears
> up that for me.
I agree. I think I would just go with "measured fan speed in RPM", as
tachometer is quite a technical term and the user doesn't need to know.
Care to send a patch?
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2014-03-07 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 14:48 Laszlo Papp
2014-03-07 15:08 ` Laszlo Papp
2014-03-07 15:25 ` Jean Delvare
2014-03-07 15:31 ` Laszlo Papp
2014-03-07 15:37 ` Jean Delvare [this message]
2014-03-07 15:47 ` Laszlo Papp
2014-03-07 18:17 ` Guenter Roeck
2014-03-08 23:50 ` [lm-sensors] " Guenter Roeck
2014-03-09 6:36 ` Laszlo Papp
2014-03-09 8:04 ` Guenter Roeck
2014-03-09 12:44 ` Laszlo Papp
2014-03-10 9:59 ` Laszlo Papp
2014-03-10 13:26 ` Guenter Roeck
2014-03-10 13:50 ` Laszlo Papp
2014-03-10 15:11 ` Guenter Roeck
2014-03-10 18:00 ` Laszlo Papp
2014-04-08 9:19 ` Pavel Machek
2014-03-10 7:11 ` George Spelvin
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=20140307163717.336873f5@endymion.delvare \
--to=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=lpapp@kde.org \
/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
all inboxes | Powered by JetHome®