From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <galak@kernel.crashing.org>
Received: from gate.crashing.org (gate.crashing.org [63.228.1.57])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by ozlabs.org (Postfix) with ESMTPS id 09F852C0081
 for <linuxppc-dev@lists.ozlabs.org>; Wed, 19 Sep 2012 23:49:24 +1000 (EST)
Subject: Re: [RFC][PATCH 0/3] iommu/fsl: Freescale PAMU driver and IOMMU API
 implementation.
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Kumar Gala <galak@kernel.crashing.org>
In-Reply-To: <1348060632-12997-1-git-send-email-b16395@freescale.com>
Date: Wed, 19 Sep 2012 08:49:14 -0500
Message-Id: <A6B66C5D-71EA-4E9F-8347-7413479BD3FC@kernel.crashing.org>
References: <1348060632-12997-1-git-send-email-b16395@freescale.com>
To: "<b16395@freescale.com>" <b16395@freescale.com>
Cc: joerg.roedel@amd.com, iommu@lists.linux-foundation.org,
 linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
 Varun Sethi <Varun.Sethi@freescale.com>
List-Id: Linux on PowerPC Developers Mail List <linuxppc-dev.lists.ozlabs.org>
List-Unsubscribe: <https://lists.ozlabs.org/options/linuxppc-dev>,
 <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=unsubscribe>
List-Archive: <http://lists.ozlabs.org/pipermail/linuxppc-dev/>
List-Post: <mailto:linuxppc-dev@lists.ozlabs.org>
List-Help: <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=help>
List-Subscribe: <https://lists.ozlabs.org/listinfo/linuxppc-dev>,
 <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=subscribe>


On Sep 19, 2012, at 8:17 AM, <b16395@freescale.com> =
<b16395@freescale.com> wrote:

> From: Varun Sethi <Varun.Sethi@freescale.com>
>=20
> This patchset provides the Freescale PAMU (Peripheral Access =
Management Unit) driver
> and the corresponding IOMMU API implementation. PAMU is the IOMMU =
present on Freescale
> QorIQ platforms. PAMU can authorize memory access, remap the memory =
address, and remap=20
> the I/O transaction type.
>=20
> This set consists of the following patches:
> 1. Addition of new field in the device (powerpc) archdata structure =
for storing iommu domain information
>   pointer. This pointer is stored when the device is attached to a =
particular iommu domain.
> 2. Addition of domain attributes required by the PAMU driver IOMMU =
API.
> 3. PAMU driver and IOMMU API implementation.
>=20
> Varun Sethi (3):
>  Store iommu domain information pointer in archdata.
>  Add iommu domain attributes required by fsl PAMU driver.
>  FSL PAMU driver and IOMMU API implementation.
>=20
> arch/powerpc/include/asm/device.h |    4 +
> drivers/iommu/Kconfig             |    7 +
> drivers/iommu/Makefile            |    1 +
> drivers/iommu/fsl_pamu.c          | 1033 =
+++++++++++++++++++++++++++++++++++++
> drivers/iommu/fsl_pamu.h          |  377 ++++++++++++++
> drivers/iommu/fsl_pamu_domain.c   |  990 =
+++++++++++++++++++++++++++++++++++
> drivers/iommu/fsl_pamu_domain.h   |   94 ++++
> drivers/iommu/fsl_pamu_proto.h    |   49 ++
> include/linux/iommu.h             |   30 ++
> 9 files changed, 2585 insertions(+), 0 deletions(-)
> create mode 100644 drivers/iommu/fsl_pamu.c
> create mode 100644 drivers/iommu/fsl_pamu.h
> create mode 100644 drivers/iommu/fsl_pamu_domain.c
> create mode 100644 drivers/iommu/fsl_pamu_domain.h
> create mode 100644 drivers/iommu/fsl_pamu_proto.h

I assume that another patch series will add device tree binding spec and =
update device trees for SoCs with PAMU?

- k