On Tuesday 29 March 2016 22:06:49 Viresh Kumar wrote:
On 29-03-16, 17:14, Arnd Bergmann wrote:
On Tuesday 29 March 2016 12:09:48 Viresh Kumar wrote:
+config CPUFREQ_DT_PLATDEV
- bool
- depends on CPUFREQ_DT
The 'depends on' line is redundant as you always 'select' the code from CPUFREQ_DT. Since they are always set together, you can also just drop the new symbol, or put the new code into the same file.
I would like to keep a separate file for this, it looks awkward to update the driver for any new user platform.
I added a separate symbol to take care of the Modular case of cpufreq-dt. i.e. I didn't wanted to add module_exit() code in the new file. Currently, it gets included in the kernel even if cpufreq-dt is selected as a Module, so we just create the platform-device just once and never touch it again.
Ok, that makes sense.
Regarding new platforms, I'd hope that we could manage to define an extension to the oppv2 binding that marks a machine as compatible with opp, so we can just look at that instead of the root compatible string. Your current series is nice in the way it gets the hack outside of my code, but it would be ideal if we could avoid propagating it further.
Arnd