From: Wolfram Sang <wsa@the-dreams.de>
To: Esben Haabendal <esben.haabendal@gmail.com>
Cc: linux-i2c@vger.kernel.org, Esben Haabendal <eha@deif.com>,
Shawn Guo <shawnguo@kernel.org>,
kernel@pengutronix.de, NXP Linux Team <linux-imx@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] arm: dts: ls1021a: Enable I2C DMA support
Date: Mon, 20 Aug 2018 11:15:31 +0200 [thread overview]
Message-ID: <20180820091531.komc6ypyybnq22nw@ninjato> (raw)
In-Reply-To: <20180816084315.7857-4-esben.haabendal@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
On Thu, Aug 16, 2018 at 10:43:14AM +0200, Esben Haabendal wrote:
> From: Esben Haabendal <eha@deif.com>
>
> Gives substantial performance improvement for transfers larger than 16
> bytes (DMA_THRESHOLD). Smaller transfers are unaffected.
>
> Signed-off-by: Esben Haabendal <eha@deif.com>
This needs to go via arm-soc. The two other patches will be in v4.19
with my pull request later this week.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-20 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180816084315.7857-1-esben.haabendal@gmail.com>
2018-08-16 8:43 ` [PATCH v4 1/3] i2c: imx: Fix race condition in dma read Esben Haabendal
2018-08-20 9:13 ` Wolfram Sang
2018-08-16 8:43 ` [PATCH v4 2/3] i2c: imx: Simplify stopped state tracking Esben Haabendal
2018-08-20 9:14 ` Wolfram Sang
2018-08-20 9:20 ` Esben Haabendal
2018-08-16 8:43 ` [PATCH v4 3/3] arm: dts: ls1021a: Enable I2C DMA support Esben Haabendal
2018-08-16 15:50 ` Uwe Kleine-König
2018-08-20 9:15 ` Wolfram Sang [this message]
2018-08-20 9:23 ` Esben Haabendal
2018-08-20 11:14 ` Wolfram Sang
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=20180820091531.komc6ypyybnq22nw@ninjato \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=eha@deif.com \
--cc=esben.haabendal@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
/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).