On 11/15/2017 09:13 AM, Stefan Roese wrote: > Hi Vinod, > > On 15.11.2017 16:52, Vinod Koul wrote: >> On Mon, Nov 13, 2017 at 09:28:46AM +0100, Stefan Roese wrote: >>> Hi Vinod, >>> >>> On 31.08.2017 12:57, Robin Murphy wrote: >>>> On 30/08/17 19:25, Dave Jiang wrote: >>>>> On 08/30/2017 11:18 AM, Robin Murphy wrote: >>>>>> On 25/08/17 21:59, Dave Jiang wrote: >>>>>>> Adding a dmaengine transaction operation that allows copy to/from a >>>>>>> scatterlist and a flat buffer. >>>>>> >>>>>> Apologies if I'm late to the party, but doesn't DMA_SG already cover >>>>>> this use-case? As far as I can see, all this does is save the caller >>>>> >from setting up a single-entry scatterlist to describe the buffer - even >>>>>> if such a simplified interface is justified it seems like something that >>>>>> could be implemented as a wrapper around dmaengine_prep_dma_sg() rather >>>>>> than the providers having to implement a whole extra callback. >>>>>> >>>>> >>>>> DMA_SG is queued to be removed in 4.14. There is no in kernel consumer >>>>> for the code. >>>> >>>> Ah, I see, that's what I was missing. So we're effectively just >>>> replacing that interface with a more pragmatic alternative - that makes >>>> sense. >>> >>> What are the plans with this new DMA_MEMCPY_SG interface? When will it >>> hit mainline or is something missing? >> >> The old one was removed in 4.14 so if you have a usage feel free to send a >> patch to add this with usage. > > No, its not the "old one" (DMA_SG) but the "new one" (DMA_MEMCPY_SG) > I'm referring to (this email thread). My impression was, that this > new interface has (or will get) in-kernel users and will be pulled at > some time. > Decided to hold off on the submission for now. If you need it and have an upstream consumer for it, feel free to push the change. -- 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
