From: sashiko-bot@kernel.org
To: "Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
Cc: robh@kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 3/3] arm64: dts: qcom: eliza-evk: Add PCIe1 with TC9563 PCIe switch
Date: Thu, 30 Jul 2026 05:10:30 +0000 [thread overview]
Message-ID: <20260730051031.20D8E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260730-eliza_evk-v6-3-40ece2d33114@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Endpoint devices incorrectly define PCI bridge properties (`device_type = "pci"`, `ranges`, etc.).
- [Low] The comment explaining that PERST# and RESX# share the same GPIO is misplaced, causing confusion about pin assignments.
--
--- Patch [3]: [PATCH v6 3/3] arm64: dts: qcom: eliza-evk: Add PCIe1 with TC9563 PCIe switch ---
commit 86f389de1416cf57b1a057c5cc8316c6fc164073
Author: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
arm64: dts: qcom: eliza-evk: Add PCIe1 with TC9563 PCIe switch
The Eliza EVK board connects PCIe1 (8GT/s x2) to a Toshiba TC9563 PCIe
switch. Enable PCIe1, QMP PHY nodes, and TC9563 nodes on I2C and PCIe.
> diff --git a/arch/arm64/boot/dts/qcom/eliza-evk.dtsi b/arch/arm64/boot/dts/qcom/eliza-evk.dtsi
> index b35fffb509765..419e737c54e6f 100644
> --- a/arch/arm64/boot/dts/qcom/eliza-evk.dtsi
> +++ b/arch/arm64/boot/dts/qcom/eliza-evk.dtsi
[ ... ]
> +&pcie1_port0 {
> + wake-gpios = <&tlmm 53 GPIO_ACTIVE_LOW>;
> + /* Same GPIO is used for both PERST# and resx-gpio */
[Severity: Low]
Is this comment placed correctly?
The comment implies that wake-gpios (TLMM 53) is the shared reset GPIO, but
resx-gpios is defined as TLMM 54 further down in the tc9563 node. Should this
comment be moved above resx-gpios or the omitted reset-gpios property to avoid
confusion?
> +
> + tc9563: pcie@0,0 {
> + compatible = "pci1179,0623";
> + reg = <0x10000 0x0 0x0 0x0 0x0>;
[ ... ]
> + pcie@3,0 {
> + reg = <0x21800 0x0 0x0 0x0 0x0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + ranges;
> + bus-range = <0x5 0xff>;
> +
> + pcie@0,0 {
> + reg = <0x50000 0x0 0x0 0x0 0x0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + ranges;
> + };
> +
> + pcie@0,1 {
> + reg = <0x50100 0x0 0x0 0x0 0x0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + ranges;
> + };
[Severity: Medium]
Are pcie@0,0 and pcie@0,1 leaf endpoints?
If these child nodes represent leaf endpoints (like Ethernet MAC devices), they
should not include properties strictly reserved for PCI-to-PCI bridges or Root
Ports such as #address-cells, #size-cells, ranges, or device_type = "pci".
Will this cause dtbs_check validation errors or cause the OF/PCI subsystem to
misinterpret these leaf nodes as PCI bridges?
> + };
> + };
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260730-eliza_evk-v6-0-40ece2d33114@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-07-30 5:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 4:48 [PATCH v6 0/3] arm64: dts: qcom: eliza-evk: Enable PCIe0 and PCIe1 with M.2 and TC9563 switch Krishna Chaitanya Chundru
2026-07-30 4:48 ` [PATCH v6 1/3] arm64: dts: qcom: eliza: Add PCIe PHY and controller nodes Krishna Chaitanya Chundru
2026-07-30 5:18 ` sashiko-bot
2026-07-30 7:54 ` Manivannan Sadhasivam
2026-07-30 4:48 ` [PATCH v6 2/3] arm64: dts: qcom: eliza-evk: Add PCIe0 with M.2 E key connector Krishna Chaitanya Chundru
2026-07-30 5:06 ` sashiko-bot
2026-07-30 5:08 ` Manivannan Sadhasivam
2026-07-30 6:23 ` Krishna Chaitanya Chundru
2026-07-30 4:48 ` [PATCH v6 3/3] arm64: dts: qcom: eliza-evk: Add PCIe1 with TC9563 PCIe switch Krishna Chaitanya Chundru
2026-07-30 5:10 ` sashiko-bot [this message]
2026-07-30 5:25 ` Manivannan Sadhasivam
2026-07-30 7:42 ` Konrad Dybcio
2026-07-30 7:52 ` Manivannan Sadhasivam
2026-07-30 7:59 ` 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=20260730051031.20D8E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linux-pci@vger.kernel.org \
--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