From: "Andreas Färber" <afaerber@suse.de>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, "Roc He" <hepeng@zidoo.tv>,
蒋丽琴 <jiang.liqin@geniatech.com>,
"Andreas Färber" <afaerber@suse.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will.deacon@arm.com>,
devicetree@vger.kernel.org
Subject: [PATCH v4 3/3] arm64: dts: realtek: Add RTD1295 RTC node
Date: Tue, 5 Sep 2017 00:53:24 +0200 [thread overview]
Message-ID: <20170904225324.29138-4-afaerber@suse.de> (raw)
In-Reply-To: <20170904225324.29138-1-afaerber@suse.de>
Add RTC node to the Realtek RTD1295 Device Tree.
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
v3 -> v4: Unchanged
v2 -> v3:
* Rebased to no longer depend on reset controller series
v1 -> v2: Unchanged
Depends on the pending clock bindings.
arch/arm64/boot/dts/realtek/rtd1295.dtsi | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/realtek/rtd1295.dtsi b/arch/arm64/boot/dts/realtek/rtd1295.dtsi
index ab72255f843f..fbbd6456079e 100644
--- a/arch/arm64/boot/dts/realtek/rtd1295.dtsi
+++ b/arch/arm64/boot/dts/realtek/rtd1295.dtsi
@@ -164,6 +164,12 @@
status = "disabled";
};
+ rtc@9801b600 {
+ compatible = "realtek,rtd1295-rtc";
+ reg = <0x9801b600 0x100>;
+ clocks = <&clkc RTD1295_CLK_EN_MISC_RTC>;
+ };
+
gic: interrupt-controller@ff011000 {
compatible = "arm,gic-400";
reg = <0xff011000 0x1000>,
--
2.13.5
next prev parent reply other threads:[~2017-09-04 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 22:53 [PATCH v4 0/3] arm64: Realtek RTD1295 RTC Andreas Färber
2017-09-04 22:53 ` [PATCH v4 1/3] dt-bindings: rtc: Add Realtek RTD1295 Andreas Färber
2017-09-04 22:53 ` [PATCH v4 2/3] " Andreas Färber
2017-09-04 22:53 ` Andreas Färber [this message]
2017-09-05 7:59 ` [PATCH v4 0/3] arm64: Realtek RTD1295 RTC Alexandre Belloni
2017-09-05 8:03 ` Andreas Färber
2017-09-05 8:09 ` Alexandre Belloni
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=20170904225324.29138-4-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=hepeng@zidoo.tv \
--cc=jiang.liqin@geniatech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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
all inboxes | Powered by JetHome®