All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Wei Deng" <wei.deng@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: monaco: Add compatible to the PCIe Root Port
Date: Mon, 27 Jul 2026 14:24:46 +0000	[thread overview]
Message-ID: <20260727142446.979011F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260727-b4-monaco-evk-m2-v1-v1-1-5429cce68599@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 `pcieport0` but fails to add the same required property to `pcieport1`.
--

--- Patch [1]: [PATCH 1/2] arm64: dts: qcom: monaco: Add compatible to the PCIe Root Port ---
commit 0ca797402b7e421fe911e89c620b4ebd792ff4af
Author: Wei Deng <wei.deng@oss.qualcomm.com>

arm64: dts: qcom: monaco: Add compatible to the PCIe Root Port

This commit adds the "pciclass,0604" compatible string to the pcieport0
node in monaco.dtsi. This enables the PCI subsystem to associate the
device tree node with the PCI-to-PCI bridge device, allowing downstream
endpoints to be correctly matched.

> diff --git a/arch/arm64/boot/dts/qcom/monaco.dtsi b/arch/arm64/boot/dts/qcom/monaco.dtsi
> index 64fc0d592282c..438ccf6eba64d 100644
> --- a/arch/arm64/boot/dts/qcom/monaco.dtsi
> +++ b/arch/arm64/boot/dts/qcom/monaco.dtsi
> @@ -2393,6 +2393,7 @@ opp-32000000 {
>  			};
>  
>  			pcieport0: pcie@0 {
> +				compatible = "pciclass,0604";
>  				device_type = "pci";
>  				reg = <0x0 0x0 0x0 0x0 0x0>;
>  				bus-range = <0x01 0xff>;

[Severity: High]
This is a pre-existing issue, but should the same compatible property be
added to the pcieport1 node in this file?

Looking further down in arch/arm64/boot/dts/qcom/monaco.dtsi, the pcieport1
node is missing this property:

			pcieport1: pcie@0 {
				device_type = "pci";
				reg = <0x0 0x0 0x0 0x0 0x0>;
				bus-range = <0x01 0xff>;
				...

Without the compatible property, the device tree node for pcieport1 will not
spawn a platform device, which prevents power control drivers like
pci-pwrctrl-slot from binding. 

Will this cause downstream nodes (such as M.2 endpoints) connected to the
second PCIe controller (pcie1) to fail to match or correctly power on?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260727-b4-monaco-evk-m2-v1-v1-0-5429cce68599@oss.qualcomm.com?part=1

  reply	other threads:[~2026-07-27 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 14:16 [PATCH 0/2] arm64: dts: qcom: Describe the PCIe M.2 Key E connector for Monaco EVK Wei Deng
2026-07-27 14:16 ` [PATCH 1/2] arm64: dts: qcom: monaco: Add compatible to the PCIe Root Port Wei Deng
2026-07-27 14:24   ` sashiko-bot [this message]
2026-07-27 14:29   ` Konrad Dybcio
2026-07-27 14:16 ` [PATCH 2/2] arm64: dts: qcom: monaco-evk: Describe the PCIe M.2 Key E connector Wei Deng
2026-07-27 14:39   ` Dmitry Baryshkov
2026-07-27 14:43   ` Konrad Dybcio

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=20260727142446.979011F00A3D@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wei.deng@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 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.