On Tuesday 19 March 2013 11:23 PM, Nishanth Menon wrote: > We now use Soc generic cpufreq-cpu0 driver using DT entries. > However to allow cpufreq-cpu0 and omap-cpufreq drivers to co-exist, > we need to ensure the following using the same image: > 1. With device tree boot, we use cpufreq-cpu0 > 2. With non device tree boot, we use omap-cpufreq > > In the case of (1), we will have cpu OPPs and regulator registered > as part of the DT, to ensure that omap-cpufreq and cpufreq-cpu0 don't > conflict in managing the frequency of the same cpu, we should not > permit init to pass in omap-cpufreq. > > In the case of (2), we will not have the cpufreq-cpu0 device, hence > only omap-cpufreq will be active. > > So, to acommodate both these usage conditions, we fail init of > omap-cpufreq when we boot with device tree. > > Cc: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> > Cc: Jon Hunter <jon-hunter@xxxxxx> > Cc: "Benoît Cousson" <b-cousson@xxxxxx> > Cc: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > Cc: Shawn Guo <shawn.guo@xxxxxxxxxx> > Cc: Keerthy <j-keerthy@xxxxxx> > Cc: linux-omap@xxxxxxxxxxxxxxx > Cc: devicetree-discuss@xxxxxxxxxxxxxxxx > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Cc: cpufreq@xxxxxxxxxxxxxxx > Cc: linux-pm@xxxxxxxxxxxxxxx > > Signed-off-by: Nishanth Menon <nm@xxxxxx> > --- I haven't followed all the DT binding for opp discussion but this patch is inline to keep non-DT cpufreq working till we move to DT only build. So FWIW, Acked-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> -- 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
