On Thu, Apr 07, 2011 at 05:38:38PM -0700, Kevin Hilman wrote: > "Rafael J. Wysocki" <rjw@xxxxxxx> writes: > > On Thursday, April 07, 2011, Kevin Hilman wrote: > >> Paul Mundt <lethal@xxxxxxxxxxxx> writes: > >> > This observation is wholly architecture agnostic, so it's not clear that > >> > keeping it in arch/arm/common is any better. It seems that this would be > >> > better suited for drivers/base/power/ with a generic Kconfig symbol. > >> > >> Sounds fine to me. > > > > Well, what platforms is the clock framework available on? > > Well, the majority of implementations of <linux/clk.h> are certainly in > ARM, but I know it's also implemented for SH, and a quick grep shows > implementations in powerpc, mips and m68k also. > We also have CONFIG_HAVE_CLK that can be used as a dependency. In any event, anything simply focusing on the clock bits can be completely generic. On SH we still have these things lumped together with hwblk IDs, but this is something we can likely transition off of with power domains. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
