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