Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757433Ab3HMKKD (ORCPT ); Tue, 13 Aug 2013 06:10:03 -0400 Received: from mailout2.samsung.com ([203.254.224.25]:11017 "EHLO mailout2.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757046Ab3HMKJH (ORCPT ); Tue, 13 Aug 2013 06:09:07 -0400 X-AuditID: cbfee61b-b7efe6d000007b11-36-520a05c256ed From: Lukasz Majewski To: Viresh Kumar , "Rafael J. Wysocki" , Zhang Rui , Eduardo Valentin Cc: "cpufreq@vger.kernel.org" , Linux PM list , Jonghwa Lee , Lukasz Majewski , Lukasz Majewski , linux-kernel , Bartlomiej Zolnierkiewicz , Daniel Lezcano , Kukjin Kim , Myungjoo Ham , durgadoss.r@intel.com Subject: [PATCH v7 5/7] cpufreq:exynos:Extend Exynos cpufreq driver to support boost framework Date: Tue, 13 Aug 2013 12:08:23 +0200 Message-id: <1376388505-30233-6-git-send-email-l.majewski@samsung.com> X-Mailer: git-send-email 1.7.10 In-reply-to: <1376388505-30233-1-git-send-email-l.majewski@samsung.com> References: <1370502472-7249-1-git-send-email-l.majewski@samsung.com> <1376388505-30233-1-git-send-email-l.majewski@samsung.com> X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsVy+t9jAd1DrFxBBhe2mFtsnLGe1eJp0w92 i3mfZS36fl5htliz/yeTRefZJ8wWvQuuslm8ecRt8ebhZkaLy7vmsFl87j3CaHG7cQWbRf/C XiaLJw/72Cw2fvVw4PdYvOclk8eda3vYPNZNe8vs0bdlFaPHo8UtjB7Hb2xn8vi8SS6APYrL JiU1J7MstUjfLoErY/vXhawFE/grdm1dxdLAeIuni5GTQ0LARGL51eXMELaYxIV769m6GLk4 hAQWMUq8v3CUGcLpYpLYd2A+K0gVm4CexOe7T5lAbBGBOYwSd466gxQxCzxgllj8/QsjSEJY IEFi7/9udhCbRUBV4tLxFrAVvAJuEncvLmKDWCcv8fR+H5jNKeAusfp/C9TqJkaJjmOH2SYw 8i5gZFjFKJpakFxQnJSea6RXnJhbXJqXrpecn7uJERy4z6R3MK5qsDjEKMDBqMTDm/GRI0iI NbGsuDL3EKMEB7OSCG8cI1eQEG9KYmVValF+fFFpTmrxIUZpDhYlcd6DrdaBQgLpiSWp2amp BalFMFkmDk6pBkam/8f81qldV/w3N+yA2a4Gp0/Gdbp3s1zqkkv+iF3U+9kx6Z2GmLi7WXTx hfUyGjeccn8UC3533vFsUXzDtc/iK+UuVVwrffi/d6FsHJcXX3j3hHVTckzELOwTWz81XZs+ qW3eRI3rvqxZUyM+zK4yXyoitumtX/S1vqaadZc36Eb+43zD2K7EUpyRaKjFXFScCABogctT WAIAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2119 Lines: 67 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 Signed-off-by: Myungjoo Ham --- 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/