From: Varun Sethi <Varun.Sethi@freescale.com>
To: <joerg.roedel@amd.com>, <iommu@lists.linux-foundation.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<timur@freescale.com>, <scottwood@freescale.com>
Cc: Varun Sethi <Varun.Sethi@freescale.com>
Subject: [PATCH 1/4 v7] iommu/fsl: Store iommu domain information pointer in archdata.
Date: Fri, 14 Dec 2012 19:21:52 +0530 [thread overview]
Message-ID: <1355493114-21776-2-git-send-email-Varun.Sethi@freescale.com> (raw)
In-Reply-To: <1355493114-21776-1-git-send-email-Varun.Sethi@freescale.com>
Add a 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
domain.
Signed-off-by: Varun Sethi <Varun.Sethi@freescale.com>
---
- no change in this version
arch/powerpc/include/asm/device.h | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/include/asm/device.h b/arch/powerpc/include/asm/device.h
index 77e97dd..6dc79fe 100644
--- a/arch/powerpc/include/asm/device.h
+++ b/arch/powerpc/include/asm/device.h
@@ -28,6 +28,10 @@ struct dev_archdata {
void *iommu_table_base;
} dma_data;
+ /* IOMMU domain information pointer. This would be set
+ * when this device is attached to an iommu_domain.
+ */
+ void *iommu_domain;
#ifdef CONFIG_SWIOTLB
dma_addr_t max_direct_dma_addr;
#endif
--
1.7.4.1
next prev parent reply other threads:[~2012-12-14 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 13:51 [PATCH 0/4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2012-12-14 13:51 ` Varun Sethi [this message]
2012-12-14 13:51 ` [PATCH 3/4 v7] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver Varun Sethi
2012-12-14 13:51 ` [PATCH 4/4 v7] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2012-12-21 1:46 ` [PATCH 0/4] " Sethi Varun-B16395
2012-12-27 6:02 ` Sethi Varun-B16395
2013-01-03 5:21 ` Sethi Varun-B16395
2013-01-06 9:51 ` Joerg Roedel
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=1355493114-21776-2-git-send-email-Varun.Sethi@freescale.com \
--to=varun.sethi@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 \
--cc=scottwood@freescale.com \
--cc=timur@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).