From: Esben Haabendal <esben.haabendal@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-i2c@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Yuan Yao <yao.yuan@freescale.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Lucas Stach <l.stach@pengutronix.de>,
Phil Reid <preid@electromag.com.au>,
Clemens Gruber <clemens.gruber@pqgruber.com>,
Peter Rosin <peda@axentia.se>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] i2c: imx: Fix race condition in dma read
Date: Thu, 09 Aug 2018 13:57:08 +0200 [thread overview]
Message-ID: <87o9ebzraj.fsf@gmail.com> (raw)
In-Reply-To: <20180724075707.7wrqltjj54gjrl4y@pengutronix.de> ("Uwe Kleine-König"'s message of "Tue, 24 Jul 2018 09:57:07 +0200")
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:
> On Mon, Jul 09, 2018 at 11:43:02AM +0200, Esben Haabendal wrote:
>> 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 | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
>> index 39cfd98c7b23..d86f152176a4 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;
>> @@ -810,6 +807,11 @@ 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;
>> imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
>> + if (i2c_imx->dma && msgs->len >= DMA_THRESHOLD && !block_data) {
>> + temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
>> + temp |= I2CR_DMAEN;
>> + imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
>> + }
>
> Does this need to be a separate write to the I2CR register? Just before
> the if there is temp written to this register, so probably this can be
> changed to just:
>
> if (i2c_imx->dma && msgs->len >= DMA_THRESHOLD && !block_data)
> temp |= I2CR_DMAEN;
>
> when moved before up one line.
Sure, that is clearly better.
> I don't find documentation for the LS processors where this
> register is described though (and the imx family doesn't seem to support
> DMA for i2c).
Yes, unfortunately, I think the LS1021A reference manual requires NDA.
> Other than that this looks reasonable and warrants a
>
> Fixes: ce1a78840ff7 ("i2c: imx: add DMA support for freescale i2c driver")
I will add that.
/Esben
next prev parent reply other threads:[~2018-08-09 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180709094304.8814-1-esben.haabendal@gmail.com>
2018-07-09 9:43 ` [PATCH v2 1/4] i2c: imx: Fix reinit_completion() use Esben Haabendal
2018-07-23 18:08 ` Wolfram Sang
2018-07-09 9:43 ` [PATCH v2 2/4] i2c: imx: Fix race condition in dma read Esben Haabendal
2018-07-24 7:57 ` Uwe Kleine-König
2018-08-09 11:57 ` Esben Haabendal [this message]
2018-07-09 9:43 ` [PATCH v2 3/4] i2c: imx: Simplify stopped state tracking Esben Haabendal
2018-07-24 7:59 ` Uwe Kleine-König
2018-08-09 12:06 ` Esben Haabendal
2018-08-09 16:26 ` Uwe Kleine-König
2018-08-10 9:25 ` Esben Haabendal
2018-08-10 12:25 ` Uwe Kleine-König
2018-07-09 9:43 ` [PATCH v2 4/4] arm: dts: ls1021a: Enable I2C DMA support Esben Haabendal
2018-07-24 8:02 ` Uwe Kleine-König
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=87o9ebzraj.fsf@gmail.com \
--to=esben.haabendal@gmail.com \
--cc=clemens.gruber@pqgruber.com \
--cc=fabio.estevam@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=preid@electromag.com.au \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa+renesas@sang-engineering.com \
--cc=yao.yuan@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).