linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: jay_chen <jay_chen@alphanetworks.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8349 DMA
Date: Tue, 11 Nov 2008 12:18:37 -0600	[thread overview]
Message-ID: <4919CC7D.2070101@freescale.com> (raw)
In-Reply-To: <0697112B46494D3DB284F1EBA6F65D4E@alphajay>

jay_chen wrote:
> I am using 2.6.14.5 and MPC8349.
> I got some DMA problems with PCI devices.
> So, I tried to understand the DMA stuff of linux.

That's very old; have you tried the latest kernel?

> I have one question about cache coherency.
> In dma-mapping.h, I found some functions are defined as NULL.
> For example:
> #define dma_cache_inv(_start,_size)  do { } while (0)
> #define dma_cache_wback(_start,_size)  do { } while (0)
> #define dma_cache_wback_inv(_start,_size) do { } while (0)
>  
> #define __dma_alloc_coherent(gfp, size, handle) NULL
> #define __dma_free_coherent(size, addr)  do { } while (0)
> #define __dma_sync(addr, size, rw)  do { } while (0)
> #define __dma_sync_page(pg, off, sz, rw) do { } while (0)
> Does this mean that I don't need to take care of cache coherency in 
> MPC83xx platform?
> So, I could use any range of memory for DMA transferring and the 
> hardware will take care of the cache coherency for me?

Yes, however it's still a good idea to call the DMA functions in case 
the code gets run on hardware that doesn't have coherent DMA, or that 
needs special DMA mapping for highmem.

Make sure that the PCI bridge is configured to snoop, and that you map 
your memory as coherence-required (normally not necessary on 
uniprocessor, but there's some weirdness in the 82xx/83xx PCI controller 
that requires it).

-Scott

  reply	other threads:[~2008-11-11 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 14:16 MPC8349 DMA jay_chen
2008-11-11 18:18 ` Scott Wood [this message]
2008-11-19 11:14   ` jay_chen
2008-11-19 16:05     ` Scott Wood

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=4919CC7D.2070101@freescale.com \
    --to=scottwood@freescale.com \
    --cc=jay_chen@alphanetworks.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;
as well as URLs for NNTP newsgroup(s).