From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: horms+renesas@verge.net.au, Magnus Damm <magnus.damm@gmail.com>,
laurent.pinchart+renesas@ideasonboard.com, joro@8bytes.org,
geert+renesas@glider.be
Subject: [PATCH 03/04] arm64: dts: r8a7795: Point FCP devices to IPMMU
Date: Thu, 27 Oct 2016 19:29:25 +0900 [thread overview]
Message-ID: <20161027102925.26426.6785.sendpatchset@little-apple> (raw)
In-Reply-To: <20161027102856.26426.48132.sendpatchset@little-apple>
From: Magnus Damm <damm+renesas@opensource.se>
Hook in the FCP devices to allow use of the VSP and DU
together with the IPMMU.
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
The patch can be merged as is, but it is recommended not
to enable IPMMU-VI until the DU driver gets updated in
mainline with the following patch series and further
updates:
[PATCH 0/6] R-Car DU: Fix IOMMU operation when connected to VSP
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 4 ++++
1 file changed, 4 insertions(+)
--- 0004/arch/arm64/boot/dts/renesas/r8a7795.dtsi
+++ work/arch/arm64/boot/dts/renesas/r8a7795.dtsi 2016-10-27 18:06:14.180607110 +0900
@@ -1569,6 +1569,7 @@
reg = <0 0xfea27000 0 0x200>;
clocks = <&cpg CPG_MOD 603>;
power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
+ iommus = <&ipmmu_vi 8>;
};
vspd1: vsp@fea28000 {
@@ -1586,6 +1587,7 @@
reg = <0 0xfea2f000 0 0x200>;
clocks = <&cpg CPG_MOD 602>;
power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
+ iommus = <&ipmmu_vi 9>;
};
vspd2: vsp@fea30000 {
@@ -1603,6 +1605,7 @@
reg = <0 0xfea37000 0 0x200>;
clocks = <&cpg CPG_MOD 601>;
power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
+ iommus = <&ipmmu_vi 10>;
};
vspd3: vsp@fea38000 {
@@ -1620,6 +1623,7 @@
reg = <0 0xfea3f000 0 0x200>;
clocks = <&cpg CPG_MOD 600>;
power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
+ iommus = <&ipmmu_vi 11>;
};
fdp1@fe940000 {
next prev parent reply other threads:[~2016-10-27 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 10:28 [PATCH 00/04] arm64: dts: r8a7795: Initial IPMMU upstream integration Magnus Damm
2016-10-27 10:29 ` [PATCH 01/04] arm64: dts: r8a7795: Add IPMMU device nodes Magnus Damm
2016-10-27 10:29 ` [PATCH 02/04] arm64: dts: r8a7795: Hook up SYS-DMAC to IPMMU Magnus Damm
2016-10-27 10:42 ` Geert Uytterhoeven
2016-10-27 11:07 ` Magnus Damm
2016-10-27 11:14 ` Geert Uytterhoeven
2016-10-27 10:29 ` Magnus Damm [this message]
2016-10-27 10:29 ` [PATCH 04/04] arm64: dts: r8a7795: Connect Ethernet AVB " Magnus Damm
2016-10-28 12:40 ` Geert Uytterhoeven
2017-01-12 15:31 ` Geert Uytterhoeven
2017-02-07 10:22 ` Geert Uytterhoeven
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=20161027102925.26426.6785.sendpatchset@little-apple \
--to=magnus.damm@gmail.com \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=joro@8bytes.org \
--cc=laurent.pinchart+renesas@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.