From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: maciej.sosnowski@intel.com
Cc: haavard.skinnemoen@atmel.com, nicolas.ferre@atmel.com,
dan.j.williams@intel.com,
linux-arm-kernel@lists.arm.linux.org.uk,
patrice.vilchez@atmel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: at_hdmac: add DMA slave transfers
Date: Thu, 30 Jul 2009 00:16:32 +0900 (JST) [thread overview]
Message-ID: <20090730.001632.39159752.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <129600E5E5FB004392DDC3FB599660D7B2980817@irsmsx504.ger.corp.intel.com>
On Wed, 29 Jul 2009 14:05:17 +0100, "Sosnowski, Maciej" <maciej.sosnowski@intel.com> wrote:
> Atsushi Nemoto wrote:
> > On Mon, 27 Jul 2009 14:24:26 +0100, "Sosnowski, Maciej" <maciej.sosnowski@intel.com> wrote:
> >>>> Your atc_chain_complete() calls dma_unmap_xxx unless
> >>>> DMA_COMPL_SKIP_XXX_UNMAP specified. But atmel-mci driver does not set
> >>>> the flag on dma_async_tx_descriptor. I suppose one of them should be
> >>>> fixed.
> >>>
> >>> atmel-mci should definitely set that flag.
> >>>
> >>> Haavard
> >>
> >> I agree with Haavard.
> >
> > Then, what should dma driver do when client driver did not set these
> > flags? If it should call dma_unmap_sg(), the dma driver should keep
> > sg and direction somewhere...
>
> Well, what about BUG_ON?
Or prep_slave_sg can preset both DMA_COMPL_SKIP_XXX_UNMAP flags, or do
not unmap in dma driver for slave channel. I suppose latter is safe
and simple.
> > Also, calling dma_map_sg() in its prep_slave_sg function will not fit
> > for sound drivers, which use DMA buffers prepared in its framework.
>
> It looks like a need for one more flag: DMA_SKIP_MAP_SG.
> What do you think?
I do not think it is worth to introduce new flag.
As Dan said, pushing dma mapping responsibility to the client looks
simple and clean way for me.
---
Atsushi Nemoto
next prev parent reply other threads:[~2009-07-29 15:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 10:42 [PATCH 1/2 v2] dmaengine: at_hdmac: new driver for the Atmel AHB DMA Controller Nicolas Ferre
2009-06-26 10:42 ` [PATCH 2/2 v2] at91/dmaengine: integration of at_hdmac driver in at91sam9rl Nicolas Ferre
2009-06-27 15:06 ` [PATCH 1/2 v2] dmaengine: at_hdmac: new driver for the Atmel AHB DMA Controller Atsushi Nemoto
2009-07-01 15:30 ` Nicolas Ferre
2009-07-03 15:12 ` Atsushi Nemoto
2009-07-01 13:58 ` Nicolas Ferre
2009-07-02 0:58 ` Dan Williams
2009-07-02 1:18 ` Dan Williams
2009-07-03 12:59 ` Sosnowski, Maciej
2009-07-03 13:03 ` Nicolas Ferre
[not found] ` <0bb1aaf3fca441453fbb9296e1a35d7921d74467.1246641180.git.nicolas.ferre@atmel.com>
2009-07-03 17:24 ` [PATCH 1/2 v3] " Nicolas Ferre
2009-07-17 10:38 ` Nicolas Ferre
2009-07-18 16:01 ` Dan Williams
2009-07-21 8:33 ` Nicolas Ferre
2009-07-22 13:35 ` Sosnowski, Maciej
2009-07-22 18:04 ` [PATCH] dmaengine: at_hdmac: add DMA slave transfers Nicolas Ferre
2009-07-23 17:13 ` Dan Williams
2009-07-24 7:35 ` Nicolas Ferre
2009-07-24 13:29 ` Atsushi Nemoto
2009-07-24 14:10 ` Haavard Skinnemoen
2009-07-27 13:24 ` Sosnowski, Maciej
2009-07-28 15:13 ` Atsushi Nemoto
2009-07-29 13:05 ` Sosnowski, Maciej
2009-07-29 15:16 ` Atsushi Nemoto [this message]
2009-07-29 14:27 ` Dan Williams
2009-07-31 3:58 ` Atsushi Nemoto
2009-07-27 13:22 ` Sosnowski, Maciej
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=20090730.001632.39159752.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=dan.j.williams@intel.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=nicolas.ferre@atmel.com \
--cc=patrice.vilchez@atmel.com \
/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
all inboxes | Powered by JetHome®