From: Christoph Hellwig <hch@lst.de>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tomasz Figa <tfiga@chromium.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Sergey Senozhatsky <senozhatsky@google.com>,
iommu@lists.linux-foundation.org
Cc: linux-media@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: add a new dma_alloc_noncontiguous API v2
Date: Sun, 7 Feb 2021 19:48:55 +0100 [thread overview]
Message-ID: <20210207184855.GA27553@lst.de> (raw)
In-Reply-To: <20210202095110.1215346-1-hch@lst.de>
Any comments?
On Tue, Feb 02, 2021 at 10:51:03AM +0100, Christoph Hellwig wrote:
> Hi all,
>
> this series adds the new noncontiguous DMA allocation API requested by
> various media driver maintainers.
>
> 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@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
---end quoted text---
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tomasz Figa <tfiga@chromium.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Sergey Senozhatsky <senozhatsky@google.com>,
iommu@lists.linux-foundation.org
Cc: linux-doc@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: add a new dma_alloc_noncontiguous API v2
Date: Sun, 7 Feb 2021 19:48:55 +0100 [thread overview]
Message-ID: <20210207184855.GA27553@lst.de> (raw)
In-Reply-To: <20210202095110.1215346-1-hch@lst.de>
Any comments?
On Tue, Feb 02, 2021 at 10:51:03AM +0100, Christoph Hellwig wrote:
> Hi all,
>
> this series adds the new noncontiguous DMA allocation API requested by
> various media driver maintainers.
>
> 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@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
---end quoted text---
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-02-07 18:49 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 9:51 add a new dma_alloc_noncontiguous API v2 Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 1/7] dma-mapping: remove the {alloc,free}_noncoherent methods Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 2/7] dma-mapping: add a dma_mmap_pages helper Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 3/7] dma-mapping: refactor dma_{alloc,free}_pages Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 4/7] dma-mapping: add a dma_alloc_noncontiguous API Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-16 18:55 ` Robin Murphy
2021-02-16 18:55 ` Robin Murphy
2021-03-01 8:09 ` Christoph Hellwig
2021-03-01 8:09 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 5/7] dma-iommu: refactor iommu_dma_alloc_remap Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 6/7] dma-iommu: implement ->alloc_noncontiguous Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-16 8:14 ` Tomasz Figa
2021-02-16 8:14 ` Tomasz Figa
2021-02-16 8:49 ` Christoph Hellwig
2021-02-16 8:49 ` Christoph Hellwig
2021-03-01 7:17 ` Sergey Senozhatsky
2021-03-01 7:17 ` Sergey Senozhatsky
2021-03-01 7:21 ` Christoph Hellwig
2021-03-01 7:21 ` Christoph Hellwig
2021-03-01 8:02 ` Sergey Senozhatsky
2021-03-01 8:02 ` Sergey Senozhatsky
2021-03-01 8:11 ` Christoph Hellwig
2021-03-01 8:11 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 7/7] media: uvcvideo: Use dma_alloc_noncontiguos API Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-04 7:39 ` Hillf Danton
2021-02-07 18:48 ` Christoph Hellwig [this message]
2021-02-07 18:48 ` add a new dma_alloc_noncontiguous API v2 Christoph Hellwig
2021-02-08 11:33 ` Tomasz Figa
2021-02-08 11:33 ` Tomasz Figa
2021-02-09 8:22 ` Christoph Hellwig
2021-02-09 8:29 ` Ricardo Ribalda
2021-02-09 8:29 ` Ricardo Ribalda
2021-02-09 14:46 ` Ricardo Ribalda
2021-02-09 14:46 ` Ricardo Ribalda
2021-02-09 17:02 ` Christoph Hellwig
2021-02-11 9:08 ` Ricardo Ribalda
2021-02-11 9:08 ` Ricardo Ribalda
2021-02-11 13:06 ` Christoph Hellwig
2021-02-11 13:06 ` Christoph Hellwig
2021-02-11 13:20 ` Ricardo Ribalda
2021-02-11 13:20 ` Ricardo Ribalda
2021-02-11 13:55 ` Laurent Pinchart
2021-02-11 13:55 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210207184855.GA27553@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=robin.murphy@arm.com \
--cc=senozhatsky@google.com \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.