On Wed, Nov 20, 2013 at 10:19:42AM +0100, Jean Delvare wrote:
> Hi Guenter,
>
> On Tue, 19 Nov 2013 13:53:58 -0800, Guenter Roeck wrote:
> > On Tue, Nov 19, 2013 at 08:41:01PM +0100, Jean Delvare wrote:
> > [ ... ]
> > > > with the same model/mask. Based on that we could declare a "tjmin" and
> > > > report that if it is 1) defined and 2) the valid bit is 0. A somewhat "safe"
> > > > temperature to report for the D5xx (model 0x1c/mask 10), based on Mike's
> > > > numbers, would then be 36 degrees C (100 - 64).
> > >
> > > Not sure where you drew the "36" from. From Mike's table it seems the
> > > valid flag wears off when the reported temperature would be < 6°C. This
> > > correlates with my findings in the ticket where the valid flag would be
> > > 0 for 1°C and 4°C.
> > >
> > Now I remember what I was thinking. In Mike's table, the real temperature at
> > which the sensor last reported 'valid' (according to the thermal diode)
> > was at 44 degrees C, or 56 degrees below TjMax.
>
> That I agree with.
>
> > Add the reported temperature
> > of 6 degrees C to that number and you get 62. Round up to 64 below TjMax,
> > or 36 degrees C.
>
> All this means is that the DTS would return 0°C at approximately 36°C
> physical (if we can trust the external sensor AND ignoring the expected
> difference between internal and external temperature measurement.) I
> don't think you can deduce tjmin from that, as the DTS scale and the
> physical scale are distinct.
>
Yes, you are right. As I say below, that calculation doesn't really make much
sense.
> > Not that this calculation really makes any sense ;-), but with Mike's 'real'
> > numbers from the thermal diode it sounds at least somewhat reasonable.
>
> It is well known that the CPU DTS loses accuracy at low temperatures,
> and Mike's numbers only show that.
>
> Tjmin should be taken from the datasheet when it is present there. When
> it is not in the datasheet, it becomes arbitrary, the only hard
> constraint being that it must be greater than the values for which the
> valid flag is no longer set (i.e. >= 6 in Mike's case.)
>
I don't see it anywhere, and I don't think it exists.
Mike's graph is quite interesting - it shows that the temperature reading error
is linear, at least for his CPU. Unfortunately, I don't think we can use
that knowledge to "fix" the reading automatically, as the error is very likely
different for other CPUs. We might consider adding an ideality factor module
parameter, though. What do you think about that ?
Another question is what temperature to use as tjmin. If we add an ideality
factor module parameter, it could be quite low, such as 20 degrees C.
We could even calculate tjmin based on the ideality factor if specified.
tjmin = tjmax - (tjmax * ideality_factor / 100); /* ideality_factor in % */
Otherwise I would prefer something higher, at least 30 degrees C.
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
