From: Derek Basehore <dbasehore@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
tony.xie@rock-chips.com, zyw@rock-chips.com, ayaka@soulik.info,
nickey.yang@rock-chips.com, zhengsq@rock-chips.com,
klaus.goger@theobroma-systems.com, dianders@chromium.org,
briannorris@chromium.org, enric.balletbo@collabora.com,
heiko@sntech.de, mark.rutland@arm.com, robh+dt@kernel.org,
Derek Basehore <dbasehore@chromium.org>
Subject: [PATCH] arm64: dts: rockchip: rk3399: Add xin32k clk
Date: Thu, 15 Nov 2018 21:17:19 -0800 [thread overview]
Message-ID: <20181116051719.23376-1-dbasehore@chromium.org> (raw)
This adds the xin32k clock to the RK3399 CPU. Even though it's not
directly used, muxes will end up traversing the entire clk tree on
calls to determine_rate if it doesn't exist.
Signed-off-by: Derek Basehore <dbasehore@chromium.org>
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
index 99e7f65c1779..3d09472978f8 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
@@ -191,6 +191,13 @@
#clock-cells = <0>;
};
+ ap_rtc_clk: ap-rtc-clk {
+ compatible = "fixed-clock";
+ clock-frequency = <32768>;
+ clock-output-names = "xin32k";
+ #clock-cells = <0>;
+ };
+
amba {
compatible = "simple-bus";
#address-cells = <2>;
--
2.19.1.1215.g8438c0b245-goog
next reply other threads:[~2018-11-16 5:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 5:17 Derek Basehore [this message]
2018-11-16 16:00 ` [PATCH] arm64: dts: rockchip: rk3399: Add xin32k clk Doug Anderson
2018-11-16 17:39 ` dbasehore .
2018-11-16 18:23 ` Heiko Stübner
[not found] ` <CAGAzgsq7uF=E3dzhyCjK4gq09_UV_aZhQbyaTnz7yDY_ErQYKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-11-16 18:23 ` Doug Anderson
2018-11-19 9:41 ` Heiko Stübner
2018-11-20 2:05 ` dbasehore .
-- strict thread matches above, loose matches on Subject: below --
2018-11-16 0:42 Derek Basehore
2018-11-16 5:03 ` Doug Anderson
2018-11-16 5:17 ` dbasehore .
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=20181116051719.23376-1-dbasehore@chromium.org \
--to=dbasehore@chromium.org \
--cc=ayaka@soulik.info \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=heiko@sntech.de \
--cc=klaus.goger@theobroma-systems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nickey.yang@rock-chips.com \
--cc=robh+dt@kernel.org \
--cc=tony.xie@rock-chips.com \
--cc=zhengsq@rock-chips.com \
--cc=zyw@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).