From mboxrd@z Thu Jan 1 00:00:00 1970 From: dan.j.williams@intel.com (Dan Williams) Date: Sun, 9 May 2010 10:26:26 -0700 Subject: [PATCH 0/7] DMAENGINE: fixes and PrimeCells In-Reply-To: References: <1272848060-28049-1-git-send-email-linus.walleij@stericsson.com> <20100507093256.GB19936@n2100.arm.linux.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, May 9, 2010 at 3:06 AM, jassi brar 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