summaryrefslogtreecommitdiff
path: root/drivers/i2c
diff options
context:
space:
mode:
authorFei Yang <fei.yang@intel.com>2011-11-07 14:40:33 -0800
committermgross <mark.gross@intel.com>2011-11-09 13:21:22 -0800
commit9767412bc65af3c4bc9181d682995d31c9ac312d (patch)
treed4084f67d84b615b88289fbdc29d701c9e873204 /drivers/i2c
parent9433e2e14a5c4d3ed6ed7245a15af7902183ff74 (diff)
downloadkernel-mfld-blackbay-9767412bc65af3c4bc9181d682995d31c9ac312d.tar.gz
kernel-mfld-blackbay-9767412bc65af3c4bc9181d682995d31c9ac312d.tar.bz2
kernel-mfld-blackbay-9767412bc65af3c4bc9181d682995d31c9ac312d.zip
I2C: the i2c controller is expected to be enabled when there is a
transfer request. Runtiem resume should only power on and initialize the device to a known default state. Enabling the device on runtime resume would trigger a spurious interrupt even when there is no function driver acutally using the i2c device, thus causing a kernel panic as dev->msgs == NULL. Change-Id: I708e0d532aa0cdd7cb5161d8643dd5186d193243 Signed-off-by: Fei Yang <fei.yang@intel.com> Reviewed-on: http://android.intel.com:8080/23503 Reviewed-by: Gross, Mark <mark.gross@intel.com> Tested-by: Gross, Mark <mark.gross@intel.com>
Diffstat (limited to 'drivers/i2c')
-rw-r--r--drivers/i2c/busses/i2c-designware-pcidrv.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/i2c/busses/i2c-designware-pcidrv.c b/drivers/i2c/busses/i2c-designware-pcidrv.c
index 9e89e7313d6..837dd223465 100644
--- a/drivers/i2c/busses/i2c-designware-pcidrv.c
+++ b/drivers/i2c/busses/i2c-designware-pcidrv.c
@@ -182,7 +182,6 @@ static int i2c_dw_pci_resume(struct device *dev)
pci_restore_state(pdev);
i2c_dw_init(i2c);
- i2c_dw_enable(i2c);
return 0;
}