mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Sherry Sun (OSS) <sherry.sun@oss.nxp.com>
Cc: amitkumar.karwar@nxp.com, neeraj.sanjaykale@nxp.com,
	marcel@holtmann.org, luiz.dentz@gmail.com, mani@kernel.org,
	bartosz.golaszewski@oss.qualcomm.com, Frank.Li@nxp.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	sherry.sun@nxp.com
Subject: Re: [PATCH] Bluetooth: btnxpuart: Check remote M.2 connector availability before pwrseq
Date: Mon, 17 Aug 2026 19:45:58 +0000	[thread overview]
Message-ID: <178699595888.1691257.12228192402111698983.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260817-btnxpuart_m2-v1-1-a23e51020794@nxp.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 17 Aug 2026 10:27:39 +0800 you wrote:
> From: Sherry Sun <sherry.sun@nxp.com>
> 
> 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



      reply	other threads:[~2026-08-17 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  2:27 Sherry Sun (OSS)
2026-08-17 19:45 ` patchwork-bot+bluetooth [this message]

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=178699595888.1691257.12228192402111698983.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=amitkumar.karwar@nxp.com \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=mani@kernel.org \
    --cc=marcel@holtmann.org \
    --cc=neeraj.sanjaykale@nxp.com \
    --cc=sherry.sun@nxp.com \
    --cc=sherry.sun@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 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®