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, imx@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
sherry.sun@nxp.com
Subject: Re: [PATCH V7] Bluetooth: btnxpuart: Add M.2 Bluetooth device support using pwrseq
Date: Thu, 06 Aug 2026 19:54:58 +0000 [thread overview]
Message-ID: <178604609814.1449574.1250783761019962599.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260721030458.1160824-1-sherry.sun@oss.nxp.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 21 Jul 2026 11:04:58 +0800 you wrote:
> From: Sherry Sun <sherry.sun@nxp.com>
>
> Power supply to the M.2 Bluetooth device attached to the host using M.2
> connector is controlled using the 'uart' pwrseq device. So add support
> for getting the pwrseq device if the OF graph link is present.
>
> Once obtained, pwrseq_power_on() is called to power up the M.2 Bluetooth
> card. The power sequencer descriptor is obtained via pwrseq_get() with
> the UART controller device (serdev->ctrl->dev), since the OF graph
> link is defined on the UART controller node.
>
> [...]
Here is the summary with links:
- [V7] Bluetooth: btnxpuart: Add M.2 Bluetooth device support using pwrseq
https://git.kernel.org/bluetooth/bluetooth-next/c/c424d3c907ec
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-06 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 3:04 [PATCH V7] Bluetooth: btnxpuart: Add M.2 Bluetooth device support using pwrseq Sherry Sun (OSS)
2026-07-21 3:12 ` sashiko-bot
2026-08-05 2:59 ` Sherry Sun (OSS)
2026-08-06 19:54 ` 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=178604609814.1449574.1250783761019962599.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--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