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 v2 0/6] arm64: dts: qcom: clean up PCI function nodes
Date: Mon, 31 Aug 2026 20:36:47 -0500 [thread overview]
Message-ID: <20260901013654.1343537-1-elder@riscstar.com> (raw)
While working on upstream support for the Toshiba TC9564 SoC I
learned that its PCIe endpoint function nodes included the
device_type property, indicating each is a "pci" device. Herve
Codina pointed out that this is not correct; only a PCI device
"that implements a PCI bus" should define that property.
I looked at other upstream devicetree files and I found four other
places with this same mistake. (All are for Qualcomm platforms,
and all are for platforms using a TC956x SoC.)
This series removes the device_type property where it is defined
for a PCI endpoint function.
It also removes the #address-cells, #size-cells, and ranges
properties in these cases, with a plan to restore them only when
they are known to be needed (to implement pci-ep-bus sub-nodes).
-Alex
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
.../boot/dts/qcom/lemans-evk-ifp-mezzanine.dtso | 8 --------
.../boot/dts/qcom/monaco-evk-ifp-mezzanine.dtso | 8 --------
.../qcs6490-rb3gen2-industrial-mezzanine.dtso | 16 ----------------
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 8 --------
.../qcom/qcs6490-thundercomm-minipc-g1iot.dts | 8 --------
arch/arm64/boot/dts/qcom/qcs8550-rb5gen2.dts | 8 --------
6 files changed, 56 deletions(-)
base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
--
2.53.0
next reply other threads:[~2026-09-01 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 1:36 Alex Elder [this message]
2026-09-01 1:36 ` [PATCH v2 1/6] arm64: dts: qcom: qcs6490-rb3gen2: clean up PCI function nodes Alex Elder
2026-09-01 7:25 ` Abel Vesa
2026-09-01 1:36 ` [PATCH v2 2/6] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: " Alex Elder
2026-09-01 7:26 ` Abel Vesa
2026-09-01 1:36 ` [PATCH v2 3/6] arm64: dts: qcom: lemans-evk-ifp-mezzanine: " Alex Elder
2026-09-01 7:26 ` Abel Vesa
2026-09-01 1:36 ` [PATCH v2 4/6] arm64: dts: qcom: monaco-evk-ifp-mezzanine: " Alex Elder
2026-09-01 7:27 ` Abel Vesa
2026-09-01 1:36 ` [PATCH v2 5/6] arm64: dts: qcom: qcs6490-thundercomm-minipc-g1iot: " Alex Elder
2026-09-01 7:27 ` Abel Vesa
2026-09-01 1:36 ` [PATCH v2 6/6] arm64: dts: qcom: qcs8550-rb5gen2: " Alex Elder
2026-09-01 7:27 ` Abel Vesa
2026-09-01 8:13 ` Manivannan Sadhasivam
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=20260901013654.1343537-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