From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: eMMC probe in imx8mm
Date: Tue, 9 Jul 2019 11:46:40 +0200 [thread overview]
Message-ID: <20190709094640.n2hrjjed5ghywsea@pengutronix.de> (raw)
In-Reply-To: <14d5d82d-ddb0-89e2-84c0-00cb980dda2a@data-modul.com>
Hi Reyhaneh,
On Fri, Jul 05, 2019 at 02:04:08PM +0000, Yazdani, Reyhaneh wrote:
> Hello everyone,
>
> I have brought up Barebox on imx8mm-evk board. Barebox is programmed on SD-card.
> In the Barebox console, when I probe eMMC, I will receive I/O error.
>
> Therefore, similar to the imx8mq device tree, I added clk node to assign
> clock-parent and clock-rates of the assigned clock of the eMMC (usdhc3):
>
> &clk {
> assigned-clocks = <&clk IMX8MM_CLK_USDHC3_ROOT>;
> assigned-clock-parents = <&clk IMX8MM_SYS_PLL1_400M>;
> assigned-clock-rates = <200000000>;
> };
>
> Now, eMMC probe works and eMMC is detected. But when I want to boot from eMMC,
>
> Loading ARM aarch64 Linux image '/mnt/mmc2/Image' takes about 13-14 seconds!!
How big is this image?
Is only the eMMC card so slow or the SD card aswell?
Does clk_dump give you any clue which clock rate the usdhc controller
actually has (and is it the same as the other controller with the SD
card)?
Just some questions, I am not very familiar with the i.MX8 clock tree.
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
next prev parent reply other threads:[~2019-07-09 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 14:04 Yazdani, Reyhaneh
2019-07-09 9:46 ` Sascha Hauer [this message]
2019-07-11 13:30 ` Yazdani, Reyhaneh
2019-07-12 6:12 ` Yazdani, Reyhaneh
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=20190709094640.n2hrjjed5ghywsea@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=RYazdani@data-modul.com \
--cc=barebox@lists.infradead.org \
/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