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] testing w83627hf treiber?
Date: Mon, 04 Dec 2006 08:06:02 +0000	[thread overview]
Message-ID: <20061204090602.07b8d41b.khali@linux-fr.org> (raw)

Hi Thomas,

(Huh, please don't use URLs as post subjects.)

On Sun, 03 Dec 2006 21:20:01 +0100, Thomas Dohl wrote:
> I've found a strange bug or what ever in the Module. :)
> I'll try to explain it.
> If I boot Linux with the module "w83627hf", everything
> is ok. But if I load the module with the workaround, like
> "modprobe w83627hf reset=1" I get a 23?C higher temperature
> of the second sensor.
> 
> At boottime:
> temp1: 34?C
> temp2: 33?C
> 
> after modprobe with reset=1
> temp1: 34?C
> temp2: 56?C (23?C more than it is)
> 
> This doesn't change after rmmod w83627hf, modprobe w83627hf.
> Only after reboot, the values return to normal.
> 
> What could that be?

Easy. The W83627*F chips have temperature offset registers. The BIOS
must write an offset for the temp2 (CPU?) temperature sensor, to
account for a different thermal diode model for example, or just to
make it look cooler to the user... When the w83627hf driver resets the
chip, the offset is reset to 0 as well, so you get the "raw" reading
again.

See, this is exactly the reason why we don't reset the chip by default:
to preserve BIOS settings.

-- 
Jean Delvare


             reply	other threads:[~2006-12-04  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04  8:06 Jean Delvare [this message]
2006-12-04  8:14 ` [lm-sensors] testing w83627hf treiber? Udo van den Heuvel
2006-12-04  8:16 ` Jean Delvare
2006-12-04 12:54 ` Jean Delvare
2006-12-04 17:28 ` Udo van den Heuvel

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=20061204090602.07b8d41b.khali@linux-fr.org \
    --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.