On Fri, 2010-06-18 at 14:10 -0400, Jonathan Cameron wrote: > On 06/18/10 18:53, Jonathan Cameron wrote: > > > > Hi, > > > > I've taken a quick look through this code. > > > > One or two specific comments below. > > > > Only big question is why have the limit functionality in this driver? > > Given the device has no hardware support and you don't have any form > > of regular polling (I think) then these limits will only be noticed if > > you query them. Hence why not leave this job to userspace? > > > > I'm not saying you are wrong to do this. Just that you need to explain > > your reasoning alongside the patch. > > Another quick query. Are the _min / _max attributes as defined in the > abi meant for alarms? I always thought they were to tell userspace the > limits on measurement? > Good question. I thought it is supposed to refer to alarm limits, but I may be wrong. Browsing through a couple of drivers, it _looks_ like the values are used for alarm limits (eg adm1025 or lm85). Limits are not always set to useful values, though. This is what my CPU board returns: lm85-i2c-0-2e Adapter: SMBus PIIX4 adapter at 0580 V1.5: +1.80 V (min = +0.00 V, max = +3.32 V) VCore: +1.29 V (min = +0.00 V, max = +2.99 V) V3.3: +3.32 V (min = +0.00 V, max = +4.38 V) V5: +5.00 V (min = +0.00 V, max = +6.64 V) V12: +12.12 V (min = +0.00 V, max = +15.94 V) The lm85 datasheet says: "If a voltage input either exceeds the value set in the voltage high limit register or falls below the value set in the voltage low limit register, the corresponding bit will be set automatically by the LM85 in the interrupt status registers (41-42h)." > Either way, one of us has misunderstood so perhaps the documentation needs > to be more specific.... Agreed. Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
