[PATCH 0/5] cpufreq:boost: CPU Boost mode support
From: Lukasz Majewski
Date: Thu Jun 06 2013 - 03:08:40 EST
This patch series introduces support for CPU overclocking technique
It is a follow up of a LAB governor proposal. Boost is a LAB component:
Boost unifies hardware based solution (e.g. Intel Nehalem) with
software oriented one (like the one done at Exynos).
For this reason cpufreq/freq_table code has been reorganized to exclude
Important design decisions:
- Boost related code is compiled-in unconditionally. I wanted to avoid
situation when a lot of #ifdef CONFIG_CPU_FREQ_BOOST are scattered at
cpufreq code (especially cpufreq.c large file)
- Only one cpufreq_boost instance is created at cpufreq driver file.
- Boost can manage overclocking when many policies are istalled in
the system (this is a preparation for b.L)
- Boost sysfs attributies are seen only when cpufreq driver supports them.
They will not show up until either CONFIG_CPU_FREQ_BOOST or device tree
cpufreq "boost_mode" attribute is defined.
- No special spin_lock for Boost was created. The one from cpufreq was
- Low level boost trigger function (*low_level_boost function callback) is
necessary to "glue" together acpi-cpufreq boost with software based one.
Tested at: HW: Exynos 4412 3.10 linux
Compile tested x86_64 defconfig (acpi) - help with HW test
Lukasz Majewski (5):
cpufreq: Define cpufreq_set_drv_attr_files() to add per CPU sysfs
cpufreq:boost: Add support for software based CPU frequency boost
cpufreq:acpi:x86: Adjust the acpi-cpufreq.c code to work with common
cpufreq:exynos:Extend exynos cpufreq driver to support boost
cpufreq:boost:Kconfig: Enable boost support at Kconfig
drivers/cpufreq/Kconfig | 7 ++
drivers/cpufreq/acpi-cpufreq.c | 64 ++++++--------
drivers/cpufreq/cpufreq.c | 175 ++++++++++++++++++++++++++++++++++++--
drivers/cpufreq/exynos-cpufreq.c | 48 +++++++++++
drivers/cpufreq/freq_table.c | 87 ++++++++++++++++++-
include/linux/cpufreq.h | 35 +++++++-
6 files changed, 369 insertions(+), 47 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/