From: Scott Wood <scottwood@freescale.com>
To: Bruce_Leonard@selinc.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Async DMA question regarding dma_async_memcpy_buf_to_buf
Date: Mon, 24 Nov 2008 13:47:09 -0600 [thread overview]
Message-ID: <492B04BD.5060402@freescale.com> (raw)
In-Reply-To: <OFDD6E2111.A0808007-ON8825750B.0067D813-8825750B.0067EC1C@selinc.com>
Bruce_Leonard@selinc.com wrote:
> The hardware doesn't care (I'm using an MPC8347E), as far as the DMA
> engine is concerned these are just addresses. All of this goes to cache
> coherency. The map/unmap functions are supposed to ensure that data is
> copied and caches flushed at the right times to ensure cache coherency. So
>
> the question is this; is the dma_async_memcpy_buf_to_buf() function
> intended to be bi-directional and is it safe to pass it a 'src' pointer
> that's actually coming from the device, or does there need to be a second
> function for doing a copy from the device to the CPU?
The "device" is the DMA engine, thus src is inherently going to the
device and dest is inherently coming from the device.
-Scott
next prev parent reply other threads:[~2008-11-24 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 18:55 Async DMA question regarding dma_async_memcpy_buf_to_buf Bruce_Leonard
2008-11-24 19:47 ` Scott Wood [this message]
2008-11-24 20:10 ` Bruce_Leonard
2008-11-24 20:16 ` Scott Wood
2008-11-24 20:49 ` Bruce_Leonard
2008-11-24 21:00 ` Scott Wood
2008-11-24 21:23 ` Bruce_Leonard
2008-11-24 21:28 ` Scott Wood
2008-11-24 21:35 ` Bruce_Leonard
-- strict thread matches above, loose matches on Subject: below --
2008-11-22 1:00 Bruce_Leonard
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=492B04BD.5060402@freescale.com \
--to=scottwood@freescale.com \
--cc=Bruce_Leonard@selinc.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.