From: jassisinghbrar@gmail.com (jassi brar)
To: linux-arm-kernel@lists.infradead.org
Subject: PL-330 DMA driver
Date: Thu, 18 Feb 2010 10:14:47 +0900 [thread overview]
Message-ID: <1b68c6791002171714u59a7d0fak7cd531de96eb0025@mail.gmail.com> (raw)
In-Reply-To: <63386a3d1002171353v36f7b5c8tdab15b1593581e02@mail.gmail.com>
On Thu, Feb 18, 2010 at 6:53 AM, Linus Walleij
<linus.ml.walleij@gmail.com> wrote:
> 2010/2/17 Guennadi Liakhovetski <g.liakhovetski@gmx.de>:
>
>> Of course, there's also a problem of reusing peripheral drivers with
>> different DMA controllers...
>
> That's what I'm facing with MMCI and a host of other peripherals.
>
> We have to either:
>
> (1) Use something, i.e the DMA engine slave
>
> (2) Fork the driver entirely to some ste-mmci.c and delete all generic
> ?code. (Repeat for each vendor using a primecell!)
>
> (3) Sprinkle mmci.c with #ifdef ARCH_U300 for our DMA engine.
> ?Or, not so bad, atleast sprinkle the smallish part I have now
> ?broken out in mmci.c that deals with DMA transfers.
>
> I think the current patch does (1) and it actually works, then if
> it gets burdensome to others, using a generic DMA engine can
> be a special case of (3) since that works for us so we're on the right
> path in two cases and (2) doesn't look good to me.
>
> Yours,
> Linus Walleij
CCing the S3C maintainer (Ben Dooks) to share his opinion.
next prev parent reply other threads:[~2010-02-18 1:14 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 [this message]
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=1b68c6791002171714u59a7d0fak7cd531de96eb0025@mail.gmail.com \
--to=jassisinghbrar@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).