Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1670509 > unrolled thread

Re: clean up and modularize arch dma_mapping interface

Started byDaniel Vetter <daniel@ffwll.ch>
First post2017-06-20 11:20 +0200
Last post2017-06-20 15:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: clean up and modularize arch dma_mapping interface Daniel Vetter <daniel@ffwll.ch> - 2017-06-20 11:20 +0200
    Re: clean up and modularize arch dma_mapping interface Christoph Hellwig <hch@lst.de> - 2017-06-20 15:20 +0200

#1670509 — Re: clean up and modularize arch dma_mapping interface

FromDaniel Vetter <daniel@ffwll.ch>
Date2017-06-20 11:20 +0200
SubjectRe: clean up and modularize arch dma_mapping interface
Message-ID<tUnuj-6Hb-59@gated-at.bofh.it>
On Thu, Jun 08, 2017 at 03:25:25PM +0200, Christoph Hellwig wrote:
> Hi all,
> 
> for a while we have a generic implementation of the dma mapping routines
> that call into per-arch or per-device operations.  But right now there
> still are various bits in the interfaces where don't clearly operate
> on these ops.  This series tries to clean up a lot of those (but not all
> yet, but the series is big enough).  It gets rid of the DMA_ERROR_CODE
> way of signaling failures of the mapping routines from the
> implementations to the generic code (and cleans up various drivers that
> were incorrectly using it), and gets rid of the ->set_dma_mask routine
> in favor of relying on the ->dma_capable method that can be used in
> the same way, but which requires less code duplication.
> 
> Btw, we don't seem to have a tree every-growing amount of common dma
> mapping code, and given that I have a fair amount of all over the tree
> work in that area in my plate I'd like to start one.  Any good reason
> to that?  Anyone willing to volunteer as co maintainer?
> 
> The whole series is also available in git:
> 
>     git://git.infradead.org/users/hch/misc.git dma-map

Ack for the 2 drm patches, but I can also pick them up through drm-misc if
you prefer that (but then it'll be 4.14).
-Daniel

> 
> Gitweb:
> 
>     http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-map
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

[toc] | [next] | [standalone]


#1670755

FromChristoph Hellwig <hch@lst.de>
Date2017-06-20 15:20 +0200
Message-ID<tUrez-FV-71@gated-at.bofh.it>
In reply to#1670509
On Tue, Jun 20, 2017 at 11:19:02AM +0200, Daniel Vetter wrote:
> Ack for the 2 drm patches, but I can also pick them up through drm-misc if
> you prefer that (but then it'll be 4.14).

Nah, I'll plan to set up a dma-mapping tree so that we'll have common
place for dma-mapping work.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web