From: Ira Snyder <iws@ovro.caltech.edu>
To: Timur Tabi <timur@freescale.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with Freescale DMA driver
Date: Tue, 23 Sep 2008 09:43:22 -0700 [thread overview]
Message-ID: <20080923164322.GC7449@ovro.caltech.edu> (raw)
In-Reply-To: <48D914DD.7080702@freescale.com>
On Tue, Sep 23, 2008 at 11:10:05AM -0500, Timur Tabi wrote:
> (Removing various CC:'s since this thread is changing topic)
>
> Ira Snyder wrote:
>
> > I hope that makes sense. I can post the code if anyone would like to see
> > it. It is not ready for mainline inclusion yet, but it is in a fairly
> > good state.
>
> Well, it's a bit goofy, but it does make sense. Since you don't have an actual
> single-function PCI device, you need to use the MPC8349's DMA controller.
>
> I don't see where you need the ability to reserve a DMA channel, though. You're
> using fsldma.c as its intended.
>
Ok. I don't really care which channel I get, just that I get one. I
won't be adding or removing DMA devices from the system, so it shouldn't
be a problem.
> > Ok. I was just wondering, since drivers/dma/fsl_dma.c has some code that
> > appears to handle external master. It is 85XX specific though. There are
> > no users in the kernel tree showing example uses.
>
> Indeed it does. It looks like a feature that was thrown in but never given much
> thought or testing. It appears that the current code just lets you turn on the
> external master pause bit in the MR register, but there's nothing to make sure
> that it actually works in a meaningful way. If there's a queue of transfers for
> a given channel, I don't see where the fsldma avoids stalled queues.
>
That was also my impression. I'll probably start by programming the
registers directly, and hopefully come up with a nice interface. When I
figure it out, I'll send patches.
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.
Thanks for all the input.
Ira
next prev parent reply other threads:[~2008-09-23 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 16:51 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 [this message]
2008-09-23 16:46 ` 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=20080923164322.GC7449@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=timur@freescale.com \
/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
Powered by JetHome