On 13-12-18, 02:32, Stephen Boyd wrote: > I have one policy for four CPUs. So take down all four of those CPUs by > writing a 0 to the online file for each CPU, and then bring them back > online. That should make cpufreq_driver->init() be called twice, once > during boot when the CPUs are bound to the cpufreq devices, and second > from the sysfs write when the user brings the first CPU in that policy > online again by writing a 1 to the online file. If that second time it > fails I suspect we hit the lockdep warning. Okay, that is a special sequence. I will try to reproduce that locally. Thanks. -- viresh
