From: Kieran Bingham <kieran@ksquared.org.uk>
To: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.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>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"open list:ARM/RENESAS ARM64 ARCHITECTURE"
<linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM64 PORT AARCH64 ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Cc: Kieran Bingham <kieran@ksquared.org.uk>
Subject: [PATCH 1/2] arm64: dts: r8a7795: add FCPF device nodes
Date: Thu, 9 Jun 2016 17:42:48 +0100 [thread overview]
Message-ID: <1465490569-31177-2-git-send-email-kieran@bingham.xyz> (raw)
In-Reply-To: <1465490569-31177-1-git-send-email-kieran@bingham.xyz>
Provide nodes for the FCP devices dedicated to the FDP device channels.
Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
---
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
index 3285a9286786..e63e5f29cceb 100644
--- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
@@ -1223,5 +1223,26 @@
power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
status = "disabled";
};
+
+ fcpf0: fcp@fe950000 {
+ compatible = "renesas,r8a7795-fcpf", "renesas,fcpf";
+ reg = <0 0xfe950000 0 0x200>;
+ clocks = <&cpg CPG_MOD 615>;
+ power-domains = <&sysc R8A7795_PD_A3VP>;
+ };
+
+ fcpf1: fcp@fe951000 {
+ compatible = "renesas,r8a7795-fcpf", "renesas,fcpf";
+ reg = <0 0xfe951000 0 0x200>;
+ clocks = <&cpg CPG_MOD 614>;
+ power-domains = <&sysc R8A7795_PD_A3VP>;
+ };
+
+ fcpf2: fcp@fe952000 {
+ compatible = "renesas,r8a7795-fcpf", "renesas,fcpf";
+ reg = <0 0xfe952000 0 0x200>;
+ clocks = <&cpg CPG_MOD 613>;
+ power-domains = <&sysc R8A7795_PD_A3VP>;
+ };
};
};
--
2.7.4
next parent reply other threads:[~2016-06-09 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465490569-31177-1-git-send-email-kieran@bingham.xyz>
2016-06-09 16:42 ` Kieran Bingham [this message]
2016-06-09 16:42 ` [PATCH 2/2] arm64: dts: r8a7795: add FDP1 device nodes Kieran Bingham
2016-06-09 16:56 [RESEND PATCH 0/2] arm64: dts: r8a7795: Add FCPF and " Kieran Bingham
2016-06-09 16:56 ` [PATCH 1/2] arm64: dts: r8a7795: add FCPF " Kieran Bingham
[not found] ` <1465491418-32752-2-git-send-email-kieran-SI8QzZ7I9JUn3X9lZQuFcg@public.gmane.org>
2016-06-10 7:28 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2016-06-30 13:32 [PATCH v2 0/2] arm64: dts: r8a7795: FCPF and FDP1 " Kieran Bingham
2016-06-30 13:32 ` [PATCH 1/2] arm64: dts: r8a7795: add FCPF " Kieran Bingham
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=1465490569-31177-2-git-send-email-kieran@bingham.xyz \
--to=kieran@ksquared.org.uk \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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).