mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "yhchen312@gmail.com" <yhchen312@gmail.com>
Cc: Damon Chen <damon.chen@realtek.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: 8852be: add .shutdown callback to quiesce device on reboot
Date: Wed, 29 Jul 2026 06:53:45 +0000	[thread overview]
Message-ID: <7311cac831b2439db0b35af5012cef9b@realtek.com> (raw)
In-Reply-To: <20260729013537.2743729-1-yhchen312@gmail.com>

yhchen312@gmail.com <yhchen312@gmail.com> wrote:
> Hi Ping-Ke,
> 
> Thanks for the review.
> 
> > Does it mean the work is running after .shutdown but before .remove?
> 
> On the reboot/poweroff path the kernel only runs device_shutdown(),
> which invokes each driver's .shutdown callback; .remove is *not* called
> on this path -- it only runs on driver unbind, module unload or
> hot-unplug.  The rfkill polling workqueue, however, keeps being scheduled
> by the rfkill core throughout the whole shutdown sequence until the
> system finally halts.  During that window the platform starts tearing
> the PCIe link down, and the next MMIO read issued by
> rtw89_ops_rfkill_poll() then targets a non-responding device, which on
> arm64 is reported as a fatal asynchronous SError.  So it is not ".remove
> after .shutdown"; .remove never runs on reboot -- the poll work simply
> outlives the link, and that is exactly what the new flag stops.

Thanks for the detail. 

Ping-Ke


  reply	other threads:[~2026-07-29  6:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  1:54 yhchen312
2026-07-28  2:45 ` Ping-Ke Shih
2026-07-29  1:35   ` yhchen312
2026-07-29  6:53     ` Ping-Ke Shih [this message]
2026-07-29  1:41   ` [PATCH v2] wifi: rtw89: pci: add .shutdown callback to stop rfkill polling " yhchen312
2026-07-29  6:52     ` Ping-Ke Shih
2026-08-02  1:28     ` Ping-Ke Shih

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=7311cac831b2439db0b35af5012cef9b@realtek.com \
    --to=pkshih@realtek.com \
    --cc=damon.chen@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yhchen312@gmail.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

all inboxes | Powered by JetHome®