From: Bjorn Helgaas <helgaas@kernel.org>
To: Matthew Leung <matthew.leung@oss.qualcomm.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] PCI: qcom: Add PCIe support for upcoming Hawi SoC
Date: Thu, 14 May 2026 12:21:51 -0500 [thread overview]
Message-ID: <20260514172151.GA410819@bhelgaas> (raw)
In-Reply-To: <20260508-hawi-pcie-v1-0-0c910906f7e5@oss.qualcomm.com>
On Fri, May 08, 2026 at 01:02:13AM +0000, Matthew Leung wrote:
> This series adds PCIe support for the Qualcomm Hawi SoC. The Hawi
> platform features two PCIe controllers: one capable of Gen3 x2 operation
> and one capable of Gen4 x1 operation. The first patch adds the device
> tree bindings documentation for the Hawi PCIe controller, and the second
> patch adds driver support by enabling the Hawi compatible string in the
> existing qcom PCIe driver.
>
> This series depends on the following prerequisite series:
> - [PATCH v3 0/7] clk: qcom: Add initial clock controllers for the
> upcoming Hawi SoC (Change-ID: 20260316-clk-hawi-1ad4cad36d6a:v3)
> - [PATCH v4 0/2] interconnect: qcom: Add support for upcoming Hawi SoC
> (Change-ID: 20260311-icc-hawi-d6dc165f8935:v4)
>
> These dependencies add necessary headers for running dt_binding_check
> against the binding.
These apply cleanly to v7.1-rc1. I suppose the dt_binding_check thing
is the only real dependency? Is there anything we need to do to
enforce the dependency when these get merged upstream during the merge
window?
> Signed-off-by: Matthew Leung <matthew.leung@oss.qualcomm.com>
> ---
> Matthew Leung (2):
> dt-bindings: PCI: qcom: Document the Hawi PCIe Controller
> PCI: qcom: Add support for Hawi
>
> .../devicetree/bindings/pci/qcom,hawi-pcie.yaml | 188 +++++++++++++++++++++
> drivers/pci/controller/dwc/pcie-qcom.c | 1 +
> 2 files changed, 189 insertions(+)
> ---
> base-commit: 4cd074ae20bbcc293bbbce9163abe99d68ae6ae0
> change-id: 20260506-hawi-pcie-f61435ca420c
> prerequisite-change-id: 20260316-clk-hawi-1ad4cad36d6a:v3
> prerequisite-patch-id: c4fbb0620d748d7f1ee675ade5167775bd31c8ac
> prerequisite-patch-id: ae5e212518cc333a1a93564cabfc6abd128df664
> prerequisite-patch-id: 3c3816e0d595589fc02383f10e48c83a61fdc9d1
> prerequisite-patch-id: cbc13fb819d1c1ee77957393f0958f05db8db864
> prerequisite-patch-id: 17e2c0cfbbea826fefa1c67d0f5dc2094ab73d76
> prerequisite-patch-id: 150dc74750377f4558deab6b179632872bcbb71c
> prerequisite-patch-id: 38fe0da5b18610aeb32c7154f9e50187ccaec6a4
> prerequisite-change-id: 20260311-icc-hawi-d6dc165f8935:v4
> prerequisite-patch-id: a1ff655f0b21d6259b158ad9f99a95bde31257e6
> prerequisite-patch-id: db21b6b20451be8475129faece7ef4191d41273c
I don't know where any of these change-ids or patch-ids come from.
next prev parent reply other threads:[~2026-05-14 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 1:02 [PATCH 0/2] PCI: qcom: Add PCIe support for upcoming Hawi SoC Matthew Leung
2026-05-08 1:02 ` [PATCH 1/2] dt-bindings: PCI: qcom: Document the Hawi PCIe Controller Matthew Leung
2026-05-08 1:21 ` sashiko-bot
2026-05-13 22:53 ` Rob Herring
2026-05-13 22:56 ` Rob Herring
2026-05-14 1:01 ` Matthew Leung
2026-05-08 1:02 ` [PATCH 2/2] PCI: qcom: Add support for Hawi Matthew Leung
2026-05-08 1:29 ` sashiko-bot
2026-05-14 17:21 ` Bjorn Helgaas [this message]
2026-05-14 19:32 ` [PATCH 0/2] PCI: qcom: Add PCIe support for upcoming Hawi SoC Matthew Leung
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=20260514172151.GA410819@bhelgaas \
--to=helgaas@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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=matthew.leung@oss.qualcomm.com \
--cc=robh@kernel.org \
/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