From: Wei Deng <wei.deng@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org, quic_chezhou@quicinc.com,
cheng.jiang@oss.qualcomm.com, shuai.zhang@oss.qualcomm.com,
jinwang.li@oss.qualcomm.com, xiuzhuo.shang@oss.qualcomm.com,
mengshi.wu@oss.qualcomm.com
Subject: [PATCH 0/2] Enable WCN6855 Bluetooth on lemans-evk via PCIe M.2 Key E connector
Date: Mon, 8 Jun 2026 14:47:00 +0530 [thread overview]
Message-ID: <20260608091702.3797437-1-wei.deng@oss.qualcomm.com> (raw)
This series enables WCN6855 Bluetooth on the lemans EVK through the
PCIe M.2 Key E connector + pwrseq-pcie-m2 path.
It depends on the "Fixes/improvements for the PCI M.2 power sequencing
driver" series (V3):
https://lore.kernel.org/r/20260519-pwrseq-m2-bt-v3-0-b39dc2ae3966@oss.qualcomm.com
Patch 1 adds 0x1103 (WCN6855) to pwrseq_m2_pci_ids[] alongside the
existing 0x1107 (WCN7850) entry, with compatible "qcom,wcn6855-bt".
Patch 2 describes the M.2 Key E connector on lemans-evk:
- pcie-m2-e-connector node, port@0 -> pcieport0,
port@3 -> uart17 (BT serdev path)
- vreg_dcin_12v (12V) + vreg_wcn_3p3 (3.3V, vin-supply 12V),
both always-on/boot-on, as required by the binding
- compatible = "pciclass,0604" on pcieport0 in lemans.dtsi so the
PCI subsystem can match the DT node to the PCI-to-PCI bridge
- serial1 = &uart17 alias
Wei Deng (2):
power: sequencing: pcie-m2: Add PCI ID 0x1103 for WCN6855 Bluetooth
arm64: dts: qcom: lemans-evk: Describe the PCIe M.2 Key E connector
arch/arm64/boot/dts/qcom/lemans-evk.dts | 75 +++++++++++++++++++++++
arch/arm64/boot/dts/qcom/lemans.dtsi | 1 +
drivers/power/sequencing/pwrseq-pcie-m2.c | 2 +
3 files changed, 78 insertions(+)
--
2.34.1
next reply other threads:[~2026-06-08 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 9:17 Wei Deng [this message]
2026-06-08 9:17 ` [PATCH 1/2] power: sequencing: pcie-m2: Add PCI ID 0x1103 for WCN6855 Bluetooth Wei Deng
2026-06-08 14:34 ` Manivannan Sadhasivam
2026-06-15 10:32 ` [PATCH v2] arm64: dts: qcom: lemans-evk: Describe the PCIe M.2 Key E connector Wei Deng
2026-06-16 0:28 ` Dmitry Baryshkov
2026-06-16 3:00 ` Wei Deng
2026-06-16 0:26 ` [PATCH 1/2] power: sequencing: pcie-m2: Add PCI ID 0x1103 for WCN6855 Bluetooth Dmitry Baryshkov
2026-06-16 3:03 ` Wei Deng
2026-06-08 9:17 ` [PATCH 2/2] arm64: dts: qcom: lemans-evk: Describe the PCIe M.2 Key E connector Wei Deng
2026-06-08 14:25 ` Bartosz Golaszewski
2026-06-08 14:19 ` (subset) [PATCH 0/2] Enable WCN6855 Bluetooth on lemans-evk via " Bartosz Golaszewski
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=20260608091702.3797437-1-wei.deng@oss.qualcomm.com \
--to=wei.deng@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jinwang.li@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mengshi.wu@oss.qualcomm.com \
--cc=quic_chezhou@quicinc.com \
--cc=robh@kernel.org \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=xiuzhuo.shang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox