i2c-i801 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
  1. Kernel driver i2c-i801
  2. Supported adapters:
  3. * Intel 82801AA and 82801AB (ICH and ICH0 - part of the
  4. '810' and '810E' chipsets)
  5. * Intel 82801BA (ICH2 - part of the '815E' chipset)
  6. * Intel 82801CA/CAM (ICH3)
  7. * Intel 82801DB (ICH4) (HW PEC supported)
  8. * Intel 82801EB/ER (ICH5) (HW PEC supported)
  9. * Intel 6300ESB
  10. * Intel 82801FB/FR/FW/FRW (ICH6)
  11. * Intel 82801G (ICH7)
  12. * Intel 631xESB/632xESB (ESB2)
  13. * Intel 82801H (ICH8)
  14. * Intel 82801I (ICH9)
  15. * Intel Tolapai
  16. * Intel ICH10
  17. Datasheets: Publicly available at the Intel website
  18. Authors:
  19. Mark Studebaker <mdsxyz123@yahoo.com>
  20. Jean Delvare <khali@linux-fr.org>
  21. Module Parameters
  22. -----------------
  23. None.
  24. Description
  25. -----------
  26. The ICH (properly known as the 82801AA), ICH0 (82801AB), ICH2 (82801BA),
  27. ICH3 (82801CA/CAM) and later devices are Intel chips that are a part of
  28. Intel's '810' chipset for Celeron-based PCs, '810E' chipset for
  29. Pentium-based PCs, '815E' chipset, and others.
  30. The ICH chips contain at least SEVEN separate PCI functions in TWO logical
  31. PCI devices. An output of lspci will show something similar to the
  32. following:
  33. 00:1e.0 PCI bridge: Intel Corporation: Unknown device 2418 (rev 01)
  34. 00:1f.0 ISA bridge: Intel Corporation: Unknown device 2410 (rev 01)
  35. 00:1f.1 IDE interface: Intel Corporation: Unknown device 2411 (rev 01)
  36. 00:1f.2 USB Controller: Intel Corporation: Unknown device 2412 (rev 01)
  37. 00:1f.3 Unknown class [0c05]: Intel Corporation: Unknown device 2413 (rev 01)
  38. The SMBus controller is function 3 in device 1f. Class 0c05 is SMBus Serial
  39. Controller.
  40. The ICH chips are quite similar to Intel's PIIX4 chip, at least in the
  41. SMBus controller.
  42. Process Call Support
  43. --------------------
  44. Not supported.
  45. I2C Block Read Support
  46. ----------------------
  47. I2C block read is supported on the 82801EB (ICH5) and later chips.
  48. SMBus 2.0 Support
  49. -----------------
  50. The 82801DB (ICH4) and later chips support several SMBus 2.0 features.
  51. Hidden ICH SMBus
  52. ----------------
  53. If your system has an Intel ICH south bridge, but you do NOT see the
  54. SMBus device at 00:1f.3 in lspci, and you can't figure out any way in the
  55. BIOS to enable it, it means it has been hidden by the BIOS code. Asus is
  56. well known for first doing this on their P4B motherboard, and many other
  57. boards after that. Some vendor machines are affected as well.
  58. The first thing to try is the "i2c_ec" ACPI driver. It could be that the
  59. SMBus was hidden on purpose because it'll be driven by ACPI. If the
  60. i2c_ec driver works for you, just forget about the i2c-i801 driver and
  61. don't try to unhide the ICH SMBus. Even if i2c_ec doesn't work, you
  62. better make sure that the SMBus isn't used by the ACPI code. Try loading
  63. the "fan" and "thermal" drivers, and check in /proc/acpi/fan and
  64. /proc/acpi/thermal_zone. If you find anything there, it's likely that
  65. the ACPI is accessing the SMBus and it's safer not to unhide it. Only
  66. once you are certain that ACPI isn't using the SMBus, you can attempt
  67. to unhide it.
  68. In order to unhide the SMBus, we need to change the value of a PCI
  69. register before the kernel enumerates the PCI devices. This is done in
  70. drivers/pci/quirks.c, where all affected boards must be listed (see
  71. function asus_hides_smbus_hostbridge.) If the SMBus device is missing,
  72. and you think there's something interesting on the SMBus (e.g. a
  73. hardware monitoring chip), you need to add your board to the list.
  74. The motherboard is identified using the subvendor and subdevice IDs of the
  75. host bridge PCI device. Get yours with "lspci -n -v -s 00:00.0":
  76. 00:00.0 Class 0600: 8086:2570 (rev 02)
  77. Subsystem: 1043:80f2
  78. Flags: bus master, fast devsel, latency 0
  79. Memory at fc000000 (32-bit, prefetchable) [size=32M]
  80. Capabilities: [e4] #09 [2106]
  81. Capabilities: [a0] AGP version 3.0
  82. Here the host bridge ID is 2570 (82865G/PE/P), the subvendor ID is 1043
  83. (Asus) and the subdevice ID is 80f2 (P4P800-X). You can find the symbolic
  84. names for the bridge ID and the subvendor ID in include/linux/pci_ids.h,
  85. and then add a case for your subdevice ID at the right place in
  86. drivers/pci/quirks.c. Then please give it very good testing, to make sure
  87. that the unhidden SMBus doesn't conflict with e.g. ACPI.
  88. If it works, proves useful (i.e. there are usable chips on the SMBus)
  89. and seems safe, please submit a patch for inclusion into the kernel.
  90. Note: There's a useful script in lm_sensors 2.10.2 and later, named
  91. unhide_ICH_SMBus (in prog/hotplug), which uses the fakephp driver to
  92. temporarily unhide the SMBus without having to patch and recompile your
  93. kernel. It's very convenient if you just want to check if there's
  94. anything interesting on your hidden ICH SMBus.
  95. **********************
  96. The lm_sensors project gratefully acknowledges the support of Texas
  97. Instruments in the initial development of this driver.
  98. The lm_sensors project gratefully acknowledges the support of Intel in the
  99. development of SMBus 2.0 / ICH4 features of this driver.