linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ipaton0@gmail.com (Iain Paton)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: dts: sunxi: A20-OlinuXino-Lime2 raise dcdc2 lower voltage limit
Date: Wed, 07 Jan 2015 22:21:45 +0000	[thread overview]
Message-ID: <54ADB179.9000209@gmail.com> (raw)

The Lime2 is not stable if the cpu core voltage is reduced below 1v. To
prevent any problems when operating points are enabled, raise the pmic dcdc2
lower voltage limit to 1v.

Signed-off-by: Iain Paton <ipaton0@gmail.com>
---

Maxime, I realise the axp209 nodes will probably end up abstracted somewhat 
differently once all of the patches Chen-Yu posted are reviewed and picked
up and I can redo the lime2 dts to fit once that's done.
For now, the lime2 dts defines the full axp209 node itself including all of
the regulators, so if the lowest opp with the 0.9v setting is enabled this 
will cause problems.

Up to you if you want to take this patch now or we wait until the axp209.dtsi
lands and refactor the lime2 dts appropriately then.

 arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
index ed364d5..910318a 100644
--- a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
+++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
@@ -159,7 +159,7 @@
 					};
 
 					vdd_cpu: dcdc2 {
-						regulator-min-microvolt = <700000>;
+						regulator-min-microvolt = <1000000>;
 						regulator-max-microvolt = <2275000>;
 						regulator-always-on;
 					};
-- 
2.1.3

             reply	other threads:[~2015-01-07 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 22:21 Iain Paton [this message]
2015-01-08  3:54 ` ARM: dts: sunxi: A20-OlinuXino-Lime2 raise dcdc2 lower voltage limit wens Tsai
2015-01-08 17:17   ` [linux-sunxi] " Iain Paton
2015-01-12  9:19     ` 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=54ADB179.9000209@gmail.com \
    --to=ipaton0@gmail.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).