From: sashiko-bot@kernel.org
To: ziniu.wang_1@oss.nxp.com
Cc: Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v3 7/7] mmc: sdhci-esdhc-imx: fix resume error handling
Date: Mon, 29 Jun 2026 09:54:02 +0000 [thread overview]
Message-ID: <20260629095403.0A7951F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260629091954.3227151-8-ziniu.wang_1@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Early return on `pm_runtime_force_resume()` failure in `sdhci_esdhc_resume()` skips necessary software state cleanups, causing a PM runtime usage counter leak and leaving IRQs unbalanced.
--
commit 007c15943feda7e921c0c9613b702cc8b9ee7f97
Author: Luke Wang <ziniu.wang_1@nxp.com>
mmc: sdhci-esdhc-imx: fix resume error handling
This commit updates the resume function to check the return value of
pm_runtime_force_resume. If it fails, the function now returns immediately
to avoid hardware panics.
> diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c b/drivers/mmc/host/sdhci-esdhc-imx.c
> --- a/drivers/mmc/host/sdhci-esdhc-imx.c
> +++ b/drivers/mmc/host/sdhci-esdhc-imx.c
> @@ -2125,12 +2125,12 @@ static int sdhci_esdhc_resume(struct device *dev)
> dev_warn(dev, "Failed to restore pinctrl state\n");
> }
>
> - pm_runtime_force_resume(dev);
> -
> - ret = mmc_gpio_set_cd_wake(host->mmc, false);
> + ret = pm_runtime_force_resume(dev);
> if (ret)
> return ret;
[Severity: High]
If pm_runtime_force_resume fails and we return early here, does this skip
necessary software state cleanups?
It looks like returning early bypasses the enable_irq() and
sdhci_disable_irq_wakeups() calls later in sdhci_esdhc_resume, which might
leave the IRQ descriptor depth and wakeup sources incorrectly configured.
[ ... ]
> @@ -2157,7 +2157,7 @@ static int sdhci_esdhc_resume(struct device *dev)
>
> pm_runtime_put_autosuspend(dev);
[Severity: High]
If the early return is taken above, this PM usage count decrement is bypassed.
Will this permanently leave the device's PM runtime usage counter elevated,
preventing both the device and its parent power domains from ever runtime
suspending again?
>
> - return ret;
> + return 0;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260629091954.3227151-1-ziniu.wang_1@oss.nxp.com?part=7
next prev parent reply other threads:[~2026-06-29 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 9:19 [PATCH v3 0/7] mmc: sdhci-esdhc-imx: fix SDIO suspend/resume issues ziniu.wang_1
2026-06-29 9:19 ` [PATCH v3 1/7] mmc: sdhci-esdhc-imx: remove unnecessary mmc_card_wake_sdio_irq check for tuning save/restore ziniu.wang_1
2026-06-29 9:29 ` sashiko-bot
2026-06-29 9:35 ` Bough Chen
2026-06-29 9:19 ` [PATCH v3 2/7] mmc: sdhci-esdhc-imx: restore DLL override for DDR modes on resume ziniu.wang_1
2026-06-29 9:30 ` sashiko-bot
2026-06-29 9:39 ` Bough Chen
2026-06-29 9:19 ` [PATCH v3 3/7] mmc: sdhci-esdhc-imx: restore pinctrl before restoring ios timing " ziniu.wang_1
2026-06-29 9:46 ` sashiko-bot
2026-06-29 9:48 ` Bough Chen
2026-06-29 9:19 ` [PATCH v3 4/7] mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt ziniu.wang_1
2026-06-29 9:51 ` Bough Chen
2026-06-29 9:19 ` [PATCH v3 5/7] mmc: sdhci-esdhc-imx: use pm_runtime_resume_and_get() in suspend ziniu.wang_1
2026-06-29 9:46 ` sashiko-bot
2026-06-29 9:19 ` [PATCH v3 6/7] mmc: sdhci-esdhc-imx: make non-fatal errors non-blocking " ziniu.wang_1
2026-06-29 9:57 ` sashiko-bot
2026-06-29 9:19 ` [PATCH v3 7/7] mmc: sdhci-esdhc-imx: fix resume error handling ziniu.wang_1
2026-06-29 9:54 ` sashiko-bot [this message]
2026-06-29 10:10 ` Luke Wang (OSS)
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=20260629095403.0A7951F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=imx@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=ziniu.wang_1@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.