Re: 32kHz clock removal causes problems omap_hsmmc

[Tony Lindgren <tony@atomide.com>]

* Peter Ujfalusi <peter.ujfalusi@ti.com> [121219 02:20]:
> On 12/19/2012 11:09 AM, Mark Brown wrote:
> > On Wed, Dec 19, 2012 at 11:00:32AM +0100, Peter Ujfalusi wrote:
> > 
> >> I don't know the state of the common clock framework for OMAPs. Is it already
> >> up in 3.7? Or going for 3.8? 3.9? 3.10?...
> >> We need CCF to resolve this. I can cook up the clock driver for the 32k clock
> >> from twl, but in order to use it we need CCF on OMAP.
> > 
> > Well, we at least ought to make sure it doesn't appear in the regulator
> > DT bindings even if it's handled via some OMAP magic - that was the key
> > point here.
> 
> 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.

The omap common clock patches are now in mainline kernel as of v3.8
merge window.

Tony