On 17 July 2014 02:48, Rafael J. Wysocki <[email protected]> wrote: > I don't like that idea, but I wonder what other people think.
Hmm, the other thread around looking at the bindings is really slow. One common thing around the platforms which want to use cpufreq-cpu0 is they have different clocks for ALL CPUs. I was wondering if instead of a clock-matching routine, we can provide some temporary relief to them via some other means. I meant we can allow cpufreq-cpu0/generic to either set policy->cpus to ALL CPUs or just 1. So that existing and these new platforms can atleast get going.. But don't know how should we do that. Not a binding ofcourse, a Kconfig option could work but multiplatform stuff would break. What else? Maybe platform data as we are handling cpufreq-cpu0 with a platform device? -- viresh -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
