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 15:28:20 -0600 [thread overview]
Message-ID: <492B1C74.9070700@freescale.com> (raw)
In-Reply-To: <OF5164841E.9891D22C-ON8825750B.0074160D-8825750B.007587B6@selinc.com>
Bruce_Leonard@selinc.com wrote:
> Maybe (with you clarification) this is starting to make sense. It doesn't
> matter if the "src" is host memory or PCI space. What the "src" and it's
> DMA_TO_DEVICE mapping is saying to the kernel is "this data needs to be
> moved into the DMA engine", while the "dest" and it's DMA_FROM_DEIVCE
> mapping is telling the kernel "this data needs to be moved from the DMA
> engine".
Right.
-Scott
next prev parent reply other threads:[~2008-11-24 21:28 UTC|newest]
Thread overview: 9+ 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
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 [this message]
2008-11-24 21:35 ` 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=492B1C74.9070700@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox