From: Tony Lindgren <tony@atomide.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>, Nishanth Menon <nm@ti.com>
Subject: Re: sdhci-omap: issues with PM features since 5.16
Date: Mon, 29 Jan 2024 13:17:33 +0200 [thread overview]
Message-ID: <20240129111733.GX5185@atomide.com> (raw)
In-Reply-To: <d09925b3-83e6-4c52-878f-4c1db7670543@smile.fr>
* Romain Naour <romain.naour@smile.fr> [240129 10:11]:
> Hello,
>
> Le 27/01/2024 à 05:48, Tony Lindgren a écrit :
> > Hi,
> >
> > * Romain Naour <romain.naour@smile.fr> [240126 20:53]:
> >> Hello,
> >>
> >> I'm upgrading the kernel from 5.10.168 to 6.1.69 (both from TI tree) on a custom
> >> board based on a AM574x SoC and I noticed a regression on the sdhci-omap driver.
> >>
> >> The emmc was working on the 5.10 kernel using mmc-hs200 powered at 1,8v (mmc2).
> >
> > Is this limited to emmc or does it also happen with the micro-sd or wlan possibly?
>
> I can't test with a wlan device but I noticed the same issue on micro-sd (the
> mmc0 interface in my first post is a micro-sd)
OK
> > If the issue is emmc related, do you have mmc-pwrseq-emmc configured in the dts?
> >
> >> I'm able to reproduce on the IDK574x evaluation board (where the emmc is powered
> >> at 3v3) with vanilla kernels.
> >
> > OK, looks like only am5729-beagleboneai.dts has configured mmc-pwrseq-emmc.
> >
> >> I had to revert all commits related to "PM runtime functions" [1] and "card
> >> power off and enable aggressive PM" [2] from kernel 5.16 to use the emmc again
> >> on both boards.
> >
> > OK, this sounds like power sequence related when the emmc gets idled.
>
> It seems mmc0 ios infos are lost at some point, just after the kernel boot they
> are correct:
>
> cat /sys/kernel/debug/mmc0/ios
> clock: 50000000 Hz
> vdd: 21 (3.3 ~ 3.4 V)
> bus mode: 2 (push-pull)
> chip select: 0 (don't care)
> power mode: 2 (on)
> bus width: 2 (4 bits)
> timing spec: 2 (sd high-speed)
> signal voltage: 0 (3.30 V)
> driver type: 0 (driver type B)
>
> And without notice, ios became wrong:
>
> cat /sys/kernel/debug/mmc0/ios
> clock: 0 Hz
> vdd: 0 (invalid)
> bus mode: 2 (push-pull)
> chip select: 0 (don't care)
> power mode: 0 (off)
> bus width: 0 (1 bits)
> timing spec: 0 (legacy)
> signal voltage: 0 (3.30 V)
> driver type: 0 (driver type B)
>
> # cat /sys/bus/mmc/devices/mmc0:1234/type
> SD
With a beagle x15, the ios values are correct after I do
something like fdisk -l /dev/mmcblk0:
# cat /sys/kernel/debug/mmc0/ios
clock: 0 Hz
vdd: 0 (invalid)
bus mode: 2 (push-pull)
chip select: 0 (don't care)
power mode: 0 (off)
bus width: 0 (1 bits)
timing spec: 0 (legacy)
signal voltage: 0 (3.30 V)
driver type: 0 (driver type B)
# fdisk -l /dev/mmcblk0
...
# cat /sys/kernel/debug/mmc0/ios
clock: 50000000 Hz
vdd: 21 (3.3 ~ 3.4 V)
bus mode: 2 (push-pull)
chip select: 0 (don't care)
power mode: 2 (on)
bus width: 2 (4 bits)
timing spec: 2 (sd high-speed)
signal voltage: 0 (3.30 V)
driver type: 0 (driver type B)
So I'm still guessing your issue is with emmc not getting reinitialized
properly as there's no mmc-pwrseq-emmc configured. Can you give it a
try? See am5729-beagleboneai.dts for an example.
Regards,
Tony
next prev parent reply other threads:[~2024-01-29 11:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 20:53 sdhci-omap: issues with PM features since 5.16 Romain Naour
2024-01-27 4:48 ` Tony Lindgren
2024-01-29 10:11 ` Romain Naour
2024-01-29 11:17 ` Tony Lindgren [this message]
2024-01-29 17:42 ` Romain Naour
2024-01-30 11:14 ` Romain Naour
2024-01-31 10:30 ` Tony Lindgren
2024-02-01 9:04 ` Romain Naour
2024-02-02 4:36 ` Tony Lindgren
2024-02-08 11:29 ` Romain Naour
2024-02-08 12:57 ` Adam Ford
2024-02-12 7:27 ` Tony Lindgren
2024-02-12 13:24 ` Adam Ford
2024-02-13 6:03 ` Tony Lindgren
2024-02-13 12:43 ` Adam Ford
2024-02-13 12:58 ` Tony Lindgren
2024-03-15 23:49 ` Romain Naour
2024-03-21 9:48 ` Tony Lindgren
2024-01-30 11:15 ` Tony Lindgren
2024-01-30 11:22 ` Romain Naour
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=20240129111733.GX5185@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=romain.naour@smile.fr \
/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