Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alex Elder" <elder@riscstar.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/5] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: use pci for device nodes
Date: Tue, 01 Sep 2026 17:34:11 +0000	[thread overview]
Message-ID: <20260901173412.239581F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260901172058.1512508-3-elder@riscstar.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] The patch claims to fix PCIe endpoints being incorrectly treated as PCI bridges by renaming them from `pcie@` back to `pci@`. However, this is a placebo fix that fails to resolve the issue because the nodes still retain the `device_type = "pci"` property.
--

commit 8f05438af7136e29082530fe0089fb496985289a
Author: Alex Elder <elder@riscstar.com>

arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: use pci for device nodes

This commit renames embedded PCIe endpoint nodes on the TC9564 SoCs from
pcie@ back to pci@ to prevent them from being incorrectly treated as PCI
bridges. The commit message states that the previous name pcie@ caused
of_node_is_pcie() to match them as bridge nodes.

> diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso
> index 46bb52c667a4d..14c64439ae1e6 100644
> --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso
> +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso
[ ... ]
> @@ -130,7 +130,7 @@ pcie@3,0 {
>  			ranges;
>  			bus-range = <0x5 0xff>;
>  
> -			pcie@0,0 {
> +			pci@0,0 {
>  				reg = <0x50000 0x0 0x0 0x0 0x0>;
>  				#address-cells = <3>;
>  				#size-cells = <2>;

[Severity: High]
This is a pre-existing issue, but does this rename actually resolve the
problem of endpoints being treated as PCI bridges?

Looking at drivers/of/address.c, the devicetree match logic in
of_bus_pci_match() is evaluated as:

    return of_node_is_type(np, "pci") || of_node_is_type(np, "pciex") ||
           of_node_is_type(np, "vci") || of_node_is_type(np, "ht") ||
           of_node_is_pcie(np);

Since the endpoint node retains the device_type = "pci" property just below
these cells, of_node_is_type(np, "pci") evaluates to true. This short-circuits
the condition before the of_node_is_pcie(np) name check is ever reached.

Because of this property, will the nodes continue to be matched as PCI buses
even with the name changed to pci@0,0, making this a placebo fix?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260901172058.1512508-1-elder@riscstar.com?part=2

  reply	other threads:[~2026-09-01 17:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 17:20 [PATCH 0/5] arm64: dts: qcom: use pci for device nodes Alex Elder
2026-09-01 17:20 ` [PATCH 1/5] arm64: dts: qcom: qcs6490-rb3gen2: " Alex Elder
2026-09-01 17:39   ` sashiko-bot
2026-09-01 17:45     ` Alex Elder
2026-09-01 20:05   ` Rob Herring
2026-09-02 12:51     ` Alex Elder
2026-09-02 16:53       ` Rob Herring
2026-09-02 18:40         ` Alex Elder
2026-09-01 17:20 ` [PATCH 2/5] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: " Alex Elder
2026-09-01 17:34   ` sashiko-bot [this message]
2026-09-01 17:20 ` [PATCH 3/5] arm64: dts: qcom: lemans-evk-ifp-mezzanine: " Alex Elder
2026-09-01 17:49   ` sashiko-bot
2026-09-01 17:20 ` [PATCH 4/5] arm64: dts: qcom: monaco-evk-ifp-mezzanine: use dev " Alex Elder
2026-09-01 17:54   ` sashiko-bot
2026-09-01 18:18     ` Alex Elder
2026-09-01 17:20 ` [PATCH 5/5] arm64: dts: qcom: qcs6490-thundercomm-minipc-g1iot: " Alex Elder
2026-09-01 18:03   ` sashiko-bot

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=20260901173412.239581F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=elder@riscstar.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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