From: Kamal Dasu <kamal.dasu@broadcom.com>
To: Ulf Hansson <ulfh@kernel.org>
Cc: Kamal Dasu <kamal.dasu@broadcom.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Avri Altman <avri.altman@sandisk.com>,
Pedro Demarchi Gomes <pedrodemargomes@gmail.com>,
Erick Shepherd <erick.shepherd@ni.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v6 3/3] mmc: core: Honor keep-power-in-suspend and reset-card-at-resume for (e)MMC
Date: Tue, 4 Aug 2026 16:38:18 -0400 [thread overview]
Message-ID: <20260804203818.881765-4-kamal.dasu@broadcom.com> (raw)
In-Reply-To: <20260804203818.881765-1-kamal.dasu@broadcom.com>
On some platforms, firmware accesses the (e)MMC card directly during
resume from Suspend-to-DRAM, before the kernel's own resume path has
run, in order to load boot code. This requires the card to remain
powered and responsive throughout suspend: putting it to sleep,
sending it a power-off notification, or removing its supply is not
safe, since firmware needs to talk to a live card. Since the card is
never power-cycled, nothing else resets it back to a known state
before the kernel reuses it after resume.
keep-power-in-suspend / MMC_PM_KEEP_POWER already exist for the first
part, but are only consumed in the SDIO suspend/resume path
(mmc_sdio_suspend()/mmc_sdio_resume()), gated on a per-function
runtime request via sdio_set_host_pm_flags(). (e)MMC has no
equivalent function-driver layer to make that request, and the
requirement here is a fixed platform characteristic rather than a
per-cycle one, so _mmc_suspend() checks host->pm_caps directly
instead of pm_flags.
When pm_caps has MMC_PM_KEEP_POWER set and pm_type is
MMC_POWEROFF_SUSPEND, skip the poweroff-notify/sleep/power-off
sequence entirely: deselect the card and mark it suspended. The
pm_type check matters because _mmc_suspend() is also called for
shutdown, driver unbind, and undervoltage, none of which are
guaranteed a subsequent _mmc_resume() call, so those still need the
normal power-off path.
reset-card-at-resume covers the second part: when set, _mmc_resume()
resets the host to its initial bus state the same way _mmc_hw_reset()
does for a non-power-cycle reset, before mmc_power_up() and
mmc_init_card() re-identify the card. This is independent of
MMC_PM_KEEP_POWER in the code, though on brcmstb both capabilities
are set together, since keeping the card powered is what creates the
unknown-state problem reset-card-at-resume addresses.
host->pm_flags is set alongside marking the card suspended, and
cleared in _mmc_resume(), so host controller resume handlers can tell
power was preserved if they need to.
Reported-by: Florian Fainelli <florian.fainelli@broadcom.com>
Closes: https://lore.kernel.org/r/20260413180551.3683969-1-florian.fainelli@broadcom.com/
Signed-off-by: Kamal Dasu <kamal.dasu@broadcom.com>
---
Changes in v6:
- Reworked around Ulf's two-property split: dropped the
unconditional mmc_set_clock()/mmc_set_initial_state() reset from
the suspend-side fast path, and instead perform it in
_mmc_resume(), gated on the new MMC_CAP2_RESET_AT_RESUME (from
reset-card-at-resume), matching the property's name and
description ("before the card can be used, it must be reset").
- No longer touches MMC_CAP2_NO_POWEROFF_SUSPEND/no-mmc-poweroff-
suspend at all -- that capability and property are gone, per the
v4 rework; this patch only adds MMC_CAP2_RESET_AT_RESUME.
Changes in v5:
- Only set host->pm_flags |= MMC_PM_KEEP_POWER after
mmc_deselect_cards() succeeds, instead of unconditionally before
it. Otherwise, if the deselect fails, the card is never marked
suspended, _mmc_resume() takes its early exit, and the flag never
gets cleared -- leaking it for the rest of uptime.
Changes in v4:
- Gated the fast path on pm_type == MMC_POWEROFF_SUSPEND; it was
previously unconditional, so it wrongly skipped the required
power-off/notify handling during shutdown, unbind and
undervoltage as well.
- Set/clear host->pm_flags |= MMC_PM_KEEP_POWER around the suspend/
resume, mirroring the SDIO convention, so host controller resume
handlers can tell power was preserved and perform a soft resume
sequence instead of assuming power was lost.
- Dropped MMC_CAP2_NO_POWEROFF_SUSPEND and the no-mmc-poweroff-
suspend DT property entirely. Reuse keep-power-in-suspend /
MMC_PM_KEEP_POWER instead, per Krzysztof's point that the new
property described the same contract as the existing one.
_mmc_suspend() now checks host->pm_caps directly rather than
pm_flags, since (e)MMC has no per-function driver to make the
dynamic sdio_set_host_pm_flags()-style request SDIO uses.
Changes in v3:
- Reworked _mmc_suspend() to skip poweroff-notify/sleep/power-off
entirely, not just SLEEP, per Ulf.
- Renamed to MMC_CAP2_NO_POWEROFF_SUSPEND/no-mmc-poweroff-suspend.
Changes in v2:
- Replaced the card-level MMC_QUIRK_BROKEN_SLEEP quirk with a host
capability, per Ulf.
- Added Reported-by/Closes crediting Florian.
drivers/mmc/core/host.c | 2 ++
drivers/mmc/core/mmc.c | 33 +++++++++++++++++++++++++++++++++
include/linux/mmc/host.h | 1 +
3 files changed, 36 insertions(+)
diff --git a/drivers/mmc/core/host.c b/drivers/mmc/core/host.c
index b7ce3137d452..1622f7846441 100644
--- a/drivers/mmc/core/host.c
+++ b/drivers/mmc/core/host.c
@@ -400,6 +400,8 @@ int mmc_of_parse(struct mmc_host *host)
if (device_property_read_bool(dev, "no-mmc-hs400"))
host->caps2 &= ~(MMC_CAP2_HS400_1_8V | MMC_CAP2_HS400_1_2V |
MMC_CAP2_HS400_ES);
+ if (device_property_read_bool(dev, "reset-card-at-resume"))
+ host->caps2 |= MMC_CAP2_RESET_AT_RESUME;
/* Must be after "non-removable" check */
if (device_property_read_u32(dev, "fixed-emmc-driver-type", &drv_type) == 0) {
diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index 05444ecf3909..f85e034c79ed 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c
@@ -2157,6 +2157,26 @@ static int _mmc_suspend(struct mmc_host *host, enum mmc_poweroff_type pm_type)
goto out;
}
+ /*
+ * Keep the card powered across an actual suspend; shutdown, unbind
+ * and undervoltage still need the normal power-off path below,
+ * since they aren't guaranteed a subsequent _mmc_resume().
+ *
+ * Check pm_caps, not pm_flags: unlike SDIO, (e)MMC has no
+ * per-function driver to request this via
+ * sdio_set_host_pm_flags(), so it's a fixed platform trait here.
+ */
+ if (pm_type == MMC_POWEROFF_SUSPEND &&
+ (host->pm_caps & MMC_PM_KEEP_POWER)) {
+ if (!mmc_host_is_spi(host))
+ err = mmc_deselect_cards(host);
+ if (!err) {
+ host->pm_flags |= MMC_PM_KEEP_POWER;
+ mmc_card_set_suspended(host->card);
+ }
+ goto out;
+ }
+
if (mmc_card_can_poweroff_notify(host->card) &&
mmc_host_can_poweroff_notify(host, pm_type))
err = mmc_poweroff_notify(host->card, notify_type);
@@ -2217,9 +2237,22 @@ static int _mmc_resume(struct mmc_host *host)
if (!mmc_card_suspended(host->card))
goto out;
+ /*
+ * Firmware or other hardware may have accessed the card while it
+ * stayed powered through suspend, leaving it in a state the kernel
+ * can no longer assume it knows. Reset the host to its initial bus
+ * state like _mmc_hw_reset() does for a non-power-cycle reset,
+ * before mmc_init_card() re-identifies the card.
+ */
+ if (host->caps2 & MMC_CAP2_RESET_AT_RESUME) {
+ mmc_set_clock(host, host->f_init);
+ mmc_set_initial_state(host);
+ }
+
mmc_power_up(host, host->card->ocr);
err = mmc_init_card(host, host->card->ocr, host->card);
mmc_card_clr_suspended(host->card);
+ host->pm_flags &= ~MMC_PM_KEEP_POWER;
out:
mmc_release_host(host);
diff --git a/include/linux/mmc/host.h b/include/linux/mmc/host.h
index ba84f02c2a10..14a407a9f9b7 100644
--- a/include/linux/mmc/host.h
+++ b/include/linux/mmc/host.h
@@ -463,6 +463,7 @@ struct mmc_host {
#define MMC_CAP2_CRYPTO 0
#endif
#define MMC_CAP2_ALT_GPT_TEGRA (1 << 28) /* Host with eMMC that has GPT entry at a non-standard location */
+#define MMC_CAP2_RESET_AT_RESUME (1 << 29) /* Card must be reset before use at resume */
bool uhs2_sd_tran; /* UHS-II flag for SD_TRAN state */
bool uhs2_app_cmd; /* UHS-II flag for APP command */
--
2.34.1
next prev parent reply other threads:[~2026-08-04 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 20:38 [PATCH v6 0/3] mmc: core: Keep the card powered across suspend when firmware needs it live Kamal Dasu
2026-08-04 20:38 ` [PATCH v6 1/3] dt-bindings: mmc: Extend keep-power-in-suspend beyond SDIO Kamal Dasu
2026-08-05 6:58 ` Krzysztof Kozlowski
2026-08-04 20:38 ` [PATCH v6 2/3] dt-bindings: mmc: Add reset-card-at-resume property Kamal Dasu
2026-08-05 6:58 ` Krzysztof Kozlowski
2026-08-04 20:38 ` Kamal Dasu [this message]
2026-08-04 20:59 ` [PATCH v6 3/3] mmc: core: Honor keep-power-in-suspend and reset-card-at-resume for (e)MMC sashiko-bot
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=20260804203818.881765-4-kamal.dasu@broadcom.com \
--to=kamal.dasu@broadcom.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@sandisk.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=erick.shepherd@ni.com \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pedrodemargomes@gmail.com \
--cc=robh@kernel.org \
--cc=ulfh@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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