From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: PL-330 DMA driver
Date: Wed, 17 Feb 2010 20:31:14 +0000 [thread overview]
Message-ID: <20100217203114.GC30033@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <63386a3d1002171026h51f34d4buc9ba0293ea08c004@mail.gmail.com>
On Wed, Feb 17, 2010 at 07:26:00PM +0100, Linus Walleij wrote:
> 2010/2/17 jassi brar <jassisinghbrar@gmail.com>:
>
> > Could maintainers please suggest what is the best place for the PL330
> > controller driver?
>
> drivers/dma/amba-pl033.c would be my bet.
>
> I have patches to support MMCI (PL180/PL181) using the generic DMA
> engine pending, I will attempt to submit patches for spi/amba-pl022.c and
> serial/amba-pl011.c when I get the time.
One of the problems with the DMA engine APIs are that the data needed to
setup the non-device side is opaque - in other words, it's specific to
the DMA engine being used.
This means primecell drivers can't define this data; they don't know what
kind of DMA engine will be used - and I'm not sure passing it in from
the platform side of things makes much sense either.
Unless... we define a base structure for DMA engines used with primecell
peripherals...
next prev parent reply other threads:[~2010-02-17 20:31 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 [this message]
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
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=20100217203114.GC30033@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).