On Mon, Feb 1, 2016 at 5:29 AM, Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> wrote: > Hello, > > On 2016-01-11 18:30, Douglas Anderson wrote: >> >> From: Tomasz Figa <tfiga@xxxxxxxxxxxx> >> >> DMA allocations might be subject to certain reqiurements specific to the >> hardware using the buffers, such as availability of kernel mapping (for >> contents fix-ups in the driver). The only entity that knows them is the >> driver, so it must share this knowledge with vb2-dc. >> >> This patch extends the alloc_ctx initialization interface to let the >> driver specify DMA attrs, which are then stored inside the allocation >> context and will be used for all allocations with that context. >> >> As a side effect, all dma_*_coherent() calls are turned into >> dma_*_attrs() calls, because the attributes need to be carried over >> through all DMA operations. >> >> Signed-off-by: Tomasz Figa <tfiga@xxxxxxxxxxxx> >> Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx> > > > Acked-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> Added both your ans Mauro's acks to the current patch in RMK's patch tracker. You can see the patch at <http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8508/2> Note that Javier has tested this series upstream on a Samsung Chromebook and validated that the allocations are working as intended, even if MFC is a bit tricky to get working properly upstream. -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
