public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v2, 4/4] arm: am33xx: Add support for mulitiple PLL input frequencies
Date: Thu, 8 Jun 2017 10:17:09 +0530	[thread overview]
Message-ID: <7ef0d989-49bd-ef37-e7f1-a835caa9b520@ti.com> (raw)
In-Reply-To: <20170607205006.68b4780d28b90c1dfd9c12fe@bidouilliste.com>



On Thursday 08 June 2017 12:20 AM, Emmanuel Vadot wrote:
> On Fri, 12 May 2017 13:20:50 -0400
> Tom Rini <trini@konsulko.com> wrote:
> 
>> On Fri, May 05, 2017 at 12:59:10PM +0530, Lokesh Vutla wrote:
>>
>>> am335x supports various sysclk frequencies which can be determined
>>> using sysboot pins. PLLs should be configures based on this
>>> sysclk frequency. Add PLL configurations for all supported
>>> frequencies.
>>>
>>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>>> Reviewed-by: Tom Rini <trini@konsulko.com>
>>
>> Applied to u-boot/master, thanks!
>>
>> -- 
>> Tom
> 
>  Hello,
> 
>  This appears to break beaglebone black support, reverting this commit
> make u-boot works again.

hmm..I see the problem. Here we are hard coding MPU freq to 1GHz even
efuse say it is not supported(I am not sure why this is being done, may
be Tom can give more details). Even in kernel I see that cpufreq is
reading efuse to determine mpu frequency. Now that we have jitter
optimized pll configurations, looks like unsupported freq is causing an
issue. Can you see if the below patch helps?

------------8<------------------8<--------------------------

  reply	other threads:[~2017-06-08  4:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  7:29 [U-Boot] [PATCH v2 0/4] arm: am33xx: Add support for dynamic programming of PLL Lokesh Vutla
2017-05-05  7:29 ` [U-Boot] [PATCH v2 1/4] configs: convert CONFIG_SYS_MPUCLK to Kconfig Lokesh Vutla
2017-05-05 14:17   ` Tom Rini
2017-05-12 17:20   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-05-05  7:29 ` [U-Boot] [PATCH v2 2/4] arm: am33xx: Fix MPU opp selection Lokesh Vutla
2017-05-05 14:17   ` Tom Rini
2017-05-12 17:20   ` [U-Boot] [U-Boot,v2,2/4] " Tom Rini
2017-05-05  7:29 ` [U-Boot] [PATCH v2 3/4] board: am335x: Introduce scale_vcores Lokesh Vutla
2017-05-12 17:20   ` [U-Boot] [U-Boot,v2,3/4] " Tom Rini
2017-05-05  7:29 ` [U-Boot] [PATCH v2 4/4] arm: am33xx: Add support for mulitiple PLL input frequencies Lokesh Vutla
2017-05-05 14:17   ` Tom Rini
2017-05-12 17:20   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-06-07 18:50     ` Emmanuel Vadot
2017-06-08  4:47       ` Lokesh Vutla [this message]
2017-06-08 17:34         ` Emmanuel Vadot
2017-06-09  0:45         ` Tom Rini
2017-06-09  4:00           ` Heiko Schocher
2017-06-09  9:25             ` Lokesh Vutla
2017-06-09 10:22               ` Heiko Schocher
2017-06-09 11:20                 ` Tom Rini
2017-06-09 15:55                   ` Heiko Schocher
2017-06-09 19:13                     ` Tom Rini
2017-06-09 19:45                       ` Robert Nelson
2017-06-09 20:00                         ` Tom Rini
2017-06-09 20:22                           ` Robert Nelson
2017-06-12  4:19                           ` Heiko Schocher
2017-06-09 19:53                       ` Emmanuel Vadot
2017-06-09 20:17                         ` Tom Rini
2017-06-09 16:53           ` Robert Nelson
2017-06-09 17:33         ` Robert Nelson
2017-06-09 17:37         ` Robert Nelson

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=7ef0d989-49bd-ef37-e7f1-a835caa9b520@ti.com \
    --to=lokeshvutla@ti.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