linux-kernel - Re: [RFC][PATCH 0/3] iommu/fsl: Freescale PAMU driver and IOMMU API implementation.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1348100042.22800.22@snotra>
Date:	Wed, 19 Sep 2012 19:14:02 -0500
From:	Scott Wood <scottwood@...escale.com>
To:	Kumar Gala <galak@...nel.crashing.org>
CC:	"<b16395@...escale.com>" <b16395@...escale.com>,
	<joerg.roedel@....com>, <iommu@...ts.linux-foundation.org>,
	<linuxppc-dev@...ts.ozlabs.org>, <linux-kernel@...r.kernel.org>,
	Varun Sethi <Varun.Sethi@...escale.com>
Subject: Re: [RFC][PATCH 0/3] iommu/fsl: Freescale PAMU driver and IOMMU API
 implementation.

On 09/19/2012 08:49:14 AM, Kumar Gala wrote:
> 
> On Sep 19, 2012, at 8:17 AM, <b16395@...escale.com>  
> <b16395@...escale.com> wrote:
> 
> > From: Varun Sethi <Varun.Sethi@...escale.com>
> >
> > 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
> > the I/O transaction type.
> >
> > 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.
> >
> > 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.
> >
> > 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?

The device trees already have PAMU in them.  A binding would be nice,  
though.

-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/