All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?
Date: Wed, 19 Feb 2014 02:55:00 +0000	[thread overview]
Message-ID: <53041D04.7000601@roeck-us.net> (raw)
In-Reply-To: <1392773023.4498.YahooMailNeo@web160503.mail.bf1.yahoo.com>

On 02/18/2014 06:27 PM, ianp wrote:
>> On Wednesday, February 19, 2014 10:00 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
Please don't drop the mailing liost from your replies.

>> That is not the same address, it is the same raw value.
>> The voltage registers are at address 0x20 .. 0x26 in above table.
>>
>
> Hmmm, I must have been looking at it the wrong way then. So if it's the raw value that is the same for both monitors, can I trust that the +5V and +12V values are accurate?
>
Ultimately you can only trust it to the point you trust the board vendor.
The chip reports what it gets on its input pins, but the board vendor
determines what is connected to those pins.

> Lastly, how can you separately show +5V and +12V in lm-sensors if both share a sinlge monitor on in4?
>

They don't. hwmonitor in Windows gives you the correct mapping for your board.

     Voltage 0    1.11 Volts [0x8B] (CPU VCORE)
     Voltage 1    0.69 Volts [0x56] (VIN1)
     Voltage 2    3.30 Volts [0xCE] (+3.3V)
     Voltage 3    4.97 Volts [0xCF] (+5V)
     Voltage 4    11.54 Volts [0xCF] (+12V)
     Voltage 5    1.69 Volts [0xD3] (VIN5)
     Voltage 6    1.90 Volts [0xED] (VIN6)

where Voltage X maps to inX.

Guenter


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

  parent reply	other threads:[~2014-02-19  2:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  1:23 [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4? ianp
2014-02-19  2:00 ` Guenter Roeck
2014-02-19  2:43 ` ianp
2014-02-19  2:55 ` Guenter Roeck [this message]
2014-02-19  3:18 ` ianp
2014-02-19  3:31 ` ianp
2014-02-19  4:11 ` Guenter Roeck
2014-02-19  4:21 ` Guenter Roeck
2014-02-19  5:38 ` ianp
2014-02-19  6:16 ` Guenter Roeck
2014-02-19  7:33 ` ianp
2014-02-19  8:53 ` Jean Delvare
2014-02-19 11:47 ` ianp
2014-02-19 12:02 ` ianp
2014-02-19 13:10 ` Jean Delvare
2014-02-19 13:52 ` ianp
2014-02-19 14:14 ` Jean Delvare
2014-02-19 14:23 ` Guenter Roeck
2014-02-19 15:05 ` ianp
2014-02-19 15:17 ` ianp
2014-02-19 16:35 ` Jean Delvare
2014-02-19 18:20 ` ianp
2014-03-09  9:38 ` 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=53041D04.7000601@roeck-us.net \
    --to=linux@roeck-us.net \
    --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.