From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: at91: clock: fix PLLA overclocked warning
Date: Mon, 9 Jul 2012 16:52:16 +0200 [thread overview]
Message-ID: <4FFAF020.1080805@atmel.com> (raw)
In-Reply-To: <1341825375-9143-1-git-send-email-jiri.prchal@aksignal.cz>
Hi Jiri,
On 07/09/2012 11:16 AM, Jiri Prchal :
> This patch fix false warning "PLLA overclocked". Maximum frequency
> for sam9260 is 210MHz as stated in atmel's datasheet. Originally there was
> plus 4.5%, so I add this 4.5% to new value too.
Well, I do not see this 4.5% in addition. It is true that Maximum
frequency had been indicated as higher but current value is 210MHz if
VDD core is @ 1.8V (for industrial temperature range).
> Signed-off-by: Jiri Prchal <jiri.prchal@aksignal.cz>
> ---
> arch/arm/mach-at91/clock.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-at91/clock.c b/arch/arm/mach-at91/clock.c
> index de2ec6b..e004308 100644
> --- a/arch/arm/mach-at91/clock.c
> +++ b/arch/arm/mach-at91/clock.c
> @@ -707,7 +707,7 @@ static int __init at91_pmc_init(unsigned long main_clock)
> if (plla.rate_hz > 800000000)
> pll_overclock = true;
> } else {
> - if (plla.rate_hz > 209000000)
> + if (plla.rate_hz > 219000000)
Well, I rework this patch using 210 MHz as stated in datasheet. We shall
keep this 209 MHz test because at91rm9200 is still using this value.
Moreover, I add a new category for 240 MHz.
> pll_overclock = true;
> }
> if (pll_overclock)
Thanks, best regards,
--
Nicolas Ferre
prev parent reply other threads:[~2012-07-09 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 9:16 [PATCH 2/2] ARM: at91: clock: fix PLLA overclocked warning Jiri Prchal
2012-07-09 14:52 ` Nicolas Ferre [this message]
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=4FFAF020.1080805@atmel.com \
--to=nicolas.ferre@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.