* Nishanth Menon <nm@xxxxxx> [130405 10:22]:
> On 10:05-20130405, Tony Lindgren wrote:
> >
> > > diff --git a/arch/arm/mach-omap2/board-generic.c b/arch/arm/mach-omap2/board-generic.c
> > > index afa509a..5b147ef 100644
> > > --- a/arch/arm/mach-omap2/board-generic.c
> > > +++ b/arch/arm/mach-omap2/board-generic.c
> > > @@ -49,6 +49,11 @@ static void __init omap_generic_init(void)
> > > omap4_panda_display_init_of();
> > > else if (of_machine_is_compatible("ti,omap4-sdp"))
> > > omap_4430sdp_display_init_of();
> > > +
> > > + if (IS_ENABLED(CONFIG_GENERIC_CPUFREQ_CPU0)) {
> > > + struct platform_device_info devinfo = { .name = "cpufreq-cpu0", };
> > > + platform_device_register_full(&devinfo);
> > > + }
> > > }
> >
> > Hmm why would the driver need this? Sounds like the driver is
> > missing support for DT?
> Nope, this was a long chain of discussion in previous iterations of this
> patch.. more or less started here:
> https://patchwork.kernel.org/patch/2251821/
> Suggested as the generic approach for cpufreq drivers.
> Paul questioned this approach in:
> http://marc.info/?l=linux-pm&m=136485349218809&w=2
How about just set it up in omap2_common_pm_init instead
of the board-generic?
Regards,
Tony
--
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
