All of lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben.haabendal@gmail.com>
To: linux-i2c@vger.kernel.org
Cc: "Esben Haabendal" <eha@deif.com>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Lucas Stach" <l.stach@pengutronix.de>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Peter Rosin" <peda@axentia.se>,
	"Wei Jinhua" <wei.jinhua1@zte.com.cn>,
	"Phil Reid" <preid@electromag.com.au>,
	"Fabio Estevam" <fabio.estevam@nxp.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v3 1/3] i2c: imx: Fix race condition in dma read
Date: Thu,  9 Aug 2018 14:32:05 +0200	[thread overview]
Message-ID: <20180809123207.9732-2-esben.haabendal@gmail.com> (raw)
In-Reply-To: <20180809123207.9732-1-esben.haabendal@gmail.com>

From: Esben Haabendal <eha@deif.com>

This fixes a race condition, where the DMAEN bit ends up being set after
I2C slave has transmitted a byte following the dummy read.  When that
happens, an interrupt is generated instead, and no DMA request is generated
to kickstart the DMA read, and a timeout happens after DMA_TIMEOUT (1 sec).

Fixed by setting the DMAEN bit before the dummy read.

Signed-off-by: Esben Haabendal <eha@deif.com>
---
 drivers/i2c/busses/i2c-imx.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
index 498c5e891649..f7bd6c21da27 100644
--- a/drivers/i2c/busses/i2c-imx.c
+++ b/drivers/i2c/busses/i2c-imx.c
@@ -668,9 +668,6 @@ static int i2c_imx_dma_read(struct imx_i2c_struct *i2c_imx,
 	struct imx_i2c_dma *dma = i2c_imx->dma;
 	struct device *dev = &i2c_imx->adapter.dev;
 
-	temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
-	temp |= I2CR_DMAEN;
-	imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
 
 	dma->chan_using = dma->chan_rx;
 	dma->dma_transfer_dir = DMA_DEV_TO_MEM;
@@ -809,6 +806,8 @@ static int i2c_imx_read(struct imx_i2c_struct *i2c_imx, struct i2c_msg *msgs, bo
 	 */
 	if ((msgs->len - 1) || block_data)
 		temp &= ~I2CR_TXAK;
+	if (i2c_imx->dma && msgs->len >= DMA_THRESHOLD && !block_data)
+		temp |= I2CR_DMAEN;
 	imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
 	imx_i2c_read_reg(i2c_imx, IMX_I2C_I2DR); /* dummy read */
 
-- 
2.18.0


  reply	other threads:[~2018-08-09 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09 12:32 [PATCH v3 0/3] i2c: imx: Fix and enable DMA support for LS1021A Esben Haabendal
2018-08-09 12:32 ` Esben Haabendal [this message]
2018-08-16  8:27   ` [PATCH v3 1/3] i2c: imx: Fix race condition in dma read Uwe Kleine-König
2018-08-09 12:32 ` [PATCH v3 2/3] i2c: imx: Simplify stopped state tracking Esben Haabendal
2018-08-16  8:23   ` Uwe Kleine-König
2018-08-09 12:32 ` [PATCH v3 3/3] arm: dts: ls1021a: Enable I2C DMA support Esben Haabendal
2018-08-27  6:51   ` Shawn Guo
2018-08-16  8:04 ` [PATCH v3 0/3] i2c: imx: Fix and enable DMA support for LS1021A Esben Haabendal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180809123207.9732-2-esben.haabendal@gmail.com \
    --to=esben.haabendal@gmail.com \
    --cc=eha@deif.com \
    --cc=fabio.estevam@nxp.com \
    --cc=l.stach@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=preid@electromag.com.au \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wei.jinhua1@zte.com.cn \
    --cc=wsa+renesas@sang-engineering.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.