From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6: Add initial SPL support for HummingBoard-i2eX
Date: Thu, 16 Apr 2015 02:18:55 +0300 [thread overview]
Message-ID: <552EF1DF.7030505@mail.bg> (raw)
In-Reply-To: <1429131475-12805-1-git-send-email-festevam@gmail.com>
Hi Fabio,
On 04/15/2015 11:57 PM, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Add the initial SPL support for HummingBoard-i2eX, which is based on a
> MX6 Dual.
>
> For more information about HummingBoard, please check:
> http://www.solid-run.com/products/hummingboard/
>
> Based on the work from Jon Nettleton and Rabeeh Khoury.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> Currently only HummingBoard-i2eX is supported.
>
> After this initial patch is accepted, then we can add the other Hummingboard
> and Cubox-i variants as well.
The patch looks nice and clean.
> +static struct mx6_ddr3_cfg mem_ddr = {
> + .mem_speed = 1600,
> + .density = 4,
> + .width = 64,
> + .banks = 8,
> + .rowaddr = 14,
> + .coladdr = 10,
> + .pagesz = 2,
> + .trcd = 1375,
> + .trcmin = 4875,
> + .trasmin = 3500,
> +};
> +
This mem_speed (1600) means that the MMDC imx6 code will calculate
timings for 1600 MT/s, but in reality the memory clock will be 528 or
532 MHz. It would be better to override the speed to 1066 to make
sure imx6 ddr code calculates proper timings.
To be honest, I don't understand why the code (arch/arm/cpu/armv7
/mx6/ddr.c) supports 1333/1600 MT/s when it's obvious that it's outside
chip specs.
> +static void ccgr_init(void)
> +{
> + struct mxc_ccm_reg *ccm = (struct mxc_ccm_reg *)CCM_BASE_ADDR;
> +
> + writel(0x00C03F3F, &ccm->CCGR0);
> + writel(0x0030FC03, &ccm->CCGR1);
> + writel(0x0FFFC000, &ccm->CCGR2);
> + writel(0x3FF00000, &ccm->CCGR3);
> + writel(0x00FFF300, &ccm->CCGR4);
> + writel(0x0F0000C3, &ccm->CCGR5);
> + writel(0x000003FF, &ccm->CCGR6);
> +}
This is nice - clocks are optimal, to the dual-core imx6 won't overheat
if left for long time in U-Boot shell.
And a couple of more notes:
- I see that you don't use the extlinux boot mechanism (from distro
defaults). Do you see any advantages of not using it?
- Would be nice to have HDMI support :)
- git patch gives a warning about one empty line
Reviewed-by: Nikolay Dimitrov <picmaster@mail.bg>
Thanks for the hard work. Regards,
Nikolay
next prev parent reply other threads:[~2015-04-15 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 20:57 [U-Boot] [PATCH] mx6: Add initial SPL support for HummingBoard-i2eX Fabio Estevam
2015-04-15 22:35 ` Tom Rini
2015-04-16 0:40 ` Fabio Estevam
2015-04-15 23:18 ` Nikolay Dimitrov [this message]
2015-04-16 0:48 ` Fabio Estevam
2015-04-16 1:24 ` Nikolay Dimitrov
2015-04-16 1:27 ` Fabio Estevam
2015-04-16 9:57 ` Nikolay Dimitrov
2015-04-16 7:39 ` Stefano Babic
2015-04-16 12:13 ` Tom Rini
2015-04-16 13:07 ` Tom Rini
2015-04-20 17:23 ` Tom Rini
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=552EF1DF.7030505@mail.bg \
--to=picmaster@mail.bg \
--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