On Fri, 2011-03-04 at 13:50 -0500, Andrew Lutomirski wrote: > On Fri, Mar 4, 2011 at 12:57 PM, Guenter Roeck > <guenter.roeck@xxxxxxxxxxxx> wrote: > > The following patch series adds support for NCT6775F and NCT6776F to the > > w83627ehf driver. It also includes some cleanup and adds support for > > the fourth temperature sensor on W83677HG-B. > > > > No code changes since v4. Resubmitting and widening audience in the hope that > > someone may find the time to review the changes prior to the next commit window. > > I'm not sure my review is worth much, but the driver seems to work. I've tested > fan speed measurement, changing pwm2_enable to 1, changing the fan speed, > and changing back to 5. Everything looks good. > > The only weird thing I noticed is that, the first time I ran sensors, I got: > fan2: 0 RPM (min = 0 RPM, div = 64) > and thereafter I get > fan2: 136 RPM (min = 0 RPM, div = 64) ALARM > > I suspect (although I haven't checked) that sensors is just reading > div after it's already changed to 64. > The driver reads rpm, finds it to be zero, and increases div as result (NCT6775F may report zero rpm if div is too low). That explains the first reading. What I don't understand is the alarm you get with the 2nd reading. Any idea where this might come from ? Is it sticky, or do you see it only once ? Thanks, Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
