summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/vf610.dtsi
diff options
context:
space:
mode:
authorStefan Agner <stefan@agner.ch>2014-11-02 23:36:44 +0300
committerShawn Guo <shawn.guo@linaro.org>2014-11-23 10:08:09 +0300
commit3f3ebfb84aad46e3b49a41fe2ed9037835b2860e (patch)
treec05f26f73bbf66a2b9105abcd89269243400290a /arch/arm/boot/dts/vf610.dtsi
parent7e41a98dcc1b220c2c705f839ba76787c08858d3 (diff)
downloadlinux-3f3ebfb84aad46e3b49a41fe2ed9037835b2860e.tar.xz
ARM: dts: vf610: assign oscillator to clock module
The clock controller module (CCM) has several clock inputs, which are connected to external crystal oscillators. To reflect this, assign these fixed clocks to the CCM node directly. This especially resolves initialization order dependencies we had with the earlier initialization code: When resolving of the fixed clocks failed in clk-vf610, the code created fixed clocks with a rate of 0. Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Diffstat (limited to 'arch/arm/boot/dts/vf610.dtsi')
-rw-r--r--arch/arm/boot/dts/vf610.dtsi25
1 files changed, 11 insertions, 14 deletions
diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
index 699da487222d..ed12d9a7be3e 100644
--- a/arch/arm/boot/dts/vf610.dtsi
+++ b/arch/arm/boot/dts/vf610.dtsi
@@ -44,21 +44,16 @@
};
};
- clocks {
- #address-cells = <1>;
- #size-cells = <0>;
-
- sxosc {
- compatible = "fixed-clock";
- #clock-cells = <0>;
- clock-frequency = <32768>;
- };
+ fxosc: fxosc {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <24000000>;
+ };
- fxosc {
- compatible = "fixed-clock";
- #clock-cells = <0>;
- clock-frequency = <24000000>;
- };
+ sxosc: sxosc {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <32768>;
};
soc {
@@ -358,6 +353,8 @@
clks: ccm@4006b000 {
compatible = "fsl,vf610-ccm";
reg = <0x4006b000 0x1000>;
+ clocks = <&sxosc>, <&fxosc>;
+ clock-names = "sxosc", "fxosc";
#clock-cells = <1>;
};