From: Matthew Leung <matthew.leung@oss.qualcomm.com>
To: Manivannan Sadhasivam <manisadhasivam.linux@gmail.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,
"Krzysztof Kozlowski" <krzk@kernel.org>
Subject: Re: [PATCH v2 0/2] PCI: qcom: Add PCIe support for upcoming Hawi SoC
Date: Thu, 4 Jun 2026 18:27:49 -0700 [thread overview]
Message-ID: <078551b4-049a-477a-a538-a02c8c7c18d1@oss.qualcomm.com> (raw)
In-Reply-To: <CAGyK6coCyziKzffGmj+fGs4U+mXEeYJ0Q2+z6xHCA+i=gop2oA@mail.gmail.com>
On 6/4/2026 5:09 AM, Manivannan Sadhasivam wrote:
> On Wed, 3 Jun 2026 01:26:53 +0200, Matthew Leung
> <matthew.leung@oss.qualcomm.com> said:
>>
>>
>> On 5/30/2026 3:06 AM, Krzysztof Kozlowski wrote:
>>> On Fri, May 29, 2026 at 01:10:07AM +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 series queued on linux-next:
>>>> - [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)
>>>
>>> It cannot depend there it makes it unmergeable and untestable. I skip
>>> review in such case, please follow standard documented practices about
>>> decoupling independent works.
>>
>> Thanks for the feedback. On checking the dependencies, the changes are
>> applied in their respective maintainer trees:
>> - clk: applied to qcom/linux.git for-next, commit d6cd9d5692ba
>> - icc: applied to djakov/icc.git icc-next, commit 07548b04dc36
>>
>> Both commits are present in my linux-next base-commit and have checked
>> dt_binding_check passes cleanly.
>>
>> I can resend with the dependency references updated accordingly.
>>
>
> No. It will still break the pci tree when this series gets merged. Please
> resubmit after v7.2-rc1.
Okay, I will resubmit after the dependencies merge on mainline.
>
> - Mani
prev parent reply other threads:[~2026-06-05 1:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 1:10 Matthew Leung
2026-05-29 1:10 ` [PATCH v2 1/2] dt-bindings: PCI: qcom: Document the Hawi PCIe Controller Matthew Leung
2026-05-30 10:06 ` Krzysztof Kozlowski
2026-06-07 20:01 ` Dmitry Baryshkov
2026-06-12 1:17 ` Matthew Leung
2026-06-12 6:22 ` Dmitry Baryshkov
2026-06-18 4:44 ` Matthew Leung
2026-06-18 5:51 ` Manivannan Sadhasivam
2026-05-29 1:10 ` [PATCH v2 2/2] PCI: qcom: Add support for Hawi Matthew Leung
2026-05-30 10:06 ` [PATCH v2 0/2] PCI: qcom: Add PCIe support for upcoming Hawi SoC Krzysztof Kozlowski
2026-06-02 23:26 ` Matthew Leung
2026-06-04 12:09 ` Manivannan Sadhasivam
2026-06-05 1:27 ` Matthew Leung [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=078551b4-049a-477a-a538-a02c8c7c18d1@oss.qualcomm.com \
--to=matthew.leung@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=manisadhasivam.linux@gmail.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
all inboxes | Powered by JetHome®