summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/kirkwood-km_kirkwood.dts
diff options
context:
space:
mode:
authorJason Cooper <jason@lakedaemon.net>2013-01-29 20:36:43 +0000
committerJason Cooper <jason@lakedaemon.net>2013-03-08 21:32:52 +0000
commit93fff4ce19f9978cc1c59db42760717477939249 (patch)
treeed50ae11f815b991b324e4490f62515f9dbeafe1 /arch/arm/boot/dts/kirkwood-km_kirkwood.dts
parent6dbe51c251a327e012439c4772097a13df43c5b8 (diff)
downloadlinux-93fff4ce19f9978cc1c59db42760717477939249.tar.gz
linux-93fff4ce19f9978cc1c59db42760717477939249.tar.bz2
linux-93fff4ce19f9978cc1c59db42760717477939249.zip
ARM: kirkwood: of_serial: fix clock gating by removing clock-frequency
When DT support for kirkwood was first introduced, there was no clock infrastructure. As a result, we had to manually pass the clock-frequency to the driver from the device node. Unfortunately, on kirkwood, with minimal config or all module configs, clock-frequency breaks booting because of_serial doesn't consume the gate_clk when clock-frequency is defined. The end result on kirkwood is that runit gets gated, and then the boot fails when the kernel tries to write to the serial port. Fix the issue by removing the clock-frequency parameter from all kirkwood dts files. Booted on dreamplug without earlyprintk and successfully logged in via ttyS0. Reported-by: Simon Baatz <gmbnomis@gmail.com> Tested-by: Simon Baatz <gmbnomis@gmail.com> Cc: <stable@vger.kernel.org> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/boot/dts/kirkwood-km_kirkwood.dts')
-rw-r--r--arch/arm/boot/dts/kirkwood-km_kirkwood.dts1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm/boot/dts/kirkwood-km_kirkwood.dts b/arch/arm/boot/dts/kirkwood-km_kirkwood.dts
index 8db3123ac80f..5bbd0542cdd3 100644
--- a/arch/arm/boot/dts/kirkwood-km_kirkwood.dts
+++ b/arch/arm/boot/dts/kirkwood-km_kirkwood.dts
@@ -34,7 +34,6 @@
};
serial@12000 {
- clock-frequency = <200000000>;
status = "ok";
};