Thread (3 messages) 3 messages, 3 authors, 2011-11-03

[PATCH-V3 2/4] arm:omap:am33xx: Update common OMAP machine specific sources

From: tony@atomide.com (Tony Lindgren)
Date: 2011-10-06 23:03:08
Also in: linux-omap

Possibly related (same subject, not in this thread)

* Kevin Hilman [off-list ref] [110930 09:35]:
"Premi, Sanjeev" [off-list ref] writes:

Actually, looking at this closer, I think the infrastructure is already
there to handle this cleanly.

Basically, dpll5 should not even be registered for SoCs where it doesn't
exist.  Then, any attempts to use DPLL5 would know it doesn't exist
because the call to clk_get() in omap3_clk_lock_dpll5() would fail.
Yes please use the SoC specific lists, see what we have now queued
up in sram-map-io branch. So using SoC specific map_io + init_early +
set_globals should do the trick.
 
I think the clock3xxx_data.c needs a bit more cleanup so that only
clocks that exist for a given SoC are registered.

Paul already did a similar cleanup for the powerdomain data files by
creating separate lists for common ones and unique ones.  Looks like we
need the same for the clock data.
Right.

Regards,

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