[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140407151107.GL19349@intel.com>
Date: Mon, 7 Apr 2014 18:11:08 +0300
From: "Westerberg, Mika" <mika.westerberg@...el.com>
To: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc: "Du, Wenkai" <wenkai.du@...el.com>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
Wolfram Sang <wsa@...-dreams.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] i2c-designware: Mask interrupts during i2c controller
enable
On Mon, Apr 07, 2014 at 03:42:52PM +0100, One Thousand Gnomes wrote:
> > I had to check BYT specs about that and I couldn't find if it does
> > posted-writes.
>
> Then I would assume it does unless you can find a hardware engineer to
> sign a statement in blood to that effect 8)
Fair enough.
> > Actually the following patch should fix the problem as well. Just move the
> > HW enable to happen last. That way we can make sure that there is a valid
> > interrupt mask programmed before the controller is enabled.
>
> This fixes the init case, it doesn't fix the question about returning
> from the IRQ before the mask write takes effect and thus taking another
> interrupt.
Do you think we can fix it with adding a dummy read right after write to
the mask register, like the snippet below?
diff --git a/drivers/i2c/busses/i2c-designware-core.c b/drivers/i2c/busses/i2c-designware-core.c
index 14c4b30d4ccc..ff9090381d8b 100644
--- a/drivers/i2c/busses/i2c-designware-core.c
+++ b/drivers/i2c/busses/i2c-designware-core.c
@@ -535,6 +535,7 @@ i2c_dw_xfer_msg(struct dw_i2c_dev *dev)
intr_mask = 0;
dw_writel(dev, intr_mask, DW_IC_INTR_MASK);
+ dw_readl(dev, DW_IC_INTR_MASK);
}
static void
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists