[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210311165250.GB25023@lst.de>
Date: Thu, 11 Mar 2021 17:52:50 +0100
From: Christoph Hellwig <hch@....de>
To: Mauro Carvalho Chehab <mchehab@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Tomasz Figa <tfiga@...omium.org>,
Ricardo Ribalda <ribalda@...omium.org>,
Sergey Senozhatsky <senozhatsky@...gle.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
iommu@...ts.linux-foundation.org
Cc: linux-media@...r.kernel.org, Robin Murphy <robin.murphy@....com>,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: add a new dma_alloc_noncontiguous API v3
Any comments? Especially on the uvcvideo conversion?
On Mon, Mar 01, 2021 at 09:52:30AM +0100, Christoph Hellwig wrote:
> Hi all,
>
> this series adds the new noncontiguous DMA allocation API requested by
> various media driver maintainers.
>
> Changes since v2:
> - rebased to Linux 5.12-rc1
> - dropped one already merged patch
> - pass an attrs argument to dma_alloc_noncontigous
> - clarify the dma_vmap_noncontiguous documentation a bit
> - fix double assignments in uvcvideo
>
> Changes since v1:
> - document that flush_kernel_vmap_range and invalidate_kernel_vmap_range
> must be called once an allocation is mapped into KVA
> - add dma-debug support
> - remove the separate dma_handle argument, and instead create fully formed
> DMA mapped scatterlists
> - use a directional allocation in uvcvideo
> - call invalidate_kernel_vmap_range from uvcvideo
> _______________________________________________
> iommu mailing list
> iommu@...ts.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
---end quoted text---
Powered by blists - more mailing lists