From: Alex Elder <elder@riscstar.com>
To: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: mani@kernel.org, krishna.chundru@oss.qualcomm.com,
dmitry.baryshkov@oss.qualcomm.com,
sushrut.trivedi@oss.qualcomm.com, umang.chheda@oss.qualcomm.com,
rosh@debian.org, jsandom@axon.com, daniel@riscstar.com,
mohd.anwar@oss.qualcomm.com, lorenzo.bianconi@oss.qualcomm.com,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/6] arm64: dts: qcom: clean up PCI function nodes
Date: Wed, 2 Sep 2026 16:43:14 -0500 [thread overview]
Message-ID: <20260902214321.1721477-1-elder@riscstar.com> (raw)
While working on upstream support for the Toshiba TC9564 SoC I
discovered that the way its PCIe endpoint function nodes are
defined in devicetree files is incorrect. Two issues have been
pointed out during the course of review:
- Only PCI bridge device nodes should contain this property:
device_type = "pci";
- Only bridge device nodes should be named "pcie@" (or "pci@")
The second of these was previously addressed by this series:
https://lore.kernel.org/lkml/20260901172058.1512508-1-elder@riscstar.com/
Instead, those changes are now included here.
These errors existed for the RB3gen2 platform, but five other Qualcomm
devicetree files had this same mistake (all describing a TC9564 SoC).
This series removes the device_type property where it is defined
for a PCI endpoint function, and renames such nodes "dev@".
The #address-cells, #size-cells, and ranges properties are also
removed for these nodes. These will be restored when they are
known to be needed (to implement pci-ep-bus sub-nodes).
-Alex
Between version 2 and version 3:
- Added Reviewed-by from Abel (and for the last patch, Mani)
- Renamed all nodes "dev@" rather than "pcie@" or "pci@"
Version 2 is available here:
https://lore.kernel.org/lkml/20260901013654.1343537-1-elder@riscstar.com/
Between version 1 and version 2:
- Added Reviewed-by from Mani and Konrad
- Added a patch that updates "qcs8550-rb5gen2.dts" as well
Version 1 is available here:
https://lore.kernel.org/lkml/20260807195846.456079-1-elder@riscstar.com/
Alex Elder (6):
arm64: dts: qcom: qcs6490-rb3gen2: clean up PCI function nodes
arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: clean up PCI
function nodes
arm64: dts: qcom: lemans-evk-ifp-mezzanine: clean up PCI function
nodes
arm64: dts: qcom: monaco-evk-ifp-mezzanine: clean up PCI function
nodes
arm64: dts: qcom: qcs6490-thundercomm-minipc-g1iot: clean up PCI
function nodes
arm64: dts: qcom: qcs8550-rb5gen2: clean up PCI function nodes
.../dts/qcom/lemans-evk-ifp-mezzanine.dtso | 12 ++--------
.../dts/qcom/monaco-evk-ifp-mezzanine.dtso | 12 ++--------
.../qcs6490-rb3gen2-industrial-mezzanine.dtso | 24 ++++---------------
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 12 ++--------
.../qcom/qcs6490-thundercomm-minipc-g1iot.dts | 12 ++--------
arch/arm64/boot/dts/qcom/qcs8550-rb5gen2.dts | 12 ++--------
6 files changed, 14 insertions(+), 70 deletions(-)
base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
--
2.53.0
next reply other threads:[~2026-09-02 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 21:43 Alex Elder [this message]
2026-09-02 21:43 ` [PATCH v3 1/6] arm64: dts: qcom: qcs6490-rb3gen2: clean up PCI function nodes Alex Elder
2026-09-02 21:43 ` [PATCH v3 2/6] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: " Alex Elder
2026-09-02 21:43 ` [PATCH v3 3/6] arm64: dts: qcom: lemans-evk-ifp-mezzanine: " Alex Elder
2026-09-02 21:43 ` [PATCH v3 4/6] arm64: dts: qcom: monaco-evk-ifp-mezzanine: " Alex Elder
2026-09-02 21:43 ` [PATCH v3 5/6] arm64: dts: qcom: qcs6490-thundercomm-minipc-g1iot: " Alex Elder
2026-09-02 21:43 ` [PATCH v3 6/6] arm64: dts: qcom: qcs8550-rb5gen2: " Alex Elder
2026-09-03 17:20 ` [PATCH v3 0/6] arm64: dts: qcom: " Bjorn Andersson
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=20260902214321.1721477-1-elder@riscstar.com \
--to=elder@riscstar.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@riscstar.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jsandom@axon.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=lorenzo.bianconi@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=rosh@debian.org \
--cc=sushrut.trivedi@oss.qualcomm.com \
--cc=umang.chheda@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