Re: [PATCH 3/4] drivers/hwmon/lm80.c: added error handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





2012/1/26 Jean Delvare <khali@xxxxxxxxxxxx>
On Thu, 5 Jan 2012 15:52:41 +0100, Frans Meulenbroeks wrote:
> 2012/1/5 Jean Delvare <khali@xxxxxxxxxxxx>
> > Are you really still using  LM80 chips? These are pretty old and I did
> > not expect anyone to be still using them. And certainly not for new
> > designs... The device (at least the incarnations that existed in
> > 1998-2000) was not reputed for its reliability...
>
> Yes, we still have them and I need to support them (just like LM75).
> (acutally we're using LM96080). They are not on my board, but we have
> external fan units that contain these chips, and my board needs to support
> these fan units.

Frans, could you please provide a register dump of your LM96080 chip?
I'd like to add that to my collection. You can get such a dump using
the i2c-dev driver + i2cdump (from package i2c-tools.)

Thanks,

Hi Jean,

I hope this is what you are looking for:

root@(none):/sys/devices/e0000000.soc8313/e0003100.i2c/i2c-1/1-0028# cat fan1_input
3668
root@(none):/sys/devices/e0000000.soc8313/e0003100.i2c/i2c-1/1-0028# i2cdump  1 0x28
No size specified (using byte-data access)
Error: Could not set address to 0x28: Device or resource busy
root@(none):/sys/devices/e0000000.soc8313/e0003100.i2c/i2c-1/1-0028# i2cdump -f 1 0x28
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1, address 0x28, mode byte
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 7f 2d 00 00 3c 18 00 00 00 00 00 00 00 00 00    ??-..<?.........
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 0c 00 00 00 00 00 00 1a 2e ff 00 00 00 00 00 00    ?......?........
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 08    ..............??
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

Not fully sure if this is correct as I had to use -f
Also fan1_input is 3668, which is hex 0e54 but I do not see that value in the dump.

Feel free to ping me if there is other info you need.

Best regards, Frans
 

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux