From: Esben Haabendal <esben.haabendal@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/3] i2c: imx: Fix and enable DMA support for LS1021A
Date: Thu, 16 Aug 2018 10:04:28 +0200 [thread overview]
Message-ID: <87in4ag2k3.fsf@gmail.com> (raw)
In-Reply-To: <20180809123207.9732-1-esben.haabendal@gmail.com> (Esben Haabendal's message of "Thu, 9 Aug 2018 14:32:04 +0200")
Esben Haabendal <esben.haabendal@gmail.com> writes:
> From: Esben Haabendal <eha@deif.com>
>
> This patch series fixes two race conditions and minor issues with tracking
> the stopped state when something goes wrong.
>
> With that in place, DMA support works with NXP LS1021A, so it is enabled in
> the last patch.
>
> Changes in v3:
>
> * Rebased to v4.18-rc8, dropping patch 1/4 which have been merged
> * Avoid unnecessary register write in patch 2/3
> * Removed unneeded braces in patch 3/3
>
> Changes in v2:
>
> * Fixed speling mistake in commit message
> * Rebased to v4.18-rc4
>
> Esben Haabendal (3):
> i2c: imx: Fix race condition in dma read
> i2c: imx: Simplify stopped state tracking
> arm: dts: ls1021a: Enable I2C DMA support
>
> arch/arm/boot/dts/ls1021a.dtsi | 6 ++++++
> drivers/i2c/busses/i2c-imx.c | 20 +++++++++-----------
> 2 files changed, 15 insertions(+), 11 deletions(-)
Uwe, will you take a look at this v3 of the series? I made all changes
you requested with v2.
/Esben
prev parent reply other threads:[~2018-08-16 11:01 UTC|newest]
Thread overview: 4+ 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 3/3] arm: dts: ls1021a: Enable I2C DMA support Esben Haabendal
2018-08-27 6:51 ` Shawn Guo
2018-08-16 8:04 ` Esben Haabendal [this message]
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=87in4ag2k3.fsf@gmail.com \
--to=esben.haabendal@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).