On Tue, Mar 13, 2012 at 06:16:39PM +0530, Ravi Kumar V wrote: > On 3/13/2012 1:44 AM, Daniel Walker wrote: > >On Mon, Mar 12, 2012 at 04:02:44PM +0530, Ravi Kumar V wrote: > >>Add DMAEngine based driver using the old MSM DMA APIs internally. > > > >What do you mean by this? > > > There is a MSM DMA driver in arch/arm/mach-msm/ which is not in > dmaengine framework standards, but that driver is been used by > client drivers nand, eMMC and serial drivers. Now if we implement > the whole dma driver using dmaengine framework then nand, eMMC like > drivers will be failed as they are using old dma driver API's, so > instead of implementing new driver from scratch we are keeping the > old dma API's as it is and using those API's in new dmaengine > framework.So that we can convert clients drivers to use dma engine > framework. Did you investigate converting the drivers (nand, eMMC, serial) ? It seems like there would be a 1:1 mapping between the API's , so it might only be a find->replace operation. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
