From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] i.MX28: Fix ref_cpu clock setup
Date: Fri, 3 Feb 2012 13:21:04 +0100 [thread overview]
Message-ID: <201202031321.04232.marek.vasut@gmail.com> (raw)
In-Reply-To: <6EA3E0BCC03CC34B89B01BD57ECBC718F56E71@POBOX.postoffice.danego.net>
> Hi,
>
> > this is how the imx-bootlets does it though. It's likely that FSL wants
> > the PLL0 to run from XTAL when doing power configuration?
>
> I was using the FLS bootlets as a reference too, but I have noticed a
> number of 'mistakes' in that code. For example:
> - Busy-indicators aren't considered when reconfiguring PLLs
> - They are linked right on top of the expection vectors
> - Sloppy printf macros left out <CR>s
Do you know why we use our own implementation of the boot code instead of imx
bootlets? ;-)
> So for me it's more of a best effort example than a Reference.
> And personally, I'd rather have the CPU running from a rock-solid - yet
> slower - xtal, than a sensitive PLL0 when I start tickering with power
> supplies.
If you can guarantee the CPU won't go insane during some power transition when
running from xtal, then it's fine by me. Then it makes me wonder though, why FSL
switched to PLL.
>
> > Maybe clock2pll should be fixed then ?
>
> That's how I started. But properly configuring PLL0 also requires to
> properly configure EMI, or the board will hand. And this is exactly what
> is done in mx28_mem_init_clock.
>
> clock2pll is broken: It disables PLL bypass without configuring PLL0 first,
> or even ungating it. I don't fully understand why it works in normal
> operation. Perhaps due to some bus-lag.
Fabio?
>
> I think it is justified to remove it, because what it intends to do, is
> done slightly later by mx28_mem_init_clock. I think FSL reused/shares this
> code with other platforms, where no mx28_mem_init_clock is present, but in
> that case they do have a bug to fix.
>
> Cheers,
>
> Robert.
Thanks
M
prev parent reply other threads:[~2012-02-03 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6EA3E0BCC03CC34B89B01BD57ECBC718F52AF0@POBOX.postoffice.danego.net>
2012-02-02 19:22 ` [U-Boot] [PATCH 2/2] i.MX28: Fix ref_cpu clock setup Marek Vasut
2012-02-03 10:57 ` Robert Deliën
2012-02-03 12:21 ` Marek Vasut [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=201202031321.04232.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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