[lm-sensors] Standalone driver for W83677HG-I, NCT6775F, NCT6776F

[lm-sensors] Standalone driver for W83677HG-I, NCT6775F, NCT6776F

[Guenter Roeck]

Hi,

a standalone driver for W83667HG-I (NCT6771F, NCT6775F) and NCT6776F
is available for testing at http://roeck-us.net/linux/drivers/w83627ehf/.

Please test and let me know if there are any problems.

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Sat, Feb 05, 2011 at 12:58:52PM -0500, Guenter Roeck wrote:
> Hi,
> 
> a standalone driver for W83667HG-I (NCT6771F, NCT6775F) and NCT6776F
> is available for testing at http://roeck-us.net/linux/drivers/w83627ehf/.
> 
> Please test and let me know if there are any problems.
> 
I should add that fan control and fan speed detection on DH57JG boards
doesn't work because Intel uses fan control provided by the PCH.

It should work on other boards, but obviously needs testing.

Guenter


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Sat, Feb 05, 2011 at 02:00:09PM -0500, Andrea Rizzolo wrote:
> hi,
> thank you very much, here on intel DH57JG it works. `sensors` output:
> 
> nct6775-isa-0680
> Adapter: ISA adapter
> in0:         +0.93 V  (min =  +0.00 V, max =  +1.74 V)
> in1:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in2:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in3:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in4:         +1.26 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in5:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in6:         +1.06 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in7:         +3.36 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in8:         +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> fan1:          0 RPM  (min =    0 RPM, div = 2)  ALARM
> fan2:          0 RPM  (min =    0 RPM, div = 2)  ALARM
> fan3:          0 RPM  (min =    0 RPM, div = 2)  ALARM
> fan4:          0 RPM  (div = 2)  ALARM
> temp1:       +31.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
> temp2:       +32.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
> temp3:       +23.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> cpu0_vid:   +2.050 V
> 
Hi Andrea,

excellent - that matches the output I get. Now all we have to do is to match the values
to actual voltages. in2 and in3 match the 3.3V seen in the BIOS, but for the others
I have no idea.

Thanks,
Guenter


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Guenter Roeck" <guenter.roeck@ericsson.com>
Sent: Saturday, February 05, 2011 8:15 PM
To: "Andrea Rizzolo" <andrea.rizzolo@gmail.com>
Cc: <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, 
NCT6775F,NCT6776F

> On Sat, Feb 05, 2011 at 02:00:09PM -0500, Andrea Rizzolo wrote:
>> hi,
>> thank you very much, here on intel DH57JG it works. `sensors` output:
>>
>> nct6775-isa-0680
>> Adapter: ISA adapter
>> in0:         +0.93 V  (min =  +0.00 V, max =  +1.74 V)
>> in1:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in2:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in3:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in4:         +1.26 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in5:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in6:         +1.06 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in7:         +3.36 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in8:         +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> fan1:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>> fan2:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>> fan3:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>> fan4:          0 RPM  (div = 2)  ALARM
>> temp1:       +31.0캜  (high =  +0.0캜, hyst =  +0.0캜)  ALARM  sensor = 
>> diode
>> temp2:       +32.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = diode
>> temp3:       +23.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = 
>> thermistor
>> cpu0_vid:   +2.050 V
>>
> Hi Andrea,
>
> excellent - that matches the output I get. Now all we have to do is to 
> match the values
> to actual voltages. in2 and in3 match the 3.3V seen in the BIOS, but for 
> the others
> I have no idea.
>
> Thanks,
> Guenter
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Hi,

Not bad, the results look almost the same as the standalone "hack" driver 
for the n6776 I'm working on, looks as if I can stop now. The only thing I'm 
seeing is that on fan headers where no fan is attached I'm seeing 164RPM.

The NCT6776F seems to use a 13-bit counter for the fans. The RPM formula is 
RPM = 1.35e6 / count. The value 1.35e6 value might come from a 22.5 kHz 
counter. Now if the counter reaches the maximum value, which is 8191 for a 
13-bit counter, we get exactly an RPM of 164.815041.

nct6776-isa-0290
Adapter: ISA adapter
in0:         +1.18 V  (min =  +0.95 V, max =  +1.26 V)
in1:         +1.02 V  (min =  +0.90 V, max =  +1.20 V)
in2:         +3.36 V  (min =  +3.01 V, max =  +3.50 V)
in3:         +3.34 V  (min =  +3.01 V, max =  +3.50 V)
in4:         +1.03 V  (min =  +1.00 V, max =  +1.10 V)
in5:         +2.04 V  (min =  +1.90 V, max =  +2.00 V)   ALARM
in6:         +0.80 V  (min =  +0.77 V, max =  +0.90 V)
in7:         +3.42 V  (min =  +3.01 V, max =  +3.50 V)
in8:         +3.30 V  (min =  +3.01 V, max =  +3.50 V)
fan1:        530 RPM  (min =    0 RPM)  ALARM
fan2:       1030 RPM  (min =    0 RPM)  ALARM
fan3:        164 RPM  (min =    0 RPM)  ALARM
fan4:        784 RPM  (min =    0 RPM)  ALARM
fan5:        164 RPM  (min =    0 RPM)  ALARM
temp1:       +23.0째C  (high = +35.0째C, hyst = +37.0째C)  sensor = 
thermistor
temp2:       -60.0째C  (high = +50.0째C, hyst = +55.0째C)  sensor = diode
temp3:       +37.0째C  (high = +50.0째C, hyst = +55.0째C)  sensor = 
thermistor
cpu0_vid:   +2.050 V


Regards
Ian Dobson 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

Hi Ian,
On Sat, Feb 05, 2011 at 04:46:22PM -0500, Ian Dobson wrote:
> 
[ ... ]
> 
> Not bad, the results look almost the same as the standalone "hack" driver 
> for the n6776 I'm working on, looks as if I can stop now. The only thing I'm 
> seeing is that on fan headers where no fan is attached I'm seeing 164RPM.
> 
Can you try again ? I updated the code to address the problem.

> The NCT6776F seems to use a 13-bit counter for the fans. The RPM formula is 
> RPM = 1.35e6 / count. The value 1.35e6 value might come from a 22.5 kHz 
> counter. Now if the counter reaches the maximum value, which is 8191 for a 
> 13-bit counter, we get exactly an RPM of 164.815041.
> 
> nct6776-isa-0290
> Adapter: ISA adapter
> in0:         +1.18 V  (min =  +0.95 V, max =  +1.26 V)
> in1:         +1.02 V  (min =  +0.90 V, max =  +1.20 V)
> in2:         +3.36 V  (min =  +3.01 V, max =  +3.50 V)
> in3:         +3.34 V  (min =  +3.01 V, max =  +3.50 V)
> in4:         +1.03 V  (min =  +1.00 V, max =  +1.10 V)
> in5:         +2.04 V  (min =  +1.90 V, max =  +2.00 V)   ALARM
> in6:         +0.80 V  (min =  +0.77 V, max =  +0.90 V)
> in7:         +3.42 V  (min =  +3.01 V, max =  +3.50 V)
> in8:         +3.30 V  (min =  +3.01 V, max =  +3.50 V)
> fan1:        530 RPM  (min =    0 RPM)  ALARM
> fan2:       1030 RPM  (min =    0 RPM)  ALARM
> fan3:        164 RPM  (min =    0 RPM)  ALARM
> fan4:        784 RPM  (min =    0 RPM)  ALARM
> fan5:        164 RPM  (min =    0 RPM)  ALARM
> temp1:       +23.0°C  (high = +35.0°C, hyst = +37.0°C)  sensor = 
> thermistor
> temp2:       -60.0°C  (high = +50.0°C, hyst = +55.0°C)  sensor = diode

This doesn't look good either. Can you report the raw values you get when reading
registers 0x150/0x151, 0x75/0x76, 0x152, and 0x200 ?

I have been wondering if I should retrieve the temperature values from 0x73/0x75/0x77.
This is another set of temperature registers supported by both chips and used as
fan monitoring source. 0x150 and 0x200 specify the temperature source for 0x151 and
0x75, respectively.

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Guenter Roeck" <guenter.roeck@ericsson.com>
Sent: Sunday, February 06, 2011 2:00 AM
To: "Ian Dobson" <i.dobson@planet-ian.com>
Cc: <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
NCT6776F

> Hi Ian,
> On Sat, Feb 05, 2011 at 04:46:22PM -0500, Ian Dobson wrote:
>>
> [ ... ]
>>
>> Not bad, the results look almost the same as the standalone "hack" driver
>> for the n6776 I'm working on, looks as if I can stop now. The only thing 
>> I'm
>> seeing is that on fan headers where no fan is attached I'm seeing 164RPM.
>>
> Can you try again ? I updated the code to address the problem.
>
>> The NCT6776F seems to use a 13-bit counter for the fans. The RPM formula 
>> is
>> RPM = 1.35e6 / count. The value 1.35e6 value might come from a 22.5 kHz
>> counter. Now if the counter reaches the maximum value, which is 8191 for 
>> a
>> 13-bit counter, we get exactly an RPM of 164.815041.
>>
>> nct6776-isa-0290
>> Adapter: ISA adapter
>> in0:         +1.18 V  (min =  +0.95 V, max =  +1.26 V)
>> in1:         +1.02 V  (min =  +0.90 V, max =  +1.20 V)
>> in2:         +3.36 V  (min =  +3.01 V, max =  +3.50 V)
>> in3:         +3.34 V  (min =  +3.01 V, max =  +3.50 V)
>> in4:         +1.03 V  (min =  +1.00 V, max =  +1.10 V)
>> in5:         +2.04 V  (min =  +1.90 V, max =  +2.00 V)   ALARM
>> in6:         +0.80 V  (min =  +0.77 V, max =  +0.90 V)
>> in7:         +3.42 V  (min =  +3.01 V, max =  +3.50 V)
>> in8:         +3.30 V  (min =  +3.01 V, max =  +3.50 V)
>> fan1:        530 RPM  (min =    0 RPM)  ALARM
>> fan2:       1030 RPM  (min =    0 RPM)  ALARM
>> fan3:        164 RPM  (min =    0 RPM)  ALARM
>> fan4:        784 RPM  (min =    0 RPM)  ALARM
>> fan5:        164 RPM  (min =    0 RPM)  ALARM
>> temp1:       +23.0°C  (high = +35.0°C, hyst = +37.0°C)  sensor >> thermistor
>> temp2:       -60.0°C  (high = +50.0°C, hyst = +55.0°C)  sensor = diode
>
> This doesn't look good either. Can you report the raw values you get when 
> reading
> registers 0x150/0x151, 0x75/0x76, 0x152, and 0x200 ?
>
> I have been wondering if I should retrieve the temperature values from 
> 0x73/0x75/0x77.
> This is another set of temperature registers supported by both chips and 
> used as
> fan monitoring source. 0x150 and 0x200 specify the temperature source for 
> 0x151 and
> 0x75, respectively.
>
> Thanks,
> Guenter

 0x150 = 0
 0x151 = 0
 0x075 = 31
 0x076 = 0
 0x152 = 0
 0x200 = c

I just added a simple
tmp=w83627ehf_read_value(data,0x150);
printk("0x150 = %0x\n",tmp);

to the drive to get the values

Regards
Ian Dobson
 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Jean Delvare]

On Sat, 5 Feb 2011 11:15:25 -0800, Guenter Roeck wrote:
> On Sat, Feb 05, 2011 at 02:00:09PM -0500, Andrea Rizzolo wrote:
> > hi,
> > thank you very much, here on intel DH57JG it works. `sensors` output:
> > 
> > nct6775-isa-0680
> > Adapter: ISA adapter
> > in0:         +0.93 V  (min =  +0.00 V, max =  +1.74 V)
> > in1:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in2:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in3:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in4:         +1.26 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in5:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in6:         +1.06 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in7:         +3.36 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in8:         +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > fan1:          0 RPM  (min =    0 RPM, div = 2)  ALARM
> > fan2:          0 RPM  (min =    0 RPM, div = 2)  ALARM
> > fan3:          0 RPM  (min =    0 RPM, div = 2)  ALARM
> > fan4:          0 RPM  (div = 2)  ALARM
> > temp1:       +31.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
> > temp2:       +32.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
> > temp3:       +23.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> > cpu0_vid:   +2.050 V
>
> Hi Andrea,
> 
> excellent - that matches the output I get. Now all we have to do is to match the values
> to actual voltages. in2 and in3 match the 3.3V seen in the BIOS, but for the others
> I have no idea.

As for the other chips in this family, in2, in3, in7 and in8 are
internal voltages so their mapping and scaling is fixed. The pin names
also strongly suggest connecting Vcore to in0, and I've never seen a
board manufacturer diverge from this. So you can start with the
following config statements:

chip "nct6775-*" "nct66776-*"

    label in0 "Vcore"
    label in2 "AVCC"
    label in3 "+3.3V"
    label in7 "3VSB"
    label in8 "Vbat"

    set in2_min  3.3 * 0.90
    set in2_max  3.3 * 1.10
    set in3_min  3.3 * 0.90
    set in3_max  3.3 * 1.10
    set in7_min  3.3 * 0.90
    set in7_max  3.3 * 1.10
    set in8_min  3.0 * 0.90
    set in8_max  3.0 * 1.10

This leaves only 4 voltage inputs to configure, presumably for +5V,
+12V, and possibly 5VSB and Vdimm. Check the labels and values in the
BIOS (write them all down if they fluctuate) and maybe we can figure it
out.

-- 
Jean Delvare

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Guenter Roeck" <guenter.roeck@ericsson.com>
Sent: Sunday, February 06, 2011 2:00 AM
To: "Ian Dobson" <i.dobson@planet-ian.com>
Cc: <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
NCT6776F

> Hi Ian,
> On Sat, Feb 05, 2011 at 04:46:22PM -0500, Ian Dobson wrote:
>>
> [ ... ]
>>
>> Not bad, the results look almost the same as the standalone "hack" driver
>> for the n6776 I'm working on, looks as if I can stop now. The only thing 
>> I'm
>> seeing is that on fan headers where no fan is attached I'm seeing 164RPM.
>>
> Can you try again ? I updated the code to address the problem.
>
>> The NCT6776F seems to use a 13-bit counter for the fans. The RPM formula 
>> is
>> RPM = 1.35e6 / count. The value 1.35e6 value might come from a 22.5 kHz
>> counter. Now if the counter reaches the maximum value, which is 8191 for 
>> a
>> 13-bit counter, we get exactly an RPM of 164.815041.
>>
>> nct6776-isa-0290
>> Adapter: ISA adapter
>> in0:         +1.18 V  (min =  +0.95 V, max =  +1.26 V)
>> in1:         +1.02 V  (min =  +0.90 V, max =  +1.20 V)
>> in2:         +3.36 V  (min =  +3.01 V, max =  +3.50 V)
>> in3:         +3.34 V  (min =  +3.01 V, max =  +3.50 V)
>> in4:         +1.03 V  (min =  +1.00 V, max =  +1.10 V)
>> in5:         +2.04 V  (min =  +1.90 V, max =  +2.00 V)   ALARM
>> in6:         +0.80 V  (min =  +0.77 V, max =  +0.90 V)
>> in7:         +3.42 V  (min =  +3.01 V, max =  +3.50 V)
>> in8:         +3.30 V  (min =  +3.01 V, max =  +3.50 V)
>> fan1:        530 RPM  (min =    0 RPM)  ALARM
>> fan2:       1030 RPM  (min =    0 RPM)  ALARM
>> fan3:        164 RPM  (min =    0 RPM)  ALARM
>> fan4:        784 RPM  (min =    0 RPM)  ALARM
>> fan5:        164 RPM  (min =    0 RPM)  ALARM
>> temp1:       +23.0°C  (high = +35.0°C, hyst = +37.0°C)  sensor >> thermistor
>> temp2:       -60.0°C  (high = +50.0°C, hyst = +55.0°C)  sensor = diode
>
> This doesn't look good either. Can you report the raw values you get when 
> reading
> registers 0x150/0x151, 0x75/0x76, 0x152, and 0x200 ?
>
> I have been wondering if I should retrieve the temperature values from 
> 0x73/0x75/0x77.
> This is another set of temperature registers supported by both chips and 
> used as
> fan monitoring source. 0x150 and 0x200 specify the temperature source for 
> 0x151 and
> 0x75, respectively.
>
> Thanks,
> Guenter

There's also something wrong with the fan alarm limits (w83627ehf.c file 
from 05-Feb-2011 18:48):-

SYSFANIN:    526 RPM  (min = 28125 RPM)  ALARM
CPUFANIN:    994 RPM  (min = 15340 RPM)  ALARM
AUXFANIN0:     0 RPM  (min = 12980 RPM)  ALARM
AUXFANIN1:   769 RPM  (min = 9642 RPM)
AUXFANIN2:     0 RPM  (min = 8035 RPM)  ALARM

The limits should be
label fan1 "SYSFANIN"
set fan1_min 400

label fan2 "CPUFANIN"
set fan2_min 600

label fan3 "AUXFANIN0"
set fan3_min 1000

label fan4 "AUXFANIN1"
set fan4_min 600

label fan5 "AUXFANIN2"
set fan5_min 1000

I'm also seeing this in the syslog

[127250.935448] w83627ehf: Found NCT6776 chip at 0x290
[127433.043365] w83627ehf w83627ehf.656: fan4 clock divider changed from 1 
to 16
[127433.043413] w83627ehf w83627ehf.656: fan5 clock divider changed from 1 
to 8
[127829.468663] w83627ehf: Found NCT6776 chip at 0x290
[127837.241797] w83627ehf w83627ehf.656: fan4 clock divider changed from 1 
to 16
[127837.241842] w83627ehf w83627ehf.656: fan5 clock divider changed from 1 
to 8

Regards
Ian Dobson


 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Jean Delvare]

On Sun, 6 Feb 2011 10:56:29 +0100, Jean Delvare wrote:
> As for the other chips in this family, in2, in3, in7 and in8 are
> internal voltages so their mapping and scaling is fixed. The pin names
> also strongly suggest connecting Vcore to in0, and I've never seen a
> board manufacturer diverge from this. So you can start with the
> following config statements:
> 
> chip "nct6775-*" "nct66776-*"

Err, typo here of course, I meant:

chip "nct6775-*" "nct6776-*"

Sorry.

> 
>     label in0 "Vcore"
>     label in2 "AVCC"
>     label in3 "+3.3V"
>     label in7 "3VSB"
>     label in8 "Vbat"
> 
>     set in2_min  3.3 * 0.90
>     set in2_max  3.3 * 1.10
>     set in3_min  3.3 * 0.90
>     set in3_max  3.3 * 1.10
>     set in7_min  3.3 * 0.90
>     set in7_max  3.3 * 1.10
>     set in8_min  3.0 * 0.90
>     set in8_max  3.0 * 1.10
> 
> This leaves only 4 voltage inputs to configure, presumably for +5V,
> +12V, and possibly 5VSB and Vdimm. Check the labels and values in the
> BIOS (write them all down if they fluctuate) and maybe we can figure it
> out.
> 


-- 
Jean Delvare

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Jean Delvare" <khali@linux-fr.org>
Sent: Sunday, February 06, 2011 11:00 AM
To: "Guenter Roeck" <guenter.roeck@ericsson.com>
Cc: "Andrea Rizzolo" <andrea.rizzolo@gmail.com>; <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
NCT6776F

> On Sun, 6 Feb 2011 10:56:29 +0100, Jean Delvare wrote:
>> As for the other chips in this family, in2, in3, in7 and in8 are
>> internal voltages so their mapping and scaling is fixed. The pin names
>> also strongly suggest connecting Vcore to in0, and I've never seen a
>> board manufacturer diverge from this. So you can start with the
>> following config statements:
>>
>> chip "nct6775-*" "nct66776-*"
>
> Err, typo here of course, I meant:
>
> chip "nct6775-*" "nct6776-*"
>
> Sorry.
>
>>
>>     label in0 "Vcore"
>>     label in2 "AVCC"
>>     label in3 "+3.3V"
>>     label in7 "3VSB"
>>     label in8 "Vbat"
>>
>>     set in2_min  3.3 * 0.90
>>     set in2_max  3.3 * 1.10
>>     set in3_min  3.3 * 0.90
>>     set in3_max  3.3 * 1.10
>>     set in7_min  3.3 * 0.90
>>     set in7_max  3.3 * 1.10
>>     set in8_min  3.0 * 0.90
>>     set in8_max  3.0 * 1.10
>>
>> This leaves only 4 voltage inputs to configure, presumably for +5V,
>> +12V, and possibly 5VSB and Vdimm. Check the labels and values in the
>> BIOS (write them all down if they fluctuate) and maybe we can figure it
>> out.
>>
>
>
> -- 
> Jean Delvare
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

OK, That might take some time, the box is currently transcoding/processing a 
large job and I don't really want to stop it and restart it.

Regards
Ian Dobson
 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Jean Delvare" <khali@linux-fr.org>
Sent: Sunday, February 06, 2011 11:00 AM
To: "Guenter Roeck" <guenter.roeck@ericsson.com>
Cc: "Andrea Rizzolo" <andrea.rizzolo@gmail.com>; <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
NCT6776F

> On Sun, 6 Feb 2011 10:56:29 +0100, Jean Delvare wrote:
>> As for the other chips in this family, in2, in3, in7 and in8 are
>> internal voltages so their mapping and scaling is fixed. The pin names
>> also strongly suggest connecting Vcore to in0, and I've never seen a
>> board manufacturer diverge from this. So you can start with the
>> following config statements:
>>
>> chip "nct6775-*" "nct66776-*"
>
> Err, typo here of course, I meant:
>
> chip "nct6775-*" "nct6776-*"
>
> Sorry.
>
>>
>>     label in0 "Vcore"
>>     label in2 "AVCC"
>>     label in3 "+3.3V"
>>     label in7 "3VSB"
>>     label in8 "Vbat"
>>
>>     set in2_min  3.3 * 0.90
>>     set in2_max  3.3 * 1.10
>>     set in3_min  3.3 * 0.90
>>     set in3_max  3.3 * 1.10
>>     set in7_min  3.3 * 0.90
>>     set in7_max  3.3 * 1.10
>>     set in8_min  3.0 * 0.90
>>     set in8_max  3.0 * 1.10
>>
>> This leaves only 4 voltage inputs to configure, presumably for +5V,
>> +12V, and possibly 5VSB and Vdimm. Check the labels and values in the
>> BIOS (write them all down if they fluctuate) and maybe we can figure it
>> out.
>>
>
>
> -- 
> Jean Delvare
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

OK looking in the specs on the w83627ehf bank0 3b-3f are the minimum fan 
speeds, on the n6776f they're not defined.

There appears to be a dual usage register "CPUFAN MODE Register / CPUFAN 
TOLERRANCE Register - Index 02h (Bank 2)" and the actual limit is readable 
in (CPUFANIN) Fan Count Limit High-byte Register - Index 3Ch (Bank 6), but 
that's read only. Maybe it's better if we handle the fan lo limit within the 
driver rather than through the chip.

Regards
Ian Dobson
 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Jean Delvare" <khali@linux-fr.org>
Sent: Sunday, February 06, 2011 10:56 AM
To: "Guenter Roeck" <guenter.roeck@ericsson.com>
Cc: "Andrea Rizzolo" <andrea.rizzolo@gmail.com>; <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
NCT6776F

> On Sat, 5 Feb 2011 11:15:25 -0800, Guenter Roeck wrote:
>> On Sat, Feb 05, 2011 at 02:00:09PM -0500, Andrea Rizzolo wrote:
>> > hi,
>> > thank you very much, here on intel DH57JG it works. `sensors` output:
>> >
>> > nct6775-isa-0680
>> > Adapter: ISA adapter
>> > in0:         +0.93 V  (min =  +0.00 V, max =  +1.74 V)
>> > in1:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > in2:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > in3:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > in4:         +1.26 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > in5:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > in6:         +1.06 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > in7:         +3.36 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > in8:         +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> > fan1:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>> > fan2:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>> > fan3:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>> > fan4:          0 RPM  (div = 2)  ALARM
>> > temp1:       +31.0캜  (high =  +0.0캜, hyst =  +0.0캜)  ALARM  sensor = 
>> > diode
>> > temp2:       +32.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = diode
>> > temp3:       +23.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = 
>> > thermistor
>> > cpu0_vid:   +2.050 V
>>
>> Hi Andrea,
>>
>> excellent - that matches the output I get. Now all we have to do is to 
>> match the values
>> to actual voltages. in2 and in3 match the 3.3V seen in the BIOS, but for 
>> the others
>> I have no idea.
>
> As for the other chips in this family, in2, in3, in7 and in8 are
> internal voltages so their mapping and scaling is fixed. The pin names
> also strongly suggest connecting Vcore to in0, and I've never seen a
> board manufacturer diverge from this. So you can start with the
> following config statements:
>
> chip "nct6775-*" "nct66776-*"
>
>    label in0 "Vcore"
>    label in2 "AVCC"
>    label in3 "+3.3V"
>    label in7 "3VSB"
>    label in8 "Vbat"
>
>    set in2_min  3.3 * 0.90
>    set in2_max  3.3 * 1.10
>    set in3_min  3.3 * 0.90
>    set in3_max  3.3 * 1.10
>    set in7_min  3.3 * 0.90
>    set in7_max  3.3 * 1.10
>    set in8_min  3.0 * 0.90
>    set in8_max  3.0 * 1.10
>
> This leaves only 4 voltage inputs to configure, presumably for +5V,
> +12V, and possibly 5VSB and Vdimm. Check the labels and values in the
> BIOS (write them all down if they fluctuate) and maybe we can figure it
> out.
>
> -- 
> Jean Delvare
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

OK Here's the infomation
nct6776-isa-0290
Adapter: ISA adapter
Vcore:       +1.18 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
AVCC:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:       +3.34 V  (min =  +2.98 V, max =  +3.63 V)
in4:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in5:         +2.04 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in6:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
3VSB:        +3.42 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:        +3.30 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
fan1:        550 RPM  (min =    0 RPM)  ALARM
fan2:       1013 RPM  (min =    0 RPM)  ALARM
fan3:          0 RPM  (min =    0 RPM)  ALARM
fan4:        824 RPM  (min =    0 RPM)  ALARM
fan5:          0 RPM  (min =    0 RPM)  ALARM
temp1:       +24.0째C  (high =  +0.0째C, hyst =  +0.0째C)  ALARM  sensor = 
thermistor
temp2:       -60.0째C  (high = +80.0째C, hyst = +75.0째C)  sensor = diode
temp3:       +38.0째C  (high = +80.0째C, hyst = +75.0째C)  sensor = 
thermistor
cpu0_vid:   +2.050 V

and BIOS
CPU temp 43
MB temp 25

CPU Volt 1.114-1.1176
3.3Volt     3.36 - 3.34
5Volt     5.160
12Volt  12.288

So it looks as if in4 * 5 is 5Volt, in5 * 6 is 12volt. This is on a asus 
p8p67 pro, but I've seen the same values on a asus p8p67 delux.

Looking in the n6776f specification if looks as if AUXTIN(temp3) and in6 
share the same pin (pin 109) so we can't have both enabled.

Regards
Ian Dobson
 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Ian Dobson" <i.dobson@planet-ian.com>
Sent: Sunday, February 06, 2011 2:37 PM
To: <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, 
NCT6775F,NCT6776F voltage input multipliers

>
>
> --------------------------------------------------
> From: "Jean Delvare" <khali@linux-fr.org>
> Sent: Sunday, February 06, 2011 10:56 AM
> To: "Guenter Roeck" <guenter.roeck@ericsson.com>
> Cc: "Andrea Rizzolo" <andrea.rizzolo@gmail.com>; 
> <lm-sensors@lm-sensors.org>
> Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
> NCT6776F
>
>> On Sat, 5 Feb 2011 11:15:25 -0800, Guenter Roeck wrote:
>>> On Sat, Feb 05, 2011 at 02:00:09PM -0500, Andrea Rizzolo wrote:
>>> > hi,
>>> > thank you very much, here on intel DH57JG it works. `sensors` output:
>>> >
>>> > nct6775-isa-0680
>>> > Adapter: ISA adapter
>>> > in0:         +0.93 V  (min =  +0.00 V, max =  +1.74 V)
>>> > in1:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > in2:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > in3:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > in4:         +1.26 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > in5:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > in6:         +1.06 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > in7:         +3.36 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > in8:         +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>> > fan1:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>>> > fan2:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>>> > fan3:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>>> > fan4:          0 RPM  (div = 2)  ALARM
>>> > temp1:       +31.0캜  (high =  +0.0캜, hyst =  +0.0캜)  ALARM  sensor 
>>> > = diode
>>> > temp2:       +32.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = diode
>>> > temp3:       +23.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = 
>>> > thermistor
>>> > cpu0_vid:   +2.050 V
>>>
>>> Hi Andrea,
>>>
>>> excellent - that matches the output I get. Now all we have to do is to 
>>> match the values
>>> to actual voltages. in2 and in3 match the 3.3V seen in the BIOS, but for 
>>> the others
>>> I have no idea.
>>
>> As for the other chips in this family, in2, in3, in7 and in8 are
>> internal voltages so their mapping and scaling is fixed. The pin names
>> also strongly suggest connecting Vcore to in0, and I've never seen a
>> board manufacturer diverge from this. So you can start with the
>> following config statements:
>>
>> chip "nct6775-*" "nct66776-*"
>>
>>    label in0 "Vcore"
>>    label in2 "AVCC"
>>    label in3 "+3.3V"
>>    label in7 "3VSB"
>>    label in8 "Vbat"
>>
>>    set in2_min  3.3 * 0.90
>>    set in2_max  3.3 * 1.10
>>    set in3_min  3.3 * 0.90
>>    set in3_max  3.3 * 1.10
>>    set in7_min  3.3 * 0.90
>>    set in7_max  3.3 * 1.10
>>    set in8_min  3.0 * 0.90
>>    set in8_max  3.0 * 1.10
>>
>> This leaves only 4 voltage inputs to configure, presumably for +5V,
>> +12V, and possibly 5VSB and Vdimm. Check the labels and values in the
>> BIOS (write them all down if they fluctuate) and maybe we can figure it
>> out.
>>
>> -- 
>> Jean Delvare
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors@lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
> OK Here's the infomation
> nct6776-isa-0290
> Adapter: ISA adapter
> Vcore:       +1.18 V  (min =  +0.00 V, max =  +1.74 V)
> in1:         +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> AVCC:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:       +3.34 V  (min =  +2.98 V, max =  +3.63 V)
> in4:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in5:         +2.04 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in6:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 3VSB:        +3.42 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:        +3.30 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
> fan1:        550 RPM  (min =    0 RPM)  ALARM
> fan2:       1013 RPM  (min =    0 RPM)  ALARM
> fan3:          0 RPM  (min =    0 RPM)  ALARM
> fan4:        824 RPM  (min =    0 RPM)  ALARM
> fan5:          0 RPM  (min =    0 RPM)  ALARM
> temp1:       +24.0째C  (high =  +0.0째C, hyst =  +0.0째C)  ALARM  sensor = 
> thermistor
> temp2:       -60.0째C  (high = +80.0째C, hyst = +75.0째C)  sensor = diode
> temp3:       +38.0째C  (high = +80.0째C, hyst = +75.0째C)  sensor = 
> thermistor
> cpu0_vid:   +2.050 V
>
> and BIOS
> CPU temp 43
> MB temp 25
>
> CPU Volt 1.114-1.1176
> 3.3Volt     3.36 - 3.34
> 5Volt     5.160
> 12Volt  12.288
>
> So it looks as if in4 * 5 is 5Volt, in5 * 6 is 12volt. This is on a asus 
> p8p67 pro, but I've seen the same values on a asus p8p67 delux.
>
> Looking in the n6776f specification if looks as if AUXTIN(temp3) and in6 
> share the same pin (pin 109) so we can't have both enabled.
>
> Regards
> Ian Dobson
>
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

also pwm output won't work, Bank 0 index 1 is the actual value used for the 
pwm output, while the setpoint for the pwm value is in Bank1,index09 
bit[7:0] (this is only used in manual mode)

so in the code we could do something like
static const u8 N677X_REG_PWM_ACTUAL[] = { 0x01, 0x03, 0x11 };
static const u16 N677X_REG_PWM_SETPOINT[] = { 0x109, 0x209, 0x309 };

in update_device we always read from _ACTUAL, and in store_pwm if the chip 
is a n677x write to _SETPOINT.

If you want I can try and write a patch.

Regards
Ian Dobson
 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Ian Dobson" <i.dobson@planet-ian.com>
Sent: Sunday, February 06, 2011 2:55 PM
To: <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, 
NCT6775F,NCT6776F pwm output

> --------------------------------------------------
> From: "Ian Dobson" <i.dobson@planet-ian.com>
> Sent: Sunday, February 06, 2011 2:37 PM
> To: <lm-sensors@lm-sensors.org>
> Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, 
> NCT6775F,NCT6776F voltage input multipliers
>
>>
>>
>> --------------------------------------------------
>> From: "Jean Delvare" <khali@linux-fr.org>
>> Sent: Sunday, February 06, 2011 10:56 AM
>> To: "Guenter Roeck" <guenter.roeck@ericsson.com>
>> Cc: "Andrea Rizzolo" <andrea.rizzolo@gmail.com>; 
>> <lm-sensors@lm-sensors.org>
>> Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
>> NCT6776F
>>
>>> On Sat, 5 Feb 2011 11:15:25 -0800, Guenter Roeck wrote:
>>>> On Sat, Feb 05, 2011 at 02:00:09PM -0500, Andrea Rizzolo wrote:
>>>> > hi,
>>>> > thank you very much, here on intel DH57JG it works. `sensors` output:
>>>> >
>>>> > nct6775-isa-0680
>>>> > Adapter: ISA adapter
>>>> > in0:         +0.93 V  (min =  +0.00 V, max =  +1.74 V)
>>>> > in1:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > in2:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > in3:         +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > in4:         +1.26 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > in5:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > in6:         +1.06 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > in7:         +3.36 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > in8:         +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>>> > fan1:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>>>> > fan2:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>>>> > fan3:          0 RPM  (min =    0 RPM, div = 2)  ALARM
>>>> > fan4:          0 RPM  (div = 2)  ALARM
>>>> > temp1:       +31.0캜  (high =  +0.0캜, hyst =  +0.0캜)  ALARM  sensor 
>>>> > = diode
>>>> > temp2:       +32.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = 
>>>> > diode
>>>> > temp3:       +23.0캜  (high = +80.0캜, hyst = +75.0캜)  sensor = 
>>>> > thermistor
>>>> > cpu0_vid:   +2.050 V
>>>>
>>>> Hi Andrea,
>>>>
>>>> excellent - that matches the output I get. Now all we have to do is to 
>>>> match the values
>>>> to actual voltages. in2 and in3 match the 3.3V seen in the BIOS, but 
>>>> for the others
>>>> I have no idea.
>>>
>>> As for the other chips in this family, in2, in3, in7 and in8 are
>>> internal voltages so their mapping and scaling is fixed. The pin names
>>> also strongly suggest connecting Vcore to in0, and I've never seen a
>>> board manufacturer diverge from this. So you can start with the
>>> following config statements:
>>>
>>> chip "nct6775-*" "nct66776-*"
>>>
>>>    label in0 "Vcore"
>>>    label in2 "AVCC"
>>>    label in3 "+3.3V"
>>>    label in7 "3VSB"
>>>    label in8 "Vbat"
>>>
>>>    set in2_min  3.3 * 0.90
>>>    set in2_max  3.3 * 1.10
>>>    set in3_min  3.3 * 0.90
>>>    set in3_max  3.3 * 1.10
>>>    set in7_min  3.3 * 0.90
>>>    set in7_max  3.3 * 1.10
>>>    set in8_min  3.0 * 0.90
>>>    set in8_max  3.0 * 1.10
>>>
>>> This leaves only 4 voltage inputs to configure, presumably for +5V,
>>> +12V, and possibly 5VSB and Vdimm. Check the labels and values in the
>>> BIOS (write them all down if they fluctuate) and maybe we can figure it
>>> out.
>>>
>>> -- 
>>> Jean Delvare
>>>
>>> _______________________________________________
>>> lm-sensors mailing list
>>> lm-sensors@lm-sensors.org
>>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>
>> OK Here's the infomation
>> nct6776-isa-0290
>> Adapter: ISA adapter
>> Vcore:       +1.18 V  (min =  +0.00 V, max =  +1.74 V)
>> in1:         +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> AVCC:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
>> +3.3V:       +3.34 V  (min =  +2.98 V, max =  +3.63 V)
>> in4:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in5:         +2.04 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in6:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> 3VSB:        +3.42 V  (min =  +2.98 V, max =  +3.63 V)
>> Vbat:        +3.30 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
>> fan1:        550 RPM  (min =    0 RPM)  ALARM
>> fan2:       1013 RPM  (min =    0 RPM)  ALARM
>> fan3:          0 RPM  (min =    0 RPM)  ALARM
>> fan4:        824 RPM  (min =    0 RPM)  ALARM
>> fan5:          0 RPM  (min =    0 RPM)  ALARM
>> temp1:       +24.0째C  (high =  +0.0째C, hyst =  +0.0째C)  ALARM  sensor 
>> = thermistor
>> temp2:       -60.0째C  (high = +80.0째C, hyst = +75.0째C)  sensor = diode
>> temp3:       +38.0째C  (high = +80.0째C, hyst = +75.0째C)  sensor = 
>> thermistor
>> cpu0_vid:   +2.050 V
>>
>> and BIOS
>> CPU temp 43
>> MB temp 25
>>
>> CPU Volt 1.114-1.1176
>> 3.3Volt     3.36 - 3.34
>> 5Volt     5.160
>> 12Volt  12.288
>>
>> So it looks as if in4 * 5 is 5Volt, in5 * 6 is 12volt. This is on a asus 
>> p8p67 pro, but I've seen the same values on a asus p8p67 delux.
>>
>> Looking in the n6776f specification if looks as if AUXTIN(temp3) and in6 
>> share the same pin (pin 109) so we can't have both enabled.
>>
>> Regards
>> Ian Dobson
>>
>>
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors@lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
> also pwm output won't work, Bank 0 index 1 is the actual value used for 
> the pwm output, while the setpoint for the pwm value is in Bank1,index09 
> bit[7:0] (this is only used in manual mode)
>
> so in the code we could do something like
> static const u8 N677X_REG_PWM_ACTUAL[] = { 0x01, 0x03, 0x11 };
> static const u16 N677X_REG_PWM_SETPOINT[] = { 0x109, 0x209, 0x309 };
>
> in update_device we always read from _ACTUAL, and in store_pwm if the chip 
> is a n677x write to _SETPOINT.
>
> If you want I can try and write a patch.
>
> Regards
> Ian Dobson
>
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Sorry my mistake, you've already split the reading/writing of the pwm 
(NCT6775_REG_PWM)

Regards
Ian Dobson
 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Jean Delvare]

On Sun, 6 Feb 2011 14:37:48 +0100, Ian Dobson wrote:
> OK Here's the infomation
> nct6776-isa-0290
> Adapter: ISA adapter
> Vcore:       +1.18 V  (min =  +0.00 V, max =  +1.74 V)
> in1:         +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> AVCC:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:       +3.34 V  (min =  +2.98 V, max =  +3.63 V)
> in4:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in5:         +2.04 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in6:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 3VSB:        +3.42 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:        +3.30 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
> fan1:        550 RPM  (min =    0 RPM)  ALARM
> fan2:       1013 RPM  (min =    0 RPM)  ALARM
> fan3:          0 RPM  (min =    0 RPM)  ALARM
> fan4:        824 RPM  (min =    0 RPM)  ALARM
> fan5:          0 RPM  (min =    0 RPM)  ALARM
> temp1:       +24.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
> thermistor
> temp2:       -60.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
> temp3:       +38.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
> thermistor
> cpu0_vid:   +2.050 V
> 
> and BIOS
> CPU temp 43
> MB temp 25
> 
> CPU Volt 1.114-1.1176
> 3.3Volt     3.36 - 3.34
> 5Volt     5.160
> 12Volt  12.288
> 
> So it looks as if in4 * 5 is 5Volt, in5 * 6 is 12volt. This is on a asus 
> p8p67 pro, but I've seen the same values on a asus p8p67 delux.

in4 * 5 = 5V is possible, in5 * 6 = 12V is not. 2.04 is the saturation
value for the ADC so it looks like in5 isn't used on your system. I'd
rather think that in1 * 12 = 12V.

> Looking in the n6776f specification if looks as if AUXTIN(temp3) and in6 
> share the same pin (pin 109) so we can't have both enabled.

This was the case on the W83667HG already, so I'm not surprised, and it
should be very easy to implement in the driver.

-- 
Jean Delvare

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Jean Delvare" <khali@linux-fr.org>
Sent: Sunday, February 06, 2011 4:53 PM
To: "Ian Dobson" <i.dobson@planet-ian.com>
Cc: <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
NCT6776F voltage input multipliers

> On Sun, 6 Feb 2011 14:37:48 +0100, Ian Dobson wrote:
>> OK Here's the infomation
>> nct6776-isa-0290
>> Adapter: ISA adapter
>> Vcore:       +1.18 V  (min =  +0.00 V, max =  +1.74 V)
>> in1:         +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> AVCC:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
>> +3.3V:       +3.34 V  (min =  +2.98 V, max =  +3.63 V)
>> in4:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in5:         +2.04 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> in6:         +0.78 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>> 3VSB:        +3.42 V  (min =  +2.98 V, max =  +3.63 V)
>> Vbat:        +3.30 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
>> fan1:        550 RPM  (min =    0 RPM)  ALARM
>> fan2:       1013 RPM  (min =    0 RPM)  ALARM
>> fan3:          0 RPM  (min =    0 RPM)  ALARM
>> fan4:        824 RPM  (min =    0 RPM)  ALARM
>> fan5:          0 RPM  (min =    0 RPM)  ALARM
>> temp1:       +24.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor 
>> >> thermistor
>> temp2:       -60.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
>> temp3:       +38.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor >> thermistor
>> cpu0_vid:   +2.050 V
>>
>> and BIOS
>> CPU temp 43
>> MB temp 25
>>
>> CPU Volt 1.114-1.1176
>> 3.3Volt     3.36 - 3.34
>> 5Volt     5.160
>> 12Volt  12.288
>>
>> So it looks as if in4 * 5 is 5Volt, in5 * 6 is 12volt. This is on a asus
>> p8p67 pro, but I've seen the same values on a asus p8p67 delux.
>
> in4 * 5 = 5V is possible, in5 * 6 = 12V is not. 2.04 is the saturation
> value for the ADC so it looks like in5 isn't used on your system. I'd
> rather think that in1 * 12 = 12V.
>
>> Looking in the n6776f specification if looks as if AUXTIN(temp3) and in6
>> share the same pin (pin 109) so we can't have both enabled.
>
> This was the case on the W83667HG already, so I'm not surprised, and it
> should be very easy to implement in the driver.
>
> -- 
> Jean Delvare

Yep, your right, here's the config I'm now using and the output

chip "nct6775-*" "nct6776-*"
# nct6776 values for Asus p8p67 pro
    label temp1 "Motherboard"
    ignore temp2
    label temp3 "CPU"

    label in0 "Vcore"
    set in0_min  1.1 * 0.85
    set in0_max  1.1 * 1.20

    label in1 "+12V"
    compute in1 @ * 12, @ / 12
    set in1_min  12 * 0.90
    set in1_max  12 * 1.15

    label in2 "AVCC"
    set in2_min  3.3 * 0.90
    set in2_max  3.3 * 1.10

    label in3 "+3.3V"
    set in3_min  3.3 * 0.90
    set in3_max  3.3 * 1.10

    label in4 "+5V"
    compute in4 @ * 5, @ / 5
    set in4_min  5 * 0.90
    set in4_max  5 * 1.10

    ignore in6

    label in7 "3VSB"
    set in7_min  3.3 * 0.90
    set in7_min  3.3 * 0.90
    set in7_max  3.3 * 1.10

    label in8 "Vbat"
    set in8_min  3.0 * 0.90
    set in8_max  3.0 * 1.15

nct6776-isa-0290
Adapter: ISA adapter
Vcore:       +1.18 V  (min =  +0.94 V, max =  +1.32 V)
+12V:       +12.29 V  (min = +10.85 V, max = +13.82 V)
AVCC:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:       +3.34 V  (min =  +2.98 V, max =  +3.63 V)
+5V:         +5.16 V  (min =  +4.52 V, max =  +5.52 V)
in5:         +2.04 V  (min =  +1.80 V, max =  +2.04 V)   ALARM
3VSB:        +3.42 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:        +3.30 V  (min =  +2.70 V, max =  +3.46 V)
fan1:        526 RPM  (min =    0 RPM)  ALARM
fan2:        995 RPM  (min =    0 RPM)  ALARM
fan3:          0 RPM  (min =    0 RPM)  ALARM
fan4:        773 RPM  (min =    0 RPM)  ALARM
fan5:          0 RPM  (min =    0 RPM)  ALARM
Motherboard: +23.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
thermistor
CPU:         +37.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
thermistor
cpu0_vid:   +2.050 V

Note 5V and 12V correspond to bios within 0.01volt

Regards
Ian Dobson
 


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Sun, Feb 06, 2011 at 06:59:40AM -0500, Ian Dobson wrote:
> 
> 
> --------------------------------------------------
> From: "Jean Delvare" <khali@linux-fr.org>
> Sent: Sunday, February 06, 2011 11:00 AM
> To: "Guenter Roeck" <guenter.roeck@ericsson.com>
> Cc: "Andrea Rizzolo" <andrea.rizzolo@gmail.com>; <lm-sensors@lm-sensors.org>
> Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, 
> NCT6776F
> 
> > On Sun, 6 Feb 2011 10:56:29 +0100, Jean Delvare wrote:
> >> As for the other chips in this family, in2, in3, in7 and in8 are
> >> internal voltages so their mapping and scaling is fixed. The pin names
> >> also strongly suggest connecting Vcore to in0, and I've never seen a
> >> board manufacturer diverge from this. So you can start with the
> >> following config statements:
> >>
> >> chip "nct6775-*" "nct66776-*"
> >
> > Err, typo here of course, I meant:
> >
> > chip "nct6775-*" "nct6776-*"
> >
> > Sorry.
> >
> >>
> >>     label in0 "Vcore"
> >>     label in2 "AVCC"
> >>     label in3 "+3.3V"
> >>     label in7 "3VSB"
> >>     label in8 "Vbat"
> >>
> >>     set in2_min  3.3 * 0.90
> >>     set in2_max  3.3 * 1.10
> >>     set in3_min  3.3 * 0.90
> >>     set in3_max  3.3 * 1.10
> >>     set in7_min  3.3 * 0.90
> >>     set in7_max  3.3 * 1.10
> >>     set in8_min  3.0 * 0.90
> >>     set in8_max  3.0 * 1.10
> >>
> >> This leaves only 4 voltage inputs to configure, presumably for +5V,
> >> +12V, and possibly 5VSB and Vdimm. Check the labels and values in the
> >> BIOS (write them all down if they fluctuate) and maybe we can figure it
> >> out.
> >>
> >
> >
> > -- 
> > Jean Delvare
> >
> > _______________________________________________
> > lm-sensors mailing list
> > lm-sensors@lm-sensors.org
> > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> 
> OK looking in the specs on the w83627ehf bank0 3b-3f are the minimum fan 
> speeds, on the n6776f they're not defined.
> 
> There appears to be a dual usage register "CPUFAN MODE Register / CPUFAN 
> TOLERRANCE Register - Index 02h (Bank 2)" and the actual limit is readable 

I should have that one already, and read it with nct6775_update_pwm().

> in (CPUFANIN) Fan Count Limit High-byte Register - Index 3Ch (Bank 6), but 
> that's read only. Maybe it's better if we handle the fan lo limit within the 
> driver rather than through the chip.
> 
Wonder if that is really read-only.

There are also registers 0x105/0x205/0x305, "Stop Value Register".
Naming is odd, but the description seems to be what we are looking for,
at least for thermal cruise mode.
There is also the "Start-up value register", which is the fan's start speed
in thermal cruise mode.

Thanks,
Guenter 

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

Hi Ian,
On Sun, Feb 06, 2011 at 04:36:10AM -0500, Ian Dobson wrote:
[ ... ]
> >> temp2:       -60.0°C  (high = +50.0°C, hyst = +55.0°C)  sensor = diode
> >
> > This doesn't look good either. Can you report the raw values you get when 
> > reading
> > registers 0x150/0x151, 0x75/0x76, 0x152, and 0x200 ?
> >
> > I have been wondering if I should retrieve the temperature values from 
> > 0x73/0x75/0x77.
> > This is another set of temperature registers supported by both chips and 
> > used as
> > fan monitoring source. 0x150 and 0x200 specify the temperature source for 
> > 0x151 and
> > 0x75, respectively.
> >
> > Thanks,
> > Guenter
> 
>  0x150 = 0
>  0x151 = 0
>  0x075 = 31
>  0x076 = 0
>  0x152 = 0
>  0x200 = c
> 
Looks like they are using PECI agent 0 as monitoring source. Odd, though, that 0x150 
reads zero but reports -60 degrees C. Is that fluctuating ?

Also, can you dump registers 0x100, 0x200, 0x300, and 0x621 to 0x626 ? Those registers
define the mapping from temperature sources to registers (0x152 was wrong; should have said 0x622).

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Sun, Feb 06, 2011 at 08:37:48AM -0500, Ian Dobson wrote:
[ ... ]
> 
> Looking in the n6776f specification if looks as if AUXTIN(temp3) and in6 
> share the same pin (pin 109) so we can't have both enabled.
> 
So they got rid of that for the nct6775f and w83667-b but reintroduced it
for nct6776f. Oh well. Would have been too simple otherwise.

Added complexity is that the sources for all temperature registers are now
selectable, but the status registers are still hardcoded.
Going to be fun to sort that out. Looks like I'll have to think about that 
a bit more.

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Andy Lutomirski]

On 02/05/2011 12:58 PM, Guenter Roeck wrote:
> Hi,
>
> a standalone driver for W83667HG-I (NCT6771F, NCT6775F) and NCT6776F
> is available for testing at http://roeck-us.net/linux/drivers/w83627ehf/.
>
> Please test and let me know if there are any problems.

It appears to mostly work on an Intel DH67GD (nct6775).  There are two 
issues:

1. The first time I ran 'sensors', my CPU fan showed 0 RPM instead of 
the correct value (~134).  Running it again shows the correct value.

2. PWM control doesn't seem to have any effect.  (The BIOS PWM control
settings definitely work.)

Thanks,
Andy

>
> Thanks,
> Guenter
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Sun, Feb 06, 2011 at 10:50:02PM -0500, Andy Lutomirski wrote:
> On 02/05/2011 12:58 PM, Guenter Roeck wrote:
> > Hi,
> >
> > a standalone driver for W83667HG-I (NCT6771F, NCT6775F) and NCT6776F
> > is available for testing at http://roeck-us.net/linux/drivers/w83627ehf/.
> >
> > Please test and let me know if there are any problems.
> 
> It appears to mostly work on an Intel DH67GD (nct6775).  There are two 
> issues:
> 
> 1. The first time I ran 'sensors', my CPU fan showed 0 RPM instead of 
> the correct value (~134).  Running it again shows the correct value.
> 
If you check the log, you might see a notice that the fan divisors were modified.
Can you check ?

> 2. PWM control doesn't seem to have any effect.  (The BIOS PWM control
> settings definitely work.)
> 
Ok, I'll look into it.

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Jean Delvare]

On Sun, 6 Feb 2011 20:50:05 -0800, Guenter Roeck wrote:
> On Sun, Feb 06, 2011 at 10:50:02PM -0500, Andy Lutomirski wrote:
> > On 02/05/2011 12:58 PM, Guenter Roeck wrote:
> > > Hi,
> > >
> > > a standalone driver for W83667HG-I (NCT6771F, NCT6775F) and NCT6776F
> > > is available for testing at http://roeck-us.net/linux/drivers/w83627ehf/.
> > >
> > > Please test and let me know if there are any problems.
> > 
> > It appears to mostly work on an Intel DH67GD (nct6775).  There are two 
> > issues:
> > 
> > 1. The first time I ran 'sensors', my CPU fan showed 0 RPM instead of 
> > the correct value (~134).  Running it again shows the correct value.
> > 
> If you check the log, you might see a notice that the fan divisors were modified.
> Can you check ?

Note: if you set a proper fan_min value in your configuration file,
"sensors -s" will set the right divisor directly so the first "sensors" will
work.

-- 
Jean Delvare

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Jean Delvare]

On Sun, 6 Feb 2011 20:50:05 -0800, Guenter Roeck wrote:
> On Sun, Feb 06, 2011 at 10:50:02PM -0500, Andy Lutomirski wrote:
> > 2. PWM control doesn't seem to have any effect.  (The BIOS PWM control
> > settings definitely work.)
>
> Ok, I'll look into it.

I had already noticed that the W83667HG was more complex than the
previous chips in this respect, and had even started writing a patch to
address the problem (which was never tested and is maybe not even
finished, I can't remember.) I don't know if the W83677HG-I is similar
in this respect, or even worse. Here is what I had back then (June
2009!) if it is of any interest to you:

---
 drivers/hwmon/w83627ehf.c |   87 ++++++++++++++++++++++++++++++++++++++-------
 1 file changed, 74 insertions(+), 13 deletions(-)

--- linux-2.6.31-rc1.orig/drivers/hwmon/w83627ehf.c	2009-06-25 09:32:17.000000000 +0200
+++ linux-2.6.31-rc1/drivers/hwmon/w83627ehf.c	2009-06-25 15:22:18.000000000 +0200
@@ -198,6 +198,10 @@ static const u8 W83627EHF_REG_TOLERANCE[
 static const u8 W83627EHF_REG_FAN_MIN_OUTPUT[] = { 0x08, 0x09, 0x15, 0x64 };
 static const u8 W83627EHF_REG_FAN_STOP_TIME[] = { 0x0C, 0x0D, 0x17, 0x66 };
 
+/* W83667HG-specific fan controller routing */
+#define W83667HG_REG_FANCTRL2_SEL	0x62
+#define W83667HG_REG_FANCTRL4_SEL	0x7C
+
 /*
  * Conversions
  */
@@ -296,7 +300,7 @@ struct w83627ehf_data {
 	u8 pwm_mode[4]; /* 0->DC variable voltage, 1->PWM variable duty cycle */
 	u8 pwm_enable[4]; /* 1->manual
 			     2->thermal cruise (also called SmartFan I) */
-	u8 pwm_num;		/* number of pwm */
+	u8 has_pwm;		/* some fan contollers can be unused */
 	u8 pwm[4];
 	u8 target_temp[4];
 	u8 tolerance[4];
@@ -514,13 +518,14 @@ static struct w83627ehf_data *w83627ehf_
 		}
 
 		for (i = 0; i < 4; i++) {
-			/* pwmcfg, tolerance mapped for i=0, i=1 to same reg */
-			if (i != 1) {
-				pwmcfg = w83627ehf_read_value(data,
+			if (!(data->has_pwm & BIT(i)))
+				continue;
+
+			pwmcfg = w83627ehf_read_value(data,
 						W83627EHF_REG_PWM_ENABLE[i]);
-				tolerance = w83627ehf_read_value(data,
+			tolerance = w83627ehf_read_value(data,
 						W83627EHF_REG_TOLERANCE[i]);
-			}
+
 			data->pwm_mode[i]  				((pwmcfg >> W83627EHF_PWM_MODE_SHIFT[i]) & 1)
 				? 0 : 1;
@@ -1217,7 +1222,7 @@ static void w83627ehf_device_remove_file
 		device_remove_file(dev, &sda_fan_div[i].dev_attr);
 		device_remove_file(dev, &sda_fan_min[i].dev_attr);
 	}
-	for (i = 0; i < data->pwm_num; i++) {
+	for (i = 0; i < 4; i++) {
 		device_remove_file(dev, &sda_pwm[i].dev_attr);
 		device_remove_file(dev, &sda_pwm_mode[i].dev_attr);
 		device_remove_file(dev, &sda_pwm_enable[i].dev_attr);
@@ -1308,8 +1313,60 @@ static int __devinit w83627ehf_probe(str
 
 	/* 627EHG and 627EHF have 10 voltage inputs; 627DHG and 667HG have 9 */
 	data->in_num = (sio_data->kind = w83627ehf) ? 10 : 9;
-	/* 667HG has 3 pwms */
-	data->pwm_num = (sio_data->kind = w83667hg) ? 3 : 4;
+
+	/*
+	 * The W83667HG has 4 fan speed controllers for 3 fan control output
+	 * pins. Controllers can be routed to pins in many different ways.
+	 * Depending on the configuration, a given controller can control
+	 * more than one fan, or no fan at all (in which case we don't
+	 * expose it.)
+	 *
+	 * To make things even more complex, the first 3 fan controllers are
+	 * compatible with the ones in older chips, but the 4th one is not.
+	 * We do not support the 4th controller on the 667HG yet.
+	 */
+	if (sio_data->kind = w83667hg) {
+		u8 fc2_sel, fc4_sel;
+		fc2_sel = w83627ehf_read_value(data, W83667HG_REG_FANCTRL2_SEL);
+		fc4_sel = w83627ehf_read_value(data, W83667HG_REG_FANCTRL4_SEL);
+
+		if (fc4_sel & BIT(4)) {
+			dev_info(dev, "%s is controlled by pwm%d "
+				 "(unsupported)\n", "SYSFANOUT", 4);
+		} else if (fc2_sel & BIT(4)) {
+			data->has_pwm |= BIT(1);
+			dev_info(dev, "%s is controlled by pwm%d\n",
+				 "SYSFANOUT", 2);
+		} else {
+			data->has_pwm |= BIT(0);
+			dev_info(dev, "%s is controlled by pwm%d\n",
+				 "SYSFANOUT", 1);
+		}
+
+		if (fc4_sel & BIT(5)) {
+			dev_info(dev, "%s is controlled by pwm%d "
+				 "(unsupported)\n", "CPUFANOUT", 4);
+		} else {
+			data->has_pwm |= BIT(1);
+			dev_info(dev, "%s is controlled by pwm%d\n",
+				 "CPUFANOUT", 2);
+		}
+
+		if (fc4_sel & BIT(6)) {
+			dev_info(dev, "%s is controlled by pwm%d "
+				 "(unsupported)\n", "AUXFANOUT", 4);
+		} else if (fc2_sel & BIT(5)) {
+			data->has_pwm |= BIT(1);
+			dev_info(dev, "%s is controlled by pwm%d\n",
+				 "AUXFANOUT", 2);
+		} else {
+			data->has_pwm |= BIT(2);
+			dev_info(dev, "%s is controlled by pwm%d\n",
+				 "AUXFANOUT", 3);
+		}
+	} else {
+		data->has_pwm = 0x0f;	/* pwm1 to pwm4 */
+	}
 
 	/* Check temp3 configuration bit for 667HG */
 	if (sio_data->kind = w83667hg) {
@@ -1407,7 +1464,7 @@ static int __devinit w83627ehf_probe(str
 			goto exit_remove;
 
 	/* if fan4 is enabled create the sf3 files for it */
-	if ((data->has_fan & (1 << 3)) && data->pwm_num >= 4)
+	if ((data->has_fan & BIT(3)) && (data->has_pwm & BIT(3)))
 		for (i = 0; i < ARRAY_SIZE(sda_sf3_arrays_fan4); i++) {
 			if ((err = device_create_file(dev,
 				&sda_sf3_arrays_fan4[i].dev_attr)))
@@ -1438,8 +1495,12 @@ static int __devinit w83627ehf_probe(str
 				|| (err = device_create_file(dev,
 					&sda_fan_min[i].dev_attr)))
 				goto exit_remove;
-			if (i < data->pwm_num &&
-				((err = device_create_file(dev,
+		}
+	}
+
+	for (i = 0; i < 4; i++) {
+		if (data->has_pwm & BIT(i)) {
+			if ((err = device_create_file(dev,
 					&sda_pwm[i].dev_attr))
 				|| (err = device_create_file(dev,
 					&sda_pwm_mode[i].dev_attr))
@@ -1448,7 +1509,7 @@ static int __devinit w83627ehf_probe(str
 				|| (err = device_create_file(dev,
 					&sda_target_temp[i].dev_attr))
 				|| (err = device_create_file(dev,
-					&sda_tolerance[i].dev_attr))))
+					&sda_tolerance[i].dev_attr)))
 				goto exit_remove;
 		}
 	}


-- 
Jean Delvare

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Andrew Lutomirski]

On Mon, Feb 7, 2011 at 2:33 AM, Jean Delvare <khali@linux-fr.org> wrote:
> On Sun, 6 Feb 2011 20:50:05 -0800, Guenter Roeck wrote:
>> On Sun, Feb 06, 2011 at 10:50:02PM -0500, Andy Lutomirski wrote:
>> > On 02/05/2011 12:58 PM, Guenter Roeck wrote:
>> > > Hi,
>> > >
>> > > a standalone driver for W83667HG-I (NCT6771F, NCT6775F) and NCT6776F
>> > > is available for testing at http://roeck-us.net/linux/drivers/w83627ehf/.
>> > >
>> > > Please test and let me know if there are any problems.
>> >
>> > It appears to mostly work on an Intel DH67GD (nct6775).  There are two
>> > issues:
>> >
>> > 1. The first time I ran 'sensors', my CPU fan showed 0 RPM instead of
>> > the correct value (~134).  Running it again shows the correct value.
>> >
>> If you check the log, you might see a notice that the fan divisors were modified.
>> Can you check ?

Yes, I got a message.  dmesg shows:

[51676.259546] w83627ehf: Found NCT6775 chip at 0x290
[51678.246682] w83627ehf w83627ehf.656: Increasing fan2 clock divider
from 32 to 64

The second line happens on the first call to 'sensors'.  Rebooting
triggers it again, but rmmod/insmod does not.

Should the driver just fix up the divisors on load instead of on first read?

I'm happy to test patches (especially for fan control) on my board.

--Andy

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Mon, Feb 07, 2011 at 02:40:00AM -0500, Jean Delvare wrote:
> On Sun, 6 Feb 2011 20:50:05 -0800, Guenter Roeck wrote:
> > On Sun, Feb 06, 2011 at 10:50:02PM -0500, Andy Lutomirski wrote:
> > > 2. PWM control doesn't seem to have any effect.  (The BIOS PWM control
> > > settings definitely work.)
> >
> > Ok, I'll look into it.
> 
> I had already noticed that the W83667HG was more complex than the
> previous chips in this respect, and had even started writing a patch to
> address the problem (which was never tested and is maybe not even
> finished, I can't remember.) I don't know if the W83677HG-I is similar
> in this respect, or even worse. Here is what I had back then (June
> 2009!) if it is of any interest to you:
> 
> ---
>  drivers/hwmon/w83627ehf.c |   87 ++++++++++++++++++++++++++++++++++++++-------
>  1 file changed, 74 insertions(+), 13 deletions(-)
> 
> --- linux-2.6.31-rc1.orig/drivers/hwmon/w83627ehf.c	2009-06-25 09:32:17.000000000 +0200
> +++ linux-2.6.31-rc1/drivers/hwmon/w83627ehf.c	2009-06-25 15:22:18.000000000 +0200
> @@ -198,6 +198,10 @@ static const u8 W83627EHF_REG_TOLERANCE[
>  static const u8 W83627EHF_REG_FAN_MIN_OUTPUT[] = { 0x08, 0x09, 0x15, 0x64 };
>  static const u8 W83627EHF_REG_FAN_STOP_TIME[] = { 0x0C, 0x0D, 0x17, 0x66 };
>  
> +/* W83667HG-specific fan controller routing */
> +#define W83667HG_REG_FANCTRL2_SEL	0x62
> +#define W83667HG_REG_FANCTRL4_SEL	0x7C
> +
Unfortunately, both registers are no longer defined in nct665/nct6776.

Thanks,
Guenter


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Mon, Feb 07, 2011 at 08:56:29AM -0500, Andrew Lutomirski wrote:
> On Mon, Feb 7, 2011 at 2:33 AM, Jean Delvare <khali@linux-fr.org> wrote:
> > On Sun, 6 Feb 2011 20:50:05 -0800, Guenter Roeck wrote:
> >> On Sun, Feb 06, 2011 at 10:50:02PM -0500, Andy Lutomirski wrote:
> >> > On 02/05/2011 12:58 PM, Guenter Roeck wrote:
> >> > > Hi,
> >> > >
> >> > > a standalone driver for W83667HG-I (NCT6771F, NCT6775F) and NCT6776F
> >> > > is available for testing at http://roeck-us.net/linux/drivers/w83627ehf/.
> >> > >
> >> > > Please test and let me know if there are any problems.
> >> >
> >> > It appears to mostly work on an Intel DH67GD (nct6775).  There are two
> >> > issues:
> >> >
> >> > 1. The first time I ran 'sensors', my CPU fan showed 0 RPM instead of
> >> > the correct value (~134).  Running it again shows the correct value.
> >> >
> >> If you check the log, you might see a notice that the fan divisors were modified.
> >> Can you check ?
> 
> Yes, I got a message.  dmesg shows:
> 
> [51676.259546] w83627ehf: Found NCT6775 chip at 0x290
> [51678.246682] w83627ehf w83627ehf.656: Increasing fan2 clock divider
> from 32 to 64
> 
> The second line happens on the first call to 'sensors'.  Rebooting
> triggers it again, but rmmod/insmod does not.
> 
That is as expected. The driver loads the sensor value, detects that it is out of range,
and automatically adjusts the divisor register.

Usually, in other drivers, it is possible to write into the divisor register.
This can then be used to initialize the divisor to a reasonable value at startup.
For some reason that is not implemented for this driver; I don't know why.

> Should the driver just fix up the divisors on load instead of on first read?
> 
No, the divisor should be writable so you can initialize it at startup. 
I'll see if I can fix that.

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Mon, Feb 07, 2011 at 09:47:22AM -0500, Guenter Roeck wrote:
[ ... ] 
> > 
> > The second line happens on the first call to 'sensors'.  Rebooting
> > triggers it again, but rmmod/insmod does not.
> > 
> That is as expected. The driver loads the sensor value, detects that it is out of range,
> and automatically adjusts the divisor register.
> 
> Usually, in other drivers, it is possible to write into the divisor register.
> This can then be used to initialize the divisor to a reasonable value at startup.
> For some reason that is not implemented for this driver; I don't know why.
> 
> > Should the driver just fix up the divisors on load instead of on first read?
> > 
> No, the divisor should be writable so you can initialize it at startup. 
> I'll see if I can fix that.
> 
Ok, I know the reason. The divider is set automatically when the minimum speed is configured.
This is because both the current speed and the minimum speed are affected by the divider
settings, and the divider value has to work for both.

So what you'll have to do is to set a minimum speed, and the problem will go away.

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Sun, Feb 06, 2011 at 08:37:48AM -0500, Ian Dobson wrote:
[ ... ]
> 
> Looking in the n6776f specification if looks as if AUXTIN(temp3) and in6 
> share the same pin (pin 109) so we can't have both enabled.
> 
Unless I am missing something, there does not seem to be a register to select AUXTIN
vs. VIN3. Only way to detect if pin109 is used for AUXTIN or VIN3 seems to be to check
if AUXTIN is selected as any of the temperature sources, and disable VIN3 (in6)
if it is.

Do you see a better way ?

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Andrew Lutomirski]

On Mon, Feb 7, 2011 at 9:57 AM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> On Mon, Feb 07, 2011 at 09:47:22AM -0500, Guenter Roeck wrote:
> [ ... ]
>> >
>> > The second line happens on the first call to 'sensors'.  Rebooting
>> > triggers it again, but rmmod/insmod does not.
>> >
>> That is as expected. The driver loads the sensor value, detects that it is out of range,
>> and automatically adjusts the divisor register.
>>
>> Usually, in other drivers, it is possible to write into the divisor register.
>> This can then be used to initialize the divisor to a reasonable value at startup.
>> For some reason that is not implemented for this driver; I don't know why.
>>
>> > Should the driver just fix up the divisors on load instead of on first read?
>> >
>> No, the divisor should be writable so you can initialize it at startup.
>> I'll see if I can fix that.
>>
> Ok, I know the reason. The divider is set automatically when the minimum speed is configured.
> This is because both the current speed and the minimum speed are affected by the divider
> settings, and the divider value has to work for both.
>
> So what you'll have to do is to set a minimum speed, and the problem will go away.

I admit I'm a bit confused as to what fan2_min does.  I have a minimum
(to warn?) fan speed set in BIOS, which seems to have nothing to do
with the initial value of fan2_min.  Changing fan2_min will cause
fan2_alarm to become set or unset, when I decrease min below input,
alarm stays set until I read it once.

This is rather curious -- it means that the sequence:
echo 200 >fan2_min
echo 100 >fan2_min
cat fan2_input
cat fan2_alarm

shows alarm=0 but

echo 200 >fan2_min
echo 100 >fan2_min
cat fan2_alarm
cat fan2_input

shows alarm=1

In any case, what does alarm (and, hence, min) do?  Userspace can
compare two numbers on its own, but no uevent seems to be generated
when an alarm is hit.

--Andy

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

Hi Andrew,

On Mon, Feb 07, 2011 at 11:50:48AM -0500, Andrew Lutomirski wrote:
[ ... ]
> >
> > So what you'll have to do is to set a minimum speed, and the problem will go away.
> 
> I admit I'm a bit confused as to what fan2_min does.  I have a minimum
> (to warn?) fan speed set in BIOS, which seems to have nothing to do
> with the initial value of fan2_min.  Changing fan2_min will cause
> fan2_alarm to become set or unset, when I decrease min below input,
> alarm stays set until I read it once.
> 
Interesting; it means that it works, but the BIOS seems to use another set
of registers to set the minimum speed.

> This is rather curious -- it means that the sequence:
> echo 200 >fan2_min
> echo 100 >fan2_min
> cat fan2_input
> cat fan2_alarm
> 
> shows alarm=0 but
> 
> echo 200 >fan2_min
> echo 100 >fan2_min
> cat fan2_alarm
> cat fan2_input
> 
> shows alarm=1
> 
> In any case, what does alarm (and, hence, min) do?  Userspace can
> compare two numbers on its own, but no uevent seems to be generated
> when an alarm is hit.
> 

The driver simply reports what it gets from the real-time status monitoring
registers.

It might make sense to improve the code to report interrupt status bits instead,
and even better to actually handle interrupts and report status changes via udev.
But that goes a bit beyond of adding support for a couple of new chips ...

Linking of alarm status changes with udev events has only just recently been
considered, and is currently only supported for GPIO fans. For the most part,
hwmon depends on polling to detect alarm conditions. This is defintely something
to be considered as an improvement to the hwmon subsystem.

Thanks,
Guenter

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

[lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

Hi all,

I published a new version of the standalone driver for W83667HG-I (NCT6771F, NCT6775F)
and NCT6776F at http://roeck-us.net/linux/drivers/w83627ehf/.

Key changes are listed in the README file. Most of the reported bugs have been fixed,
though I am not sure about PWM configuration on NCT6775F and fan min limits on NCT6776F.

For PWM configuration on NCT6775F, I did not find a problem. I can set and read PWM values,
but since my board does not connect the chip to actual fans I have no idea if the settings
have any effect. So this will need to be re-tested on a board which actually uses the chip 
for fan control.

For the fan min limits on NCT6776F, the code still uses the set of registers starting at
0x63a. The prototype driver we got from Nuvoton does set those registers, so presumably
it should work unless that driver has a bug. Worth to re-test, especially since
I fixed a problem in the speed setting code. 

Please test the new code and let me know if there are any problems. And thanks a lot 
to all the feedback I got for the first revision of the code.

Guenter


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Andrew Lutomirski]

On Mon, Feb 7, 2011 at 12:58 PM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> Hi all,
>
> I published a new version of the standalone driver for W83667HG-I (NCT6771F, NCT6775F)
> and NCT6776F at http://roeck-us.net/linux/drivers/w83627ehf/.
>
> Key changes are listed in the README file. Most of the reported bugs have been fixed,
> though I am not sure about PWM configuration on NCT6775F and fan min limits on NCT6776F.
>

I don't see a README.  What's w83627ehf.c.18?

> For PWM configuration on NCT6775F, I did not find a problem
. I can set and read PWM values,
> but since my board does not connect the chip to actual fans I have no idea if the settings
> have any effect. So this will need to be re-tested on a board which actually uses the chip
> for fan control.

Something's weird.

# cat pwm2_enable
5
# cat pwm2_mode
1
# echo 1 >pwm2_enable
# cat pwm2_enable
5
# echo 1 >pwm2_enable
# cat pwm2_enable
5
# echo 2 >pwm2_enable
# cat pwm2_enable
6

[fiddle with pwm2 here.  values written stick but have no effect.]

# echo 3 >pwm2_enable
[root@midnight w83627ehf.656]# cat pwm2_enable
8
[root@midnight w83627ehf.656]# echo 1 >pwm2_enable
[root@midnight w83627ehf.656]# cat pwm2_enable
8

Note: I won't swear that my motherboard uses this particular chip to
drive the PWMs, but I assume it does since it can certainly measure
fan speed w/ this chip and it controls the PWMs somehow.

>
> For the fan min limits on NCT6776F, the code still uses the set of registers starting at
> 0x63a. The prototype driver we got from Nuvoton does set those registers, so presumably
> it should work unless that driver has a bug. Worth to re-test, especially since
> I fixed a problem in the speed setting code.

Alarm code still seems to work.

--Andy

>
> Please test the new code and let me know if there are any problems. And thanks a lot
> to all the feedback I got for the first revision of the code.
>
> Guenter
>
>

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Mon, Feb 07, 2011 at 01:20:22PM -0500, Andrew Lutomirski wrote:
> On Mon, Feb 7, 2011 at 12:58 PM, Guenter Roeck
> <guenter.roeck@ericsson.com> wrote:
> > Hi all,
> >
> > I published a new version of the standalone driver for W83667HG-I (NCT6771F, NCT6775F)
> > and NCT6776F at http://roeck-us.net/linux/drivers/w83627ehf/.
> >
> > Key changes are listed in the README file. Most of the reported bugs have been fixed,
> > though I am not sure about PWM configuration on NCT6775F and fan min limits on NCT6776F.
> >
> 
> I don't see a README.  What's w83627ehf.c.18?
> 
Sorry, it is there now. w83627ehf.c.18 is a port of rev1 to 2.6.18.

> > For PWM configuration on NCT6775F, I did not find a problem
> . I can set and read PWM values,
> > but since my board does not connect the chip to actual fans I have no idea if the settings
> > have any effect. So this will need to be re-tested on a board which actually uses the chip
> > for fan control.
> 
> Something's weird.
> 
> # cat pwm2_enable
> 5

5 means it is running in SmartFan IV mode.

> # cat pwm2_mode
> 1
> # echo 1 >pwm2_enable
> # cat pwm2_enable
> 5
> # echo 1 >pwm2_enable
> # cat pwm2_enable
> 5
> # echo 2 >pwm2_enable
> # cat pwm2_enable
> 6
> 
That was a bug. 

> [fiddle with pwm2 here.  values written stick but have no effect.]
> 
> # echo 3 >pwm2_enable
> [root@midnight w83627ehf.656]# cat pwm2_enable
> 8
> [root@midnight w83627ehf.656]# echo 1 >pwm2_enable
> [root@midnight w83627ehf.656]# cat pwm2_enable
> 8
> 
> Note: I won't swear that my motherboard uses this particular chip to
> drive the PWMs, but I assume it does since it can certainly measure
> fan speed w/ this chip and it controls the PWMs somehow.
> 
It uses it per Intel specifications.

Anyway, please try again. I updated the code to fix the pwmX_enable bug.

Thanks,
Guenter

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Andrew Lutomirski]

On Mon, Feb 7, 2011 at 1:48 PM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> On Mon, Feb 07, 2011 at 01:20:22PM -0500, Andrew Lutomirski wrote:
>> On Mon, Feb 7, 2011 at 12:58 PM, Guenter Roeck
>> <guenter.roeck@ericsson.com> wrote:
>> > Hi all,
>> >
>> > I published a new version of the standalone driver for W83667HG-I (NCT6771F, NCT6775F)
>> > and NCT6776F at http://roeck-us.net/linux/drivers/w83627ehf/.
>> >
>> > Key changes are listed in the README file. Most of the reported bugs have been fixed,
>> > though I am not sure about PWM configuration on NCT6775F and fan min limits on NCT6776F.
>> >
>>
>> I don't see a README.  What's w83627ehf.c.18?
>>
> Sorry, it is there now. w83627ehf.c.18 is a port of rev1 to 2.6.18.

Thanks!  FWIW, it's invisible in the directory listing, though.

>
> Anyway, please try again. I updated the code to fix the pwmX_enable bug.

Mostly works.

If I set pwm2_enable to 1, then pwm2 controls the fan.

If I try to set pwm2_enable to 5, I get:

# echo 5 >pwm2_enable
bash: echo: write error: Invalid argument

which means I can't undo what I just did.  (If I patch the driver to
accept '5', then it works.)

Are there docs (e.g. a patch to Documentation/hwmon/w83627ehf, but an
email explanation would do) for how SmartFan works, or, more
generally, for how to program the various modes?  If you have a link
to a datasheet, I can try to write something.

In BIOS, I have settings related to target temperatures, minimum pwm
output, etc.

Thanks for working on this driver!  I'd be happy to add my Tested-by:
if you submit it upstream.

--Andy

>
> Thanks,
> Guenter
>

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

Hi Andrew,

On Mon, 2011-02-07 at 14:53 -0500, Andrew Lutomirski wrote:
[ ... ]
> >
> > Anyway, please try again. I updated the code to fix the pwmX_enable bug.
> 
> Mostly works.
> 
> If I set pwm2_enable to 1, then pwm2 controls the fan.
> 
> If I try to set pwm2_enable to 5, I get:
> 
> # echo 5 >pwm2_enable
> bash: echo: write error: Invalid argument
> 
For now that is on purpose. Problem is that if SmartFanIV mode was not
initialized by the BIOS, it probably won't work. There are lots of
parameters which have to be configured. So one can not just let users
enable it without forcing them to configure all the other parameters ..
which is currently not possible with the sysfs ABI.

So this is really a one-way street for now.

Nuvoton's position on this matter is that fan control should be left to
the board vendor to prevent system damage, ie that users should not try
to configure it at all other than through the BIOS. They might have a
point.

> which means I can't undo what I just did.  (If I patch the driver to
> accept '5', then it works.)
> 
> Are there docs (e.g. a patch to Documentation/hwmon/w83627ehf, but an
> email explanation would do) for how SmartFan works, or, more
> generally, for how to program the various modes?  If you have a link

Not yet. I'll have to update the document before I can submit the
driver.

> to a datasheet, I can try to write something.
> 
I do have a datasheet, but it is unfortunately non-public. You would
have to request it from Nuvoton directly. It should not be a problem to
get it if you let them know what you need it for.

> In BIOS, I have settings related to target temperatures, minimum pwm
> output, etc.
> 
> Thanks for working on this driver!  I'd be happy to add my Tested-by:
> if you submit it upstream.
> 
Thanks a lot for your help testing it!

Guenter



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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Andrew Lutomirski]

On Mon, Feb 7, 2011 at 3:26 PM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> Hi Andrew,
>
> On Mon, 2011-02-07 at 14:53 -0500, Andrew Lutomirski wrote:
> [ ... ]
>> >
>> > Anyway, please try again. I updated the code to fix the pwmX_enable bug.
>>
>> Mostly works.
>>
>> If I set pwm2_enable to 1, then pwm2 controls the fan.
>>
>> If I try to set pwm2_enable to 5, I get:
>>
>> # echo 5 >pwm2_enable
>> bash: echo: write error: Invalid argument
>>
> For now that is on purpose. Problem is that if SmartFanIV mode was not
> initialized by the BIOS, it probably won't work. There are lots of
> parameters which have to be configured. So one can not just let users
> enable it without forcing them to configure all the other parameters ..
> which is currently not possible with the sysfs ABI.

I guess what you'd want is a "set lots of parameters all at once" interface.

>
> So this is really a one-way street for now.
>
> Nuvoton's position on this matter is that fan control should be left to
> the board vendor to prevent system damage, ie that users should not try
> to configure it at all other than through the BIOS. They might have a
> point.

Fair enough.  I actually plan to let BIOS configure everything, since
it seems to work nicely.  But as long as there is a driver that offers
fan control, might as well have it work properly.  (I care a lot more
about the sensors than the fan control.)

Should there be a "read-only" module option?

--Andy

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Jean Delvare]

On Mon, 7 Feb 2011 09:44:12 -0800, Guenter Roeck wrote:
> Hi Andrew,
> 
> On Mon, Feb 07, 2011 at 11:50:48AM -0500, Andrew Lutomirski wrote:
> [ ... ]
> > >
> > > So what you'll have to do is to set a minimum speed, and the problem will go away.
> > 
> > I admit I'm a bit confused as to what fan2_min does.  I have a minimum
> > (to warn?) fan speed set in BIOS, which seems to have nothing to do
> > with the initial value of fan2_min.  Changing fan2_min will cause
> > fan2_alarm to become set or unset, when I decrease min below input,
> > alarm stays set until I read it once.
> > 
> Interesting; it means that it works, but the BIOS seems to use another set
> of registers to set the minimum speed.

The BIOS doesn't necessarily use limit registers. It is totally
possible that the speed is simply checked at boot time against the
specified limit, and the hardware monitoring chip isn't even aware of
it.

Motherboard vendors have been under- or even misusing the hardware
monitoring features of the chips they selected for years, and while it
gets slowly better over time, it's still dangerous to assume that they
always know what they are doing and that they always do the right thing.

-- 
Jean Delvare

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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Guenter Roeck]

On Mon, 2011-02-07 at 15:35 -0500, Jean Delvare wrote:
> On Mon, 7 Feb 2011 09:44:12 -0800, Guenter Roeck wrote:
> > Hi Andrew,
> > 
> > On Mon, Feb 07, 2011 at 11:50:48AM -0500, Andrew Lutomirski wrote:
> > [ ... ]
> > > >
> > > > So what you'll have to do is to set a minimum speed, and the problem will go away.
> > > 
> > > I admit I'm a bit confused as to what fan2_min does.  I have a minimum
> > > (to warn?) fan speed set in BIOS, which seems to have nothing to do
> > > with the initial value of fan2_min.  Changing fan2_min will cause
> > > fan2_alarm to become set or unset, when I decrease min below input,
> > > alarm stays set until I read it once.
> > > 
> > Interesting; it means that it works, but the BIOS seems to use another set
> > of registers to set the minimum speed.
> 
> The BIOS doesn't necessarily use limit registers. It is totally
> possible that the speed is simply checked at boot time against the
> specified limit, and the hardware monitoring chip isn't even aware of
> it.
> 
> Motherboard vendors have been under- or even misusing the hardware
> monitoring features of the chips they selected for years, and while it
> gets slowly better over time, it's still dangerous to assume that they
> always know what they are doing and that they always do the right thing.
> 
Good point. Maybe not dangerous, but it might well be a fallacy or maybe
a delusion ;).

However, adding smartfan features would really require a board using it.
So that will have to wait until someone is willing to do that.

I'll do something else, though - let users configure SmartFan IV if it
was configured at startup. That should be safe enough.

Guenter



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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Pilcher]

Just a quick note that this driver (10-Mar-2011?) seems to be working
well on my Intel DQ67SW.  Temperature and fan monitoring were pretty
easy to set up (no thermistors, thank goodness!); I haven't bothered
with fan control, since that seems to be working "automagically".

As always, trying to figure out how they've wired up the voltages will
be the most challenging part.  I was hoping that Intel might be more
forthcoming in this area than other manufacturers, but that does not
appear to be the case.

With a bit of luck, I should be able to post a config for this board
relatively shortly.

What kernel version is this updated driver likely to appear in?  I'd
love to get rid of the DKMS hackery.

Thanks!

-- 
====================================
Ian Pilcher                                         arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
====================================


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

Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,

[Ian Dobson]

--------------------------------------------------
From: "Ian Pilcher" <arequipeno@gmail.com>
Sent: Sunday, April 10, 2011 5:28 PM
To: <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, 
NCT6775F,NCT6776F [rev 2]

> Just a quick note that this driver (10-Mar-2011?) seems to be working
> well on my Intel DQ67SW.  Temperature and fan monitoring were pretty
> easy to set up (no thermistors, thank goodness!); I haven't bothered
> with fan control, since that seems to be working "automagically".
>
> As always, trying to figure out how they've wired up the voltages will
> be the most challenging part.  I was hoping that Intel might be more
> forthcoming in this area than other manufacturers, but that does not
> appear to be the case.
>
> With a bit of luck, I should be able to post a config for this board
> relatively shortly.
>
> What kernel version is this updated driver likely to appear in?  I'd
> love to get rid of the DKMS hackery.
>
> Thanks!
>
> -- 
> ====================================
> Ian Pilcher                                         arequipeno@gmail.com
> "If you're going to shift my paradigm ... at least buy me dinner first."
> ====================================
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Hi,

The merge request went in during the .39 merge window, so the driver should 
make it into 2.6.39

Regards
Ian Dobson
 


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