On Friday 26 February 2016 17:07:09 Li Yang wrote:
>
> I don't have a perfect solution either. But I think this is still
> better than making cpufreq not usable. The cpufreq driver will print
> out an error message if thermal is not reachable. Maybe this can
> relief the confusion a little bit?
With my patch, the configuration will just force the cpufreq
driver to be a loadable module as well if thermal is a module,
so the dependency can be resolved by loading the thermal module first.
I think that is really the best way around the problem, and it
matches what other platforms do for the same problem.
Arnd
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
