[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111124010855.GN31337@atomide.com>
Date: Wed, 23 Nov 2011 17:08:55 -0800
From: Tony Lindgren <tony@...mide.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Greg KH <greg@...ah.com>, Mike Turquette <mturquette@...aro.org>,
linaro-dev@...ts.linaro.org, eric.miao@...aro.org,
grant.likely@...retlab.ca, jeremy.kerr@...onical.com,
Mike Turquette <mturquette@...com>, sboyd@...cinc.com,
magnus.damm@...il.com, dsaxena@...aro.org,
linux-arm-kernel@...ts.infradead.org, arnd.bergmann@...aro.org,
patches@...aro.org, tglx@...utronix.de, linux-omap@...r.kernel.org,
richard.zhao@...aro.org, shawn.guo@...escale.com, paul@...an.com,
linus.walleij@...ricsson.com, broonie@...nsource.wolfsonmicro.com,
linux-kernel@...r.kernel.org, amit.kucheria@...aro.org,
skannan@...cinc.com
Subject: Re: [PATCH v3 5/5] clk: export tree topology and clk data via sysfs
* Russell King - ARM Linux <linux@....linux.org.uk> [111123 14:07]:
> On Wed, Nov 23, 2011 at 10:55:19AM -0800, Tony Lindgren wrote:
> > What else are you aware of that is really needed early for clocks other
> > than clockevent?
>
> TWD will lose its auto-calibration. Then there's various clock source
> and clock event implementations. These all call for the clk API to be
> up and running at init_early time.
If we can't initialize those later on, then it sounds like some clocks
and some parts of the clock fwk code needs to be static.
However, we could still make big chunks of the clock framework into a
regular device driver for allocating non-static clocks, debugfs interface
and so on.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists