summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/vf610-cosmic.dts
diff options
context:
space:
mode:
authorStefan Agner <stefan@agner.ch>2014-11-02 21:36:44 +0100
committerShawn Guo <shawn.guo@linaro.org>2014-11-23 08:08:09 +0100
commit3f3ebfb84aad46e3b49a41fe2ed9037835b2860e (patch)
treec05f26f73bbf66a2b9105abcd89269243400290a /arch/arm/boot/dts/vf610-cosmic.dts
parentdt-bindings: arm: add Freescale LS1021A SoC device tree binding (diff)
downloadlinux-3f3ebfb84aad46e3b49a41fe2ed9037835b2860e.tar.xz
linux-3f3ebfb84aad46e3b49a41fe2ed9037835b2860e.zip
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-cosmic.dts')
-rw-r--r--arch/arm/boot/dts/vf610-cosmic.dts14
1 files changed, 8 insertions, 6 deletions
diff --git a/arch/arm/boot/dts/vf610-cosmic.dts b/arch/arm/boot/dts/vf610-cosmic.dts
index 3fd1b74e1216..b0ce8b8b2e0e 100644
--- a/arch/arm/boot/dts/vf610-cosmic.dts
+++ b/arch/arm/boot/dts/vf610-cosmic.dts
@@ -23,14 +23,16 @@
reg = <0x80000000 0x10000000>;
};
- clocks {
- enet_ext {
- compatible = "fixed-clock";
- #clock-cells = <0>;
- clock-frequency = <50000000>;
- };
+ enet_ext: enet_ext {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <50000000>;
};
+};
+&clks {
+ clocks = <&sxosc>, <&fxosc>, <&enet_ext>;
+ clock-names = "sxosc", "fxosc", "enet_ext";
};
&fec1 {