On Wed, 2012-12-19 at 10:32 +0000, Mark Brown wrote: > On Wed, Dec 19, 2012 at 11:18:11AM +0100, Peter Ujfalusi wrote: > > > Sure. It must be a clock driver. I already have similar driver (for McPDM fclk > > clock) for twl6040. > > Let me check linux-next, if CCF is there for OMAP I can send the 32k clock > > driver soon (after writing it and testing it). It is going to be for 3.9 but > > we can roll it with us I think locally to resolv issues. > > 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" Let me know if you need more info. -- Luca. -- 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
