Re: [PATCH] Bluetooth: btnxpuart: Check remote M.2 connector availability before pwrseq
| Newsgroups | org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178699595888.1691257.12228192402111698983.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>: On Mon, 17 Aug 2026 10:27:39 +0800 you wrote: > From: Sherry Sun <[email protected]> > > The current code uses of_graph_is_present() to decide whether to enter > the pwrseq path. However, of_graph_is_present() only checks for the > structural presence of a port/ports sub-node and does not check the > status property. This causes problems when a DT overlay disables the > remote M.2 connector node (e.g., switching from PCIe WiFi to SDIO WiFi): > the port node still exists, so of_graph_is_present() returns true, but > the pwrseq provider never registers because the connector is disabled, > leading to an infinite -EPROBE_DEFER loop. > > [...] Here is the summary with links: - Bluetooth: btnxpuart: Check remote M.2 connector availability before pwrseq https://git.kernel.org/bluetooth/bluetooth-next/c/f716a05f4967 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html