summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVic Yang <victoryang@google.com>2015-01-15 15:08:42 -0800
committerChromeOS Commit Bot <chromeos-commit-bot@chromium.org>2015-01-17 01:00:07 +0000
commit1d0a7f8713902f68e9aab35e1a0284ff7b9b75cd (patch)
tree39a11f91cd7fe868652ee7d85832fff4fc6da824
parent7e8567fd5ecba1dbac6773667b66a58cbd9b85b2 (diff)
downloadchrome-ec-1d0a7f8713902f68e9aab35e1a0284ff7b9b75cd.tar.gz
mec1322: Fix I2C interrupt bug
On boot, we shouldn't enabled I2C interrupt. The interrupt is only enabled when we are waiting for data or transfer completion. BRANCH=None BUG=chrome-os-partner:35308 TEST=Boot on Glower and do i2cscan. Change-Id: I534302ac057f2592f52d80d85cee66c35c6121d2 Signed-off-by: Vic Yang <victoryang@google.com> Reviewed-on: https://chromium-review.googlesource.com/241113 Tested-by: Vic Yang <victoryang@chromium.org> Reviewed-by: Randall Spangler <rspangler@chromium.org> Commit-Queue: Vic Yang <victoryang@chromium.org>
-rw-r--r--chip/mec1322/i2c.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/chip/mec1322/i2c.c b/chip/mec1322/i2c.c
index 038d4763d9..372ed20130 100644
--- a/chip/mec1322/i2c.c
+++ b/chip/mec1322/i2c.c
@@ -88,7 +88,6 @@ static void configure_port(int port, int kbps)
MEC1322_I2C_CONFIG(port) |= 1 << 29; /* ENIDI */
MEC1322_INT_ENABLE(12) |= (1 << port);
MEC1322_INT_BLK_EN |= 1 << 12;
- task_enable_irq(MEC1322_IRQ_I2C_0 + port);
}
static void reset_port(int port)