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 v2 1/2] ARM: dts: rockchip: increase vdd_arm voltage for rk3066a based boards
Date: Fri, 15 Jan 2016 21:25:21 +0800 [thread overview]
Message-ID: <1452864321-505-1-git-send-email-andy.yan@rock-chips.com> (raw)
In-Reply-To: <1452864223-423-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>
---
Changes in v2:
- move the opp table to rk3066a.dtsi, make it as the default opp table
for rk3066a based board.
arch/arm/boot/dts/rk3066a.dtsi | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/rk3066a.dtsi b/arch/arm/boot/dts/rk3066a.dtsi
index 946f187..ff0530e 100644
--- a/arch/arm/boot/dts/rk3066a.dtsi
+++ b/arch/arm/boot/dts/rk3066a.dtsi
@@ -61,11 +61,13 @@
reg = <0x0>;
operating-points = <
/* kHz uV */
- 1008000 1075000
- 816000 1025000
- 600000 1025000
- 504000 1000000
- 312000 975000
+ 1416000 1300000
+ 1200000 1175000
+ 1008000 1125000
+ 816000 1125000
+ 600000 1100000
+ 504000 1100000
+ 312000 1075000
>;
clock-latency = <40000>;
clocks = <&cru ARMCLK>;
--
1.9.1
next prev parent reply other threads:[~2016-01-15 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 13:23 [PATCH v2 0/2] fix rk3066a based boards hang when cpufreq changes Andy Yan
2016-01-15 13:25 ` Andy Yan [this message]
2016-01-15 13:26 ` [PATCH v2 2/2] ARM: dts: rockchip: enable pwm3 as pwm regulator for rk3066a based boards Andy Yan
2016-01-17 23:16 ` [PATCH v2 0/2] fix rk3066a based boards hang when cpufreq changes Heiko Stuebner
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=1452864321-505-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