From: David Owens <daowens01@gmail.com>
To: linux-omap@vger.kernel.org
Cc: linux-mmc@vger.kernel.org
Subject: sdhci-omap: additional PM issue since 5.16
Date: Thu, 23 Jan 2025 16:09:43 -0600 [thread overview]
Message-ID: <1c5f72c4-3d55-4d62-b690-8c68b76a15d2@gmail.com> (raw)
Hello,
I have a AM574x system and encountered an eMMC regression when upgrading from 5.15 to 6.1.38. The eMMC is using mmc-hs200 powered at 1.8v. Reads from /dev/mmcblk1boot0 will return expected data except when a delay of several seconds is inserted between reads. With a delay between reads, the read will occasionally (~50% of the time) return garbage data. Using hexdump, I was able to determine that the "bad" data is actually coming from /dev/mmcblk1, not /dev/mmcblk1boot0. The same thing happens when reading from /dev/mmcblk1boot1.
Much like a previous report in the linux-omap mailing list [1], I too was able to correct the regression by reverting the commit "mmc: sdhci-omap: Allow SDIO card power off and enable aggressive PM" [2]. Unlike the previous report, applying the sdhci-omap patch [3] did not resolve my issue. Only reverting the original commit allowed for reliable reads from /dev/mmcblk1boot0. I also don't see the same I/O errors mentioned in the previous posting. Reads always succeed and return the correct amount of data, its just from the wrong device.
[1] https://lore.kernel.org/all/2e5f1997-564c-44e4-b357-6343e0dae7ab@smile.fr/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3edf588e7fe00e90d1dc7fb9e599861b2c2cf442
[3] https://lore.kernel.org/linux-omap/20240315234444.816978-1-romain.naour@smile.fr/T/#u
Regards,
Dave
next reply other threads:[~2025-01-23 22:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:09 David Owens [this message]
2025-01-24 10:36 ` sdhci-omap: additional PM issue since 5.16 Romain Naour
2025-01-24 17:15 ` David Owens
2025-01-24 18:49 ` David
2025-01-27 9:06 ` Romain Naour
2025-01-27 21:20 ` Robert Nelson
2025-02-26 15:36 ` Robert Nelson
2025-02-26 16:06 ` Andreas Kemnade
2025-03-07 4:28 ` Tony Lindgren
2025-03-07 14:42 ` Robert Nelson
2025-03-09 17:58 ` Andreas Kemnade
2025-03-12 11:55 ` Ulf Hansson
2025-03-20 4:14 ` Tony Lindgren
2025-03-20 8:47 ` Ulf Hansson
2025-04-01 4:00 ` Tony Lindgren
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=1c5f72c4-3d55-4d62-b690-8c68b76a15d2@gmail.com \
--to=daowens01@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.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