From: Christian Hewitt <firstname.lastname@example.org> To: Jaehoon Chung <email@example.com> Cc: Krzysztof Kozlowski <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, Marian Mihailescu <email@example.com>, Marek Szyprowski <firstname.lastname@example.org>, Sylwester Nawrocki <email@example.com>, Ulf Hansson <firstname.lastname@example.org> Subject: Re: BUG: Cannot boot Odroid XU4 from eMMC without this patch Date: Fri, 1 Oct 2021 17:41:17 +0400 [thread overview] Message-ID: <974A393B-EE0A-487F-8315-D4E0498DAA25@gmail.com> (raw) In-Reply-To: <email@example.com> > On 1 Oct 2021, at 4:40 am, Jaehoon Chung <firstname.lastname@example.org> wrote: > > On 9/27/21 8:09 PM, Krzysztof Kozlowski wrote: >> On Mon, 13 Sept 2021 at 06:32, Christian Hewitt >> <email@example.com> wrote: >>> >>> https://protect2.fireeye.com/v1/url?k=6f7d4070-30e6793d-6f7ccb3f-0cc47aa8f5ba-2c8976d4b015314f&q=1&e=776d64d2-22f3-400a-a241-42af8b5f60d0&u=https%3A%2F%2Fgithub.com%2Fchewitt%2Flinux%2Fcommit%2F8a4ebfb43a394e5dc5e9fafc92a50d5e81a4f258 >>> >>> If I boot any recent kernel without the above patch, the emmc module on the XU4 is not detected, see: >>> >>> Without: >>> >>> [ 3.227837] mmc0: tuning execution failed: -5 >>> [ 3.231229] mmc0: error -5 whilst initialising MMC card >>> [ 3.536450] mmc0: tuning execution failed: -5 >>> [ 3.539680] mmc0: error -5 whilst initialising MMC card >>> [ 3.794056] mmc0: tuning execution failed: -5 >>> [ 3.794212] mmc0: error -5 whilst initialising MMC card >>> [ 4.111097] mmc0: tuning execution failed: -5 >>> [ 4.115356] mmc0: error -5 whilst initialising MMC card >>> [ 4.426164] mmc0: tuning execution failed: -5 >>> [ 4.429678] mmc0: error -5 whilst initialising MMC card >>> [ 4.756226] mmc0: tuning execution failed: -5 >>> [ 4.760641] mmc0: error -5 whilst initialising MMC card >>> >>> With: >>> >>> [ 3.305461] mmc0: new HS400 MMC card at address 0001 >>> [ 3.307444] mmcblk0: mmc0:0001 8GME4R 7.28 GiB >>> [ 3.308132] mmcblk0boot0: mmc0:0001 8GME4R 4.00 MiB >>> [ 3.309172] mmcblk0boot1: mmc0:0001 8GME4R 4.00 MiB >>> [ 3.310255] mmcblk0rpmb: mmc0:0001 8GME4R 512 KiB, chardev (246:0) >>> [ 3.315963] mmcblk0: p1 p2 >>> >>> The patch is sourced from a Linux 5.4 patchset used by several retro gaming distros for XU4 images shared in the HardKernel forums. I would be happy to submit it, but the original patch has no description in the commit message. Not being a coding developer myself I cannot explain whether it is correct or what it’s doing to add one. All I can do is confirm that it works, and is needed. SD card boot is not an issue. >>> >>> I’ve CC’d the original author (Marian) in case he remembers the patch and can comment. It would be good to get this upstream. >> >> The patch might have sense but would require describing conditions - >> what MMC input and output clock settings work and which do not work. >> Also someone would need to test other Exynos5422 boards and other >> Exynos with HS200 and HS400 support (Exynos5433, Exynos7). I think >> this should not affect SD cards. > > > Thanks for adding me. > I didn't see XU4 booting fail with linux-5.15-rc1 kernel. > > [ 4.561934] mmc1: new HS400 MMC card at address 0001 > [ 4.572401] mmcblk1: mmc1:0001 SDW16G 14.7 GiB > [ 4.602555] mmcblk1: p1 p2 p3 p4 < p5 p6 p7 > > [ 4.623201] mmcblk1boot0: mmc1:0001 SDW16G 4.00 MiB > [ 4.640465] mmcblk1boot1: mmc1:0001 SDW16G 4.00 MiB > > Which kernel version did you use? The original report is against 5.14.0, but I see the same with 5.15-rc3 dmesg: http://ix.io/3AuL dmesg | grep mmc: http://ix.io/3AuO And if I pick that patch to my kernel branch all is good: dmesg: http://ix.io/3Avf dmesg | grep mmc: http://ix.io/3Ave Here’s an SD (or eMMC) bootable image for an XU4 that exhibits the problem. You need to run “systemctl stop kodi” once the UART console is available else it attempts to run Kodi and Panfrost (the image is created for some Panfrost poking) currently wedges the board. Once the Kodi service is stopped “systemctl mask kodi” will prevent it from running again. https://chewitt.libreelec.tv/testing/LibreELEC-Exynos.arm-10.0.0-odroid-xu4.img.gz Kernel defconfig for the image: http://sprunge.us/G6uxty - basically the exynos config but with a wide variety of not-needed drivers (other SoCs, network cards, etc.) disabled. The board is booting from u-boot 2020.04 in case that matters. Christian
next prev parent reply other threads:[~2021-10-01 13:41 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-13 4:27 Christian Hewitt 2021-09-27 11:09 ` Krzysztof Kozlowski 2021-10-01 0:40 ` Jaehoon Chung 2021-10-01 13:41 ` Christian Hewitt [this message] 2021-10-06 22:16 ` Jaehoon Chung 2021-10-07 4:36 ` Christian Hewitt 2021-10-07 11:05 ` Jaehoon Chung 2021-10-20 11:14 ` Jaehoon Chung 2021-10-04 10:07 ` Marek Szyprowski 2021-10-04 13:01 ` Krzysztof Kozlowski 2021-10-04 15:51 ` Marek Szyprowski 2021-10-06 10:40 ` Ulf Hansson 2021-10-06 22:12 ` Jaehoon Chung 2021-10-06 22:01 ` Jaehoon Chung
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=974A393B-EE0A-487F-8315-D4E0498DAA25@gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: BUG: Cannot boot Odroid XU4 from eMMC without this patch' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).