Thread (1 message) 1 message, 1 author, 2012-03-05

[PULL REQUEST v2] ARM: kirkwood: fdt: convert kirkwood init funcs to fdt

From: arnd@arndb.de (Arnd Bergmann)
Date: 2012-03-05 20:16:26
Also in: linux-devicetree

On Monday 05 March 2012, Jason wrote:
quoted
The clock frequency part being hardcoded to 200000 in the common .dtsi 
file looks wrong.  The clock may differ, and it used to (and should) be 
probed at run time, please see kirkwood_find_tclk().
So, should I EXPORT_SYMBOL_GPL(kirkwood_find_tclk); and have each driver
call it?
If the drivers want to use it, I think it has to be orion_find_tclk for
drivers that are shared between multiple plat-orion platforms.
One alternate idea I had was to have kirkwood-dreamplug.dts root hold

tclk: clock-frequency = <200000000>;

and then have the drivers ask for it.  afaict, tclk is constant per
board.

I'm fine with either way, but I'd rather have it in the dt.
IMHO it's best to leave any such hacks out of the device tree for
now, until we have the proper clk bindings in place for kirkwood,
and then we can just use those.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help