[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50D19E52.9030003@ti.com>
Date: Wed, 19 Dec 2012 12:00:34 +0100
From: Peter Ujfalusi <peter.ujfalusi@...com>
To: Luciano Coelho <coelho@...com>
CC: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Felipe Balbi <balbi@...com>, <svenkatr@...com>,
<linux-omap@...r.kernel.org>, <linux-mmc@...r.kernel.org>,
<cjb@...top.org>, <lrg@...com>, <linux-kernel@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>
Subject: Re: 32kHz clock removal causes problems omap_hsmmc
On 12/19/2012 11:56 AM, Peter Ujfalusi wrote:
> BTW: have you happened to ubdate u-boot recently? There is a nice easter egg
> added there:
> f3f98bb ARM: OMAP4/5: Do not configure non essential pads, clocks, dplls.
>
> Which means that _essential_ clocks and pads are no longer configured.
Meanwhile you can try to hack the u-boot to enable the 32k from there. It is
going to stay up since we do not have code to control it in the kernel anymore.
Also do something like this at the same time to get things working:
diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h
index cbc9bdb..b0ff1ec 100644
--- a/include/configs/omap4_common.h
+++ b/include/configs/omap4_common.h
@@ -271,4 +271,8 @@
#define CONFIG_SYS_THUMB_BUILD
+/* Configure all pins and clocks */
+#define CONFIG_SYS_ENABLE_PADS_ALL
+#define CONFIG_SYS_CLOCKS_ENABLE_ALL
+
#endif /* __CONFIG_OMAP4_COMMON_H */
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists