Hi Jean, Its working now. Thank you very much for your patch. dmesg output -------------------- w83627hf: Found W83627HF chip at 0x290 Using 6-bit VID table for VIA C7-D CPU # sensors -------------- w83627hf-isa-0290 Adapter: ISA adapter in0: +0.69 V (min = +0.00 V, max = +4.08 V) in1: +1.06 V (min = +0.00 V, max = +4.08 V) in2: +3.30 V (min = +2.82 V, max = +3.79 V) in3: +2.99 V (min = +3.57 V, max = +1.98 V) ALARM in4:
+3.28 V (min = +1.98 V, max = +4.05 V) in5: +3.30 V (min = +3.57 V, max = +3.30 V) ALARM in6: +3.33 V (min = +1.78 V, max = +0.53 V) ALARM in7: +3.30 V (min = +0.77 V, max = +2.29 V) ALARM in8: +3.52 V (min = +3.06 V, max = +0.64 V) ALARM fan1: 0 RPM (min = 13775 RPM, div = 2) ALARM fan2: 0 RPM (min = -1 RPM, div = 2) ALARM fan3: 0 RPM (min = 3515 RPM, div = 2) ALARM temp1: +52.0 C (high = +9.0 C, hyst = +32.0 C)
ALARM sensor = thermistor temp2: +38.5 C (high = +120.0 C, hyst = +115.0 C) sensor = diode temp3: -48.0 C (high = +120.0 C, hyst = +115.0 C) sensor = thermistor cpu0_vid: +1.212 V beep_enable: enabled One thing I understood is there is no interrupt mechanism in sensor chip so we need to read data from chip's memory. So for periodic data we need to do polling at userspace (like sensord). Can I implement timer in driver and do polling in Kernel? What I want to do is get userspace event only when Alarm is raised. If I implement timer and netlink communication in driver will it be
correct way to do it? As I do not find any other way. Best Regards, Krunal Patel --- On Mon, 20/6/11, Jean Delvare <khali@xxxxxxxxxxxx> wrote:
|
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors