Agree! To enable DMA_SG in the dmaengine framework we need to have its consumer first. We will recommend same to xilinx users and hope to see some real usecase getting upstreamed :) Thanks, Radhey > -----Original Message----- > From: Vinod Koul [mailto:vinod.koul@xxxxxxxxx] > Sent: Tuesday, December 19, 2017 9:39 AM > To: Radhey Shyam Pandey <radheys@xxxxxxxxxx> > Cc: dmaengine@xxxxxxxxxxxxxxx; Anirudha Sarangi <anirudh@xxxxxxxxxx>; Appana > Durga Kedareswara Rao <appanad@xxxxxxxxxx> > Subject: Re: DMA_SG removed : How to support M2M on userspace allocated > buffers? > > On Mon, Dec 18, 2017 at 12:38:17PM +0000, Radhey Shyam Pandey wrote: > > Hi All, > > > > In kernel upgrade 4.14 DMA_SG is removed from DMA framework since it > > was a dead code and having no consumers in the kernel. > > http://www.spinics.net/lists/dmaengine/msg13835.html > > > > However, there are some xilinx customers using this feature out of the > > tree and are dependent on DMA_SG. Removing DMA_SG from framework will > > break such use cases i.e doing memory to memory transfer on userspace > > allocated (malloc) buffers. > > > > What is the recommendation from the community on supporting above > > usecase? > > Submit a driver along with this feature, its that simple :) > > -- > ~Vinod -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html