public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: 宾西蒙 <binximeng@gmail.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
	Jim Cromie <jim.cromie@gmail.com>,
	H Hartley Sweeten <hsweeten@visionengravers.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ethan Lawrence <e.law87@yahoo.com>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
	lars4910@hotmail.com, birdie@permonline.ru, jadcock@cox.net
Subject: Re: [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver.
Date: Sat, 03 Jul 2010 12:15:48 +0200	[thread overview]
Message-ID: <1278152148.7319.11.camel@xli51> (raw)
In-Reply-To: <20100703103536.2fdd833e@hyperion.delvare>

在 2010-07-03六的 10:35 +0200,Jean Delvare写道:
> Hi Guenter,
> 
> On Fri, 2 Jul 2010 02:23:26 -0700, Guenter Roeck wrote:
> > +    w83667hg-i   9      5       3       3      0xb340 0xc1    0x5ca3
> 
> As discussed before, this one is a 677 series, not 667. That being
> said, I admit that the device ID proximity between the 667HG-B and the
> 677HG-I is troubling, and invites to optimism as far as compatibility
> between these two chips is concerned.

I think we got something confused here, I was looking for the W836
*seven* 7 HG-I driver (which has ID 0xb470) and not the W836 *six* 7
HG-I one, although maybe someone else might benefit from that one.

It has at least 5 fans, with 3 pwm and 1 voltage regulatory. Using the
w83667hg driver, I can only see the speed of fan2 and fan3 in sensors
output. the w83627dhg-p already seems to read out 3 of the 5 fan speeds.
The temperatures seem rather wonky, I might need to compare with the
bios readings some more.


  reply	other threads:[~2010-07-03 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02  9:23 [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver Guenter Roeck
2010-07-03  8:35 ` Jean Delvare
2010-07-03 10:15   ` 宾西蒙 [this message]
2010-07-03 20:56     ` Jean Delvare
2010-07-03 21:28       ` Guenter Roeck
2010-07-03 15:11   ` Guenter Roeck

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=1278152148.7319.11.camel@xli51 \
    --to=binximeng@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=birdie@permonline.ru \
    --cc=e.law87@yahoo.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=hsweeten@visionengravers.com \
    --cc=jadcock@cox.net \
    --cc=jim.cromie@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=lars4910@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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