[lm-sensors] ATI SMBus - new information

[lm-sensors] ATI SMBus - new information

[Rudolf Marek]

Hello all owners of ATI SMBus,

Part of my last night was a chase to ATI SMBUS. Today I'm quite confident it is just
i801 clone. The only thing that is different is the base address.

If you still have such systems, please provide following:

lspci
lspci -x -x -x
cat /proc/acpi/dsdt
(best would be to run IASL to disassembly the DSDT table but I can do it on my own)
cat /proc/ioports

Post it back to the list please.
I dont own such systems myself but I think I can try to develop missing parts to i2c-i801.c
Of course I will need testers. I must warn you that this try might damage your hardware or render it
unusable. I would prefer to test it on desktop PC rather than notebook.

I think I will be able to create patch later today.

The details I know so far:
Base address will be likely 0x1000
The base address register is located in device 0x14, function 0, offset 0x90
Rest of the controller seems to follow the i801 SMBUS cotroller.

Thanks,
Regards
Rudolf

[lm-sensors] ATI SMBus - new information

[Rudolf Marek]

Hello all,

Update. Please send me the DSDT tables directly. The mailing list will throw them away.(bin attachment)
See the attachment for the patch.

Please note, the code was not tested. I belive it should work, but it may do bad things to your HW.
On the other hand you want the ATI SMBUS support :)

This patch is for 2.6 driver of i2c-i801.c After applying the patch you should be able to modprobe i2c-i801
if you modprobe i2c-dev then you should be able to run i2cdetect and i2cdump.

i2cdump 0
should show that 0x50 or above is used.

40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: 50 51 XX XX XX XX XX XX XX XX XX XX XX XX XX XX

If you see all XX it means there is nothing or my patch does not work.

If so you can try to dump the address:
i2cdump 0 0x50

00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01    ??????@.?P`.??.?
10: 0e 04 0c 01 02 20 00 60 70 00 00 3c 28 3c 28 40    ????? .`p..<(<(@

....

If the output is similar to this one then you can run sensors-detect to detect the chips (leave the i2c-i801 loaded)

Please report how it goes.
Good luck.

Thanks,
Regards
Rudolf
-------------- next part --------------
diff -Naur a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
--- a/drivers/i2c/busses/i2c-i801.c	2005-09-30 23:17:35.000000000 +0200
+++ b/drivers/i2c/busses/i2c-i801.c	2005-10-22 21:36:20.000000000 +0200
@@ -119,6 +119,22 @@
 	unsigned char temp;
 
 	/* Note: we keep on searching until we have found 'function 3' */
+	
+	if (PCI_DEVFN(0x14,0) = dev->devfn) {
+		I801_dev = dev;
+		pci_read_config_word(I801_dev, 0x90, &i801_smba);
+		i801_smba &= 0xfff0;
+		isich4 = 0; //dont know yet
+
+		if (!request_region(i801_smba, (isich4 ? 16 : 8), "i801-smbus")) {
+			dev_err(&dev->dev, "I801_smb region 0x%x already in use!\n",
+				i801_smba);
+			error_return = -EBUSY;
+			goto END;
+		}
+		return 0;
+	}	
+
 	if(PCI_FUNC(dev->devfn) != 3)
 		return -ENODEV;
 
@@ -557,6 +573,9 @@
 	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_16) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH7_17) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ESB2_17) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_ATI, 0x4353) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_ATI, 0x4363) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_ATI, 0x4372) },
 	{ 0, }
 };
 

[lm-sensors] ATI SMBus - new information

[Pavel Ruzicka]

Hello,

> Please note, the code was not tested. I belive it should work, but it may
> do bad things to your HW. On the other hand you want the ATI SMBUS support
> :)

It looks like it works.

There are some informations from my system:

[root@home /]# i2cdetect -l
i2c-0   unknown         SMBus I801 adapter at 0400              Algorithm 
unavailable

[root@home /]# i2cdump 0 0x50
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/0, address 0x50, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01    ??????@.?P`.??.?
10: 0e 04 08 01 02 20 00 60 70 00 00 3c 28 3c 28 40    ????? .`p..<(<(@
20: 60 60 40 40 00 00 00 00 00 00 00 00 00 00 00 00    ``@@............
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7c    ...............|
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: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

--------------------------------------------------------------
#sensors-detect
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Failed!
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Winbond W83L785R'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Philips NE1619'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `VIA VT1211 (I2C)'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ALi M5879'... Failed!
Probing for `SMSC LPC47M15x or LPC47M192'... Success!
    (confidence 6, driver `to-be-written')
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8712F'... Failed!
Client found at address 0x38
Probing for `Philips Semiconductors SAA1064'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): YES
Probing for `National Semiconductor LM78'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
  Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
  Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
  Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
  Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8712F'
  Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
  Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
  Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
  Trying address 0x0ca8... Failed!

Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
  Success... found at address 0x0800

#lsmod
smsc47m1                9552  0
eeprom                  7056  0
i2c_isa                 2624  0
i2c_i801                8852  0
i2c_sensor              3136  2 smsc47m1,eeprom
i2c_dev                10176  0
i2c_core               19416  6 
smsc47m1,eeprom,i2c_isa,i2c_i801,i2c_sensor,i2c_dev

[root@home linux]# sensors
smsc47m1-isa-0800
Adapter: ISA adapter
fan1:        0 RPM  (min =  640 RPM, div = 8)          ALARM
fan2:     1050 RPM  (min =  640 RPM, div = 8)

Best regards,

Pavel Ruzicka

[lm-sensors] ATI SMBus - new information

[Jean Delvare]

Hi all,

> It looks like it works.
>
> There are some informations from my system:
>
> [root@home /]# i2cdetect -l
> i2c-0   unknown         SMBus I801 adapter at 0400

Rudolf:
Maybe it would be wise to have a different name string for the ATI
variants? Like the i2c-amd756 driver does.

You'll also need to update sensors-detect with the proper "match"
entry for these devices, so that the script can suggest i2c-i801 as the
bus driver.

> Probing for `SMSC LPC47M15x or LPC47M192'... Success!
>     (confidence 6, driver `to-be-written')

There is a driver being developed for this but I think it ain't ready
yet.

> Client found at address 0x2f

Pavel:
I wonder what is there. Can you please do:

i2cdump 0 0x2f b

--
Jean Delvare

[lm-sensors] ATI SMBus - new information

[David Goodenough]

Rudolf,

I am not quite sure why I am included in the CC list for this note.  I do not 
have one of these chips on my system as far as I know, the only only
ATI chip I have is a Radeon video chip.

David

On Saturday 22 October 2005 21:12, Rudolf Marek wrote:
> Hello all,
>
> Update. Please send me the DSDT tables directly. The mailing list will
> throw them away.(bin attachment) See the attachment for the patch.
>
> Please note, the code was not tested. I belive it should work, but it may
> do bad things to your HW. On the other hand you want the ATI SMBUS support
> :)
>
> This patch is for 2.6 driver of i2c-i801.c After applying the patch you
> should be able to modprobe i2c-i801 if you modprobe i2c-dev then you should
> be able to run i2cdetect and i2cdump.
>
> i2cdump 0
> should show that 0x50 or above is used.
>
> 40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 50: 50 51 XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>
> If you see all XX it means there is nothing or my patch does not work.
>
> If so you can try to dump the address:
> i2cdump 0 0x50
>
> 00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01    ??????@.?P`.??.?
> 10: 0e 04 0c 01 02 20 00 60 70 00 00 3c 28 3c 28 40    ????? .`p..<(<(@
>
> ....
>
> If the output is similar to this one then you can run sensors-detect to
> detect the chips (leave the i2c-i801 loaded)
>
> Please report how it goes.
> Good luck.
>
> Thanks,
> Regards
> Rudolf

[lm-sensors] ATI SMBus - new information

[Rudolf Marek]

David Goodenough wrote:
> Rudolf,
> 
> I am not quite sure why I am included in the CC list for this note.  I do not 
> have one of these chips on my system as far as I know, the only only
> ATI chip I have is a Radeon video chip.
> 

> I have a laptop (a Samsumg P28) which has lots of ATI chips in it.  One of 
> them (according to lspci) is an SmBus controller, and it has a PCI id of
> 1002:4353.  Looking at the lmsensors web site there are no bus drivers
> for any ATI chips.  This seems to be one of the functions in the Ati 
> 9000 IGP chip, which is also the video driver.  It is marked as being
> the 9100 IGP chip in the linux PCI repository, but I guess they use the
> same silicon in both chips.

You wrote this correct :) ?

The PCI ID matches so my driver will work for you too.

Regards
Rudolf

[lm-sensors] ATI SMBus - new information

[Pavel Ruzicka]

Hi,

> > Client found at address 0x2f
>
> Pavel:
> I wonder what is there. Can you please do:
>
> i2cdump 0 0x2f b
> --
> Jean Delvare

There is dump, what do you want:

[root@home pavouk]# i2cdump 0 0x2f b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0, address 0x2f, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 0f 00 00 07 00 18 00 00 ff ff ff ff ff ff ff    ??..?.?.........
10: ff ff ff ff 14 62 02 05 ff ff ff ff ff ff ff ff    ....?b??........
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

Best regards,

Pavel Ruzicka

[lm-sensors] ATI SMBus - new information

[Jean Delvare]

Hi Pavel,

On 2005-10-24, Pavel Ruzicka wrote:
> There is dump, what do you want:
>
> [root@home pavouk]# i2cdump 0 0x2f b
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c/0, address 0x2f, mode byte
> Continue? [Y/n]
>     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
> 00: 80 0f 00 00 07 00 18 00 00 ff ff ff ff ff ff ff    ??..?.?.........
> 10: ff ff ff ff 14 62 02 05 ff ff ff ff ff ff ff ff    ....?b??........
> 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

Hm, I have no idea what this can be, sorry.

--
Jean Delvare

[lm-sensors] ATI SMBus - new information

[Rudolf Marek]

> It looks like it works.

Cool.

I will add some more information to the archive. It seems it is ICH4 compatible because it reserves for ACPI the 16 bytes.
So HW PEC should be supported too.

Pavel could you please dump with isadump:

isadump -f 0x400 16

Thanks

Regards
Rudolf

[lm-sensors] ATI SMBus - new information

[Pavel Ruzicka]

Hi Rudolf,

> I will add some more information to the archive. It seems it is ICH4
> compatible because it reserves for ACPI the 16 bytes. So HW PEC should be
> supported too.
>
> Pavel could you please dump with isadump:

Here is requested isadump:
-----------------------------------
[root@home ~]# isadump -f 0x400 16
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address range 0x400 to 0x40f.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 37 ae 3c 00 00 00 00 00 00 00 00 a0 00
-----------------------------------

> Regards
> Rudolf

Best regards,

Pavel Ruzicka

[lm-sensors] ATI SMBus - new information

[Rudolf Marek]

Patrick wrote:
> Rudolf,
>
> Googling around I found your posting at
> >http://lists.lm-sensors.org/pipermail/lm-sensors/2005-October/013946.html
> I have an Acer Ferrari with the ATI Xpress 200 chipset and am interested
> in a module for the ATI SMBus so I can see temps and fan speed with
> gkrellm. In your posting I read the info you require so have attached
> it. If you need anything else please let me know.

Thanks for the information.

You can try the patch
http://lists.lm-sensors.org/pipermail/lm-sensors/2005-October/013962.html

It should work. But I cant give you any warranty that it wont destroy
the notebook. On the other hand we know this works at least in one case ;)

Just load:

modprobe i2c-i801
sensors-detect

Hopefuly it will find some sensors.

Regards
Rudolf

[lm-sensors] ATI SMBus - new information

[Rudolf Marek]

> 
> Here is requested isadump:
> -----------------------------------
> [root@home ~]# isadump -f 0x400 16
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address range 0x400 to 0x40f.
> Continue? [Y/n]
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: 00 00 00 37 ae 3c 00 00 00 00 00 00 00 00 a0 00
> -----------------------------------

Thanks,

This is slightly different that what should be the default of i801 conteroller. There are two other candidates left:
i2c-viapro and i2c-piix4.

They have both compatible commands and both have even the base addr at PCI config space 0x90.
Intel PIIX4 is used inside Serverworks and other chipsets so this leads me to the fact that they sold it to ATI too.
(or ATI copied it). I checked all PCI config space dumps I had (thank you all for posting them!) and it seems that
the registers are same.

I developed new patch. Please see attachment. As you can see it is quite simple one. It just add PCI IDs to PIIX4 driver.

Please can you repeat your tests with this patch?
(apply patch to i2c-piix4 and modprobe i2c-piix4; modprobe i2c-dev)

Additionaly I want to know:
i2cdetect 0
i2cdump 0 0x50
i2cdump 0 0x50 c
i2cdump 0 0x50
i2cdetect 0

If this sequence produces same results. Also please modprobe eeprom driver and try to read from the chip this way:
hexdump -C /sys/bus/i2c/devices/0-0050/eeprom

Thank you very much

Regards
Rudolf


-------------- next part --------------
diff -Naur c/drivers/i2c/busses/i2c-piix4.c d/drivers/i2c/busses/i2c-piix4.c
--- c/drivers/i2c/busses/i2c-piix4.c	2005-10-28 02:02:08.000000000 +0200
+++ d/drivers/i2c/busses/i2c-piix4.c	2005-11-05 21:20:02.801161750 +0100
@@ -423,6 +423,12 @@
 	  .driver_data = 3 },
 	{ PCI_DEVICE(PCI_VENDOR_ID_EFAR, PCI_DEVICE_ID_EFAR_SLC90E66_3),
 	  .driver_data = 0 },
+	{ PCI_DEVICE(PCI_VENDOR_ID_ATI, 0x4353),
+	  .driver_data = 0 },
+	{ PCI_DEVICE(PCI_VENDOR_ID_ATI, 0x4363),
+	  .driver_data = 0 },	
+	{ PCI_DEVICE(PCI_VENDOR_ID_ATI, 0x4372),
+	  .driver_data = 0 },
 	{ 0, }
 };
 

[lm-sensors] ATI SMBus - new information

[Pavel Ruzicka]

Hi,

> I developed new patch. Please see attachment. As you can see it is quite
> simple one. It just add PCI IDs to PIIX4 driver.
>
> Please can you repeat your tests with this patch?
> (apply patch to i2c-piix4 and modprobe i2c-piix4; modprobe i2c-dev)

It works for me.

> Additionaly I want to know:
> i2cdetect 0
> i2cdump 0 0x50
> i2cdump 0 0x50 c
> i2cdump 0 0x50
> i2cdetect 0
> If this sequence produces same results. Also please modprobe eeprom driver
> and try to read from the chip this way: hexdump -C
> /sys/bus/i2c/devices/0-0050/eeprom

Dump is in attachment.
I tried decode-dimms.pl and it works for my two dimms.

There are found clients with sensors-detect:
------------------------------ 
Client found at address 0x2d
Probing for `SMSC LPC47M15x or LPC47M192'... Success!
    (confidence 6, driver `to-be-written')
Client found at address 0x2f
Client found at address 0x38
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x69
------------------------------

If I understand correctly, is it possible to access chip LPC47MXXX
through i2c or isa?
Driver smsc47m1 always use i2c-isa driver.

Best regards,

Pavel Ruzicka
-------------- next part --------------
[root@home i2c_adapter]# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX 2d XX 2f
30: XX XX XX XX XX XX XX XX 38 XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: 50 51 XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX

[root@home i2c_adapter]# i2cdump 0 0x50
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/0, address 0x50, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01    ??????@.?P`.??.?
10: 0e 04 08 01 02 20 00 60 70 00 00 3c 28 3c 28 40    ????? .`p..<(<(@
20: 60 60 40 40 00 00 00 00 00 00 00 00 00 00 00 00    ``@@............
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7c    ...............|
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: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

[root@home i2c_adapter]# i2cdump 0 0x50 c
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0, address 0x50, mode byte consecutive read
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01    ??????@.?P`.??.?
10: 0e 04 08 01 02 20 00 60 70 00 00 3c 28 3c 28 40    ????? .`p..<(<(@
20: 60 60 40 40 00 00 00 00 00 00 00 00 00 00 00 00    ``@@............
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7c    ...............|
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: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

[root@home i2c_adapter]# i2cdump 0 0x50
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/0, address 0x50, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01    ??????@.?P`.??.?
10: 0e 04 08 01 02 20 00 60 70 00 00 3c 28 3c 28 40    ????? .`p..<(<(@
20: 60 60 40 40 00 00 00 00 00 00 00 00 00 00 00 00    ``@@............
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7c    ...............|
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: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

[root@home i2c_adapter]# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX 2d XX 2f
30: XX XX XX XX XX XX XX XX 38 XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: 50 51 XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX


[root@home i2c_adapter]# hexdump -C /sys/bus/i2c/devices/0-0050/eeprom
00000000  80 08 07 0d 0a 02 40 00  04 50 60 00 82 08 00 01  |......@..P`.....|
00000010  0e 04 08 01 02 20 00 60  70 00 00 3c 28 3c 28 40  |..... .`p..<(<(@|
00000020  60 60 40 40 00 00 00 00  00 00 00 00 00 00 00 00  |``@@............|
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 7c  |...............||
00000040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000080  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |????????????????|
*
00000100

[root@home devices]# hexdump -C /sys/bus/i2c/devices/0-0051/eeprom
00000000  80 08 07 0d 0a 02 40 00  04 50 60 00 82 08 00 01  |......@..P`.....|
00000010  0e 04 08 01 02 20 00 60  70 00 00 3c 28 3c 28 40  |..... .`p..<(<(@|
00000020  60 60 40 40 00 00 00 00  00 00 00 00 00 00 00 00  |``@@............|
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 7c  |...............||
00000040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000080  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |????????????????|
*
00000100

[lm-sensors] ATI SMBus - new information

[Rudolf Marek]

> 
> It works for me.

good

> If I understand correctly, is it possible to access chip LPC47MXXX
> through i2c or isa?

10:40 < khali> Driver smsc47m1 always use i2c-isa driver.
10:40 < khali> it's not the same part of the device being accessed
10:41 < khali> throught ISA we have fan monitoring and control
10:41 < khali> on SMBus we have temperature and voltage monitoring

10:39 < khali> and a driver is supposed to be in progress, but it's a long time
               we didn't hear about it

Thomas,
Any news?


Last test the BUS transport will be the byte write mode.

i2cdump 0 0x2d

Should give you a register dump.

Datasheet is here
http://www.smsc.com/main/tools/discontinued/47m15x.pdf

Now please read the value on offset 0x31 (5V high limit) and add one to it and write it back to chip

i2cset 0 0x2d 0x31 0xyourvall

Readback should match.

Thanks

Regards
Rudolf

[lm-sensors] ATI SMBus - new information

[Pavel Ruzicka]

Hi Rudolf,

> 10:41 < khali> on SMBus we have temperature and voltage monitoring

On my system from MSI RS480M2-IL with LPC47M997 is supported only
CPU and SYSTEM temperature reading. Voltage reading is not supported in a 
hardware monitoring section of SMSC chip.

> i2cdump 0 0x2d
>
> Should give you a register dump.

Here is my actual dump:
----------------------
[root@home ~]# i2cdump 0 0x2d
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/0, address 0x2d, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX 50 02    XXXXXXXXXXXXXXP?
20: 00 00 00 00 87 c4 2f 23 XX XX XX ff 00 ff 00 ff    ....??/#XXX.....
30: 00 ff 00 ff 00 ff 00 3a 80 7f 80 XX XX XX 55 20    .......:???XXXU
40: 29 0f 0c XX XX XX XX 00 XX 80 00 02 00 00 XX 04    )??XXXX.X?.?..X?
50: 00 00 74 XX ff 00 ff 00 7f 80 XX XX XX XX XX XX    ..tX....??XXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
----------------------

> Datasheet is here
> http://www.smsc.com/main/tools/discontinued/47m15x.pdf

Registers are same on my system with LPC47M997.

> Now please read the value on offset 0x31 (5V high limit) and add one to it
> and write it back to chip
>
> i2cset 0 0x2d 0x31 0xyourvall
> Readback should match.

It works for me. But voltage measuring is not available on my system.
I tried other offsets with R/W registers and they worked too.

Here is interesting registers of my chip:
0x26 Remote Diode Temperature Reading 1	(CPU temperature) Value 0x30 48 C
0x27 Ambient Temperature Reading	(System temperature) Value 0x24 36 C
0x37 Remote Temperature High Limit 1 Value 0x3c 60 C
0x38 Remote Temperature Low Limit 1 Value 0x80 128 C
0x39 Remote Temperature High Limit 1 Value 0x7f 127 C
0x3A Remote Temperature Low Limit 1 Value 0x80 128 C

These temperatures are probably in a Celsius. They are changing when I load
processor. They look good and identical to BIOS and Winblows measuring tool.

Register 0x37 is possible to change in a BIOS.

I don't understand how limits works on a 0x37 to 0x3A offsets.
Can you point me to a documentation or a little explain, how they works? ;-)

Thanks.

Best regards,

Pavel Ruzicka

[lm-sensors] ATI SMBus - new information

[Pavel Ruzicka]

Hi,

> I don't understand how limits works on a 0x37 to 0x3A offsets.
> Can you point me to a documentation or a little explain, how they works?

I found explanation of my question on page 135 of this datasheet:
http://www.smsc.com/main/tools/discontinued/47m15x.pdf

Pavel Ruzicka