From: dan.j.williams@intel.com (Dan Williams)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] DMAENGINE: fixes and PrimeCells
Date: Sun, 9 May 2010 10:26:26 -0700 [thread overview]
Message-ID: <k2le9c3a7c21005091026y9140dd46i8020c49ebef7c06c@mail.gmail.com> (raw)
In-Reply-To: <l2r1b68c6791005090306ld948bebfqa1e7d22321e302aa@mail.gmail.com>
On Sun, May 9, 2010 at 3:06 AM, jassi brar <jassisinghbrar@gmail.com> wrote:
> This discussion is purely about what the current DMA API misses and what
> a generic DMA API should do. So, that the current DMA API fills up those
> gap, if possible. I would love to get started implementing the generic
> DMA API for reference but my priorities are decided by my employer.
Well, the only significant miss that has been identified so far is
dynamic channel allocation for the device-to-mem case. Everything
else can be done with small tweaks to the existing interface. But
some of this discussion reminds me of Section 2.4 of
Documentaion/SubmittingPatches:
4) Don't over-design.
Don't try to anticipate nebulous future cases which may or may not
be useful: "Make it as simple as you can, and no simpler."
Let's just wait for the code before outlining what can and cannot be
done, especially given where we started [1].
--
Dan
[1]: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=include/linux/dmaengine.h;hb=v2.6.18#l160
next prev parent reply other threads:[~2010-05-09 17:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 0:54 [PATCH 0/7] DMAENGINE: fixes and PrimeCells Linus Walleij
2010-05-07 9:13 ` Linus Walleij
2010-05-07 9:32 ` Russell King - ARM Linux
2010-05-07 11:43 ` Linus Walleij
2010-05-07 12:31 ` jassi brar
2010-05-07 16:10 ` Linus Walleij
2010-05-08 2:37 ` jassi brar
2010-05-08 22:24 ` Dan Williams
2010-05-09 3:48 ` jassi brar
2010-05-09 7:47 ` Dan Williams
2010-05-09 10:06 ` jassi brar
2010-05-09 17:26 ` Dan Williams [this message]
2010-05-09 22:51 ` jassi brar
2010-05-07 23:54 ` Dan Williams
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=k2le9c3a7c21005091026y9140dd46i8020c49ebef7c06c@mail.gmail.com \
--to=dan.j.williams@intel.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).