From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: PL-330 DMA driver
Date: Wed, 24 Feb 2010 00:44:22 +0000 [thread overview]
Message-ID: <20100224004422.GD30679@trinity.fluff.org> (raw)
In-Reply-To: <20100218103203.GB20243@n2100.arm.linux.org.uk>
On Thu, Feb 18, 2010 at 10:32:03AM +0000, Russell King - ARM Linux wrote:
> On Wed, Feb 17, 2010 at 11:24:28PM -0700, Dan Williams wrote:
> > On Tue, Feb 16, 2010 at 10:50 PM, jassi brar <jassisinghbrar@gmail.com> wrote:
> > > Hello,
> > >
> > > ?Many Samsung SoCs have PL-330 as the DMA controller and the driver
> > > is missing in the mainline.
> > >
> > > A few months ago, Joonyoung Shim of Samsung, attempted the driver for PL-330
> > > based on the DMA API(drivers/dma/), but the patches weren't accepted.
> >
> > Looking back at the archives seems I missed this patch. So it was not
> > rejected just overlooked. Do we want to move forward on that patch as
> > it stands, or go a different direction? If it is resubmitted I will
> > get it in the queue for 2.6.34.
>
> If it's a generic ARM primecell, it's likely it will be used elsewhere as
> well (primecells are gaining popularity at the moment.) Having it not
> be specific to S3C would be a big advantage, unless of course everyone
> specifically wants to have divergent copies of the same code.
Which is great, until you find out that the S3C PL080 isn't a vanilla
PL080, and has extra registers.
I'm in favour of some form of generic DMA API, but we're going to have
to sort out whether it is dmaengine, dmaengine with some updates or
something entirely new.
The current dmaengine API doesn't have any support for circular buffer
mangement, and from what I remeber of reading stuff last time, adding
to the queue from a buffer done callback is a no-no.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-02-24 0:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 5:50 PL-330 DMA driver jassi brar
2010-02-17 7:07 ` Joonyoung Shim
2010-02-17 9:45 ` jassi brar
2010-02-17 18:26 ` Linus Walleij
2010-02-17 20:31 ` Russell King - ARM Linux
2010-02-17 21:32 ` Guennadi Liakhovetski
2010-02-17 21:53 ` Linus Walleij
2010-02-18 1:14 ` jassi brar
2010-02-17 21:46 ` Linus Walleij
2010-02-18 6:24 ` Dan Williams
2010-02-18 6:36 ` jassi brar
2010-02-18 10:32 ` Russell King - ARM Linux
2010-02-24 0:44 ` Ben Dooks [this message]
2010-02-24 8:31 ` Russell King - ARM Linux
2010-02-18 12:01 ` Joonyoung Shim
2010-02-18 17:55 ` Linus Walleij
2010-02-23 12:14 ` Joonyoung Shim
2010-02-24 0:46 ` Ben Dooks
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=20100224004422.GD30679@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.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).