From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Abraham Subject: Re: [PATCH 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250 Date: Fri, 13 Jun 2014 12:30:22 +0530 Message-ID: References: <1402639693-31108-1-git-send-email-cw00.choi@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: cpufreq-owner@vger.kernel.org To: Viresh Kumar Cc: Chanwoo Choi , "cpufreq@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , linux-samsung-soc , Mike Turquette , Shawn Guo , Kukjin Kim , Tomasz Figa , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Kyungmin Park , "Rafael J. Wysocki" List-Id: linux-samsung-soc@vger.kernel.org On Fri, Jun 13, 2014 at 12:06 PM, Viresh Kumar wrote: > cpufreq@vger.kernel.org is dead now. Anyway you should be using linux-pm > instead. > > On 13 June 2014 11:38, Chanwoo Choi wrote: >> This patchset use cpufreq-cpu0 driver to support Exynos3250 cpufreq. So, this >> patchset is based on following patchset[1] by Thomas Abraham. >> [1] http://www.spinics.net/lists/linux-samsung-soc/msg31593.html >> >> Chanwoo Choi (4): >> clk: samsung: exynos3250: Use cpu-clock provider type to support cpufreq >> clk: samsung: Add support for cpu clocks of Exynos3250 >> Documentation: devicetree: Add cpu clock configuration data binding for Exynos3250 >> ARM: dts: Exynos: Add cpu clock table and armclk divider table for Exynos3250 >> >> .../devicetree/bindings/clock/exynos3250-clock.txt | 32 ++++++++++++++++++++++ >> arch/arm/boot/dts/exynos3250.dtsi | 28 +++++++++++++++++++ >> drivers/clk/samsung/clk-cpu.c | 31 +++++++++++++++++---- >> drivers/clk/samsung/clk-exynos3250.c | 14 +++++++--- >> 4 files changed, 96 insertions(+), 9 deletions(-) > > Nothing really cpufreq specific. Would *eagerly* wait for the patch that > removes existing driver files :) The next version of the exynos cpufreq cleanup patches are being prepared. But exynos4x12 cpufreq driver will not be included for cleanup since the boost frequency bindings need more work. Thanks, Thomas. > -- > To unsubscribe from this list: send the line "unsubscribe cpufreq" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: ta.omasab@gmail.com (Thomas Abraham) Date: Fri, 13 Jun 2014 12:30:22 +0530 Subject: [PATCH 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250 In-Reply-To: References: <1402639693-31108-1-git-send-email-cw00.choi@samsung.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Jun 13, 2014 at 12:06 PM, Viresh Kumar wrote: > cpufreq at vger.kernel.org is dead now. Anyway you should be using linux-pm > instead. > > On 13 June 2014 11:38, Chanwoo Choi wrote: >> This patchset use cpufreq-cpu0 driver to support Exynos3250 cpufreq. So, this >> patchset is based on following patchset[1] by Thomas Abraham. >> [1] http://www.spinics.net/lists/linux-samsung-soc/msg31593.html >> >> Chanwoo Choi (4): >> clk: samsung: exynos3250: Use cpu-clock provider type to support cpufreq >> clk: samsung: Add support for cpu clocks of Exynos3250 >> Documentation: devicetree: Add cpu clock configuration data binding for Exynos3250 >> ARM: dts: Exynos: Add cpu clock table and armclk divider table for Exynos3250 >> >> .../devicetree/bindings/clock/exynos3250-clock.txt | 32 ++++++++++++++++++++++ >> arch/arm/boot/dts/exynos3250.dtsi | 28 +++++++++++++++++++ >> drivers/clk/samsung/clk-cpu.c | 31 +++++++++++++++++---- >> drivers/clk/samsung/clk-exynos3250.c | 14 +++++++--- >> 4 files changed, 96 insertions(+), 9 deletions(-) > > Nothing really cpufreq specific. Would *eagerly* wait for the patch that > removes existing driver files :) The next version of the exynos cpufreq cleanup patches are being prepared. But exynos4x12 cpufreq driver will not be included for cleanup since the boost frequency bindings need more work. Thanks, Thomas. > -- > To unsubscribe from this list: send the line "unsubscribe cpufreq" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html