From: "Heiko Stübner" <heiko@sntech.de>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: "Stéphane Marchesin" <marcheu@chromium.org>,
"Grant Grundler" <grundler@chromium.org>,
"Simon Xue" <xxm@rock-chips.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Russell King" <linux@arm.linux.org.uk>,
"moderated list:ARM/Rockchip SoC..."
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] ARM: dts: rk3288: add VOP iommu nodes
Date: Tue, 14 Oct 2014 00:33:41 +0200 [thread overview]
Message-ID: <4094180.e6s5oT6HgP@phil> (raw)
In-Reply-To: <1412965848-18663-4-git-send-email-djkurtz@chromium.org>
Hi Daniel,
Am Samstag, 11. Oktober 2014, 02:30:48 schrieb Daniel Kurtz:
> Add device nodes for the VOP iommus.
> Device nodes for other iommus will be added in later patches.
>
> The iommu nodes use the #iommu-cells property as described in:
> Documentation/devicetree/bindings/iommu/iommu.txt
>
> Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
> Signed-off-by: Simon Xue <xxm@rock-chips.com>
> ---
> arch/arm/boot/dts/rk3288.dtsi | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
> index 5950b0a..cbc92fa 100644
> --- a/arch/arm/boot/dts/rk3288.dtsi
> +++ b/arch/arm/boot/dts/rk3288.dtsi
> @@ -271,6 +271,24 @@
> status = "disabled";
> };
>
> + vopb_mmu: iommu@0xff930300 {
please use the address without the 0x here ... iommu@ff930300
Thanks
Heiko
> + compatible = "rockchip,iommu";
> + reg = <0xff930300 0x100>;
> + interrupts = <GIC_SPI 15 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "vopb_mmu";
> + #iommu-cells = <0>;
> + status = "disabled";
> + };
> +
> + vopl_mmu: iommu@0xff940300 {
> + compatible = "rockchip,iommu";
> + reg = <0xff940300 0x100>;
> + interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "vopl_mmu";
> + #iommu-cells = <0>;
> + status = "disabled";
> + };
> +
> gic: interrupt-controller@ffc01000 {
> compatible = "arm,gic-400";
> interrupt-controller;
next prev parent reply other threads:[~2014-10-13 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1412965848-18663-1-git-send-email-djkurtz@chromium.org>
[not found] ` <1412965848-18663-1-git-send-email-djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-10-10 18:30 ` [PATCH v3 1/3] iommu/rockchip: rk3288 iommu driver Daniel Kurtz
2014-10-10 18:30 ` [PATCH v3 2/3] dt-bindings: iommu: Add documentation for rockchip iommu Daniel Kurtz
2014-10-10 18:30 ` [PATCH v3 3/3] ARM: dts: rk3288: add VOP iommu nodes Daniel Kurtz
2014-10-13 22:33 ` Heiko Stübner [this message]
2014-10-14 7:22 ` Daniel Kurtz
2014-10-14 7:23 ` Daniel Kurtz
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=4094180.e6s5oT6HgP@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=galak@codeaurora.org \
--cc=grundler@chromium.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=marcheu@chromium.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=xxm@rock-chips.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).