From: Michael Wu <michael@allwinnertech.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
ulf.hansson@linaro.org, linus.walleij@linaro.org, brgl@bgdev.pl,
avri.altman@wdc.com, wsa+renesas@sang-engineering.com,
victor.shih@genesyslogic.com.tw, andy-ld.lu@mediatek.com
Cc: jason.lai@genesyslogic.com.tw, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [RESEND] mmc: core: Fix system shutdown hang in mmc_bus_shutdown
Date: Thu, 16 Oct 2025 14:38:09 +0800 [thread overview]
Message-ID: <6ac35d5e-7d2f-9af6-d1c4-831725c33896@allwinnertech.com> (raw)
In-Reply-To: <9f666390-653d-4834-800d-8997665b6dac@intel.com>
Hello,
The execution timing of this `host->detect` work actually depends on
when the WiFi driver executes its unload procedure. This is something we
cannot control and cannot handle using `reboot_notifier_list` and
`register_reboot_notifier()` operations. Moreover, different WiFi
drivers may have different handling sequences for this timing.
From this perspective, we believe it's not convenient to address the
issue in that way.
We noticed that the `mmc_bus_shutdown` function calling
`cancel_delayed_work_sync` was newly added. Therefore, we suggest
removing this part first.
On 10/15/2025 3:09 PM, Adrian Hunter wrote:
> reboot_notifier_list and
> register_reboot_notifier()
--
Regards,
Michael Wu
next prev parent reply other threads:[~2025-10-16 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 6:07 [RESEND] mmc: core: Fix system shutdown hang in mmc_bus_shutdown Michael Wu
2025-10-15 6:30 ` Linus Walleij
2025-10-15 7:09 ` Adrian Hunter
2025-10-16 6:38 ` Michael Wu [this message]
2025-10-16 6:51 ` Adrian Hunter
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=6ac35d5e-7d2f-9af6-d1c4-831725c33896@allwinnertech.com \
--to=michael@allwinnertech.com \
--cc=adrian.hunter@intel.com \
--cc=andy-ld.lu@mediatek.com \
--cc=avri.altman@wdc.com \
--cc=brgl@bgdev.pl \
--cc=jason.lai@genesyslogic.com.tw \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=victor.shih@genesyslogic.com.tw \
--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