On Tue, Nov 27, 2012 at 9:33 AM, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > On 27 November 2012 14:54, Sudeep K N <sudeepholla.maillist@xxxxxxxxx> wrote: >> On Sat, Nov 24, 2012 at 7:39 PM, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: >> [...] >>> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-spear.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-spear.txt >>> new file mode 100644 >>> index 0000000..4cf2819 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-spear.txt >>> @@ -0,0 +1,29 @@ >>> +SPEAr cpufreq driver >>> +------------------- >>> + >>> +SPEAr SoC cpufreq driver for CPU frequency scaling. >>> +It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) systems >>> +which share clock across all CPUs. >> >> If this is the case, is there any particular reason why you cannot use >> the generic >> cpufreq-cpu0 driver ? > > Please go through the discussion already done with Shawn. There is lot of > SPEAr specific code here. > Sorry I missed the fact that there are more patches, I based my commit on clock related changes in current patch. -- Regards, Sudeep -- 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
