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