chip initializations in 2.6

Jean Delvare khali at
Thu Jan 22 10:27:21 CET 2004

> anybody working on a patch to remove limit initializations by chip
> drivers in 2.6?

I think I remember MMH was planing to work on this, but I don't know how
far he went.

Note that some drivers were committed without limit initializations
(asb100.c, lm85.c, lm90.c, w83l785ts.c, eeprom.c) and others were
already fixed (lm75.c, lm83.c and w83781d.c). So this leaves a short
list of drivers that need to be fixed:

A few more thoughts:
1* Recent and less recent changes to the it87 driver in CVS should be
ported to 2.6 as well.
2* I would remove much more than just limits initializations from the
drivers, considering the number of reported problems that could be
solved with init=0. I remember proposing a common policy for all
drivers, must be somewhere in the mailing list archive, although I
can't find it at the moment. I think I suggested that only the minimal
init commands would be issued by default (init=1), they could be
disabled with init=0, or we could reset the chip and reconfigure it
completely with init=2.

Aha, post is here:
(here I talk about a third value for limits, but I guess this is now off

Comments welcome.

Jean Delvare

More information about the lm-sensors mailing list