All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sherry Sun <sherry.sun@oss.nxp.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	 Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Bartosz Golaszewski <brgl@kernel.org>,
	 Manivannan Sadhasivam <mani@kernel.org>,
	Amitkumar Karwar <amitkumar.karwar@nxp.com>,
	 Neeraj Kale <neeraj.sanjaykale@nxp.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	 linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,  linux-pci@vger.kernel.org,
	linux-pm@vger.kernel.org,
	 Rahul Samana <rahul.samana@oss.qualcomm.com>,
	Wei Deng <wei.deng@oss.qualcomm.com>,
	 Loic Poulain <loic.poulain@oss.qualcomm.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 0/5] Rework M.2 Bluetooth instantiation using the auxiliary bus
Date: Fri, 18 Sep 2026 17:48:08 +0800	[thread overview]
Message-ID: <aq0IfMrMISvQUwbv@shlinux88> (raw)
In-Reply-To: <20260915-pci-m2-bt-rework-v1-0-3c7d9cf9c010@oss.qualcomm.com>

On Tue, Sep 15, 2026 at 04:24:01PM +0200, Manivannan Sadhasivam wrote:
>Hi,
>
>This series reworks the PCIe M.2 Bluetooth instantiation using the auxiliary
>bus.
>
>The Bluetooth interface of the QCA2066, WCN6855, WCN7850 and NXP 88W8987
>M.2 modules is accessed over UART, but the modules show up at runtime over
>PCIe and are not described in firmware like devicetree. To make the serdev
>bus match the Bluetooth driver, the power sequencing driver was creating a
>devicetree node at runtime using an of_changeset. But, creating a node just for
>driver matching is not recommended as per Krzysztof [1].
>
>So this series reworks the instantiation to use the auxiliary bus instead. The
>power sequencing driver still allocates the UART serdev, but now hands it over
>through an auxiliary device along with the power sequencing target. So this
>series adds auxiliary driver support to hci_qca and btnxpuart drivers binding to
>this device and brings up the controller over the existing UART transport.
>Finally, it drops the serdev based M.2 code from both BT drivers.
>
>Dependency
>==========
>
>This series depends on Monza series from Loic [2] and reuses its
>pwrseq_is_controllable() API.
>
>[1] https://lore.kernel.org/linux-pci/768142f0-2638-41f3-a34f-dc80bb99eb7f@kernel.org
>[2] https://lore.kernel.org/all/20260904-monza-wireless-v6-0-d8c5042b3efd@oss.qualcomm.com
>

For the NXP 88W8987 M.2 module related changes:
Tested-by: Sherry Sun <sherry.sun@nxp.com>

Best Regards
Sherry Sun

>Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
>---
>Manivannan Sadhasivam (5):
>      Bluetooth: hci_qca: Add auxiliary driver for PCIe M.2 modules
>      Bluetooth: btnxpuart: Add auxiliary driver for PCIe M.2 modules
>      power: sequencing: pcie-m2: Create auxiliary device for the M.2 BT interface
>      Bluetooth: hci_qca: Drop serdev based M.2 power sequencing code
>      Bluetooth: btnxpuart: Drop serdev based M.2 power sequencing code
>
> MAINTAINERS                               |   1 +
> drivers/bluetooth/Kconfig                 |   2 +
> drivers/bluetooth/btnxpuart.c             | 193 +++++++++++++++++++-----------
> drivers/bluetooth/hci_qca.c               | 138 +++++++++++++++------
> drivers/power/sequencing/Kconfig          |   2 +-
> drivers/power/sequencing/pwrseq-pcie-m2.c | 137 +++++++++++----------
> include/linux/pwrseq/pcie-m2-bt.h         |  38 ++++++
> 7 files changed, 343 insertions(+), 168 deletions(-)
>---
>base-commit: e5e04726cdd043e309677071ab1b65a4b18f422b
>change-id: 20260806-pci-m2-bt-rework-78dc2c926f00
>prerequisite-message-id: 20260904-monza-wireless-v6-0-d8c5042b3efd@oss.qualcomm.com
>prerequisite-patch-id: c4e777757ca9358cc4dd35e23738cd7dc1ead1a0
>prerequisite-patch-id: 09600595c2e80b12eda3aae39af192847d0f03d0
>prerequisite-patch-id: afe88432c4d459e9094c0e6dd31ebeab6c9f2f08
>prerequisite-patch-id: 60fd7b13447ccad7546fa8e5b5609d8f133f788f
>prerequisite-patch-id: 61dcbe55fdb6f33a3229c197f16a678785aa16d8
>prerequisite-patch-id: 14099e5c573d7c41b899c3f9bb9126aa23f1553e
>prerequisite-patch-id: 647ee15b77671054b4bb012afa9ba8694b6c86c5
>prerequisite-patch-id: c3a774cae81a6fad287731a38f1b76c7e8babc4c
>prerequisite-patch-id: 18b0fa62060a1a2c96e76051944d692699035572
>prerequisite-patch-id: df02ab167976ac1f0d5a38c78e559a7372b16c1f
>prerequisite-patch-id: 3f2dddd108677252a539cdb1eb661912836289ca
>
>Best regards,
>--
>மணிவண்ணன் சதாசிவம்
>

      parent reply	other threads:[~2026-09-18  9:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 14:24 [PATCH 0/5] Rework M.2 Bluetooth instantiation using the auxiliary bus Manivannan Sadhasivam
2026-09-15 14:24 ` Manivannan Sadhasivam via B4 Relay
2026-09-15 14:24 ` [PATCH 1/5] Bluetooth: hci_qca: Add auxiliary driver for PCIe M.2 modules Manivannan Sadhasivam
2026-09-15 14:24   ` Manivannan Sadhasivam via B4 Relay
2026-09-15 17:11   ` Rework M.2 Bluetooth instantiation using the auxiliary bus bluez.test.bot
2026-09-16  9:39   ` [PATCH 1/5] Bluetooth: hci_qca: Add auxiliary driver for PCIe M.2 modules Bartosz Golaszewski
2026-09-15 14:24 ` [PATCH 2/5] Bluetooth: btnxpuart: " Manivannan Sadhasivam
2026-09-15 14:24   ` Manivannan Sadhasivam via B4 Relay
2026-09-15 14:51   ` Andy Shevchenko
2026-09-15 14:24 ` [PATCH 3/5] power: sequencing: pcie-m2: Create auxiliary device for the M.2 BT interface Manivannan Sadhasivam
2026-09-15 14:24   ` Manivannan Sadhasivam via B4 Relay
2026-09-16  9:19   ` Bartosz Golaszewski
2026-09-21  7:58     ` Manivannan Sadhasivam
2026-09-21  9:08       ` Bartosz Golaszewski
2026-09-21  9:51         ` Bartosz Golaszewski
2026-09-21 11:03           ` Manivannan Sadhasivam
2026-09-15 14:24 ` [PATCH 4/5] Bluetooth: hci_qca: Drop serdev based M.2 power sequencing code Manivannan Sadhasivam
2026-09-15 14:24   ` Manivannan Sadhasivam via B4 Relay
2026-09-15 14:24 ` [PATCH 5/5] Bluetooth: btnxpuart: " Manivannan Sadhasivam
2026-09-15 14:24   ` Manivannan Sadhasivam via B4 Relay
2026-09-18  9:48 ` Sherry Sun [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=aq0IfMrMISvQUwbv@shlinux88 \
    --to=sherry.sun@oss.nxp.com \
    --cc=amitkumar.karwar@nxp.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brgl@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=loic.poulain@oss.qualcomm.com \
    --cc=luiz.dentz@gmail.com \
    --cc=mani@kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=marcel@holtmann.org \
    --cc=neeraj.sanjaykale@nxp.com \
    --cc=p.zabel@pengutronix.de \
    --cc=rahul.samana@oss.qualcomm.com \
    --cc=wei.deng@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.