From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] AM335x PLL configuration
Date: Thu, 28 Feb 2013 15:20:26 -0500 [thread overview]
Message-ID: <20130228202026.GA20569@bill-the-cat> (raw)
In-Reply-To: <5128ABE9.9020001@mimc.co.uk>
On Sat, Feb 23, 2013 at 11:45:45AM +0000, Mark Jackson wrote:
> All the current TI AM335x boards currently appear to start with an MPU clock of 550MHx and a core clock of 1GHz,
> based on #defines in include/asm/arch-am33xx/clocks_am33xx.h
>
> I assume most people then pass control over to (eg) cpufreq once Linux boots.
>
> However I would like to just boot up at the max clock speed (i.e. 720MHz).
>
> Is there any merit in reworking this to allow the clock speeds to be specified in the config heaeder file ?
>
> Or would it be better to allow the board init code to adjust the clock settings "on-the-fly" ?
>
> I could just add some extra code to my own board.c file, but that doesn't seem like a very elegant solution !!
>
> Maybe someone else already has a solution for this ?
The "vendor" tree has a partial solution for this, which is to make the
initial speed be the safe value (550MHz) and then if we can, depending
on board, run the clock up. For example, Beaglebone can be USB bus
powered or wall-powered, but it's only safe to run up to 720MHz (due to
potenital power spikes later on during kernel boot) if on wall power.
So yes, if you want to start down the road of allowing boards to say "I
know I can now run at ...", please do so!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130228/49d5dc80/attachment-0001.pgp>
prev parent reply other threads:[~2013-02-28 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 11:45 [U-Boot] AM335x PLL configuration Mark Jackson
2013-02-28 20:20 ` Tom Rini [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=20130228202026.GA20569@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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