All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] RE: vt8231.c
Date: Tue, 15 Nov 2005 13:15:24 +0000	[thread overview]
Message-ID: <P5kp9Axl.1132056103.6789130.khali@localhost> (raw)
In-Reply-To: <20051102092453.47B1712E9E@bluewhale.planbit.co.uk>


Hi Roger,

On 2005-11-15, Roger Lucas wrote:
> We have another sample of the board here now, so we will be repeating the
> measurements to ensure that the VIA results are predictable from board to
> board.

OK, great. I've tried some mathematics on the formulae to find out if
anything obvious with regards to the physical meaning of the constants
would spring out, but did not find anything.

> I agree that whatever we do, the VIA users must apply some kind of
> equation to get their correct temperature, but I feel that the safest
> approach is "first do no wrong".

Fair enough.

> I am extremely uncomfortable with the situation where we release a
> driver that we know will give incorrect information under some
> conditions.  I feel that it is much better to return the result from
> the driver as a register value and put the text below:

The problem is that the standard sysfs interface sets some contraints on
what we can or cannot do. In particular, it dictates that the magnitude
for temperature values is 3. This suggests that the value we would be
returning would be REG * 1000. As it seems that there are an additional
2 bits of resolution, that would be (REG << 2 + ADDREG) * 250.

> # If you have an Intel CPU, then uncomment the line below
> # temp0_input = (@-65)/0.9686, (@*0.9686)+65
>
> # If you have an VIA EPIA CPU, then uncomment the line below
> # temp0_input = (@-45)/0.7809, (@*0.7809)+45

s/temp0_input =/compute temp1/, but yes.

BTW, does this suggest that you decided that the diode temperature would
be temp1, and thermistor-based ones are temp2+? I have no objection a
priori, just curious.

> This way, an incorrect value is never returned and the user must
> correctly set the board configuration before a temperature is
> returned.

By commenting out both compute lines, I'd rather say that an incorrect
value will *always* be returned. I'd prefer to keep the Intel line by
default so as to preserve backward compatibility as much as we can.

I think you will end up with a dedicated configuration file for your
board anyway. The best we can do to help out VIA EPIA users is to make
this file publicly available.

Thanks,
--
Jean Delvare

  parent reply	other threads:[~2005-11-15 13:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 10:25 [lm-sensors] RE: vt8231.c Roger Lucas
2005-11-02 14:24 ` Jean Delvare
2005-11-02 15:17 ` Roger Lucas
2005-11-02 19:47 ` Knut Petersen
2005-11-02 20:15 ` Roger Lucas
2005-11-02 20:26 ` Jean Delvare
2005-11-02 21:50 ` Grant Coady
2005-11-02 21:56 ` Jean Delvare
2005-11-03  0:28 ` Roger Lucas
2005-11-03  4:26 ` Mark M. Hoffman
2005-11-03  6:11 ` Grant Coady
2005-11-06 17:00 ` Jean Delvare
2005-11-06 20:22 ` Roger Lucas
2005-11-07 10:37 ` Jean Delvare
2005-11-07 20:56 ` Roger Lucas
2005-11-09 13:03 ` Jean Delvare
2005-11-09 15:43 ` Roger Lucas
2005-11-15  8:33 ` Jean Delvare
2005-11-15 12:14 ` Roger Lucas
2005-11-15 13:15 ` Jean Delvare [this message]
2005-11-15 13:46 ` Roger Lucas
2005-11-15 20:17 ` 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=P5kp9Axl.1132056103.6789130.khali@localhost \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.