On Fri, Jul 20, 2012 at 9:20 PM, Turquette, Mike <mturquette@xxxxxx> wrote: > On Fri, Jul 20, 2012 at 5:33 AM, Shawn Guo <shawn.guo@xxxxxxxxxx> wrote: >> On Fri, Jul 20, 2012 at 12:22:14PM +0530, Shilimkar, Santosh wrote: >>> This *_CPU0 doesn't seems to be appropriate since this infrastructure will be >>> used on SMP systems where CPUs shares clock/voltage rails. May be you can >>> get rid of that unless there is a strong need. >>> >> All the resource handlers, clk, regulator, opp, DT node, are retrieved >> from CPU0 device even for SMP. I hope the naming of the driver could >> tell: >> >> - The driver supports UP >> - The driver supports SMP where CPUs shares clock/voltage rails by >> managing CPU0 (resource) >> - The driver does not support SMP where individual CPU can scale >> clock/voltage independently. >> > > How about cpufreq-single-thread.c and CONFIG_CPUFREQ_SINGLE_THREAD? > That makes sense for both UP and SMP. > Indeed. This sounds more appropriate and also reflects what actually happens with a UP or shared clock SMP case. Regards Santosh -- 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
