From: "Dan Williams" <dan.j.williams@intel.com>
To: "Zhang Wei-r63237" <Wei.Zhang@freescale.com>
Cc: shannon.nelson@intel.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, paulus@samba.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 3/4] Extend the DMA-engine API.
Date: Wed, 11 Jul 2007 09:56:31 -0700 [thread overview]
Message-ID: <e9c3a7c20707110956r5ea91fd1q1d0b33b9583fe91c@mail.gmail.com> (raw)
In-Reply-To: <46B96294322F7D458F9648B60E15112C6F3CED@zch01exm26.fsl.freescale.net>
On 7/11/07, Zhang Wei-r63237 <Wei.Zhang@freescale.com> wrote:
> Hi, Dan,
>
> Do you mention here: http://marc.info/?l=linux-raid&m=118290909614463&w=2 ?
> I see the async_tx is located at crypto/ of the above page, but my patch is for DMA engine in drivers/dma and for DMA engine driver.
>
> Thanks!
> Wei.
Hi Wei,
I was referring to:
http://marc.info/?l=linux-raid&m=118290909528910&w=2
async_tx is an api that exploits the raw capabilities of the new
dmaengine interface. For your case when the existing api calls do not
provide the proper interface you can open code something like the
following:
tx = dev->device_prep_dma_<operation>(chan, len, int_flag)
tx->tx_set_src(dma_addr_t, tx, index /* for multi-source ops */)
tx->tx_set_dest(dma_addr_t, tx, index)
tx->tx_submit(tx)
The expectation is that the most common usages of dmaengines will use
async_tx calls, or the 'dma_async_memcpy_foo_to_bar' helper routines.
--
Dan
next prev parent reply other threads:[~2007-07-11 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 9:45 [PATCH 3/4] Extend the DMA-engine API Zhang Wei
2007-07-10 15:46 ` Randy Dunlap
2007-07-10 18:41 ` Dan Williams
2007-07-11 7:39 ` Zhang Wei-r63237
2007-07-11 16:56 ` Dan Williams [this message]
2007-07-12 6:31 ` Zhang Wei-r63237
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=e9c3a7c20707110956r5ea91fd1q1d0b33b9583fe91c@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=Wei.Zhang@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=shannon.nelson@intel.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;
as well as URLs for NNTP newsgroup(s).