linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH/RFC] ARM: dts: r8a7790: IPMMU-DS SYS-DMAC prototype
Date: Tue, 20 Sep 2016 21:12:11 +0900	[thread overview]
Message-ID: <20160920121211.14870.27506.sendpatchset@little-apple> (raw)

From: Magnus Damm <damm+renesas@opensource.se>

Hook up the SYS-DMAC devices to IPMMU-DS on r8a7790 and enable that
particular IPMMU instance. Depending on kernel version LPAE may need
to be enabled before the IPMMU driver becomes available.

Useful to test the IPMMU with the devices hooked up to the SYS-DMAC
via the DMA Engine framework together with the following workaround:
[PATCH/RFC] iommu/ipmmu-vmsa: IPMMU SYS-DMAC iova mapping workaround

Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---

 Tested with renesas-drivers-2016-09-13-v4.8-rc6

 arch/arm/boot/dts/r8a7790.dtsi |   31 ++++++++++++++++++++++++++++++-
 1 file changed, 30 insertions(+), 1 deletion(-)

--- 0003/arch/arm/boot/dts/r8a7790.dtsi
+++ work/arch/arm/boot/dts/r8a7790.dtsi	2016-09-20 20:23:34.420607110 +0900
@@ -362,6 +362,21 @@
 		power-domains = <&sysc R8A7790_PD_ALWAYS_ON>;
 		#dma-cells = <1>;
 		dma-channels = <15>;
+		iommus = <&ipmmu_ds 0>,
+		       <&ipmmu_ds 1>,
+		       <&ipmmu_ds 2>,
+		       <&ipmmu_ds 3>,
+		       <&ipmmu_ds 4>,
+		       <&ipmmu_ds 5>,
+		       <&ipmmu_ds 6>,
+		       <&ipmmu_ds 7>,
+		       <&ipmmu_ds 8>,
+		       <&ipmmu_ds 9>,
+		       <&ipmmu_ds 10>,
+		       <&ipmmu_ds 11>,
+		       <&ipmmu_ds 12>,
+		       <&ipmmu_ds 13>,
+		       <&ipmmu_ds 14>;
 	};
 
 	dmac1: dma-controller@e6720000 {
@@ -393,6 +408,21 @@
 		power-domains = <&sysc R8A7790_PD_ALWAYS_ON>;
 		#dma-cells = <1>;
 		dma-channels = <15>;
+		iommus = <&ipmmu_ds 15>,
+		       <&ipmmu_ds 16>,
+		       <&ipmmu_ds 17>,
+		       <&ipmmu_ds 18>,
+		       <&ipmmu_ds 19>,
+		       <&ipmmu_ds 20>,
+		       <&ipmmu_ds 21>,
+		       <&ipmmu_ds 22>,
+		       <&ipmmu_ds 23>,
+		       <&ipmmu_ds 24>,
+		       <&ipmmu_ds 25>,
+		       <&ipmmu_ds 26>,
+		       <&ipmmu_ds 27>,
+		       <&ipmmu_ds 28>,
+		       <&ipmmu_ds 29>;
 	};
 
 	audma0: dma-controller@ec700000 {
@@ -1877,7 +1907,6 @@
 		interrupts = <GIC_SPI 198 IRQ_TYPE_LEVEL_HIGH>,
 			     <GIC_SPI 199 IRQ_TYPE_LEVEL_HIGH>;
 		#iommu-cells = <1>;
-		status = "disabled";
 	};
 
 	ipmmu_mp: mmu@ec680000 {

                 reply	other threads:[~2016-09-20 12:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160920121211.14870.27506.sendpatchset@little-apple \
    --to=magnus.damm@gmail.com \
    --cc=linux-renesas-soc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).