From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Roland Stigge <stigge@antcom.de>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
dwmw2@infradead.org, kevin.wells@nxp.com, srinivas.bakki@nxp.com,
linux-arm-kernel@lists.infradead.org, hechtb@googlemail.com,
lars@metafoo.de, b32955@freescale.com, leiwen@marvell.com,
dedekind1@gmail.com
Subject: Re: [PATCH v4] MTD: LPC32xx SLC NAND driver
Date: Sun, 3 Jun 2012 21:37:49 +0100 [thread overview]
Message-ID: <20120603203749.GD23368@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4FCBBFD4.9090401@antcom.de>
On Sun, Jun 03, 2012 at 09:49:40PM +0200, Roland Stigge wrote:
> Hi!
>
> Thanks for the suggestions!
>
> On 03/06/12 21:09, Russell King - ARM Linux wrote:
> >> + dma_async_issue_pending(host->dma_chan);
> >> +
> >> + wait_for_completion_timeout(&host->comp, msecs_to_jiffies(1000));
> >
> > What about unmapping the buffer upon completion?
>
> OK - by not specifying DMA_COMPL_SKIP_*_UNMAP in flags, I was thinking
> that this happens somehow magically. ;-) But maybe I was just confused.
Slave transfers should never be automatically unmapped by the DMA engine
driver.
prev parent reply other threads:[~2012-06-03 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 18:38 [PATCH v4] MTD: LPC32xx SLC NAND driver Roland Stigge
[not found] ` <1338748689-29645-1-git-send-email-stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
2012-06-03 19:09 ` Russell King - ARM Linux
2012-06-03 19:27 ` PLEASE, REMOVE MY EMAIL ADDRESS FROM ITS LIST William F.
2012-06-03 19:33 ` Russell King - ARM Linux
2012-06-03 23:07 ` William F.
2012-06-03 19:49 ` [PATCH v4] MTD: LPC32xx SLC NAND driver Roland Stigge
2012-06-03 20:37 ` Russell King - ARM Linux [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=20120603203749.GD23368@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=hechtb@googlemail.com \
--cc=kevin.wells@nxp.com \
--cc=lars@metafoo.de \
--cc=leiwen@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=srinivas.bakki@nxp.com \
--cc=stigge@antcom.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).