From: richard.gong@linux.intel.com
To: catalin.marinas@arm.com, will.deacon@arm.com,
dinguyen@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
atull@kernel.org, mdf@kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-fpga@vger.kernel.org, yves.vandervennet@linux.intel.com,
richard.gong@linux.intel.com
Subject: [PATCHv2 5/7] arm64: dts: stratix10: add fpga manager and region
Date: Thu, 1 Mar 2018 18:19:33 -0600 [thread overview]
Message-ID: <1519949975-13548-6-git-send-email-richard.gong@linux.intel.com> (raw)
In-Reply-To: <1519949975-13548-1-git-send-email-richard.gong@linux.intel.com>
From: Alan Tull <atull@kernel.org>
Add the Stratix10 FPGA manager and a FPGA region to the
device tree.
Signed-off-by: Alan Tull <atull@kernel.org>
---
v2: this patch is added in patch set version 2
---
arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi b/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi
index 4395e76..2f0067e 100644
--- a/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi
@@ -107,6 +107,14 @@
interrupt-parent = <&intc>;
ranges = <0 0 0 0xffffffff>;
+ base_fpga_region {
+ #address-cells = <0x1>;
+ #size-cells = <0x1>;
+
+ compatible = "fpga-region";
+ fpga-mgr = <&fpga_mgr>;
+ };
+
clkmgr: clock-controller@ffd10000 {
compatible = "intel,stratix10-clkmgr";
reg = <0xffd10000 0x1000>;
@@ -138,6 +146,10 @@
};
};
+ fpga_mgr: fpga-mgr@0 {
+ compatible = "intel,stratix10-soc-fpga-mgr";
+ };
+
gmac0: ethernet@ff800000 {
compatible = "altr,socfpga-stmmac", "snps,dwmac-3.74a", "snps,dwmac";
reg = <0xff800000 0x2000>;
--
2.7.4
next prev parent reply other threads:[~2018-03-02 0:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 0:19 [PATCHv2 0/7] Add Intel Stratix10 FPGA manager and service layer richard.gong
2018-03-02 0:19 ` [PATCHv2 1/7] dt-bindings, firmware: add Intel Stratix10 service layer binding richard.gong
2018-03-07 19:39 ` Rob Herring
2018-03-02 0:19 ` [PATCHv2 2/7] arm64: dts: stratix10: add service driver binding to base dtsi richard.gong
2018-03-02 0:19 ` [PATCHv2 3/7] driver, misc: add Intel Stratix10 service layer driver richard.gong
2018-03-15 16:48 ` Greg KH
2018-03-16 17:39 ` Richard Gong
2018-03-02 0:19 ` [PATCHv2 4/7] dt-bindings: fpga: add Stratix10 SoC FPGA manager binding richard.gong
2018-03-07 19:47 ` Rob Herring
2018-03-07 22:20 ` Alan Tull
2018-03-08 1:24 ` Rob Herring
2018-03-08 15:32 ` Alan Tull
2018-03-08 22:27 ` Rob Herring
2018-03-02 0:19 ` richard.gong [this message]
2018-03-02 0:19 ` [PATCHv2 6/7] fpga: add intel stratix10 soc fpga manager driver richard.gong
2018-03-02 0:19 ` [PATCHv2 7/7] defconfig: enable fpga and service layer richard.gong
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=1519949975-13548-6-git-send-email-richard.gong@linux.intel.com \
--to=richard.gong@linux.intel.com \
--cc=arnd@arndb.de \
--cc=atull@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mdf@kernel.org \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=yves.vandervennet@linux.intel.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).