Re: [PATCH 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250

Thomas Abraham <[email protected]>
Newsgroups org.kernel.vger.cpufreq,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-samsung-soc
Message-ID <CAJuA9aj0Hf62oskD3J=mmX9QKm5eBmgREx0wvtU-az5Re7H9NA@mail.gmail.com>
On Fri, Jun 13, 2014 at 12:06 PM, Viresh Kumar <[email protected]> wrote:
> [email protected] is dead now. Anyway you should be using linux-pm
> instead.
>
> On 13 June 2014 11:38, Chanwoo Choi <[email protected]> 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 [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.