From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] mmc: tmio-mmc: add DMA SG synchronisation
Date: Thu, 06 Feb 2014 12:01:16 +0000 [thread overview]
Message-ID: <52F3798C.4040906@codethink.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1401311248320.3234@axis700.grange>
On 31/01/14 11:54, Guennadi Liakhovetski wrote:
> According to the DMA API data has to be synchronised before starting
> a DMA transfer to device and after completing a DMA transfer from device.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
I've got 1/3 and 2/3, but not 3/3 ?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
prev parent reply other threads:[~2014-02-06 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.1401311237080.3234@axis700.grange>
[not found] ` <Pine.LNX.4.64.1401311249070.3234@axis700.grange>
2014-02-04 0:57 ` [PATCH 2/3] mmc: sh-mmcif: add DMA SG synchronisation Simon Horman
[not found] ` <Pine.LNX.4.64.1401311248320.3234@axis700.grange>
2014-02-04 0:57 ` [PATCH 1/3] mmc: tmio-mmc: " Simon Horman
2014-02-06 12:01 ` Ben Dooks [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=52F3798C.4040906@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).