cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2
authorViresh Kumar <viresh.kumar@linaro.org>
Wed, 16 Aug 2017 05:37:27 +0000 (11:07 +0530)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Thu, 24 Aug 2017 23:41:03 +0000 (01:41 +0200)
commitedeec420de2407618de097977e76b572d9de1bcf
tree87a78ea59dea36b66c5108e4eb8924d340073c8b
parentec4259aa4497d61d7dc168e0c303971b1fc6747d
cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2

The initial idea of creating the cpufreq-dt-platdev.c file was to keep a
list of platforms that use the "operating-points" (V1) bindings and
create cpufreq device for them only, as we weren't sure which platforms
would want the device to get created automatically as some had their own
cpufreq drivers as well, or wanted to initialize cpufreq after doing
some stuff from platform code.

But that wasn't the case with platforms using "operating-points-v2"
property. We wanted the device to get created automatically without the
need of adding them to the whitelist. Though, we will still have some
exceptions where we don't want to create the device automatically.

Rename the earlier platform list as *whitelist* and create a new
*blacklist* as well.

The cpufreq-dt device will get created if:
- The platform is there in the whitelist OR
- The platform has "operating-points-v2" property in CPU0's DT node and
  isn't part of the blacklist .

Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Reviewed-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/cpufreq-dt-platdev.c