i2c-piix4 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. Kernel driver i2c-piix4
  2. Supported adapters:
  3. * Intel 82371AB PIIX4 and PIIX4E
  4. * Intel 82443MX (440MX)
  5. Datasheet: Publicly available at the Intel website
  6. * ServerWorks OSB4, CSB5, CSB6 and HT-1000 southbridges
  7. Datasheet: Only available via NDA from ServerWorks
  8. * Standard Microsystems (SMSC) SLC90E66 (Victory66) southbridge
  9. Datasheet: Publicly available at the SMSC website http://www.smsc.com
  10. Authors:
  11. Frodo Looijaard <frodol@dds.nl>
  12. Philip Edelbrock <phil@netroedge.com>
  13. Module Parameters
  14. -----------------
  15. * force: int
  16. Forcibly enable the PIIX4. DANGEROUS!
  17. * force_addr: int
  18. Forcibly enable the PIIX4 at the given address. EXTREMELY DANGEROUS!
  19. * fix_hstcfg: int
  20. Fix config register. Needed on some boards (Force CPCI735).
  21. Description
  22. -----------
  23. The PIIX4 (properly known as the 82371AB) is an Intel chip with a lot of
  24. functionality. Among other things, it implements the PCI bus. One of its
  25. minor functions is implementing a System Management Bus. This is a true
  26. SMBus - you can not access it on I2C levels. The good news is that it
  27. natively understands SMBus commands and you do not have to worry about
  28. timing problems. The bad news is that non-SMBus devices connected to it can
  29. confuse it mightily. Yes, this is known to happen...
  30. Do 'lspci -v' and see whether it contains an entry like this:
  31. 0000:00:02.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
  32. Flags: medium devsel, IRQ 9
  33. Bus and device numbers may differ, but the function number must be
  34. identical (like many PCI devices, the PIIX4 incorporates a number of
  35. different 'functions', which can be considered as separate devices). If you
  36. find such an entry, you have a PIIX4 SMBus controller.
  37. On some computers (most notably, some Dells), the SMBus is disabled by
  38. default. If you use the insmod parameter 'force=1', the kernel module will
  39. try to enable it. THIS IS VERY DANGEROUS! If the BIOS did not set up a
  40. correct address for this module, you could get in big trouble (read:
  41. crashes, data corruption, etc.). Try this only as a last resort (try BIOS
  42. updates first, for example), and backup first! An even more dangerous
  43. option is 'force_addr=<IOPORT>'. This will not only enable the PIIX4 like
  44. 'force' foes, but it will also set a new base I/O port address. The SMBus
  45. parts of the PIIX4 needs a range of 8 of these addresses to function
  46. correctly. If these addresses are already reserved by some other device,
  47. you will get into big trouble! DON'T USE THIS IF YOU ARE NOT VERY SURE
  48. ABOUT WHAT YOU ARE DOING!
  49. The PIIX4E is just an new version of the PIIX4; it is supported as well.
  50. The PIIX/PIIX3 does not implement an SMBus or I2C bus, so you can't use
  51. this driver on those mainboards.
  52. The ServerWorks Southbridges, the Intel 440MX, and the Victory766 are
  53. identical to the PIIX4 in I2C/SMBus support.
  54. A few OSB4 southbridges are known to be misconfigured by the BIOS. In this
  55. case, you have you use the fix_hstcfg module parameter. Do not use it
  56. unless you know you have to, because in some cases it also breaks
  57. configuration on southbridges that don't need it.