On 19 October 2013 22:05, Mark Brown <broonie@xxxxxxxxxx> wrote:
> Hi,
>
> I've not yet had a chance to bisect this but it appears that Arndale
> boot has broken for me recently in -next; I'm getting absolutely no
> serial output at all afther the bootloader hands off to Linux so no
> useful diagnostics. Is this a known issue?
>
On next-20131018, bisect points to following commit.
commit 65cd4f6c99c1170bd0114dbd71b978012ea44d28
Author: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
Date: Thu Jul 18 16:21:18 2013 -0700
Subject: arch_timer: Move to generic sched_clock framework
I don't know if this is a fix, but removing armv7-timer DT node brings
Arndale back to booting state.
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts/exynos5250.dtsi
index 9db5047..bb583f6 100644
--- a/arch/arm/boot/dts/exynos5250.dtsi
+++ b/arch/arm/boot/dts/exynos5250.dtsi
@@ -90,19 +90,6 @@
#clock-cells = <1>;
};
- timer {
- compatible = "arm,armv7-timer";
- interrupts = <1 13 0xf08>,
- <1 14 0xf08>,
- <1 11 0xf08>,
- <1 10 0xf08>;
- /* Unfortunately we need this since some versions of U-Boot
- * on Exynos don't set the CNTFRQ register, so we need the
- * value from DT.
- */
- clock-frequency = <24000000>;
- };
-
mct@101C0000 {
compatible = "samsung,exynos4210-mct";
reg = <0x101C0000 0x800>;
--
Tushar Behera
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
