Re: arm64: dts: meson: Boot failure with using eMMC

From: Jerome Brunet <jbrunet@baylibre.com>
To: Bob <pigiron@protonmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Cc: "linux-amlogic@lists.infradead.org" <linux-amlogic@lists.infradead.org>
Subject: Re: arm64: dts: meson: Boot failure with using eMMC
Date: Mon, 13 May 2019 11:53:21 +0200	[thread overview]
Message-ID: <dc6ee617fb0902ae05289b2bc794c8362fd08eae.camel@baylibre.com> (raw)
In-Reply-To: <7yaiVYWS-VlbP5H6BTXnSiNE_w6ZJQRMX8DjxBa7gDLaZ4PoWFPg_CZkd9EU0-UVVuGvpxrlTJR1_6i64BP7eSb3XZdCV9vv3NFhHsmifA8=@protonmail.com>

On Sat, 2019-05-11 at 20:49 +0000, Bob wrote:
> Even though I come with a problem, I first want to thank you folks for all
> that you do. It's much appreciated.
> 
> So on to the problem. I've got an Odroid C2 (meson-gxbb) with an eMMC chip
> that Ameridroid claims to be an "eMMC Version 4.5 - HS200 interface with
> 8bit DDR mode from Samsung".

Could you share the complete part number that is written on the samsung MMC
module ?

> 
> I run the Arch Linux "mainline" kernel and it had been working well. But when
> I upgraded the kernel from 4.20 to 5.0 it failed to boot when UBoot couldn't
> mount the root filesystem, so it dropped into it's shell. Using an USB serial
> dongle, I noticed that none of the usual /dev/mmcblk* files were created.
> 
> I saved the failing boot output from the USB dongle, downgraded back to the
> 4.20 kernel, and now it booted successfully. When I compared the good/bad
> dongle outputs it seems that the first error messages were:
> 
>    [2.790141] meson-gx-mmc d0074000.mmc: no support for card's volts
>        (snip)
>    [2.799730] mmc0: error -22 whilst initialising MMC card
> 
> I then did a bunch of "git bisect" compiles on Linus' "vanilla" kernel from his
> git tree and ultimately it pointed to commit:
> 
>    arm64: dts: meson: disable pad bias for mmc pinmuxes
>    96a13691c1ddfafc301d1ee451d91fc2cca48d27
> 
> Sure enough, when I now revert that commit in /boot/dtbs/amlogic/meson-gxbb-
> odroidc2.dtb on the latest shipping 5.1 kernel, it boots successfully. That
> same 5.1 kernel fails to boot with the same error messages when that commit
> is engaged.

Would you mind trying this branch from kevin:

https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/log/?h=integ

This particular commit might be useful considering your bisect results:

https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/commit/?h=integ&id=1c10023f4d1b75ed164f60bb0ee6bc239655408c

> 
> 
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic