From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Esben Haabendal <esben.haabendal@gmail.com>
Cc: linux-i2c@vger.kernel.org, Esben Haabendal <eha@deif.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Lucas Stach <l.stach@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Wei Jinhua <wei.jinhua1@zte.com.cn>,
Phil Reid <preid@electromag.com.au>,
Peter Rosin <peda@axentia.se>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] i2c: imx: Simplify stopped state tracking
Date: Thu, 16 Aug 2018 10:23:48 +0200 [thread overview]
Message-ID: <20180816082348.wei7fnbqbzowe6er@pengutronix.de> (raw)
In-Reply-To: <20180809123207.9732-3-esben.haabendal@gmail.com>
On Thu, Aug 09, 2018 at 02:32:06PM +0200, Esben Haabendal wrote:
> From: Esben Haabendal <eha@deif.com>
>
> Always update the stopped state when busy status have been checked.
> This is identical to what was done before, with the exception of error
> handling.
> Without this change, some errors cause the stopped state to be left in
> incorrect state in i2c_imx_stop(), i2c_imx_dma_read(), i2c_imx_read() and
> i2c_imx_xfer().
>
> Signed-off-by: Esben Haabendal <eha@deif.com>
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2018-08-16 8:24 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 ` [PATCH v3 1/3] i2c: imx: Fix race condition in dma read Esben Haabendal
2018-08-16 8:27 ` 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 [this message]
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=20180816082348.wei7fnbqbzowe6er@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=eha@deif.com \
--cc=esben.haabendal@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=preid@electromag.com.au \
--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.