Hi Guenter, > > The temp1_max is supposed to be more than temp1_input and > > temp1_max_hyst is supposed to be lesser than temp1_input. > > By default the temp1_max_hyst is left at 0. > > > Should be set to something useful. Also, it does not have to be less > than temp1_input, as long as it is less than temp1_max (which was my > understanding). Worst case you would get another interrupt (when the > temperature crosses temp1_max_hyst from below) which you would ignore. Yes. I agree with you. I have no clue on what exact value to set to max and max_hyst initially. Can we set temp1_max to 70 and temp1_max_hyst to 50 ? > Interrupts should be enabled, and you can send uevents and sysfs notifications > whenever a threshold is crossed. All you would have to do is to keep the old > alarm > state and send events whenever it changes. > > Example: > temp=40, max_threshold=50, max=60 > > 1st interrupt when temp reaches 50 -> ignore > 2nd interrupt when temp reaches 60 -> set alarm, send uevent and sysfs > notifications > 3rd interrupt when temp reaches 60 (from above) -> ignore > 4th interrupt when temp reaches 50 (from above) -> reset alarm, send uevent and > sysfs notifications > Thank you for the example. The example is very clear. I will submit a patch to add this functionality to coretemp. Thanks, Durga _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
