From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: PL-330 DMA driver
Date: Wed, 17 Feb 2010 19:26:00 +0100 [thread overview]
Message-ID: <63386a3d1002171026h51f34d4buc9ba0293ea08c004@mail.gmail.com> (raw)
In-Reply-To: <1b68c6791002162150wb8fbae8ya1e5b3c0a56b7fad@mail.gmail.com>
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.
In drivers/dma/coh901318.c we found that implementing a generic
DMA engine over some random custom DMA controller is actually
quite straight forward. If you're making it custom I think seriously
you're doing something wrong.
The key to making the DMA controller wholly abstract is to configure
the driver with platform data containing information on how to
set up/tear down/refill/etc any DMA channel on the system, so
the DMA engine knows all about all channels, and the driver
using it just knows that it's requesting some rx or tx channel with
some platform filter (all from platform data).
This way replacing the DMA enginge, as in resynthesize your SoC
with some totally different DMA controller, and the driver using it
still works.
There may be DMA controllers so esoteric that they cannot be
handled by DMA engine, what do I know, I haven't seen one
yet.
Linus Walleij
next prev parent reply other threads:[~2010-02-17 18:26 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 [this message]
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
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=63386a3d1002171026h51f34d4buc9ba0293ea08c004@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--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).