All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] PL330: Add common core driver
Date: Mon, 26 Apr 2010 05:56:27 +0100	[thread overview]
Message-ID: <20100426045627.GI28105@trinity.fluff.org> (raw)
In-Reply-To: <q2y63386a3d1004241859v8b31f756rb6ff9b4a7452ba@mail.gmail.com>

On Sun, Apr 25, 2010 at 03:59:26AM +0200, Linus Walleij wrote:
> 2010/4/24 jassi brar <jassisinghbrar@gmail.com>:
> 
> > You mean the DMA engine driver for PL330, right?
> > Since Joonyoung's driver was pre-empted by these patches,
> > he might want to re-write parts of his driver for this backend.
> > If he doesn't show any interest in a few days, I'll do it.
> 
> Great, my interest here is mainly that this PrimeCell has
> a DMAengine API, if it e.g. runs the DMAengine tests
> nicely, we know it works.

I'd like to make a decision once and for-all about whether to go with
DMAengine or try7 and design something that SoC types can agree on.
 
> > Btw, I think that driver should be divided in two files
> > drivers/dma/api-pl330.c with common code and
> > drivers/dma/<soc>-pl330.c for platform specific stuff like IRQ,
> > registers base mapping and other quirks(if any). Any opinions?

Possibly, but I think it may be better to pass these things via platform
device for registers and irqs, and platform data for the quirks.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2010-04-26  4:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  7:27 [PATCH 1/7] PL330: Add common core driver jassisinghbrar at gmail.com
2010-04-23 21:49 ` Linus Walleij
2010-04-23 23:20   ` jassi brar
2010-04-25  1:59     ` Linus Walleij
2010-04-26  4:56       ` Ben Dooks [this message]
2010-04-26  6:41         ` jassi brar
2010-04-26  4:54 ` Ben Dooks
2010-04-26  6:20   ` jassi brar
2010-04-26  7:09     ` [PATCH 1/7] PL330: Add common core driver\ Ben Dooks
2010-05-01 21:01       ` Dan Williams
2010-05-02  0:23         ` jassi brar

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=20100426045627.GI28105@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.