[meta-freescale] Commit 1b673ef breaks riotboard boot

[Fabio Estevam]

Hi Nikolay,

On Mon, Apr 27, 2015 at 1:33 AM, Nikolay Dimitrov <picmaster at mail.bg> wrote:
> Hi Fabio,
>
> Commit 1b673ef (linux-fslc, branch "patch-4.0") breaks booting of
> riotboard. Reverting the patch allows the board to boot properly. It
> looks like the patch causes some issue with the sdcard detection, as
> shown below in the logs (only the emmc is detected):

Thanks for reporting it. I don't have access to a riotboard, so will
need some help to debugging this problem.

The commit you pointed out has reached 4.1-rc1 now as 8d86e4fcccf61bafe.

This commit has been in linux-next for sometime and I haven't seen
such behaviour in the boards I have access to. Also, Olof's boot farm
contains hummingboard and wandboard and they are booting fine in
linux-next and 4.1-rc1. Please check:
http://arm-soc.lixom.net/bootlogs/mainline/v4.1-rc1/wandboard-arm-imx_v6_v7_defconfig.html

Could you please try booting 4.1-rc1 on riotboard? I would like to
understand if this issue only happens on linux-fslc branch or not.

>
> [    1.447707] sdhci: Secure Digital Host Controller Interface driver
> [    1.453974] sdhci: Copyright(c) Pierre Ossman
> [    1.458488] sdhci-pltfm: SDHCI platform and OF driver helper
> [    1.465423] sdhci-esdhc-imx 2194000.usdhc: could not get ultra high speed
> state, work on normal mode
> [    1.474725] sdhci-esdhc-imx 2194000.usdhc: Got CD GPIO
> [    1.479985] sdhci-esdhc-imx 2194000.usdhc: Got WP GPIO

CD and WP GPIO were retrieved here.

> [    1.485574] sdhci-esdhc-imx 2194000.usdhc: No vqmmc regulator found
> [    1.539993] mmc0: SDHCI controller on 2194000.usdhc [2194000.usdhc] using
> ADMA
> [    1.551185] sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed
> state, work on normal mode
> [    1.574222] sdhci-esdhc-imx 2198000.usdhc: Got CD GPIO
> [    1.589766] sdhci-esdhc-imx 2198000.usdhc: Got WP GPIO

Same here.

> [    1.606144] sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found
> ...
> [    2.408926] VFS: Cannot open root device "mmcblk0p2" or
> unknown-block(179,2): error -6

Could this be related to the old mmc probe order issue? What is the
mmc port you want to mount the rootfs? Has it changed to mmcblk1?

Also, could you please remove 'wp-gpios' from the dts to see if this
makes any difference?

Thanks,

Fabio Estevam