Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Robert Nelson <robertcnelson@gmail.com>,
	Andreas Kemnade <andreas@kemnade.info>,
	Romain Naour <romain.naour@smile.fr>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Kevin Hilman <khilman@baylibre.com>,
	Roger Quadros <rogerq@kernel.org>,
	Jason Kridner <jkridner@beagleboard.org>,
	"Aldea, Andrei" <a-aldea@ti.com>, David <daowens01@gmail.com>,
	linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: sdhci-omap: additional PM issue since 5.16
Date: Tue, 1 Apr 2025 07:00:58 +0300	[thread overview]
Message-ID: <20250401040058.GH4957@atomide.com> (raw)
In-Reply-To: <CAPDyKFqY-XtVrmXnkYbW+8XZ3eHukMKyG6FKXRh=vz4gmXujEQ@mail.gmail.com>

* Ulf Hansson <ulf.hansson@linaro.org> [250320 08:48]:
> On Thu, 20 Mar 2025 at 05:14, Tony Lindgren <tony@atomide.com> wrote:
> >
> > Hi,
> >
> > * Ulf Hansson <ulf.hansson@linaro.org> [250312 11:56]:
> > > On Fri, 7 Mar 2025 at 05:28, Tony Lindgren <tony@atomide.com> wrote:
> > > > Based on the symptoms, it sounds like there might be a missing flush of
> > > > a posted write in the PM runtime suspend/resume path. This could cause
> > > > something in the sequence happen in the wrong order for some of the
> > > > related surrounding resources like power, clocks or interrupts.
> > >
> > > SDIO is entirely different in this regard compared to eMMC/SD. So if
> > > there are no reports of issues I suggest we keep the SDIO part.
> >
> > Hmm just wondering if you have any guesses what causes the eMMC/SD related
> > PM to break?
> >
> > Regards,
> >
> > Tony
> 
> Well, I have recently been looking a bit closer at the runtime PM
> support of the eMMC/SD card. We seem to have some kind of related
> problems [1], but I am not really sure yet.
> 
> That said, I believe I may have found some *potential* issues and I am
> working on a few patches for it (for the mmc core), I will keep you
> and the people in $subject posted. Although, it's not quite clear to
> me, why these problems have turned up at this point and not a lot
> earlier. I have a feeling there is something that I am missing.
> 
> Also note that, if the problems are sdhci/sdhci-omap specific, it
> becomes a bit more difficult for me to help out.
> 
> Luckily, it seems like David shared a pretty simple script with us,
> which should reproduce the problem in just a few minutes. There are
> also debugfs and the runtime PM-sysfs interface one can use to play
> with the behaviour of MMC_CAP_AGGRESSIVE_PM.

OK thanks for the description. AFAIK this is issue has not been happening
with the eMMC and the old mmc-omap-hs driver. Sounds like the issue might
be also eMMC specific.

Regards,

Tony

> [1]
> https://bugzilla.kernel.org/show_bug.cgi?id=218821
> https://lore.kernel.org/all/CAPDyKFq4-fL3oHeT9phThWQJqzicKeA447WBJUbtcKPhdZ2d1A@mail.gmail.com/T/

      reply	other threads:[~2025-04-01  4:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 22:09 sdhci-omap: additional PM issue since 5.16 David Owens
2025-01-24 10:36 ` 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 [this message]

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=20250401040058.GH4957@atomide.com \
    --to=tony@atomide.com \
    --cc=a-aldea@ti.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=daowens01@gmail.com \
    --cc=jkridner@beagleboard.org \
    --cc=khilman@baylibre.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robertcnelson@gmail.com \
    --cc=rogerq@kernel.org \
    --cc=romain.naour@smile.fr \
    --cc=ulf.hansson@linaro.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