[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180110152617.GB17790@lst.de>
Date: Wed, 10 Jan 2018 16:26:17 +0100
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Christoph Hellwig <hch@....de>, iommu@...ts.linux-foundation.org,
linux-mips@...ux-mips.org, linux-ia64@...r.kernel.org,
linux-sh@...r.kernel.org, sparclinux@...r.kernel.org,
Guan Xuetao <gxt@...c.pku.edu.cn>, linux-arch@...r.kernel.org,
linux-s390@...r.kernel.org, linux-c6x-dev@...ux-c6x.org,
linux-hexagon@...r.kernel.org, x86@...nel.org,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
linux-snps-arc@...ts.infradead.org,
linux-m68k@...ts.linux-m68k.org, patches@...ups.riscv.org,
linux-metag@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Michal Simek <monstr@...str.eu>, linux-parisc@...r.kernel.org,
linux-cris-kernel@...s.com, linux-kernel@...r.kernel.org,
linux-alpha@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH 11/33] dma-mapping: move swiotlb arch helpers to a new
header
On Wed, Jan 10, 2018 at 02:56:01PM +0000, Robin Murphy wrote:
> I took a look at these, and it seems their phys_to_dma() usage is doing the
> thing which we subsequently formalised as dma_map_resource(). I've had a
> crack at a quick patch to update the CESA driver; qcom_nandc looks slightly
> more complex in that the changes probably need to span the BAM dmaengine
> driver as well.
Sounds great, although probably something for the next merge window.
In the meantime does this patch looks good to you?
Powered by blists - more mailing lists