From: Apelete Seketeli <apelete@seketeli.net>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Chris Ball <chris@printf.net>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
Alex Smith <alex.smith@imgtec.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/2] mmc: jz4740: prepare next dma transfer in parallel with current transfer
Date: Tue, 12 Aug 2014 20:10:17 +0200 [thread overview]
Message-ID: <20140812181017.GA28666@amegan> (raw)
In-Reply-To: <CAPDyKFo4q+YWDgezZPqAHet0sBPE5WvnZzm00MHdf-+jZAY93Q@mail.gmail.com>
On Tue, Aug-12-2014 at 06:22:04 PM +0200, Ulf Hansson wrote:
> On 21 July 2014 06:37, Apelete Seketeli <apelete@seketeli.net> wrote:
> > Make use of the MMC asynchronous request capability to prepare the
> > next DMA transfer request in parallel with the current transfer.
> > This is done by adding pre-request and post-request callbacks that are
> > used by the MMC framework during an active data transfer.
> >
> > It should help reduce the impact of DMA preparation overhead on the SD
> > card performance.
> >
> > Signed-off-by: Apelete Seketeli <apelete@seketeli.net>
>
> Thanks! Queued for 3.18.
W00t \o/ <-- hacker joy. Thank you :).
Just out of curiosity, why not pulling these for 3.17 ?
Cheers.
--
Apelete
next prev parent reply other threads:[~2014-08-12 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 4:37 [PATCH v6 0/2] Use DMA for data transfers in JZ4740 MMC driver Apelete Seketeli
2014-07-21 4:37 ` [PATCH v6 1/2] mmc: jz4740: add dma infrastructure for data transfers Apelete Seketeli
2014-08-12 16:21 ` Ulf Hansson
2014-07-21 4:37 ` [PATCH v6 2/2] mmc: jz4740: prepare next dma transfer in parallel with current transfer Apelete Seketeli
2014-08-12 16:22 ` Ulf Hansson
2014-08-12 18:10 ` Apelete Seketeli [this message]
2014-08-12 20:15 ` Ulf Hansson
2014-08-12 18:12 ` Chris Ball
2014-08-12 20:02 ` Apelete Seketeli
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=20140812181017.GA28666@amegan \
--to=apelete@seketeli.net \
--cc=alex.smith@imgtec.com \
--cc=chris@printf.net \
--cc=hsweeten@visionengravers.com \
--cc=lars@metafoo.de \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yongjun_wei@trendmicro.com.cn \
/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