Re: 32kHz clock removal causes problems omap_hsmmc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 (unless
>> it was one of the other reverts that coincidentally made a difference,
>> but we don't know what they were) so it's unlikely that just randomly
>> implementing clock support is going to fix anything immediately here.
> 
> This is exactly what I had to revert (as I mentioned in the other email,
> I had to revert the other patches otherwise compilation would break):
> 
> 0e8e5c34 "regulator: twl: Remove references to 32kHz clock from DT bindings"
> 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 it 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 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.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux