From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH] OMAP: iommu flush page table entries from L1 and L2 cache Date: Mon, 18 Apr 2011 15:25:41 +0200 Message-ID: <201104181525.43481.arnd@arndb.de> References: <20110414223036.GA7335@n2100.arm.linux.org.uk> <20110418110502.GI12272@atomide.com> <20110418.144246.77604458849535045.Hiroshi.DOYU@nokia.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de ([212.227.126.186]:65430 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751703Ab1DRNZu (ORCPT ); Mon, 18 Apr 2011 09:25:50 -0400 In-Reply-To: <20110418.144246.77604458849535045.Hiroshi.DOYU@nokia.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Hiroshi DOYU Cc: tony@atomide.com, linux@arm.linux.org.uk, fernando.lugo@ti.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, grgupta@ti.com, h-kanigeri2@ti.com On Monday 18 April 2011, Hiroshi DOYU wrote: > From: ext Tony Lindgren > > have a generic replacement for this code we should start using it. > > I'm afraid that there's no general IOMMU APIs yet, or already? If > there is, migrating to those general IOMMU API is the way, but still > SoC dependent parts remain, anyway. I guess that more or less general > IOMMU API is composed of common set of client APIs(like IOVMM) and the > registration of H/W dependent functions(like omap iommu), I guess. As I explained, we have a surplus of generic iommu APIs already, see include/linux/dma-mapping.h and include/linux/iommu.h The dma-mapping interface handles IOMMUs on all other architectures that have them. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Mon, 18 Apr 2011 15:25:41 +0200 Subject: [PATCH] OMAP: iommu flush page table entries from L1 and L2 cache In-Reply-To: <20110418.144246.77604458849535045.Hiroshi.DOYU@nokia.com> References: <20110414223036.GA7335@n2100.arm.linux.org.uk> <20110418110502.GI12272@atomide.com> <20110418.144246.77604458849535045.Hiroshi.DOYU@nokia.com> Message-ID: <201104181525.43481.arnd@arndb.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Monday 18 April 2011, Hiroshi DOYU wrote: > From: ext Tony Lindgren > > have a generic replacement for this code we should start using it. > > I'm afraid that there's no general IOMMU APIs yet, or already? If > there is, migrating to those general IOMMU API is the way, but still > SoC dependent parts remain, anyway. I guess that more or less general > IOMMU API is composed of common set of client APIs(like IOVMM) and the > registration of H/W dependent functions(like omap iommu), I guess. As I explained, we have a surplus of generic iommu APIs already, see include/linux/dma-mapping.h and include/linux/iommu.h The dma-mapping interface handles IOMMUs on all other architectures that have them. Arnd