From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: rockchip: increase vdd_arm voltage for rk3066a-rayeager board
Date: Thu, 14 Jan 2016 13:45:02 +0100 [thread overview]
Message-ID: <1709463.R522kSjgXB@phil> (raw)
In-Reply-To: <1452774860-16572-1-git-send-email-andy.yan@rock-chips.com>
Hi Andy,
Am Donnerstag, 14. Januar 2016, 20:34:20 schrieb Andy Yan:
> 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 {
Does this only apply to the rayeager-board / px2 soc or for all rk3066a/px2
boards? I.e. the original values come from some sdk kernel and I might've
transcribed that wrong at the time and I remember having problems trying to
reach higher frequencies as well.
So could you check what the full operating points looks like for both and if
this can move to the rk3066a.dtsi, as both should be able to reach at least
1.4GHz / 1.6GHz.
Thanks
Heiko
parent reply other threads:[~2016-01-14 12:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1452774860-16572-1-git-send-email-andy.yan@rock-chips.com>]
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=1709463.R522kSjgXB@phil \
--to=heiko@sntech.de \
--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