Devicetree
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH v2 00/15] arm64: dts: qcom: Move PCIe phy/GPIOs to root port nodes
Date: Mon, 28 Sep 2026 22:14:54 -0500	[thread overview]
Message-ID: <179065171018.2673486.1615895752148178183.b4-ty@b4> (raw)
In-Reply-To: <20260917-root_port_v2-v2-0-6272b7caae9a@oss.qualcomm.com>


On Thu, 17 Sep 2026 17:55:14 +0530, Krishna Chaitanya Chundru wrote:
> The PCIe PHY references and PERST/WAKE GPIO properties are defined on a
> per-root-port basis and do not belong to the PCIe controller (RC)
> node. Keeping these properties at the controller level makes the
> description less accurate and prevents clean per-port customization.
> 
> This series moves the PHY references (phys, phy-names) from the PCIe
> controller node to the corresponding root port nodes (pcie@0), namely
> pcie0_port0, pcie1_port0, and pcie2_port0. Labels are added to these
> port nodes to enable board-level overrides where required.
> 
> [...]

Applied, thanks!

[01/15] arm64: dts: qcom: qcs6490-vicharak-axon-mini: Move PCIe phy and GPIOs to root port node
        commit: e1e7e255a164cf5c4ab80bb136a4fbdfbb72df3d
[02/15] arm64: dts: qcom: msm8998: Move PCIe phy and GPIOs to root port node
        commit: 9f614fc7197e56797fd8cd9d0e5dc0045e2905c1
[03/15] arm64: dts: qcom: qcs404: Move PCIe phy and GPIOs to root port node
        commit: 1c8f96f67858fba43eb7356be26ccf5d4a019d55
[04/15] arm64: dts: qcom: sar2130p: Move PCIe phy and GPIOs to root port node
        commit: 0384f5b00e222a53ccb5f2e6b1ce246c3b11512c
[05/15] arm64: dts: qcom: sc8180x: Move PCIe phy and GPIOs to root port node
        commit: dea048d7c7ce0f6e659824af6c760f8c82850f49
[06/15] arm64: dts: qcom: sdm845: Move PCIe phy and GPIOs to root port node
        commit: 6b4a3c676e28a92697570e0cd7593ad73eb7840f
[07/15] arm64: dts: qcom: sm8150: Move PCIe phy and GPIOs to root port node
        commit: 9e753907e6ba0190d2ccae8ad3efb21d467b4628
[08/15] arm64: dts: qcom: sm8250: Move PCIe phy and GPIOs to root port node
        commit: 69c776ac585d3124c68bd8e5c39a99cd7a90dcb3
[09/15] arm64: dts: qcom: sm8350: Move PCIe phy and GPIOs to root port node
        commit: 23658da80a4f40e0c8adb7c1214f4e6d7f29c20d
[10/15] arm64: dts: qcom: sm8450: Move PCIe phy and GPIOs to root port node
        commit: 2fd4f062b950e6f46a5f44965c02c14c194a034e
[11/15] arm64: dts: qcom: talos: Move PCIe phy and GPIOs to root port node
        commit: 1518512ca05b3ad6c819026f09e932e99fba0ac6
[12/15] arm64: dts: qcom: sm8650: Move PCIe phy and GPIOs to root port node
        commit: c51818ded215b07e4fd6468cc28a1a4e7bd1231f
[13/15] arm64: dts: qcom: msm8996: Move PCIe phy and GPIOs to root port node
        commit: acb0ce210eed553242dc35795bf70abede7f35d0
[14/15] arm64: dts: qcom: lemans: Move PCIe phy and GPIOs to root port node
        commit: e3a8a50e2a0416305c580121c7346520a4bf462d
[15/15] arm64: dts: qcom: sm8550: Move PCIe phy and GPIOs to root port node
        commit: bbc442a64823f1483177b387ca5fc06c563b2e2f

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2026-09-29  3:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 12:25 [PATCH v2 00/15] arm64: dts: qcom: Move PCIe phy/GPIOs to root port nodes Krishna Chaitanya Chundru
2026-09-17 12:25 ` [PATCH v2 01/15] arm64: dts: qcom: qcs6490-vicharak-axon-mini: Move PCIe phy and GPIOs to root port node Krishna Chaitanya Chundru
2026-09-17 15:11   ` Abel Vesa
2026-09-17 12:25 ` [PATCH v2 02/15] arm64: dts: qcom: msm8998: " Krishna Chaitanya Chundru
2026-09-17 15:11   ` Abel Vesa
2026-09-17 12:25 ` [PATCH v2 03/15] arm64: dts: qcom: qcs404: " Krishna Chaitanya Chundru
2026-09-17 15:11   ` Abel Vesa
2026-09-17 12:25 ` [PATCH v2 04/15] arm64: dts: qcom: sar2130p: " Krishna Chaitanya Chundru
2026-09-17 15:12   ` Abel Vesa
2026-09-17 12:25 ` [PATCH v2 05/15] arm64: dts: qcom: sc8180x: " Krishna Chaitanya Chundru
2026-09-17 15:13   ` Abel Vesa
2026-09-17 12:25 ` [PATCH v2 06/15] arm64: dts: qcom: sdm845: " Krishna Chaitanya Chundru
2026-09-17 15:13   ` Abel Vesa
2026-09-18 10:04   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 07/15] arm64: dts: qcom: sm8150: " Krishna Chaitanya Chundru
2026-09-17 15:19   ` Abel Vesa
2026-09-18 10:06   ` Konrad Dybcio
2026-09-21 11:46     ` Abel Vesa
2026-09-18 10:06   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 08/15] arm64: dts: qcom: sm8250: " Krishna Chaitanya Chundru
2026-09-17 15:19   ` Abel Vesa
2026-09-18 10:06   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 09/15] arm64: dts: qcom: sm8350: " Krishna Chaitanya Chundru
2026-09-17 15:18   ` Abel Vesa
2026-09-18 10:07   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 10/15] arm64: dts: qcom: sm8450: " Krishna Chaitanya Chundru
2026-09-17 15:18   ` Abel Vesa
2026-09-18 10:07   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 11/15] arm64: dts: qcom: talos: " Krishna Chaitanya Chundru
2026-09-17 15:14   ` Abel Vesa
2026-09-18 10:08   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 12/15] arm64: dts: qcom: sm8650: " Krishna Chaitanya Chundru
2026-09-17 15:15   ` Abel Vesa
2026-09-18 10:08   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 13/15] arm64: dts: qcom: msm8996: " Krishna Chaitanya Chundru
2026-09-17 15:15   ` Abel Vesa
2026-09-18 10:08   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 14/15] arm64: dts: qcom: lemans: " Krishna Chaitanya Chundru
2026-09-17 15:15   ` Abel Vesa
2026-09-18 10:09   ` Konrad Dybcio
2026-09-17 12:25 ` [PATCH v2 15/15] arm64: dts: qcom: sm8550: " Krishna Chaitanya Chundru
2026-09-17 15:16   ` Abel Vesa
2026-09-18 10:09   ` Konrad Dybcio
2026-09-29  3:14 ` Bjorn Andersson [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=179065171018.2673486.1615895752148178183.b4-ty@b4 \
    --to=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krishna.chundru@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --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