From: Weiyi Lu <weiyi.lu@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Mike Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>
Cc: James Liao <jamesjj.liao@mediatek.com>,
Fan Chen <fan.chen@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-clk@vger.kernel.org, srv_heupstream@mediatek.com,
Weiyi Lu <weiyi.lu@mediatek.com>
Subject: [PATCH v2 4/5] arm64: dts: add clock device nodes of MT2712
Date: Mon, 12 Mar 2018 15:03:41 +0800 [thread overview]
Message-ID: <20180312070342.4335-6-weiyi.lu@mediatek.com> (raw)
In-Reply-To: <20180312070342.4335-1-weiyi.lu@mediatek.com>
add new clocks according to ECO design change
Signed-off-by: Weiyi Lu <weiyi.lu@mediatek.com>
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index fdf66f4fe7c3..d7688bc9db1b 100644
--- a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
@@ -199,6 +199,34 @@
clock-output-names = "clkaud_ext_i_2";
};
+ clki2si0_mck_i: oscillator@6 {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <30000000>;
+ clock-output-names = "clki2si0_mck_i";
+ };
+
+ clki2si1_mck_i: oscillator@7 {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <30000000>;
+ clock-output-names = "clki2si1_mck_i";
+ };
+
+ clki2si2_mck_i: oscillator@8 {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <30000000>;
+ clock-output-names = "clki2si2_mck_i";
+ };
+
+ clktdmin_mclk_i: oscillator@9 {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <30000000>;
+ clock-output-names = "clktdmin_mclk_i";
+ };
+
timer {
compatible = "arm,armv8-timer";
interrupt-parent = <&gic>;
--
2.12.5
next prev parent reply other threads:[~2018-03-12 7:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 7:03 [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support Weiyi Lu
2018-03-12 7:03 ` Weiyi Lu
2018-03-12 7:03 ` [PATCH v2 1/5] dt-bindings: soc: update MT2712 power dt-bindings Weiyi Lu
2018-03-19 1:32 ` Matthias Brugger
2018-03-12 7:03 ` [PATCH v2 2/5] soc: mediatek: update power domain data of MT2712 Weiyi Lu
2018-03-19 1:33 ` Matthias Brugger
[not found] ` <20180312070342.4335-1-weiyi.lu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-03-12 7:03 ` [PATCH v2 3/5] dt-bindings: clock: add clocks for MT2712 Weiyi Lu
2018-03-18 12:48 ` Rob Herring
2018-03-19 21:38 ` Stephen Boyd
2018-03-12 7:03 ` Weiyi Lu [this message]
2018-03-12 7:03 ` [PATCH v2 5/5] clk: mediatek: update clock driver of MT2712 Weiyi Lu
2018-03-19 21:38 ` Stephen Boyd
2018-03-20 6:07 ` [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support Weiyi Lu
2018-03-20 7:23 ` Stephen Boyd
2018-03-21 9:11 ` Matthias Brugger
2018-04-17 14:22 ` Matthias Brugger
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=20180312070342.4335-6-weiyi.lu@mediatek.com \
--to=weiyi.lu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=fan.chen@mediatek.com \
--cc=jamesjj.liao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=srv_heupstream@mediatek.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).