All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Oliver Pinter <oliver.pntr@gmail.com>
Cc: LM Sensors <lm-sensors@lm-sensors.org>, linux-kernel@vger.kernel.org
Subject: Re: [lm-sensors] Bad value with w83627thf
Date: Fri, 16 May 2008 14:26:34 +0000	[thread overview]
Message-ID: <20080516162634.26207258@hyperion.delvare> (raw)
In-Reply-To: <6101e8c40805160645x5982d5ads61a422f5600f7507@mail.gmail.com>

Hi Oliver,

On Fri, 16 May 2008 15:45:01 +0200, Oliver Pinter wrote:
> the battery is CR2032, and it is 3V, im older kernel alway reported
> bad value 0,02V or 2,4V (i think it is a possible value), after i
> inserted new battery, show 2,4V.
> from the 2.6.26-rcX kernel showed the 3+ V. when i reboot to older
> kernel, the this state remained, but when turned off the pc, then not.

This can be easily explained. In kernel 2.6.25, we fixed a bug where
the w83627hf driver assumed that the BIOS had enabled VBat monitoring
[1]. With previous kernels, the VBat value would be wrong if the BIOS
did not actually enable VBat monitoring. Since kernel 2.6.25, the
w83627hf driver doesn't assume anything from the BIOS as far as VBat is
concerned, and enables monitoring if needed.

When you reboot your machine, the W83627THF device is not reset, so the
configuration steps done by the w83627hf driver of kernel 2.6.25+
remain. However, if you stop the machine then start it again, the
configuration is lost.

[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hï878b11ba245d14b7db7816217a825d6a894182

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: "Oliver Pinter" <oliver.pntr@gmail.com>
Cc: "LM Sensors" <lm-sensors@lm-sensors.org>, linux-kernel@vger.kernel.org
Subject: Re: Bad value with w83627thf
Date: Fri, 16 May 2008 16:26:34 +0200	[thread overview]
Message-ID: <20080516162634.26207258@hyperion.delvare> (raw)
In-Reply-To: <6101e8c40805160645x5982d5ads61a422f5600f7507@mail.gmail.com>

Hi Oliver,

On Fri, 16 May 2008 15:45:01 +0200, Oliver Pinter wrote:
> the battery is CR2032, and it is 3V, im older kernel alway reported
> bad value 0,02V or 2,4V (i think it is a possible value), after i
> inserted new battery, show 2,4V.
> from the 2.6.26-rcX kernel showed the 3+ V. when i reboot to older
> kernel, the this state remained, but when turned off the pc, then not.

This can be easily explained. In kernel 2.6.25, we fixed a bug where
the w83627hf driver assumed that the BIOS had enabled VBat monitoring
[1]. With previous kernels, the VBat value would be wrong if the BIOS
did not actually enable VBat monitoring. Since kernel 2.6.25, the
w83627hf driver doesn't assume anything from the BIOS as far as VBat is
concerned, and enables monitoring if needed.

When you reboot your machine, the W83627THF device is not reset, so the
configuration steps done by the w83627hf driver of kernel 2.6.25+
remain. However, if you stop the machine then start it again, the
configuration is lost.

[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ef878b11ba245d14b7db7816217a825d6a894182

-- 
Jean Delvare

  reply	other threads:[~2008-05-16 14:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 12:59 Bad value with w83627thf Oliver Pinter
2008-05-16 12:59 ` Oliver Pinter
2008-05-16 13:27 ` [lm-sensors] " Jean Delvare
2008-05-16 13:27   ` Jean Delvare
2008-05-16 13:45   ` [lm-sensors] " Oliver Pinter
2008-05-16 13:45     ` Oliver Pinter
2008-05-16 14:26     ` Jean Delvare [this message]
2008-05-16 14:26       ` Jean Delvare
2008-05-16 14:34       ` [lm-sensors] " Oliver Pinter
2008-05-16 14:34         ` Oliver Pinter

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=20080516162634.26207258@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=oliver.pntr@gmail.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 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.