From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com ([192.55.52.115]:16686 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752213AbcIOQSd (ORCPT ); Thu, 15 Sep 2016 12:18:33 -0400 Date: Thu, 15 Sep 2016 21:56:51 +0530 From: Vinod Koul To: Niklas =?iso-8859-1?Q?S=F6derlund?= , Arnd Bergmann Cc: linux-renesas-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org, iommu@lists.linux-foundation.org, linux@armlinux.org.uk, hch@infradead.org, dan.j.williams@intel.com, robin.murphy@arm.com, laurent.pinchart@ideasonboard.com, linus.walleij@linaro.org, arnd@arndb.de Subject: Re: [PATCHv9 0/6] dmaengine: rcar-dmac: add iommu support for slave transfers Message-ID: <20160915162650.GZ13920@localhost> References: <20160810112219.17964-1-niklas.soderlund+renesas@ragnatech.se> <20160810173710.GK9681@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160810173710.GK9681@localhost> Sender: linux-renesas-soc-owner@vger.kernel.org List-ID: On Wed, Aug 10, 2016 at 11:07:10PM +0530, Vinod Koul wrote: > On Wed, Aug 10, 2016 at 01:22:13PM +0200, Niklas S�derlund wrote: > > Hi, > > > > This series tries to solve the problem with DMA with device registers > > (MMIO registers) that are behind an IOMMU for the rcar-dmac driver. A > > recent patch '9575632 (dmaengine: make slave address physical)' > > clarifies that DMA slave address provided by clients is the physical > > address. This puts the task of mapping the DMA slave address from a > > phys_addr_t to a dma_addr_t on the DMA engine. > > > > Without an IOMMU this is easy since the phys_addr_t and dma_addr_t are > > the same and no special care is needed. However if you have a IOMMU you > > need to map the DMA slave phys_addr_t to a dma_addr_t using something > > like this. > > > > This series is based on top of v4.8-rc1. And I'm hoping to be able to collect a > > Ack from Russell King on patch 4/6 that adds the ARM specific part and then be > > able to take the whole series through the dmaengine tree. If this is not the > > best route I'm more then happy to do it another way. > > > > It's tested on a Koelsch with CONFIG_IPMMU_VMSA and by enabling the > > ipmmu_ds node in r8a7791.dtsi. I verified operation by interacting with > > /dev/mmcblk1, i2c and the serial console which are devices behind the > > iommu. > > As I said in last one, the dmaengine parts look fine to me. But to go thru > dmaengine tree I would need ACK on non dmaengine patches. I havent heard back from this one and I am inclined to merge this one now. If anyone has any objects, please speak up now... Also ACKs welcome... -- ~Vinod