public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v2] PPC440EPx: Reconfigure PLL for 667MHz processor
Date: Mon, 25 Feb 2008 14:58:57 +0100	[thread overview]
Message-ID: <200802251458.58021.sr@denx.de> (raw)
In-Reply-To: <2C7DE72B9BD00F44BAECA5B0CBB87395072486@hermes.terascala.com>

Mike,

On Wednesday 20 February 2008, Mike Nuss wrote:
> > 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.
>
> I agree that this could be much more configurable. Apparently no one has
> needed those options yet, as there currenntly isn't any code to reconfigure
> the clocks at all. I would guess most people are using an EEPROM to set
> things up.

Right. All boards I have seem so far, are equipped with such an EEPROM. And I 
would always recommend to add it to a 4xx design.

> As for shortsightedness, keep in mind that I'm not a full time U-Boot
> developer. I solved a problem to get our board working and I'm happy to
> share the solution I came up with, but I just don't have the resources to
> solve a problem that someone else might have later. IMO, with the basics in
> this patch, it should be easy enough for anyone to modify it for additional
> configurations if they are needed.

Yes, I understand your situation. Thanks for changing the patch as I 
suggested. I'm inclined to accept your patch (if nobody objects) as is for 
the next merge window. If somebody needs an extended version of this PLL 
reconfiguration, he or she can easily adapt your code.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2008-02-25 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 21:59 [U-Boot-Users] [PATCH v2] PPC440EPx: Reconfigure PLL for 667MHz processor Mike Nuss
2008-02-25 13:58 ` Stefan Roese [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-20 16:54 Mike Nuss
2008-02-20 21:38 ` Matthias Fuchs
2008-03-27  9:49 ` 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=200802251458.58021.sr@denx.de \
    --to=sr@denx.de \
    --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