[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160321152601.GA11674@infradead.org>
Date: Mon, 21 Mar 2016 08:26:01 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Dan Williams <dan.j.williams@...el.com>,
Vinod Koul <vinod.koul@...el.com>,
linux-renesas-soc@...r.kernel.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
iommu@...ts.linux-foundation.org, robin.murphy@....com,
geert+renesas@...der.be, Linus Walleij <linus.walleij@...aro.org>,
Arnd Bergmann <arnd@...db.de>, linux-arch@...r.kernel.org
Subject: Re: [PATCH v5 3/9] dma-mapping: add dma_{map,unmap}_resource
On Thu, Mar 17, 2016 at 01:33:51PM +0200, Laurent Pinchart wrote:
> The good news is that, given that no code uses this new API at the moment,
> there isn't much to audit. The patch series implements the resource mapping
> for arch/arm only, and makes use of it in the rcar-dmac driver only. Would you
> like anything audited else than the arch/arm dma mapping implementation, the
> rcar-dmac driver and the code that then deals with the dma addresses (I'm
> thinking about the IOMMU subsystem and the ipmmu-vmsa driver in particular) ?
Yes, it would be good to do an audit of all the ARM dma_ops as well
as generic code like drivers/base/dma-*.c, lib/dma-debug.c and
include/linux/dma-*.h
Powered by blists - more mailing lists