From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Alex Elder <elder@riscstar.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: krishna.chundru@oss.qualcomm.com,
dmitry.baryshkov@oss.qualcomm.com, mani@kernel.org,
sushrut.trivedi@oss.qualcomm.com, umang.chheda@oss.qualcomm.com,
rosh@debian.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] arm64: dts: qcom: clean up PCI function nodes
Date: Tue, 18 Aug 2026 14:36:54 +0200 [thread overview]
Message-ID: <40868661-4a52-44bf-8ff2-790c222c10bc@oss.qualcomm.com> (raw)
In-Reply-To: <20260807195846.456079-1-elder@riscstar.com>
On 8/7/26 9:58 PM, Alex Elder wrote:
> 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
For the series:
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
prev parent reply other threads:[~2026-08-18 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 19:58 Alex Elder
2026-08-07 19:58 ` [PATCH 1/5] arm64: dts: qcom: qcs6490-rb3gen2: " Alex Elder
2026-08-07 19:58 ` [PATCH 2/5] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: " Alex Elder
2026-08-07 19:58 ` [PATCH 3/5] arm64: dts: qcom: lemans-evk-ifp-mezzanine: " Alex Elder
2026-08-07 19:58 ` [PATCH 4/5] arm64: dts: qcom: monaco-evk: " Alex Elder
2026-08-07 19:58 ` [PATCH 5/5] arm64: dts: qcom: qcs6490-thundercomm-minipc-g1iot: " Alex Elder
2026-08-11 5:29 ` [PATCH 0/5] arm64: dts: qcom: " Manivannan Sadhasivam
2026-08-18 12:36 ` Konrad Dybcio [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=40868661-4a52-44bf-8ff2-790c222c10bc@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=elder@riscstar.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=mani@kernel.org \
--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
all inboxes | Powered by JetHome®