From: Andy Yan <andy.yan@rock-chips.com>
To: heiko@sntech.de, naobsd@gmail.com
Cc: robh+dt@kernel.org, linux@arm.linux.org.uk,
devicetree@vger.kernel.org, galak@codeaurora.org,
linux-kernel@vger.kernel.org, ijc+devicetree@hellion.org.uk,
linux-rockchip@lists.infradead.org, pawel.moll@arm.com,
mark.rutland@arm.com, inux-arm-kernel@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: [PATCH 1/2] ARM: dts: rockchip: increase vdd_arm voltage for rk3066a-rayeager board
Date: Thu, 14 Jan 2016 20:34:20 +0800 [thread overview]
Message-ID: <1452774860-16572-1-git-send-email-andy.yan@rock-chips.com> (raw)
In-Reply-To: <1452774780-16493-1-git-send-email-andy.yan@rock-chips.com>
The current vdd_arm voltage is too low, increase it will make
the system more stable.
Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
---
arch/arm/boot/dts/rk3066a-rayeager.dts | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/rk3066a-rayeager.dts b/arch/arm/boot/dts/rk3066a-rayeager.dts
index 0bf6876..3d4c104 100644
--- a/arch/arm/boot/dts/rk3066a-rayeager.dts
+++ b/arch/arm/boot/dts/rk3066a-rayeager.dts
@@ -159,6 +159,14 @@
&cpu0 {
cpu0-supply = <&vdd_arm>;
+ operating-points = <
+ /* kHz uV */
+ 1008000 1125000
+ 816000 1125000
+ 600000 1100000
+ 504000 1100000
+ 312000 1075000
+ >;
};
&emac {
--
1.9.1
next prev parent reply other threads:[~2016-01-14 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 12:33 [PATCH 0/2] fix rk3066a-rayeager board hang when cpufreq changes Andy Yan
2016-01-14 12:34 ` Andy Yan [this message]
[not found] ` <1452774860-16572-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-01-14 12:45 ` [PATCH 1/2] ARM: dts: rockchip: increase vdd_arm voltage for rk3066a-rayeager board Heiko Stuebner
2016-01-14 12:35 ` [PATCH 2/2] ARM: dts: rockchip: enable pwm3 as pwm regulator " Andy Yan
2016-01-14 12:41 ` Heiko Stuebner
2016-01-15 10:41 ` Andy Yan
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=1452774860-16572-1-git-send-email-andy.yan@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=inux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=naobsd@gmail.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).