mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Xue <xxm@rock-chips.com>
To: Joerg Roedel <joro@8bytes.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-rockchip@lists.infradead.org,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, Simon Xue <xxm@rock-chips.com>
Subject: [PATCH V3 2/4] ARM: dts: rockchip: rk322x add iommu nodes
Date: Mon, 24 Jul 2017 10:32:08 +0800	[thread overview]
Message-ID: <1500863530-32792-2-git-send-email-xxm@rock-chips.com> (raw)
In-Reply-To: <1500863530-32792-1-git-send-email-xxm@rock-chips.com>

Add VPU/VDEC/VOP/IEP iommu nodes

Signed-off-by: Simon Xue <xxm@rock-chips.com>
---
changes since V2:
 - none

 arch/arm/boot/dts/rk322x.dtsi | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/arch/arm/boot/dts/rk322x.dtsi b/arch/arm/boot/dts/rk322x.dtsi
index f3e4ffd..36f7c4b 100644
--- a/arch/arm/boot/dts/rk322x.dtsi
+++ b/arch/arm/boot/dts/rk322x.dtsi
@@ -500,6 +500,42 @@
 		status = "disabled";
 	};
 
+	vpu_mmu: iommu@20020800 {
+		compatible = "rockchip,iommu";
+		reg = <0x20020800 0x100>;
+		interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;
+		interrupt-names = "vpu_mmu";
+		iommu-cells = <0>;
+		status = "disabled";
+	};
+
+	vdec_mmu: iommu@20030480 {
+		compatible = "rockchip,iommu";
+		reg = <0x20030480 0x40>, <0x200304c0 0x40>;
+		interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>;
+		interrupt-names = "vdec_mmu";
+		iommu-cells = <0>;
+		status = "disabled";
+	};
+
+	vop_mmu: iommu@20053f00 {
+		compatible = "rockchip,iommu";
+		reg = <0x20053f00 0x100>;
+		interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
+		interrupt-names = "vop_mmu";
+		iommu-cells = <0>;
+		status = "disabled";
+	};
+
+	iep_mmu: iommu@20070800 {
+		compatible = "rockchip,iommu";
+		reg = <0x20070800 0x100>;
+		interrupts = <GIC_SPI 31 IRQ_TYPE_LEVEL_HIGH>;
+		interrupt-names = "iep_mmu";
+		iommu-cells = <0>;
+		status = "disabled";
+	};
+
 	emmc: dwmmc@30020000 {
 		compatible = "rockchip,rk3288-dw-mshc";
 		reg = <0x30020000 0x4000>;
-- 
1.9.1

  reply	other threads:[~2017-07-24  2:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24  2:32 [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 " Simon Xue
2017-07-24  2:32 ` Simon Xue [this message]
2017-08-21 21:17   ` [PATCH V3 2/4] ARM: dts: rockchip: rk322x " Heiko Stuebner
2017-07-24  2:32 ` [PATCH V3 3/4] ARM64: dts: rockchip: rk3368 " Simon Xue
2017-08-21 21:08   ` Heiko Stuebner
2017-07-24  2:32 ` [PATCH V3 4/4] ARM64: dts: rockchip: rk3399 " Simon Xue
2017-08-21 21:14   ` Heiko Stuebner
2017-07-26 10:58 ` [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 " Joerg Roedel
2017-07-26 11:44   ` Heiko Stübner
2017-07-26 12:27     ` Joerg Roedel
2017-07-26 13:53       ` Heiko Stübner
2017-07-27 12:15         ` Joerg Roedel
2017-07-27 12:26           ` Heiko Stübner
2017-07-27 12:45             ` Joerg Roedel
2017-08-21 21:08 ` Heiko Stuebner

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=1500863530-32792-2-git-send-email-xxm@rock-chips.com \
    --to=xxm@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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

all inboxes | Powered by JetHome®