From: Timur Tabi <timur@freescale.com>
To: Ira Snyder <iws@ovro.caltech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with Freescale DMA driver
Date: Tue, 23 Sep 2008 11:46:25 -0500 [thread overview]
Message-ID: <48D91D61.2080800@freescale.com> (raw)
In-Reply-To: <20080923164322.GC7449@ovro.caltech.edu>
Ira Snyder wrote:
> In this case, I probably would like to reserve a DMA channel for my
> exclusive use. That way I won't run into problems by programming the DMA
> by hand.
If you write your own DMA driver, the current method for reserving a DMA channel
is to change the compatible property for that channel in the device tree to
something other than "fsl,elo-dma-channel" (or "fsl,eloplus-dma-channel").
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2008-09-23 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 16:51 Problems with Freescale DMA driver Ira Snyder
2008-09-18 21:58 ` Dan Williams
2008-09-18 22:02 ` Timur Tabi
2008-09-22 23:04 ` Ira Snyder
2008-09-23 14:03 ` Timur Tabi
2008-09-23 15:59 ` Ira Snyder
2008-09-23 16:10 ` Timur Tabi
2008-09-23 16:43 ` Ira Snyder
2008-09-23 16:46 ` 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=48D91D61.2080800@freescale.com \
--to=timur@freescale.com \
--cc=iws@ovro.caltech.edu \
--cc=linux-kernel@vger.kernel.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).