On Fri, Mar 08, 2013 at 02:30:27PM +0100, Daniel Mack wrote: > On 08.03.2013 03:15, Mark Brown wrote:
> > Wouldn't this just be set up by the DT in the same way that other > > off-SoC hardware is? > Well, I thought so too. To repeat, in my DT, I have: OK, I got CCed in part way through the thread. > I would have expected that "fixed-clock" is matched by a driver lurking > around for DT boards, just like what the "fixed-regulator" driver does > for instance. But the clock device isn't initialized unless board code > explicitly calls of_clk_init() with a table mentioning "fixed-clock", as > in my patch. > I don't know the clock framework well enough, but it seems that either > all DT boards are supposed to do the same in their generic bits (which > sounds like a lot of code duplication), or the fixed-clock driver should > behave like any other driver wrt its probing from DT. I'm open to > suggestions :) Your expectation sounds like what I'd expect too...
signature.asc
Description: Digital signature
