On Sun, May 9, 2010 at 3:06 AM, jassi brar <jassisinghbrar@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
