From: Sudeep.Holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/7] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data
Date: Fri, 07 Feb 2014 16:20:27 +0000 [thread overview]
Message-ID: <52F507CB.6090300@arm.com> (raw)
In-Reply-To: <1391788548-13056-6-git-send-email-thomas.ab@samsung.com>
On 07/02/14 15:55, Thomas Abraham wrote:
> From: Thomas Abraham <thomas.ab@samsung.com>
>
> For all Exynos based platforms, add CPU nodes, operating points and cpu
> clock data for migrating from Exynos specific cpufreq driver to using
> generic cpufreq-cpu0 driver.
>
> Signed-off-by: Thomas Abraham <thomas.ab@samsung.com>
[...]
> diff --git a/arch/arm/boot/dts/exynos4x12.dtsi b/arch/arm/boot/dts/exynos4x12.dtsi
> index 5c412aa..c613fc2 100644
> --- a/arch/arm/boot/dts/exynos4x12.dtsi
> +++ b/arch/arm/boot/dts/exynos4x12.dtsi
> @@ -31,6 +31,42 @@
> mshc0 = &mshc_0;
> };
>
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + cpu at 0 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a9";
> + reg = <0>;
> + clocks = <&clock 12>;
> + clock-names = "cpu";
> +
> + operating-points = <
> + 1500000 1350000
> + 1400000 1287500
> + 1300000 1250000
> + 1200000 1187500
> + 1100000 1137500
> + 1000000 1087500
> + 900000 1037500
> + 800000 1000000
> + 700000 987500
> + 600000 975000
> + 500000 950000
> + 400000 925000
> + 300000 900000
> + 200000 900000
> + >;
> + clock-latency = <200000>;
> + boost-frequency = <1500000 1350000>;
This is confusing, 1350000 is not in the OPP frequency list or this is still
following old binding with voltage. Either case this needs to be fixed.
Regards,
Sudeep
next prev parent reply other threads:[~2014-02-07 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 15:55 [PATCH v3 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms Thomas Abraham
2014-02-07 15:55 ` [PATCH v3 1/7] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies Thomas Abraham
2014-02-07 16:16 ` Nishanth Menon
2014-02-08 5:19 ` Thomas Abraham
2014-02-08 16:31 ` Nishanth Menon
2014-02-10 8:20 ` Lukasz Majewski
2014-02-12 14:58 ` Tomasz Figa
2014-02-13 8:02 ` Thomas Abraham
2014-02-13 11:08 ` Tomasz Figa
2014-02-07 15:55 ` [PATCH v3 2/7] clk: samsung: add infrastructure to register cpu clocks Thomas Abraham
2014-02-10 9:00 ` Lukasz Majewski
2014-02-12 18:25 ` Tomasz Figa
2014-02-13 7:58 ` Thomas Abraham
2014-02-13 14:31 ` Tomasz Figa
2014-02-07 15:55 ` [PATCH v3 3/7] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5 Thomas Abraham
2014-02-07 15:55 ` [PATCH v3 4/7] clk: exynos: use cpu-clock provider type to represent arm clock Thomas Abraham
2014-02-07 15:55 ` [PATCH v3 5/7] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data Thomas Abraham
2014-02-07 16:20 ` Sudeep Holla [this message]
2014-02-08 5:20 ` Thomas Abraham
2014-02-07 15:55 ` [PATCH v3 6/7] ARM: Exynos: switch to using generic cpufreq-cpu0 driver Thomas Abraham
2014-02-07 15:55 ` [PATCH v3 7/7] cpufreq: exynos: remove all exynos specific cpufreq driver support Thomas Abraham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F507CB.6090300@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).