On Tue, Jan 29, 2013 at 08:23:40, Shawn Guo wrote: > As multiplatform build is being adopted by more and more ARM platforms, > initcall function should be used very carefully. For example, when > GENERIC_CPUFREQ_CPU0 is built in the kernel, cpu0_cpufreq_driver_init() > will be called on all the platforms to initialize cpufreq-cpu0 driver. > > To eliminate this undesired the effect, the patch changes cpufreq-cpu0 > driver to have it instantiated as a platform_driver. Then it will only > run on platforms that create the platform_device "cpufreq-cpu0". > > Along with the change, it also changes cpu_dev to be &pdev->dev, > so that managed functions can start working, and module build gets > supported too. > > The existing users of cpufreq-cpu0 driver highbank and am33xx are also > updated accordingly to adapt the changes. > > Signed-off-by: Shawn Guo <shawn.guo@xxxxxxxxxx> > Cc: Mark Langsdorf <mark.langsdorf@xxxxxxxxxxx> > Cc: AnilKumar Ch <anilkumar@xxxxxx> > Cc: Tony Lindgren <tony@xxxxxxxxxxx> > Cc: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > --- > Changes since v1: > * Migrate cpufreq-cpu0 users in the same patch > > Rafael, > > The patch is based on Mark's highbank-cpufreq series and Nishanth's > "PM / OPP : export symbol consolidation" sereis. > > Mark, AnilKumar, > > I only compile-tested it on highbank and omap2. Please give it a test > no hardware to make sure cpufreq-cpu0 still works for you. Thanks. Hi Shawn, I hope this is based on linux-omap/master, to test the driver I have to add some patches on top of this patch, because of recent changes. I will provide the test details once I am done. Thanks AnilKumar -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
