public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Thierry Bultel <tbultel@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0
Date: Fri, 21 Mar 2014 19:47:48 +0100	[thread overview]
Message-ID: <532C8954.3010409@free.fr> (raw)
In-Reply-To: <53283D62.7060200@denx.de>

Le 18/03/2014 13:34, Stefano Babic a ?crit :
> Hi Thierry,
>
>
> On 18/03/2014 12:28, tbultel at free.fr wrote:
>>
>> Hi,
>>
>> I am working on a board (AMOS820 from Via) based on the mx6qsabrelite.
>>
>> The BSP provided by the manufacturer is quite old.
>> I managed to port it from Freescale uboot-imx rel_imx_3.0.35_4.1.0 to u-boot
>> mainline, and basically the latest issue I have is the cpu frequency.
>>
>> The kernel I use is the rel_imx_3.0.35_4.1.0 as well (same tag name)
>>
>> With the old u-boot, it runs at 1Ghz because the BSP explicitly has a call to
>>
>> clk_config(CONFIG_REF_CLK_FREQ, 1000, CPU_CLK);
>>
>> With the new u-boot, it runs at default freq which is 800Mhz (at least, what I
>> guess from the Bogomips because no other log says it)
> It is can taken as reference, but checking the BogoMIPS is not the right
> way to proof it. You should take a look at the CCM registers when Linux
> is running ( CCM_ANALOG_PLL_ARM).
>
>> I have attempted to pass "arm_freq=1000" to the boot args but that does not
>> change anything.
> Well, this is a kernel issue, and related to an ancient version.
>
>> My concern is that clk_config does not seem to be available anymore, there is
>> get_mcu_main_clk but no set routine.
> It was never available in mainline.
>
>> I wonder if it is intentional, I could write a set routine but I wonder if it
>> could be accepted as a patch.
> Why not ? All patches are discussed here and if it makes sense to merge
> it, it will be merged.

Hi Stefano,
many thanks for your advice,

It is now running at 1Ghz. I still have a couple of issues that prevent me to submit
a patch as is:

1) The kernel (old, I know) I am using does not like that PCIe to have been formerly probed by
u-boot. It hangs at probing if so.
Thus I have to patch my kernel, or add an environment variable to not initialize PCIe when
set, in order to keep compatible with old kernels. For now, in order to boot, I have
temporary disabled PCIe support in U-boot.

2) The splashscreen (loaded at 10000000) disappears when loading the kernel
Would you have any idea or hints about it ?

Best Regards
Thierry



> Best regards,
> Stefano Babic
>

  reply	other threads:[~2014-03-21 18:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 11:28 [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0 tbultel at free.fr
2014-03-18 12:34 ` Stefano Babic
2014-03-21 18:47   ` Thierry Bultel [this message]
2014-03-21 22:50     ` Eric Nelson
2014-03-22  1:33       ` Marek Vasut
2014-03-22 15:13         ` Eric Nelson
2014-03-22 15:17         ` [U-Boot] [PATCH] ARM: mx6: Disable PCIe on SABRE Lite/Nitrogen6x Eric Nelson
2014-03-22 18:26           ` Marek Vasut
2014-03-22 20:50             ` Thierry Bultel
2014-03-22 21:49               ` Eric Nelson
2014-03-23  0:15                 ` Marek Vasut
2014-03-23  0:11               ` Marek Vasut
2014-03-23 16:50               ` Stefano Babic
2014-03-23 16:48             ` Stefano Babic
2014-04-01  8:17           ` Stefano Babic

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=532C8954.3010409@free.fr \
    --to=tbultel@free.fr \
    --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