lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 13 Aug 2013 12:08:23 +0200 From: Lukasz Majewski <l.majewski@...sung.com> To: Viresh Kumar <viresh.kumar@...aro.org>, "Rafael J. Wysocki" <rjw@...k.pl>, Zhang Rui <rui.zhang@...el.com>, Eduardo Valentin <eduardo.valentin@...com> Cc: "cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>, Linux PM list <linux-pm@...r.kernel.org>, Jonghwa Lee <jonghwa3.lee@...sung.com>, Lukasz Majewski <l.majewski@...sung.com>, Lukasz Majewski <l.majewski@...ess.pl>, linux-kernel <linux-kernel@...r.kernel.org>, Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>, Daniel Lezcano <daniel.lezcano@...aro.org>, Kukjin Kim <kgene.kim@...sung.com>, Myungjoo Ham <myungjoo.ham@...sung.com>, durgadoss.r@...el.com Subject: [PATCH v7 5/7] cpufreq:exynos:Extend Exynos cpufreq driver to support boost framework The cpufreq_driver's boost_supported flag is true only when boost support is explicitly enabled. Boost related attributes are exported only under the same condition. Signed-off-by: Lukasz Majewski <l.majewski@...sung.com> Signed-off-by: Myungjoo Ham <myungjoo.ham@...sung.com> --- Changes for v7: - Replace CONFIG_CPU_FREQ_BOOST_SW with CONFIG_ARM_EXYNOS_CPU_FREQ_BOOST_SW - Move boost_supported initialization to struct cpufreq_driver exynos_driver Changes for v6: - Replace exynos_driver.boost_supported = 1 to = true - Protect boost attributes export with CONFIG_CPU_FREQ_BOOST_SW Changes for v5: - None Changes for v4: - None Changes for v3: - Remove low level boost code - Move boost management code to cpufreq core code - Use boost_supported flag to indicate if driver supports over clocking Changes for v2: - Removal of struct cpufreq_boost - Removal of the CONFIG_CPU_FREQ_BOOST flag - low_level_boost with valid address when boost is supported drivers/cpufreq/exynos-cpufreq.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c index b9f9aee..2786aba 100644 --- a/drivers/cpufreq/exynos-cpufreq.c +++ b/drivers/cpufreq/exynos-cpufreq.c @@ -270,6 +270,9 @@ static int exynos_cpufreq_cpu_exit(struct cpufreq_policy *policy) static struct freq_attr *exynos_cpufreq_attr[] = { &cpufreq_freq_attr_scaling_available_freqs, +#ifdef CONFIG_ARM_EXYNOS_CPU_FREQ_BOOST_SW + &cpufreq_freq_attr_scaling_boost_freqs, +#endif NULL, }; @@ -282,6 +285,9 @@ static struct cpufreq_driver exynos_driver = { .exit = exynos_cpufreq_cpu_exit, .name = "exynos_cpufreq", .attr = exynos_cpufreq_attr, +#ifdef CONFIG_ARM_EXYNOS_CPU_FREQ_BOOST_SW + .boost_supported = true, +#endif #ifdef CONFIG_PM .suspend = exynos_cpufreq_suspend, .resume = exynos_cpufreq_resume, -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists