From: sashiko-bot@kernel.org
To: "Rahul Samana" <rahul.samana@oss.qualcomm.com>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 5/6] arm64: dts: qcom: kodiak: mark PCIe root port as bridge
Date: Mon, 27 Jul 2026 15:59:40 +0000 [thread overview]
Message-ID: <20260727155940.D93B11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727-rb3-industrial-bt-uart-v2-5-2d100f30e202@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] The patch adds `compatible = "pciclass,0604"` to the `pcie0_port` root port node in `kodiak.dtsi` to ensure the PCI core and slot power control drivers can associate the DT node with the enumerated PCI-to-PCI bridge, which enables child node matching. However, the patch fails to apply this exact same fix to the sibling `pcie1_port0` root port node.
--
--- Patch [5]: [PATCH v2 5/6] arm64: dts: qcom: kodiak: mark PCIe root port as bridge ---
commit 570e5e44fe4845eb64dbbfbc0bb38b9d4ae991da
Author: Rahul Samana <rahul.samana@oss.qualcomm.com>
arm64: dts: qcom: kodiak: mark PCIe root port as bridge
The patch adds the compatible = "pciclass,0604" property to the pcie0_port
device tree node. This allows the PCI core to associate the OF node with
the enumerated PCI-to-PCI bridge device, enabling proper matching for child
nodes.
> diff --git a/arch/arm64/boot/dts/qcom/kodiak.dtsi b/arch/arm64/boot/dts/qcom/kodiak.dtsi
> index fa540d8c2615d..12594967d2c26 100644
> --- a/arch/arm64/boot/dts/qcom/kodiak.dtsi
> +++ b/arch/arm64/boot/dts/qcom/kodiak.dtsi
> @@ -2296,6 +2296,7 @@ pcie0: pcie@1c00000 {
> status = "disabled";
>
> pcie0_port: pcie@0 {
> + compatible = "pciclass,0604";
> device_type = "pci";
> reg = <0x0 0x0 0x0 0x0 0x0>;
> bus-range = <0x01 0xff>;
[Severity: High]
This isn't a bug introduced by this patch, but should the exact same fix be
applied to the secondary PCIe root port node (pcie1_port0)?
Looking further down in arch/arm64/boot/dts/qcom/kodiak.dtsi, pcie1_port0
has an identical structure but is missing the "pciclass,0604" property:
pcie1_port0: pcie@0 {
device_type = "pci";
reg = <0x0 0x0 0x0 0x0 0x0>;
bus-range = <0x01 0xff>;
Without this property on pcie1_port0, won't devices connected to the
secondary PCIe port fail to properly associate their OF nodes with the
enumerated PCI devices?
This could prevent downstream devices from acquiring essential DT properties
like regulators and GPIOs.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727-rb3-industrial-bt-uart-v2-0-2d100f30e202@oss.qualcomm.com?part=5
next prev parent reply other threads:[~2026-07-27 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 15:45 [PATCH v2 0/6] Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial Rahul Samana
2026-07-27 15:45 ` [PATCH v2 1/6] dt-bindings: bluetooth: qca: add QCC2072 Rahul Samana
2026-07-27 15:55 ` sashiko-bot
2026-07-27 16:32 ` Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial bluez.test.bot
2026-07-27 15:45 ` [PATCH v2 2/6] Bluetooth: qca: add QCC2072 support Rahul Samana
2026-07-27 15:56 ` sashiko-bot
2026-07-27 15:45 ` [PATCH v2 3/6] power: sequencing: pwrseq-pcie-m2: add QCC2072 Rahul Samana
2026-07-27 15:51 ` sashiko-bot
2026-07-27 15:45 ` [PATCH v2 4/6] arm64: dts: qcom: qcs6490-rb3gen2: label BT PMU and M.2 PCI node Rahul Samana
2026-07-27 15:50 ` sashiko-bot
2026-07-27 15:45 ` [PATCH v2 5/6] arm64: dts: qcom: kodiak: mark PCIe root port as bridge Rahul Samana
2026-07-27 15:57 ` Rahul Samana
2026-07-27 15:59 ` sashiko-bot [this message]
2026-07-27 15:45 ` [PATCH v2 6/6] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay Rahul Samana
2026-07-27 16: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=20260727155940.D93B11F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rahul.samana@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.