[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ac35d5e-7d2f-9af6-d1c4-831725c33896@allwinnertech.com>
Date: Thu, 16 Oct 2025 14:38:09 +0800
From: Michael Wu <michael@...winnertech.com>
To: Adrian Hunter <adrian.hunter@...el.com>, ulf.hansson@...aro.org,
linus.walleij@...aro.org, brgl@...ev.pl, avri.altman@....com,
wsa+renesas@...g-engineering.com, victor.shih@...esyslogic.com.tw,
andy-ld.lu@...iatek.com
Cc: jason.lai@...esyslogic.com.tw, linux-mmc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [RESEND] mmc: core: Fix system shutdown hang in mmc_bus_shutdown
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
Powered by blists - more mailing lists