linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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>,
	<scottwood@freescale.com>, <timur@freescale.com>
Cc: Varun Sethi <Varun.Sethi@freescale.com>
Subject: [PATCH 1/4 v2] iommu/fsl: Store iommu domain information pointer in archdata.
Date: Tue, 20 Nov 2012 19:24:54 +0530	[thread overview]
Message-ID: <1353419697-31269-2-git-send-email-Varun.Sethi@freescale.com> (raw)
In-Reply-To: <1353419697-31269-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>
---
 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

  reply	other threads:[~2012-11-20 14:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 13:54 [PATCH 0/4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2012-11-20 13:54 ` Varun Sethi [this message]
2012-11-26  5:33   ` [PATCH 1/4 v2] iommu/fsl: Store iommu domain information pointer in archdata Sethi Varun-B16395
2012-11-28 17:35     ` Kumar Gala
2012-11-20 13:54 ` [PATCH 2/4] iommu/fsl: Add PAMU bypass enable register to ccsr_guts structure Varun Sethi
2012-11-25 13:21   ` Kumar Gala
2012-11-20 13:54 ` [PATCH 3/4 v5] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver Varun Sethi
2012-11-26  5:24   ` Sethi Varun-B16395
2012-12-02  8:12   ` Sethi Varun-B16395
2012-12-02 14:03   ` Joerg Roedel
2012-12-02 15:11     ` Tabi Timur-B04825
2012-12-03 16:57     ` Sethi Varun-B16395
2012-12-03 17:03       ` Scott Wood
2012-12-04 11:53         ` Sethi Varun-B16395
2012-12-04 18:22           ` Scott Wood
2012-12-10 10:10             ` Sethi Varun-B16395
2012-12-11  1:00               ` Scott Wood
2012-12-11  4:50                 ` Sethi Varun-B16395
2012-12-03 17:27       ` Joerg Roedel
2012-12-03 17:36         ` Scott Wood
2012-11-20 13:54 ` [PATCH 4/4 v5] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2012-11-20 22:52   ` Timur Tabi
  -- strict thread matches above, loose matches on Subject: below --
2012-11-05 11:19 [PATCH 0/4] " Varun Sethi
2012-11-05 11:19 ` [PATCH 1/4 v2] iommu/fsl: Store iommu domain information pointer in archdata Varun Sethi

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=1353419697-31269-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).