On Fri, Mar 22, 2013 at 07:13:33PM +0530, Viresh Kumar wrote:
I have never gone into coding for any non-ARM platform and am really not aware of acpi-cpufreq driver and its users. That's why i told everybody where the issue is, and they just need to fix acpi-cpufreq driver with right values of policy->cpus (affected_cpus) and everything else would work after that.
No, you're breaking existing drivers with your changes - nobody will fix stuff *you're* breaking.
You need to get the hardware and test your changes on *that* hardware too. Otherwise, the offending patches should be reverted until you can provide a patchset which works on everything.
Geez, the fact that I even need to explain this...