2005-04-17 06:20:36 +08:00
|
|
|
Kernel driver i2c-i801
|
|
|
|
|
|
|
|
Supported adapters:
|
|
|
|
* Intel 82801AA and 82801AB (ICH and ICH0 - part of the
|
|
|
|
'810' and '810E' chipsets)
|
|
|
|
* Intel 82801BA (ICH2 - part of the '815E' chipset)
|
|
|
|
* Intel 82801CA/CAM (ICH3)
|
2007-07-12 20:12:31 +08:00
|
|
|
* Intel 82801DB (ICH4) (HW PEC supported)
|
|
|
|
* Intel 82801EB/ER (ICH5) (HW PEC supported)
|
2005-04-17 06:20:36 +08:00
|
|
|
* Intel 6300ESB
|
|
|
|
* Intel 82801FB/FR/FW/FRW (ICH6)
|
2006-12-11 04:21:31 +08:00
|
|
|
* Intel 82801G (ICH7)
|
|
|
|
* Intel 631xESB/632xESB (ESB2)
|
|
|
|
* Intel 82801H (ICH8)
|
2008-02-25 03:03:42 +08:00
|
|
|
* Intel 82801I (ICH9)
|
2008-10-23 02:21:29 +08:00
|
|
|
* Intel EP80579 (Tolapai)
|
|
|
|
* Intel 82801JI (ICH10)
|
2010-11-01 04:06:59 +08:00
|
|
|
* Intel 5/3400 Series (PCH)
|
2011-03-20 21:50:53 +08:00
|
|
|
* Intel 6 Series (PCH)
|
2010-11-01 04:06:59 +08:00
|
|
|
* Intel Patsburg (PCH)
|
2011-03-20 21:50:53 +08:00
|
|
|
* Intel DH89xxCC (PCH)
|
2011-05-25 02:58:49 +08:00
|
|
|
* Intel Panther Point (PCH)
|
2012-03-27 03:47:19 +08:00
|
|
|
* Intel Lynx Point (PCH)
|
2007-10-14 05:56:31 +08:00
|
|
|
Datasheets: Publicly available at the Intel website
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2010-11-01 04:07:00 +08:00
|
|
|
On Intel Patsburg and later chipsets, both the normal host SMBus controller
|
|
|
|
and the additional 'Integrated Device Function' controllers are supported.
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
Authors:
|
|
|
|
Mark Studebaker <mdsxyz123@yahoo.com>
|
2008-01-28 01:14:50 +08:00
|
|
|
Jean Delvare <khali@linux-fr.org>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
Module Parameters
|
|
|
|
-----------------
|
|
|
|
|
2010-05-22 00:40:54 +08:00
|
|
|
* disable_features (bit vector)
|
|
|
|
Disable selected features normally supported by the device. This makes it
|
|
|
|
possible to work around possible driver or hardware bugs if the feature in
|
|
|
|
question doesn't work as intended for whatever reason. Bit values:
|
i2c-i801: Enable IRQ for SMBus transactions
Add a new 'feature' to i2c-i801 to enable using PCI interrupts.
When the feature is enabled, then an isr is installed for the device's
PCI IRQ.
An I2C/SMBus transaction is always terminated by one of the following
interrupt sources: FAILED, BUS_ERR, DEV_ERR, or on success: INTR.
When the isr fires for one of these cases, it sets the ->status variable
and wakes up the waitq. The waitq then saves off the status code, and
clears ->status (in preparation for some future transaction).
The SMBus controller generates an INTR irq at the end of each
transaction where INTREN was set in the HST_CNT register.
No locking is needed around accesses to priv->status since all writes to
it are serialized: it is only ever set once in the isr at the end of a
transaction, and cleared while no interrupts can occur. In addition, the
I2C adapter lock guarantees that entire I2C transactions for a single
adapter are always serialized.
For this patch, the INTREN bit is set only for SMBus block, byte and word
transactions, but not for I2C reads or writes. The use of the DS
(BYTE_DONE) interrupt with byte-by-byte I2C transactions is implemented in
a subsequent patch.
The interrupt feature has only been enabled for COUGARPOINT hardware.
In addition, it is disabled if SMBus is using the SMI# interrupt.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
2012-07-24 20:13:58 +08:00
|
|
|
0x01 disable SMBus PEC
|
|
|
|
0x02 disable the block buffer
|
|
|
|
0x08 disable the I2C block read functionality
|
|
|
|
0x10 don't use interrupts
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
Description
|
|
|
|
-----------
|
|
|
|
|
|
|
|
The ICH (properly known as the 82801AA), ICH0 (82801AB), ICH2 (82801BA),
|
2008-10-23 02:21:29 +08:00
|
|
|
ICH3 (82801CA/CAM) and later devices (PCH) are Intel chips that are a part of
|
2005-04-17 06:20:36 +08:00
|
|
|
Intel's '810' chipset for Celeron-based PCs, '810E' chipset for
|
|
|
|
Pentium-based PCs, '815E' chipset, and others.
|
|
|
|
|
|
|
|
The ICH chips contain at least SEVEN separate PCI functions in TWO logical
|
|
|
|
PCI devices. An output of lspci will show something similar to the
|
|
|
|
following:
|
|
|
|
|
|
|
|
00:1e.0 PCI bridge: Intel Corporation: Unknown device 2418 (rev 01)
|
|
|
|
00:1f.0 ISA bridge: Intel Corporation: Unknown device 2410 (rev 01)
|
|
|
|
00:1f.1 IDE interface: Intel Corporation: Unknown device 2411 (rev 01)
|
|
|
|
00:1f.2 USB Controller: Intel Corporation: Unknown device 2412 (rev 01)
|
|
|
|
00:1f.3 Unknown class [0c05]: Intel Corporation: Unknown device 2413 (rev 01)
|
|
|
|
|
|
|
|
The SMBus controller is function 3 in device 1f. Class 0c05 is SMBus Serial
|
|
|
|
Controller.
|
|
|
|
|
|
|
|
The ICH chips are quite similar to Intel's PIIX4 chip, at least in the
|
|
|
|
SMBus controller.
|
|
|
|
|
|
|
|
|
|
|
|
Process Call Support
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
Not supported.
|
|
|
|
|
|
|
|
|
|
|
|
I2C Block Read Support
|
|
|
|
----------------------
|
|
|
|
|
2008-01-28 01:14:50 +08:00
|
|
|
I2C block read is supported on the 82801EB (ICH5) and later chips.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
SMBus 2.0 Support
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
The 82801DB (ICH4) and later chips support several SMBus 2.0 features.
|
|
|
|
|
2007-02-14 05:09:00 +08:00
|
|
|
|
i2c-i801: Enable IRQ for SMBus transactions
Add a new 'feature' to i2c-i801 to enable using PCI interrupts.
When the feature is enabled, then an isr is installed for the device's
PCI IRQ.
An I2C/SMBus transaction is always terminated by one of the following
interrupt sources: FAILED, BUS_ERR, DEV_ERR, or on success: INTR.
When the isr fires for one of these cases, it sets the ->status variable
and wakes up the waitq. The waitq then saves off the status code, and
clears ->status (in preparation for some future transaction).
The SMBus controller generates an INTR irq at the end of each
transaction where INTREN was set in the HST_CNT register.
No locking is needed around accesses to priv->status since all writes to
it are serialized: it is only ever set once in the isr at the end of a
transaction, and cleared while no interrupts can occur. In addition, the
I2C adapter lock guarantees that entire I2C transactions for a single
adapter are always serialized.
For this patch, the INTREN bit is set only for SMBus block, byte and word
transactions, but not for I2C reads or writes. The use of the DS
(BYTE_DONE) interrupt with byte-by-byte I2C transactions is implemented in
a subsequent patch.
The interrupt feature has only been enabled for COUGARPOINT hardware.
In addition, it is disabled if SMBus is using the SMI# interrupt.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
2012-07-24 20:13:58 +08:00
|
|
|
Interrupt Support
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
PCI interrupt support is supported on the 82801EB (ICH5) and later chips.
|
|
|
|
|
|
|
|
|
2007-02-14 05:09:00 +08:00
|
|
|
Hidden ICH SMBus
|
|
|
|
----------------
|
|
|
|
|
|
|
|
If your system has an Intel ICH south bridge, but you do NOT see the
|
|
|
|
SMBus device at 00:1f.3 in lspci, and you can't figure out any way in the
|
|
|
|
BIOS to enable it, it means it has been hidden by the BIOS code. Asus is
|
|
|
|
well known for first doing this on their P4B motherboard, and many other
|
|
|
|
boards after that. Some vendor machines are affected as well.
|
|
|
|
|
|
|
|
The first thing to try is the "i2c_ec" ACPI driver. It could be that the
|
|
|
|
SMBus was hidden on purpose because it'll be driven by ACPI. If the
|
|
|
|
i2c_ec driver works for you, just forget about the i2c-i801 driver and
|
|
|
|
don't try to unhide the ICH SMBus. Even if i2c_ec doesn't work, you
|
|
|
|
better make sure that the SMBus isn't used by the ACPI code. Try loading
|
|
|
|
the "fan" and "thermal" drivers, and check in /proc/acpi/fan and
|
|
|
|
/proc/acpi/thermal_zone. If you find anything there, it's likely that
|
|
|
|
the ACPI is accessing the SMBus and it's safer not to unhide it. Only
|
|
|
|
once you are certain that ACPI isn't using the SMBus, you can attempt
|
|
|
|
to unhide it.
|
|
|
|
|
|
|
|
In order to unhide the SMBus, we need to change the value of a PCI
|
|
|
|
register before the kernel enumerates the PCI devices. This is done in
|
|
|
|
drivers/pci/quirks.c, where all affected boards must be listed (see
|
|
|
|
function asus_hides_smbus_hostbridge.) If the SMBus device is missing,
|
|
|
|
and you think there's something interesting on the SMBus (e.g. a
|
|
|
|
hardware monitoring chip), you need to add your board to the list.
|
|
|
|
|
|
|
|
The motherboard is identified using the subvendor and subdevice IDs of the
|
|
|
|
host bridge PCI device. Get yours with "lspci -n -v -s 00:00.0":
|
|
|
|
|
|
|
|
00:00.0 Class 0600: 8086:2570 (rev 02)
|
|
|
|
Subsystem: 1043:80f2
|
|
|
|
Flags: bus master, fast devsel, latency 0
|
|
|
|
Memory at fc000000 (32-bit, prefetchable) [size=32M]
|
|
|
|
Capabilities: [e4] #09 [2106]
|
|
|
|
Capabilities: [a0] AGP version 3.0
|
|
|
|
|
|
|
|
Here the host bridge ID is 2570 (82865G/PE/P), the subvendor ID is 1043
|
|
|
|
(Asus) and the subdevice ID is 80f2 (P4P800-X). You can find the symbolic
|
|
|
|
names for the bridge ID and the subvendor ID in include/linux/pci_ids.h,
|
|
|
|
and then add a case for your subdevice ID at the right place in
|
|
|
|
drivers/pci/quirks.c. Then please give it very good testing, to make sure
|
|
|
|
that the unhidden SMBus doesn't conflict with e.g. ACPI.
|
|
|
|
|
|
|
|
If it works, proves useful (i.e. there are usable chips on the SMBus)
|
|
|
|
and seems safe, please submit a patch for inclusion into the kernel.
|
|
|
|
|
|
|
|
Note: There's a useful script in lm_sensors 2.10.2 and later, named
|
|
|
|
unhide_ICH_SMBus (in prog/hotplug), which uses the fakephp driver to
|
|
|
|
temporarily unhide the SMBus without having to patch and recompile your
|
|
|
|
kernel. It's very convenient if you just want to check if there's
|
|
|
|
anything interesting on your hidden ICH SMBus.
|
|
|
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
**********************
|
|
|
|
The lm_sensors project gratefully acknowledges the support of Texas
|
|
|
|
Instruments in the initial development of this driver.
|
|
|
|
|
|
|
|
The lm_sensors project gratefully acknowledges the support of Intel in the
|
|
|
|
development of SMBus 2.0 / ICH4 features of this driver.
|