From: sashiko-bot@kernel.org
To: hongxing.zhu@oss.nxp.com
Cc: robh@kernel.org, conor+dt@kernel.org, Frank.Li@kernel.org,
imx@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 3/3] arm64: dts: imx943: Avoid 32-bit PCIe window System RAM overlap
Date: Thu, 20 Aug 2026 08:40:00 +0000 [thread overview]
Message-ID: <20260820084000.A72A81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820083620.877251-4-hongxing.zhu@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message incorrectly claims to modify the CPU address instead of the PCIe bus address.
--
--- Patch [3]: [PATCH v1 3/3] arm64: dts: imx943: Avoid 32-bit PCIe window System RAM overlap ---
commit 06a8fbf859a9df88332de43a908bb91e8293759a
Author: Richard Zhu <hongxing.zhu@nxp.com>
arm64: dts: imx943: Avoid 32-bit PCIe window System RAM overlap
This commit updates the PCIe non-prefetchable memory range for the imx943 to
avoid overlapping with DRAM. It adjusts the outbound address space
configuration to use a safe, reserved range.
> diff --git a/arch/arm64/boot/dts/freescale/imx943.dtsi b/arch/arm64/boot/dts/freescale/imx943.dtsi
> --- a/arch/arm64/boot/dts/freescale/imx943.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx943.dtsi
[ ... ]
> @@ -219,7 +219,7 @@ pcie1: pcie@4c380000 {
> <0 0x4c3c0000 0 0x4000>;
> reg-names = "dbi", "config", "atu", "app";
> ranges = <0x43000000 0xa 0x00000000 0xa 0x00000000 0x0 0xe0000000>,
> - <0x82000000 0x0 0xe0000000 0xa 0xe0000000 0x0 0x10000000>,
> + <0x82000000 0x0 0x10000000 0xa 0xe0000000 0x0 0x10000000>,
[Severity: Medium]
The commit message states that this moves the PCIe non-prefetchable memory
CPU address from 0xe0000000 to 0x10000000. Is this description accurate?
Looking at the ranges property in pcie1, the format is
<child_hi child_mid child_low parent_hi parent_low size_hi size_low>.
This change modifies the third cell (child_low), which represents the PCIe
bus address, from 0xe0000000 to 0x10000000. However, the fourth and fifth
cells representing the parent CPU address remain completely unchanged at
0xa 0xe0000000.
Does the code need to change the parent CPU address cells instead, or should
the commit message be updated to reflect that the child bus address is what
is actually being modified?
> <0x81000000 0x0 0x00000000 0xa 0xf0000000 0x0 0x00100000>;
> #address-cells = <3>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260820083620.877251-1-hongxing.zhu@oss.nxp.com?part=3
prev parent reply other threads:[~2026-08-20 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 8:36 [PATCH v1 0/3] arm64: dts: imx9x: Fix PCIe memory window overlap with System RAM hongxing.zhu
2026-08-20 8:36 ` [PATCH v1 1/3] arm64: dts: imx95: Avoid 32-bit PCIe window System RAM overlap hongxing.zhu
2026-08-20 8:42 ` sashiko-bot
2026-08-20 15:24 ` Frank Li
2026-08-20 8:36 ` [PATCH v1 2/3] arm64: dts: imx94: Avoid 32-bit pcie window system ram overlap hongxing.zhu
2026-08-20 8:40 ` sashiko-bot
2026-08-20 8:36 ` [PATCH v1 3/3] arm64: dts: imx943: Avoid 32-bit PCIe window System RAM overlap hongxing.zhu
2026-08-20 8:40 ` sashiko-bot [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=20260820084000.A72A81F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hongxing.zhu@oss.nxp.com \
--cc=imx@lists.linux.dev \
--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.