mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Mogens Lauridsen <mlauridsen171@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: i.MX53: Set pll3 directly to 216MHz.
Date: Thu, 28 Jun 2018 10:30:21 +0200	[thread overview]
Message-ID: <20180628083021.j6gqwiopqk34vqtl@pengutronix.de> (raw)
In-Reply-To: <20180627140711.16764-1-mlauridsen171@gmail.com>

On Wed, Jun 27, 2018 at 04:07:11PM +0200, Mogens Lauridsen wrote:
> PLL3 was first set to 400MHz and then some peripheral was switched
> to PLL3. Finally PLL3 was set to 216MHz. This could make some
> i.MX538 hang in a dead loop in the boot process.

Let's see what the code currently does:

By reset default the clock path to the DDR is:

PLL2 (192MHz) -> periph_clk -> main_bus_clk -> axi_a_podf -> axi_a (/1 = 192MHz) -> ddr_clk_root

PLL2 is running at 192MHz. The code now tries to switch PLL2 from 192MHz
to 400MHz. This requires that the RAM is driven by some other clock
during
the PLL reconfiguration. The code switches the clock path to:

PLL3 (400MHz) -> periph_clk -> main_bus_clk -> axi_a_podf -> axi_a (/2 = 200MHz) -> ddr_clk_root

Then PLL2 is reconfigured to 400MHz and the DDR clock path is switched
back to the original path, this time with the PLL runnning at 400MHz, so
RAM is then running at the desired speed.

The code configures PLL3 to 400MHz probably to keep the DDR frequency
nearly constant during the transition.

I have no idea why your change helps you. When I understand correctly
then you are running nearly at half the frequency during the transition
(400/216).

I'm afraid to merge such change as long as we do not fully understand
what we are doing and why it helps.

BTW the current code is the same as on U-Boot which is derived from the
original Freescale code, so this is not exactly new or barebox specific.

Do you have anything special in your dcd table that influences the
clocks in an unexpected way?

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-06-28  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 14:07 Mogens Lauridsen
2018-06-28  8:30 ` Sascha Hauer [this message]
2018-06-28 13:56   ` Mogens Lauridsen
2018-06-29  8:10     ` Sascha Hauer
2018-07-02  9:56       ` Mogens Lauridsen
2018-07-06  6:17         ` Sascha Hauer

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=20180628083021.j6gqwiopqk34vqtl@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mlauridsen171@gmail.com \
    /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