diff mbox

[resend,v2,1/2] ARM: dts: sun4i: a10-lime: Override and remove 1008MHz OPP setting

Message ID 1427216007-9185-2-git-send-email-wens@csie.org (mailing list archive)
State New, archived
Headers show

Commit Message

Chen-Yu Tsai March 24, 2015, 4:53 p.m. UTC 
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(+)

Comments

Iain Paton March 26, 2015, 5:11 p.m. UTC | #1 
On 24/03/15 16:53, Chen-Yu Tsai wrote:
> The Olimex A10-Lime is known to be unstable when running at 1008MHz.

> +			operating-points = <
> +				/* kHz    uV */
> +				912000  1350000
> +				864000  1300000

If we're dropping the top speed to 912 in the kernel, should we do the 
same in u-boot?

I was already planning on sending a patch to add the 912MHz setting to 
u-boot due to sun7i requesting CONFIG_CLK_FULL_SPEED of 912 but getting 
overclocked to 960 instead. I can easily do this at the same time.

Rgds,
Iain
diff mbox

Patch

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@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@01c00000 {
 		emac: ethernet@01c0b000 {
 			pinctrl-names = "default";