From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch u-boot git arm/next] davinci: display correct clock info
Date: Wed, 29 Apr 2009 23:35:32 -0700 [thread overview]
Message-ID: <200904292335.33059.david-b@pacbell.net> (raw)
In-Reply-To: <20090430061017.GC31304@game.jcrosoft.org>
On Wednesday 29 April 2009, Jean-Christophe PLAGNIOL-VILLARD wrote:
> my idea is more this
> the lowlovel will init the pll (lowlevel_init.S or other stage bootloader)
Right ...
> so instead of hardcoding the PPLDIV read it in the register
> and then calculate the clock rate
That's all this code does: read the PLL registers
(and divider taps), and display settings in use by
the current board. It happens that some SoCs have
slightly different PLL configuration (like pre/post
dividers) and feed important components (ARM, DSP,
DDR) from different PLL dividers.
> and it need it set the other non used clock
> depending on the IP used by u-boot (at runtime)
I don't know what you mean here. PLL/tap configuration
is distinct from clock distribution on the chip.
The cpu/arm926ejs/davinci/psc.c code handles clock
distribution (and resets). So for example the dm355
chips leave most modules clocked but in reset, while
the dm6446 leaves them unclocked and in reset ... so
modules needed by u-boot get uniformly taken out of
reset and clocked. But that's *unrelated* to this
PLL display code.
- Dave
next prev parent reply other threads:[~2009-04-30 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 22:38 [U-Boot] [patch u-boot git arm/next] davinci: display correct clock info David Brownell
2009-04-29 23:17 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-29 23:21 ` Ben Warren
2009-04-30 0:13 ` David Brownell
2009-04-30 6:10 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-30 6:35 ` David Brownell [this message]
2009-04-30 7:18 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-30 9:07 ` David Brownell
2009-05-01 1:23 ` David Brownell
2009-05-01 12:49 ` Jean-Christophe PLAGNIOL-VILLARD
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=200904292335.33059.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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