From: Kumar Gala <galak@kernel.crashing.org>
To: "<b16395@freescale.com>" <b16395@freescale.com>
Cc: <iommu@lists.linux-foundation.org>, <joerg.roedel@amd.com>,
<linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
Varun Sethi <Varun.Sethi@freescale.com>
Subject: Re: [RFC][PATCH 0/3] iommu/fsl: Freescale PAMU driver and IOMMU API implementation.
Date: Wed, 19 Sep 2012 08:49:14 -0500 [thread overview]
Message-ID: <A6B66C5D-71EA-4E9F-8347-7413479BD3FC@kernel.crashing.org> (raw)
In-Reply-To: <1348060632-12997-1-git-send-email-b16395@freescale.com>
On Sep 19, 2012, at 8:17 AM, <b16395@freescale.com> <b16395@freescale.com> wrote:
> From: Varun Sethi <Varun.Sethi@freescale.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?
- k
next prev parent reply other threads:[~2012-09-19 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 13:17 b16395
2012-09-19 13:17 ` [RFC][PATCH 1/3] iommu/fsl: Store iommu domain information pointer in archdata b16395
2012-09-19 13:50 ` Kumar Gala
2012-10-04 16:30 ` Sethi Varun-B16395
2012-09-19 13:17 ` [RFC][PATCH 2/3] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver b16395
2012-09-19 13:52 ` Kumar Gala
2012-09-20 0:12 ` Scott Wood
2012-09-20 9:46 ` Sethi Varun-B16395
2012-09-20 13:19 ` Kumar Gala
2012-09-19 13:17 ` [RFC][PATCH 3/3] iommu/fsl: Freescale PAMU driver and IOMMU API implementation b16395
2012-09-19 14:18 ` Kumar Gala
2012-09-19 13:49 ` Kumar Gala [this message]
2012-09-20 0:14 ` [RFC][PATCH 0/3] " Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A6B66C5D-71EA-4E9F-8347-7413479BD3FC@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Varun.Sethi@freescale.com \
--cc=b16395@freescale.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®