From: Timur Tabi <timur@freescale.com>
To: Chuck Ketcham <chuckk2333@yahoo.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Using dmaengine on Freescale P2020 RDB
Date: Fri, 8 Apr 2011 10:29:20 -0500 [thread overview]
Message-ID: <BANLkTi=o2uEq9jeU0J+rRBUcXd1ukGdjqQ@mail.gmail.com> (raw)
In-Reply-To: <327152.93855.qm@web36406.mail.mud.yahoo.com>
On Wed, Apr 6, 2011 at 2:40 PM, Chuck Ketcham <chuckk2333@yahoo.com> wrote:
> Three of the channels were not used because they were already publicly al=
located. =A0One channel was
> not used because it didn't have DMA_MEMCPY capability.
That's strange, because all four DMA channels are identical.
> 2. If dmaengine is correct, what can I do to free up a channel for my own=
use?
There must be something else in your system using up the channels.
--=20
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2011-04-08 15:30 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
2011-04-06 20:29 ` Chuck Ketcham
2011-04-06 21:28 ` Ira W. Snyder
2011-04-08 15:29 ` Timur Tabi [this message]
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='BANLkTi=o2uEq9jeU0J+rRBUcXd1ukGdjqQ@mail.gmail.com' \
--to=timur@freescale.com \
--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).