cpufreq: make ti-cpufreq explicitly non-modular
authorPaul Gortmaker <paul.gortmaker@windriver.com>
Tue, 14 Feb 2017 00:45:02 +0000 (19:45 -0500)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 15 Feb 2017 23:58:52 +0000 (00:58 +0100)
commit149ab8649667eb50863495d841a7ba1110fc17d3
tree1e826162ed6b04420c76cfbf297ddb23d565df55
parentf451014692ae34e587b00de6745e16661cf734d8
cpufreq: make ti-cpufreq explicitly non-modular

The Kconfig currently controlling compilation of this code is:

drivers/cpufreq/Kconfig.arm:config ARM_TI_CPUFREQ
drivers/cpufreq/Kconfig.arm:    bool "Texas Instruments CPUFreq support"

...meaning that it currently is not being built as a module by anyone.

Lets remove the couple traces of modular infrastructure use, so that
when reading the driver there is no doubt it is builtin-only.

Since module_init translates to device_initcall in the non-modular
case, the init ordering remains unchanged with this commit.

We also delete the MODULE_LICENSE tag etc. since all that information
is already contained at the top of the file in the comments.

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/ti-cpufreq.c