From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Ujfalusi Subject: Re: 32kHz clock removal causes problems omap_hsmmc Date: Wed, 19 Dec 2012 11:56:20 +0100 Message-ID: <50D19D54.2000307@ti.com> References: <1352968293.10872.51.camel@cumari.coelho.fi> <20121218095450.GB27751@arwen.pp.htv.fi> <20121219094552.GN4985@opensource.wolfsonmicro.com> <50D19040.5090404@ti.com> <20121219100909.GO4985@opensource.wolfsonmicro.com> <50D19463.5010605@ti.com> <20121219103206.GQ4985@opensource.wolfsonmicro.com> <1355913954.5273.21.camel@cumari.coelho.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from bear.ext.ti.com ([192.94.94.41]:57292 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751018Ab2LSK41 (ORCPT ); Wed, 19 Dec 2012 05:56:27 -0500 In-Reply-To: <1355913954.5273.21.camel@cumari.coelho.fi> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Luciano Coelho Cc: Mark Brown , Felipe Balbi , svenkatr@ti.com, linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org, cjb@laptop.org, lrg@ti.com, linux-kernel@vger.kernel.org, Tony Lindgren On 12/19/2012 11:45 AM, Luciano Coelho wrote: >> Well, we still haven't got the foggiest idea what the actual problem= is >> beyond that it's probably related to the 32kHz clock in some way (un= less >> it was one of the other reverts that coincidentally made a differenc= e, >> but we don't know what they were) so it's unlikely that just randoml= y >> implementing clock support is going to fix anything immediately here= =2E >=20 > This is exactly what I had to revert (as I mentioned in the other ema= il, > I had to revert the other patches otherwise compilation would break): >=20 > 0e8e5c34 "regulator: twl: Remove references to 32kHz clock from DT bi= ndings" > e76ab829 "regulator: twl: Remove references to the twl4030 regulator" > 029dd3ce "regulator: twl: Remove another unused variable warning" Yeah. 32k clock is not provided by twl. As I said I need to take a look at CCF to see if it already there. If i= t is clock driver + mapping + patch for wl12xx should fix the issue you are = facing. > Let me know if you need more info. BTW: have you happened to ubdate u-boot recently? There is a nice easte= r egg added there: f3f98bb ARM: OMAP4/5: Do not configure non essential pads, clocks, dpll= s. Which means that _essential_ clocks and pads are no longer configured. --=20 P=C3=A9ter