blob: d29dea0f323287a3617205de7f12880e706a0cd8 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001Kernel driver i2c-i801
2
3Supported adapters:
4 * Intel 82801AA and 82801AB (ICH and ICH0 - part of the
5 '810' and '810E' chipsets)
6 * Intel 82801BA (ICH2 - part of the '815E' chipset)
7 * Intel 82801CA/CAM (ICH3)
Oleg Ryjkov7edcb9a2007-07-12 14:12:31 +02008 * Intel 82801DB (ICH4) (HW PEC supported)
9 * Intel 82801EB/ER (ICH5) (HW PEC supported)
Linus Torvalds1da177e2005-04-16 15:20:36 -070010 * Intel 6300ESB
11 * Intel 82801FB/FR/FW/FRW (ICH6)
Jason Gastona980a992006-12-10 21:21:31 +010012 * Intel 82801G (ICH7)
13 * Intel 631xESB/632xESB (ESB2)
14 * Intel 82801H (ICH8)
Gaston, Jason Dd28dc712008-02-24 20:03:42 +010015 * Intel 82801I (ICH9)
Seth Heasleyc429a242008-10-22 20:21:29 +020016 * Intel EP80579 (Tolapai)
17 * Intel 82801JI (ICH10)
Seth Heasleye30d9852010-10-31 21:06:59 +010018 * Intel 5/3400 Series (PCH)
Seth Heasley662cda82011-03-20 14:50:53 +010019 * Intel 6 Series (PCH)
Seth Heasleye30d9852010-10-31 21:06:59 +010020 * Intel Patsburg (PCH)
Seth Heasley662cda82011-03-20 14:50:53 +010021 * Intel DH89xxCC (PCH)
Seth Heasley6e2a8512011-05-24 20:58:49 +020022 * Intel Panther Point (PCH)
Seth Heasley062737f2012-03-26 21:47:19 +020023 * Intel Lynx Point (PCH)
James Ralston4a8f1dd2012-09-10 10:14:02 +020024 * Intel Lynx Point-LP (PCH)
Seth Heasleyc2db409c2013-01-30 15:25:32 +000025 * Intel Avoton (SOC)
James Ralstona3fc0ff2013-02-14 09:15:33 +000026 * Intel Wellsburg (PCH)
Seth Heasley1505c0b2013-06-19 16:59:57 -070027 * Intel Coleto Creek (PCH)
Jason Gastone07bc672007-10-13 23:56:31 +020028 Datasheets: Publicly available at the Intel website
Linus Torvalds1da177e2005-04-16 15:20:36 -070029
David Woodhouse55fee8d2010-10-31 21:07:00 +010030On Intel Patsburg and later chipsets, both the normal host SMBus controller
31and the additional 'Integrated Device Function' controllers are supported.
32
Linus Torvalds1da177e2005-04-16 15:20:36 -070033Authors:
Linus Torvalds1da177e2005-04-16 15:20:36 -070034 Mark Studebaker <mdsxyz123@yahoo.com>
Jean Delvare63420642008-01-27 18:14:50 +010035 Jean Delvare <khali@linux-fr.org>
Linus Torvalds1da177e2005-04-16 15:20:36 -070036
37
38Module Parameters
39-----------------
40
Jean Delvareadff6872010-05-21 18:40:54 +020041* disable_features (bit vector)
42Disable selected features normally supported by the device. This makes it
43possible to work around possible driver or hardware bugs if the feature in
44question doesn't work as intended for whatever reason. Bit values:
Daniel Kurtz636752b2012-07-24 14:13:58 +020045 0x01 disable SMBus PEC
46 0x02 disable the block buffer
47 0x08 disable the I2C block read functionality
48 0x10 don't use interrupts
Linus Torvalds1da177e2005-04-16 15:20:36 -070049
50
51Description
52-----------
53
54The ICH (properly known as the 82801AA), ICH0 (82801AB), ICH2 (82801BA),
Seth Heasleyc429a242008-10-22 20:21:29 +020055ICH3 (82801CA/CAM) and later devices (PCH) are Intel chips that are a part of
Linus Torvalds1da177e2005-04-16 15:20:36 -070056Intel's '810' chipset for Celeron-based PCs, '810E' chipset for
57Pentium-based PCs, '815E' chipset, and others.
58
59The ICH chips contain at least SEVEN separate PCI functions in TWO logical
60PCI devices. An output of lspci will show something similar to the
61following:
62
63 00:1e.0 PCI bridge: Intel Corporation: Unknown device 2418 (rev 01)
64 00:1f.0 ISA bridge: Intel Corporation: Unknown device 2410 (rev 01)
65 00:1f.1 IDE interface: Intel Corporation: Unknown device 2411 (rev 01)
66 00:1f.2 USB Controller: Intel Corporation: Unknown device 2412 (rev 01)
67 00:1f.3 Unknown class [0c05]: Intel Corporation: Unknown device 2413 (rev 01)
68
69The SMBus controller is function 3 in device 1f. Class 0c05 is SMBus Serial
70Controller.
71
Linus Torvalds1da177e2005-04-16 15:20:36 -070072The ICH chips are quite similar to Intel's PIIX4 chip, at least in the
73SMBus controller.
74
Linus Torvalds1da177e2005-04-16 15:20:36 -070075
76Process Call Support
77--------------------
78
79Not supported.
80
81
82I2C Block Read Support
83----------------------
84
Jean Delvare63420642008-01-27 18:14:50 +010085I2C block read is supported on the 82801EB (ICH5) and later chips.
Linus Torvalds1da177e2005-04-16 15:20:36 -070086
87
88SMBus 2.0 Support
89-----------------
90
91The 82801DB (ICH4) and later chips support several SMBus 2.0 features.
92
Jean Delvare099ab112007-02-13 22:09:00 +010093
Daniel Kurtz636752b2012-07-24 14:13:58 +020094Interrupt Support
95-----------------
96
97PCI interrupt support is supported on the 82801EB (ICH5) and later chips.
98
99
Jean Delvare099ab112007-02-13 22:09:00 +0100100Hidden ICH SMBus
101----------------
102
103If your system has an Intel ICH south bridge, but you do NOT see the
104SMBus device at 00:1f.3 in lspci, and you can't figure out any way in the
105BIOS to enable it, it means it has been hidden by the BIOS code. Asus is
106well known for first doing this on their P4B motherboard, and many other
107boards after that. Some vendor machines are affected as well.
108
109The first thing to try is the "i2c_ec" ACPI driver. It could be that the
110SMBus was hidden on purpose because it'll be driven by ACPI. If the
111i2c_ec driver works for you, just forget about the i2c-i801 driver and
112don't try to unhide the ICH SMBus. Even if i2c_ec doesn't work, you
113better make sure that the SMBus isn't used by the ACPI code. Try loading
114the "fan" and "thermal" drivers, and check in /proc/acpi/fan and
115/proc/acpi/thermal_zone. If you find anything there, it's likely that
116the ACPI is accessing the SMBus and it's safer not to unhide it. Only
117once you are certain that ACPI isn't using the SMBus, you can attempt
118to unhide it.
119
120In order to unhide the SMBus, we need to change the value of a PCI
121register before the kernel enumerates the PCI devices. This is done in
122drivers/pci/quirks.c, where all affected boards must be listed (see
123function asus_hides_smbus_hostbridge.) If the SMBus device is missing,
124and you think there's something interesting on the SMBus (e.g. a
125hardware monitoring chip), you need to add your board to the list.
126
127The motherboard is identified using the subvendor and subdevice IDs of the
128host bridge PCI device. Get yours with "lspci -n -v -s 00:00.0":
129
13000:00.0 Class 0600: 8086:2570 (rev 02)
131 Subsystem: 1043:80f2
132 Flags: bus master, fast devsel, latency 0
133 Memory at fc000000 (32-bit, prefetchable) [size=32M]
134 Capabilities: [e4] #09 [2106]
135 Capabilities: [a0] AGP version 3.0
136
137Here the host bridge ID is 2570 (82865G/PE/P), the subvendor ID is 1043
138(Asus) and the subdevice ID is 80f2 (P4P800-X). You can find the symbolic
139names for the bridge ID and the subvendor ID in include/linux/pci_ids.h,
140and then add a case for your subdevice ID at the right place in
141drivers/pci/quirks.c. Then please give it very good testing, to make sure
142that the unhidden SMBus doesn't conflict with e.g. ACPI.
143
144If it works, proves useful (i.e. there are usable chips on the SMBus)
145and seems safe, please submit a patch for inclusion into the kernel.
146
147Note: There's a useful script in lm_sensors 2.10.2 and later, named
148unhide_ICH_SMBus (in prog/hotplug), which uses the fakephp driver to
149temporarily unhide the SMBus without having to patch and recompile your
150kernel. It's very convenient if you just want to check if there's
151anything interesting on your hidden ICH SMBus.
152
153
Linus Torvalds1da177e2005-04-16 15:20:36 -0700154**********************
155The lm_sensors project gratefully acknowledges the support of Texas
156Instruments in the initial development of this driver.
157
158The lm_sensors project gratefully acknowledges the support of Intel in the
159development of SMBus 2.0 / ICH4 features of this driver.