2011-06-02 04:18:22 +07:00
|
|
|
#
|
|
|
|
|
# ARM CPU Frequency scaling drivers
|
|
|
|
|
#
|
|
|
|
|
|
2014-03-14 13:40:54 +07:00
|
|
|
# big LITTLE core layer and glue drivers
|
2013-04-01 19:57:49 +07:00
|
|
|
config ARM_BIG_LITTLE_CPUFREQ
|
2013-05-04 13:33:54 +07:00
|
|
|
tristate "Generic ARM big LITTLE CPUfreq driver"
|
2014-06-06 04:50:10 +07:00
|
|
|
depends on ARM && BIG_LITTLE && ARM_CPU_TOPOLOGY && HAVE_CLK
|
2013-12-12 05:12:27 +07:00
|
|
|
select PM_OPP
|
2013-05-04 13:33:54 +07:00
|
|
|
help
|
|
|
|
|
This enables the Generic CPUfreq driver for ARM big.LITTLE platforms.
|
2013-04-01 19:57:49 +07:00
|
|
|
|
|
|
|
|
config ARM_DT_BL_CPUFREQ
|
2013-05-04 13:33:54 +07:00
|
|
|
tristate "Generic probing via DT for ARM big LITTLE CPUfreq driver"
|
|
|
|
|
depends on ARM_BIG_LITTLE_CPUFREQ && OF
|
2013-04-01 19:57:49 +07:00
|
|
|
help
|
2013-05-04 13:33:54 +07:00
|
|
|
This enables probing via DT for Generic CPUfreq driver for ARM
|
|
|
|
|
big.LITTLE platform. This gets frequency tables from DT.
|
2013-04-01 19:57:49 +07:00
|
|
|
|
2014-03-14 13:40:54 +07:00
|
|
|
config ARM_VEXPRESS_SPC_CPUFREQ
|
|
|
|
|
tristate "Versatile Express SPC based CPUfreq driver"
|
|
|
|
|
depends on ARM_BIG_LITTLE_CPUFREQ && ARCH_VEXPRESS_SPC
|
|
|
|
|
help
|
|
|
|
|
This add the CPUfreq driver support for Versatile Express
|
|
|
|
|
big.LITTLE platforms using SPC for power management.
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 19:54:09 +07:00
|
|
|
config ARM_EXYNOS_CPUFREQ
|
cpufreq: exynos: allow modular build
The exynos cpufreq driver code recently gained a dependency on the
cooling code, which may be a loadable module. This breaks an ARM
allmodconfig build:
drivers/built-in.o: In function `exynos_cpufreq_probe':
:(.text+0x1748e8): undefined reference to `of_cpufreq_cooling_register'
To avoid this problem, change cpufreq Kconfig to allow the drivers
to be loadable modules as well and enforce a dependency on the
thermal module.
This change, in order to allow module builds on this cpufreq
driver, properly constructs the driver into a single module,
instead of several modules. The change also keeps the proper
platform dependency, and therefore, it wont load in platforms
that are not supposed to be loaded. The user will be able to
build the support for all platforms, or select which platforms
(s)he wants (as originally), except that now it can be a module,
instead.
Besides, it will still keep the driver only on those configs
that expect it to be on. And it won't compile/load on platforms
that it is not supposed to. It brings the config ARM_EXYNOS_CPU_FREQ_BOOST_SW
closer to this driver, so it looks better in the menuconfig.
We intentionally change ARM_EXYNOS5440_CPUFREQ to be tristate too, to
avoid future troubles.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Kukjin Kim <kgene@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-pm@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org
Fixes: e725d26c4857 ("cpufreq: exynos: Use device tree to determine if cpufreq cooling should be registered")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
2015-02-01 01:35:18 +07:00
|
|
|
tristate "SAMSUNG EXYNOS CPUfreq Driver"
|
|
|
|
|
depends on CPU_EXYNOS4210 || SOC_EXYNOS4212 || SOC_EXYNOS4412 || SOC_EXYNOS5250
|
|
|
|
|
depends on THERMAL
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Samsung EXYNOS platforms.
|
|
|
|
|
Supported SoC versions are:
|
|
|
|
|
Exynos4210, Exynos4212, Exynos4412, and Exynos5250.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
2013-04-04 19:54:09 +07:00
|
|
|
|
|
|
|
|
config ARM_EXYNOS4210_CPUFREQ
|
2013-08-09 19:04:55 +07:00
|
|
|
bool "SAMSUNG EXYNOS4210"
|
2014-05-26 04:26:03 +07:00
|
|
|
depends on CPU_EXYNOS4210
|
cpufreq: exynos: allow modular build
The exynos cpufreq driver code recently gained a dependency on the
cooling code, which may be a loadable module. This breaks an ARM
allmodconfig build:
drivers/built-in.o: In function `exynos_cpufreq_probe':
:(.text+0x1748e8): undefined reference to `of_cpufreq_cooling_register'
To avoid this problem, change cpufreq Kconfig to allow the drivers
to be loadable modules as well and enforce a dependency on the
thermal module.
This change, in order to allow module builds on this cpufreq
driver, properly constructs the driver into a single module,
instead of several modules. The change also keeps the proper
platform dependency, and therefore, it wont load in platforms
that are not supposed to be loaded. The user will be able to
build the support for all platforms, or select which platforms
(s)he wants (as originally), except that now it can be a module,
instead.
Besides, it will still keep the driver only on those configs
that expect it to be on. And it won't compile/load on platforms
that it is not supposed to. It brings the config ARM_EXYNOS_CPU_FREQ_BOOST_SW
closer to this driver, so it looks better in the menuconfig.
We intentionally change ARM_EXYNOS5440_CPUFREQ to be tristate too, to
avoid future troubles.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Kukjin Kim <kgene@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-pm@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org
Fixes: e725d26c4857 ("cpufreq: exynos: Use device tree to determine if cpufreq cooling should be registered")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
2015-02-01 01:35:18 +07:00
|
|
|
depends on ARM_EXYNOS_CPUFREQ
|
2013-08-09 19:04:55 +07:00
|
|
|
default y
|
2013-04-04 19:54:09 +07:00
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Samsung EXYNOS4210
|
|
|
|
|
SoC (S5PV310 or S5PC210).
|
|
|
|
|
|
2013-08-09 19:04:55 +07:00
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2013-04-04 19:54:09 +07:00
|
|
|
config ARM_EXYNOS4X12_CPUFREQ
|
2013-08-09 19:04:55 +07:00
|
|
|
bool "SAMSUNG EXYNOS4x12"
|
2014-05-26 04:26:03 +07:00
|
|
|
depends on SOC_EXYNOS4212 || SOC_EXYNOS4412
|
cpufreq: exynos: allow modular build
The exynos cpufreq driver code recently gained a dependency on the
cooling code, which may be a loadable module. This breaks an ARM
allmodconfig build:
drivers/built-in.o: In function `exynos_cpufreq_probe':
:(.text+0x1748e8): undefined reference to `of_cpufreq_cooling_register'
To avoid this problem, change cpufreq Kconfig to allow the drivers
to be loadable modules as well and enforce a dependency on the
thermal module.
This change, in order to allow module builds on this cpufreq
driver, properly constructs the driver into a single module,
instead of several modules. The change also keeps the proper
platform dependency, and therefore, it wont load in platforms
that are not supposed to be loaded. The user will be able to
build the support for all platforms, or select which platforms
(s)he wants (as originally), except that now it can be a module,
instead.
Besides, it will still keep the driver only on those configs
that expect it to be on. And it won't compile/load on platforms
that it is not supposed to. It brings the config ARM_EXYNOS_CPU_FREQ_BOOST_SW
closer to this driver, so it looks better in the menuconfig.
We intentionally change ARM_EXYNOS5440_CPUFREQ to be tristate too, to
avoid future troubles.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Kukjin Kim <kgene@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-pm@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org
Fixes: e725d26c4857 ("cpufreq: exynos: Use device tree to determine if cpufreq cooling should be registered")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
2015-02-01 01:35:18 +07:00
|
|
|
depends on ARM_EXYNOS_CPUFREQ
|
2013-08-09 19:04:55 +07:00
|
|
|
default y
|
2013-04-04 19:54:09 +07:00
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Samsung EXYNOS4X12
|
|
|
|
|
SoC (EXYNOS4212 or EXYNOS4412).
|
|
|
|
|
|
2013-08-09 19:04:55 +07:00
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2013-04-04 19:54:09 +07:00
|
|
|
config ARM_EXYNOS5250_CPUFREQ
|
2013-08-09 19:04:55 +07:00
|
|
|
bool "SAMSUNG EXYNOS5250"
|
2014-05-26 04:26:03 +07:00
|
|
|
depends on SOC_EXYNOS5250
|
cpufreq: exynos: allow modular build
The exynos cpufreq driver code recently gained a dependency on the
cooling code, which may be a loadable module. This breaks an ARM
allmodconfig build:
drivers/built-in.o: In function `exynos_cpufreq_probe':
:(.text+0x1748e8): undefined reference to `of_cpufreq_cooling_register'
To avoid this problem, change cpufreq Kconfig to allow the drivers
to be loadable modules as well and enforce a dependency on the
thermal module.
This change, in order to allow module builds on this cpufreq
driver, properly constructs the driver into a single module,
instead of several modules. The change also keeps the proper
platform dependency, and therefore, it wont load in platforms
that are not supposed to be loaded. The user will be able to
build the support for all platforms, or select which platforms
(s)he wants (as originally), except that now it can be a module,
instead.
Besides, it will still keep the driver only on those configs
that expect it to be on. And it won't compile/load on platforms
that it is not supposed to. It brings the config ARM_EXYNOS_CPU_FREQ_BOOST_SW
closer to this driver, so it looks better in the menuconfig.
We intentionally change ARM_EXYNOS5440_CPUFREQ to be tristate too, to
avoid future troubles.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Kukjin Kim <kgene@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-pm@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org
Fixes: e725d26c4857 ("cpufreq: exynos: Use device tree to determine if cpufreq cooling should be registered")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
2015-02-01 01:35:18 +07:00
|
|
|
depends on ARM_EXYNOS_CPUFREQ
|
2013-08-09 19:04:55 +07:00
|
|
|
default y
|
2013-04-04 19:54:09 +07:00
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Samsung EXYNOS5250
|
|
|
|
|
SoC.
|
|
|
|
|
|
2013-08-09 19:04:55 +07:00
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2013-12-20 21:24:51 +07:00
|
|
|
config ARM_EXYNOS_CPU_FREQ_BOOST_SW
|
|
|
|
|
bool "EXYNOS Frequency Overclocking - Software"
|
2014-09-03 20:18:12 +07:00
|
|
|
depends on ARM_EXYNOS_CPUFREQ && THERMAL
|
2013-12-20 21:24:51 +07:00
|
|
|
select CPU_FREQ_BOOST_SW
|
|
|
|
|
select EXYNOS_THERMAL
|
|
|
|
|
help
|
|
|
|
|
This driver supports software managed overclocking (BOOST).
|
|
|
|
|
It allows usage of special frequencies for Samsung Exynos
|
|
|
|
|
processors if thermal conditions are appropriate.
|
|
|
|
|
|
2014-04-23 02:40:10 +07:00
|
|
|
It requires, for safe operation, thermal framework with properly
|
2013-12-20 21:24:51 +07:00
|
|
|
defined trip points.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
cpufreq: exynos: allow modular build
The exynos cpufreq driver code recently gained a dependency on the
cooling code, which may be a loadable module. This breaks an ARM
allmodconfig build:
drivers/built-in.o: In function `exynos_cpufreq_probe':
:(.text+0x1748e8): undefined reference to `of_cpufreq_cooling_register'
To avoid this problem, change cpufreq Kconfig to allow the drivers
to be loadable modules as well and enforce a dependency on the
thermal module.
This change, in order to allow module builds on this cpufreq
driver, properly constructs the driver into a single module,
instead of several modules. The change also keeps the proper
platform dependency, and therefore, it wont load in platforms
that are not supposed to be loaded. The user will be able to
build the support for all platforms, or select which platforms
(s)he wants (as originally), except that now it can be a module,
instead.
Besides, it will still keep the driver only on those configs
that expect it to be on. And it won't compile/load on platforms
that it is not supposed to. It brings the config ARM_EXYNOS_CPU_FREQ_BOOST_SW
closer to this driver, so it looks better in the menuconfig.
We intentionally change ARM_EXYNOS5440_CPUFREQ to be tristate too, to
avoid future troubles.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Kukjin Kim <kgene@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-pm@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org
Fixes: e725d26c4857 ("cpufreq: exynos: Use device tree to determine if cpufreq cooling should be registered")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
2015-02-01 01:35:18 +07:00
|
|
|
config ARM_EXYNOS5440_CPUFREQ
|
|
|
|
|
tristate "SAMSUNG EXYNOS5440"
|
|
|
|
|
depends on SOC_EXYNOS5440
|
|
|
|
|
depends on HAVE_CLK && OF
|
|
|
|
|
select PM_OPP
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Samsung EXYNOS5440
|
|
|
|
|
SoC. The nature of exynos5440 clock controller is
|
|
|
|
|
different than previous exynos controllers so not using
|
|
|
|
|
the common exynos framework.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2013-04-04 19:54:09 +07:00
|
|
|
config ARM_HIGHBANK_CPUFREQ
|
|
|
|
|
tristate "Calxeda Highbank-based"
|
2014-09-09 21:28:03 +07:00
|
|
|
depends on ARCH_HIGHBANK && CPUFREQ_DT && REGULATOR
|
2013-04-04 19:54:09 +07:00
|
|
|
default m
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Calxeda Highbank SoC
|
|
|
|
|
based boards.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
config ARM_IMX6Q_CPUFREQ
|
2013-12-20 09:12:16 +07:00
|
|
|
tristate "Freescale i.MX6 cpufreq support"
|
|
|
|
|
depends on ARCH_MXC
|
2013-04-04 19:54:09 +07:00
|
|
|
depends on REGULATOR_ANATOP
|
2014-07-14 04:59:00 +07:00
|
|
|
select PM_OPP
|
2013-04-04 19:54:09 +07:00
|
|
|
help
|
2013-12-20 09:12:16 +07:00
|
|
|
This adds cpufreq driver support for Freescale i.MX6 series SoCs.
|
2013-04-04 19:54:09 +07:00
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2013-04-04 19:54:14 +07:00
|
|
|
config ARM_INTEGRATOR
|
|
|
|
|
tristate "CPUfreq driver for ARM Integrator CPUs"
|
|
|
|
|
depends on ARCH_INTEGRATOR
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This enables the CPUfreq driver for ARM Integrator CPUs.
|
|
|
|
|
If in doubt, say Y.
|
|
|
|
|
|
2013-04-04 19:54:09 +07:00
|
|
|
config ARM_KIRKWOOD_CPUFREQ
|
2014-08-30 23:46:12 +07:00
|
|
|
def_bool MACH_KIRKWOOD
|
2013-04-04 19:54:09 +07:00
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Marvell Kirkwood
|
|
|
|
|
SoCs.
|
|
|
|
|
|
2012-02-16 02:01:11 +07:00
|
|
|
config ARM_OMAP2PLUS_CPUFREQ
|
|
|
|
|
bool "TI OMAP2+"
|
2012-04-14 03:32:30 +07:00
|
|
|
depends on ARCH_OMAP2PLUS
|
2012-02-16 02:01:11 +07:00
|
|
|
default ARCH_OMAP2PLUS
|
|
|
|
|
|
2013-04-04 19:54:15 +07:00
|
|
|
config ARM_S3C_CPUFREQ
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Internal configuration node for common cpufreq on Samsung SoC
|
|
|
|
|
|
|
|
|
|
config ARM_S3C24XX_CPUFREQ
|
|
|
|
|
bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
|
|
|
|
|
depends on ARCH_S3C24XX
|
|
|
|
|
select ARM_S3C_CPUFREQ
|
|
|
|
|
help
|
|
|
|
|
This enables the CPUfreq driver for the Samsung S3C24XX family
|
|
|
|
|
of CPUs.
|
|
|
|
|
|
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq>.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
config ARM_S3C24XX_CPUFREQ_DEBUG
|
|
|
|
|
bool "Debug CPUfreq Samsung driver core"
|
|
|
|
|
depends on ARM_S3C24XX_CPUFREQ
|
|
|
|
|
help
|
|
|
|
|
Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
|
|
|
|
|
|
|
|
|
|
config ARM_S3C24XX_CPUFREQ_IODEBUG
|
|
|
|
|
bool "Debug CPUfreq Samsung driver IO timing"
|
|
|
|
|
depends on ARM_S3C24XX_CPUFREQ
|
|
|
|
|
help
|
|
|
|
|
Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
|
|
|
|
|
|
|
|
|
|
config ARM_S3C24XX_CPUFREQ_DEBUGFS
|
|
|
|
|
bool "Export debugfs for CPUFreq"
|
|
|
|
|
depends on ARM_S3C24XX_CPUFREQ && DEBUG_FS
|
|
|
|
|
help
|
|
|
|
|
Export status information via debugfs.
|
|
|
|
|
|
|
|
|
|
config ARM_S3C2410_CPUFREQ
|
|
|
|
|
bool
|
|
|
|
|
depends on ARM_S3C24XX_CPUFREQ && CPU_S3C2410
|
|
|
|
|
select S3C2410_CPUFREQ_UTILS
|
|
|
|
|
help
|
|
|
|
|
CPU Frequency scaling support for S3C2410
|
|
|
|
|
|
|
|
|
|
config ARM_S3C2412_CPUFREQ
|
|
|
|
|
bool
|
|
|
|
|
depends on ARM_S3C24XX_CPUFREQ && CPU_S3C2412
|
|
|
|
|
default y
|
|
|
|
|
select S3C2412_IOTIMING
|
|
|
|
|
help
|
|
|
|
|
CPU Frequency scaling support for S3C2412 and S3C2413 SoC CPUs.
|
|
|
|
|
|
2012-02-16 17:42:32 +07:00
|
|
|
config ARM_S3C2416_CPUFREQ
|
|
|
|
|
bool "S3C2416 CPU Frequency scaling support"
|
|
|
|
|
depends on CPU_S3C2416
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for the Samsung S3C2416 and
|
|
|
|
|
S3C2450 SoC. The S3C2416 supports changing the rate of the
|
|
|
|
|
armdiv clock source and also entering a so called dynamic
|
|
|
|
|
voltage scaling mode in which it is possible to reduce the
|
2014-04-23 02:40:10 +07:00
|
|
|
core voltage of the CPU.
|
2012-02-16 17:42:32 +07:00
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
config ARM_S3C2416_CPUFREQ_VCORESCALE
|
2012-10-03 01:16:53 +07:00
|
|
|
bool "Allow voltage scaling for S3C2416 arm core"
|
|
|
|
|
depends on ARM_S3C2416_CPUFREQ && REGULATOR
|
2012-02-16 17:42:32 +07:00
|
|
|
help
|
|
|
|
|
Enable CPU voltage scaling when entering the dvs mode.
|
|
|
|
|
It uses information gathered through existing hardware and
|
|
|
|
|
tests but not documented in any datasheet.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2013-04-04 19:54:15 +07:00
|
|
|
config ARM_S3C2440_CPUFREQ
|
|
|
|
|
bool "S3C2440/S3C2442 CPU Frequency scaling support"
|
|
|
|
|
depends on ARM_S3C24XX_CPUFREQ && (CPU_S3C2440 || CPU_S3C2442)
|
|
|
|
|
select S3C2410_CPUFREQ_UTILS
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
CPU Frequency scaling support for S3C2440 and S3C2442 SoC CPUs.
|
|
|
|
|
|
2011-06-07 08:43:01 +07:00
|
|
|
config ARM_S3C64XX_CPUFREQ
|
|
|
|
|
bool "Samsung S3C64XX"
|
|
|
|
|
depends on CPU_S3C6410
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Samsung S3C6410 SoC.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2011-06-02 04:18:22 +07:00
|
|
|
config ARM_S5PV210_CPUFREQ
|
|
|
|
|
bool "Samsung S5PV210 and S5PC110"
|
|
|
|
|
depends on CPU_S5PV210
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for Samsung S5PV210 and
|
|
|
|
|
S5PC110 SoCs.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2013-04-04 19:54:16 +07:00
|
|
|
config ARM_SA1100_CPUFREQ
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config ARM_SA1110_CPUFREQ
|
|
|
|
|
bool
|
|
|
|
|
|
2012-11-27 20:05:26 +07:00
|
|
|
config ARM_SPEAR_CPUFREQ
|
|
|
|
|
bool "SPEAr CPUFreq support"
|
|
|
|
|
depends on PLAT_SPEAR
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver support for SPEAr SOCs.
|
2013-06-12 13:35:48 +07:00
|
|
|
|
|
|
|
|
config ARM_TEGRA_CPUFREQ
|
|
|
|
|
bool "TEGRA CPUFreq support"
|
|
|
|
|
depends on ARCH_TEGRA
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver support for TEGRA SOCs.
|
2014-11-24 10:59:26 +07:00
|
|
|
|
|
|
|
|
config ARM_PXA2xx_CPUFREQ
|
|
|
|
|
tristate "Intel PXA2xx CPUfreq driver"
|
|
|
|
|
depends on PXA27x || PXA25x
|
|
|
|
|
help
|
|
|
|
|
This add the CPUFreq driver support for Intel PXA2xx SOCs.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|