From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v2] PPC440EPx: Reconfigure PLL for 667MHz processor
Date: Wed, 20 Feb 2008 22:38:29 +0100 [thread overview]
Message-ID: <200802202238.30238.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <1203526460-4974-1-git-send-email-mike@terascala.com>
Hi Mike,
don't you think this is a little bit to shortsighted?
There are many other parameters beyond the CPU clock that could be
modified in such a way. We have some code in the PMC440 board
code that sets up the PCI sync clock dynamically dependant on
a GPIO (M66EN pci pin). So I would vote for a more generic configuration than
by a CPU frequency parameter. Just think about this: should 667 MHz on an EPx
always mean 166 MHz PLB clock? 667MHZ with 133MHz PLB might also be
a typical configuration (e.g. when you need 66MHz EBC clock ....).
So what about a function that takes the complete strapping values
as parameters (I think 4 longs) instead of nothing but the CPU frequency.
Matthias
On Wednesday 20 February 2008 17:54:20 Mike Nuss wrote:
> On PPC440EPx without a bootstrap I2C EEPROM, the PLL can be reconfigured
> after startup to change the speed of the clocks. This patch adds the
> option CFG_PLL_RECONFIG. If this option is set to 667, the CPU
> initialization code will reconfigure the PLL to run the system with a CPU
> frequency of 667MHz and PLB frequency of 166MHz, without the need for an
> external EEPROM.
>
> Signed-off-by: Mike Nuss <mike@terascala.com>
> Cc: Stefan Roese <sr@denx.de>
next prev parent reply other threads:[~2008-02-20 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 16:54 [U-Boot-Users] [PATCH v2] PPC440EPx: Reconfigure PLL for 667MHz processor Mike Nuss
2008-02-20 21:38 ` Matthias Fuchs [this message]
2008-03-27 9:49 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2008-02-20 21:59 Mike Nuss
2008-02-25 13:58 ` Stefan Roese
2008-02-20 16:45 Mike Nuss
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=200802202238.30238.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.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