From: wens@csie.org (Chen-Yu Tsai)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend v2 1/2] ARM: dts: sun4i: a10-lime: Override and remove 1008MHz OPP setting
Date: Wed, 25 Mar 2015 00:53:26 +0800 [thread overview]
Message-ID: <1427216007-9185-2-git-send-email-wens@csie.org> (raw)
In-Reply-To: <1427216007-9185-1-git-send-email-wens@csie.org>
The Olimex A10-Lime is known to be unstable when running at 1008MHz.
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
---
arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts b/arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts
index ab7891c43231..75742f8f96f3 100644
--- a/arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts
+++ b/arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts
@@ -56,6 +56,22 @@
model = "Olimex A10-OLinuXino-LIME";
compatible = "olimex,a10-olinuxino-lime", "allwinner,sun4i-a10";
+ cpus {
+ cpu0: cpu at 0 {
+ /*
+ * The A10-Lime is known to be unstable
+ * when running at 1008 MHz
+ */
+ operating-points = <
+ /* kHz uV */
+ 912000 1350000
+ 864000 1300000
+ 624000 1250000
+ >;
+ cooling-max-level = <2>;
+ };
+ };
+
soc at 01c00000 {
emac: ethernet at 01c0b000 {
pinctrl-names = "default";
--
2.1.4
next prev parent reply other threads:[~2015-03-24 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:53 [PATCH resend v2 0/2] ARM: dts: sunxi: Fix cpufreq instabilities Chen-Yu Tsai
2015-03-24 16:53 ` Chen-Yu Tsai [this message]
2015-03-26 17:11 ` [linux-sunxi] [PATCH resend v2 1/2] ARM: dts: sun4i: a10-lime: Override and remove 1008MHz OPP setting Iain Paton
2015-03-24 16:53 ` [PATCH resend v2 2/2] ARM: dts: sunxi: Remove overclocked/overvoltaged OPP Chen-Yu Tsai
2015-03-24 21:51 ` [PATCH resend v2 0/2] ARM: dts: sunxi: Fix cpufreq instabilities Maxime Ripard
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=1427216007-9185-2-git-send-email-wens@csie.org \
--to=wens@csie.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.