From: Linghui Wu <linghui.wu@oss.qualcomm.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Bjorn Andersson <andersson@kernel.org>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Abel Vesa" <abelvesa@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Sushrut Shree Trivedi" <sushrut.trivedi@oss.qualcomm.com>,
"Miaoqing Pan" <miaoqing.pan@oss.qualcomm.com>,
"Hangtian Zhu" <hangtian.zhu@oss.qualcomm.com>,
"Shuai Zhang" <shuai.zhang@oss.qualcomm.com>,
"Cheng Jiang" <cheng.jiang@oss.qualcomm.com>,
"Wei Deng" <wei.deng@oss.qualcomm.com>,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Linghui Wu" <linghui.wu@oss.qualcomm.com>
Subject: [PATCH v5 0/4] PCI: qcom: add Shikra PCIe and M.2 Wi-Fi/BT support
Date: Thu, 12 Nov 2026 16:33:51 +0800 [thread overview]
Message-ID: <20261112083355.3884737-1-linghui.wu@oss.qualcomm.com> (raw)
Add PCIe controller support for the Qualcomm Shikra platform and an
overlay for M.2 Key-E Wi-Fi and Bluetooth modules on the Shikra IQS EVK.
The previous overlay revisions depended on PCIe controller and device
tree changes that were only present in the Qualcomm downstream kernel.
Include the required PCIe binding, driver match data and controller/PHY
nodes so the overlay can be reviewed and built against linux-next.
The overlay describes the board variant where hardware rework selects
the M.2 connectivity path instead of the onboard WCN3988 path.
The series has been validated on Shikra hardware.
Changes in v5:
- Rebase the series onto linux-next next-20261111.
- Include the Shikra PCIe binding, driver and DTS prerequisites.
- Make the overlay self-contained on the upstream Shikra device tree.
- Build and validate the base DTB, DTBO and composite DTB.
- Start a new review thread instead of replying to an older revision.
Changes in v4:
- Build a composite DTB to validate that the overlay applies to the base DTB.
- Explain that the product design does not operate the onboard and M.2
connectivity paths simultaneously.
- Report Bluetooth UART and HCI validation.
Linghui Wu (1):
arm64: dts: qcom: shikra-iqs: add M.2 Wi-Fi and Bluetooth overlay
Sushrut Shree Trivedi (3):
dt-bindings: PCI: qcom: document the Shikra PCIe controller
PCI: qcom: add support for the Shikra PCIe controller
arm64: dts: qcom: shikra: add PCIe PHY and controller nodes
.../devicetree/bindings/arm/qcom-soc.yaml | 1 +
.../bindings/pci/qcom,pcie-shikra.yaml | 192 ++++++++++++++++++
arch/arm64/boot/dts/qcom/Makefile | 2 +
.../dts/qcom/shikra-iqs-evk-m2-wifi-bt.dtso | 122 +++++++++++
arch/arm64/boot/dts/qcom/shikra.dtsi | 158 ++++++++++++++
drivers/pci/controller/dwc/pcie-qcom.c | 1 +
6 files changed, 476 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/qcom,pcie-shikra.yaml
create mode 100644 arch/arm64/boot/dts/qcom/shikra-iqs-evk-m2-wifi-bt.dtso
base-commit: aaa2f954c21b205a0bcd0961e5b2be4e82e58455
--
2.43.0
next reply other threads:[~2026-11-12 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:33 Linghui Wu [this message]
2026-11-12 8:33 ` [PATCH v5 1/4] dt-bindings: PCI: qcom: document the Shikra PCIe controller Linghui Wu
2026-11-12 8:33 ` [PATCH v5 2/4] PCI: qcom: add support for " Linghui Wu
2026-11-12 8:33 ` [PATCH v5 3/4] arm64: dts: qcom: shikra: add PCIe PHY and controller nodes Linghui Wu
2026-11-12 8:33 ` [PATCH v5 4/4] arm64: dts: qcom: shikra-iqs: add M.2 Wi-Fi and Bluetooth overlay Linghui Wu
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=20261112083355.3884737-1-linghui.wu@oss.qualcomm.com \
--to=linghui.wu@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=hangtian.zhu@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=miaoqing.pan@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=sushrut.trivedi@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 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®