linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ira W. Snyder" <iws@ovro.caltech.edu>
To: Chuck Ketcham <chuckk2333@yahoo.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Using dmaengine on Freescale P2020 RDB
Date: Wed, 6 Apr 2011 13:10:30 -0700	[thread overview]
Message-ID: <20110406201029.GC7312@ovro.caltech.edu> (raw)
In-Reply-To: <327152.93855.qm@web36406.mail.mud.yahoo.com>

On Wed, Apr 06, 2011 at 12:40:58PM -0700, Chuck Ketcham wrote:
> All,
> 
> I have a Freescale P2020 Reference Design Board.  I am investigating the possibility of using the dmaengine capability in the 2.6.32.13 kernel to transfer data from memory out onto the PCIe bus.  As a first step, I thought I would try the DMA test client (dmatest.ko) to make sure the dmaengine was functioning.  I know this doesn't transfer anything over PCIe but only transfers from one memory buffer to another, but I figured I need to get this working first.  Anyway I built dmatest.ko and ran it (with insmod), and discovered it didn't do anything.  I added some printk's to the kernel to investigate what was going on and I found that all attempts to find a channel within dma_request_channel were unsuccessful.  Three of the channels were not used because they were already publicly allocated.  One channel was not used because it didn't have DMA_MEMCPY capability.
> 
> Here are my questions then:
> 1. Is the dmaengine the appropriate method to use for transferring data from memory out onto the PCIe bus?
> 2. If dmaengine is correct, what can I do to free up a channel for my own use?
> 

I use the Freescale DMA engine to transfer lots of data out to PCI, on
an 8349EA chip. The P2020 DMA engine uses the same driver.

I hunch you have enabled CONFIG_NET_DMA, which will claim the channels.
You should disable it to use the devices for other uses.

If you want an example of using the DMA engine to transfer from DDR
memory to the PowerPC local bus, search the mailing list archives for
"CARMA Board Drivers" (RFCv7 was the latest posting). Transferring from
DDR to PCI works exactly the same way.

Hope it helps,
Ira

  reply	other threads:[~2011-04-06 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 19:40 Using dmaengine on Freescale P2020 RDB Chuck Ketcham
2011-04-06 20:10 ` Ira W. Snyder [this message]
2011-04-06 20:29   ` Chuck Ketcham
2011-04-06 21:28     ` Ira W. Snyder
2011-04-08 15:29 ` Timur Tabi

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=20110406201029.GC7312@ovro.caltech.edu \
    --to=iws@ovro.caltech.edu \
    --cc=chuckk2333@yahoo.com \
    --cc=linuxppc-dev@lists.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).