From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: mvebu: update cpu clock frequency
Date: Thu, 2 Jul 2015 22:04:59 +0200 [thread overview]
Message-ID: <20150702200459.GF13481@lunn.ch> (raw)
In-Reply-To: <1435866158-910-1-git-send-email-gregory.clement@free-electrons.com>
On Thu, Jul 02, 2015 at 09:42:38PM +0200, Gregory CLEMENT wrote:
> Since u-boot 2015_T1.0p6 there are new requency settings available.
Hi Gregory
Missing f in f_requency.
Also, what has u-boot got to do with this? I would expect this is a
property of the hardware. What happens is an older u-boot is used?
Thanks
Andrew
>
> Based on a patch from Nadav Haklai <nadavh@marvell.com>
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> ---
> drivers/clk/mvebu/armada-38x.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/clk/mvebu/armada-38x.c b/drivers/clk/mvebu/armada-38x.c
> index 8bccf4ecdab6..c64037e2e89f 100644
> --- a/drivers/clk/mvebu/armada-38x.c
> +++ b/drivers/clk/mvebu/armada-38x.c
> @@ -46,10 +46,11 @@ static u32 __init armada_38x_get_tclk_freq(void __iomem *sar)
> }
>
> static const u32 armada_38x_cpu_frequencies[] __initconst = {
> - 0, 0, 0, 0,
> - 1066 * 1000 * 1000, 0, 0, 0,
> + 666 * 1000 * 1000, 0, 800 * 1000 * 1000, 0,
> + 1066 * 1000 * 1000, 0, 1200 * 1000 * 1000, 0,
> 1332 * 1000 * 1000, 0, 0, 0,
> - 1600 * 1000 * 1000,
> + 1600 * 1000 * 1000, 0, 0, 0,
> + 1866 * 1000 * 1000, 0, 0, 2000 * 1000 * 1000,
> };
>
> static u32 __init armada_38x_get_cpu_freq(void __iomem *sar)
> --
> 2.1.0
>
next prev parent reply other threads:[~2015-07-02 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 19:42 [PATCH] clk: mvebu: update cpu clock frequency Gregory CLEMENT
2015-07-02 20:04 ` Andrew Lunn [this message]
2015-07-02 20:21 ` Gregory CLEMENT
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=20150702200459.GF13481@lunn.ch \
--to=andrew@lunn.ch \
--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).