From: Phil Nitschke <philn@avalon.com.au>
To: linuxppc-embedded@ozlabs.org
Subject: DMA buffer synchronisation
Date: Tue, 25 Jul 2006 18:39:54 +0930 [thread overview]
Message-ID: <1153818594.10422.50.camel@lamorak.int.avalon.com.au> (raw)
Hi,
I'm transferring data using DMA from a custom PCI device memory into
RAM. Can someone advise me on the correct buffer synchronisation
strategy for the following 3 scenarios:
Assuming I have three buffers, buf_A, and buf_B, both created using
dma_alloc_noncoherent(NULL, 32 * PAGE_SIZE, ...), and buf_C (much
larger), remapped into the processor's virtual address space using
ioremap(), and 'n' is the number of bytes to copy using DMA channel
'dmanr', ...
1/. DMA copy from PCI device memory into buf_B:
/* ...prepare DMA engine, then: */
WARN_ON(buf_B != L1_CACHE_ALIGN(buf_B));
dma_sync_single_range_for_device(NULL, buf_B, 0, n, DMA_FROM_DEVICE);
mv64x6x_enable_dma(dmanr);
wait_for_completion_interruptible_timeout(...)
dma_sync_single_range_for_cpu(NULL, buf_B, 0, n, DMA_FROM_DEVICE);
2/. DMA copy from buf_A to buf_B (same as above, except now sync the src
buffer prior to DMA):
/* ...prepare DMA engine, check buffer alignment (x2), then: */
dma_sync_single_range_for_device(NULL, buf_A, 0, n, DMA_TO_DEVICE);
dma_sync_single_range_for_device(NULL, buf_B, 0, n, DMA_FROM_DEVICE);
mv64x6x_enable_dma(dmanr);
wait_for_completion_interruptible_timeout(...)
dma_sync_single_range_for_cpu(NULL, buf_B, 0, n, DMA_FROM_DEVICE);
3/. DMA from PCI device memory into ioremap()'ed buffer, buf_C:
/* ...prepare DMA engine, check buffer alignment, then: */
/* No buffer sync-ing is required? */
mv64x6x_enable_dma(dmanr);
wait_for_completion_interruptible_timeout(...)
/* No buffer sync'ing is required? */
Will this approach work (particularly case 3/.)? I tried dma_sync-ing
the region, but got an 'oops' (kernel access of bad area).
I'm using the 2.6.16 kernel (compiled with CONFIG_NOT_COHERENT_CACHE
defined) on an Artesyn PmPPC7448 processor. The processor utilises its
Marvell MV64460 as the DMA controller for the transaction.
Thanks,
--
Phil
reply other threads:[~2006-07-25 9:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1153818594.10422.50.camel@lamorak.int.avalon.com.au \
--to=philn@avalon.com.au \
--cc=Phil.Nitschke@avalon.com.au \
--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