From: Chuck Ketcham <chuckk2333@yahoo.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Using dmaengine on Freescale P2020 RDB
Date: Wed, 6 Apr 2011 12:40:58 -0700 (PDT) [thread overview]
Message-ID: <327152.93855.qm@web36406.mail.mud.yahoo.com> (raw)
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?
Thank you.
Chuck
next reply other threads:[~2011-04-06 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 19:40 Chuck Ketcham [this message]
2011-04-06 20:10 ` Using dmaengine on Freescale P2020 RDB Ira W. Snyder
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=327152.93855.qm@web36406.mail.mud.yahoo.com \
--to=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 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.