From: Frank Li <Frank.li@nxp.com>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
kernel@pengutronix.de, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: dts: imx95: Correct the range of PCIe app-reg region
Date: Fri, 14 Mar 2025 10:16:03 -0400 [thread overview]
Message-ID: <Z9Q6I2roECiCkXG9@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250314060104.390065-1-hongxing.zhu@nxp.com>
On Fri, Mar 14, 2025 at 02:01:04PM +0800, Richard Zhu wrote:
> Correct the range of PCIe app-reg region from 0x2000 to 0x4000 refer to
> SerDes_SS memory map of i.MX95 Rerference Manual.
>
> Fixes: 3b1d5deb29ff ("arm64: dts: imx95: add pcie[0,1] and pcie-ep[0,1] support")
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx95.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
> index 6b8470cb3461..0e6a9e639d76 100644
> --- a/arch/arm64/boot/dts/freescale/imx95.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
> @@ -1542,7 +1542,7 @@ pcie0: pcie@4c300000 {
> reg = <0 0x4c300000 0 0x10000>,
> <0 0x60100000 0 0xfe00000>,
> <0 0x4c360000 0 0x10000>,
> - <0 0x4c340000 0 0x2000>;
> + <0 0x4c340000 0 0x4000>;
> reg-names = "dbi", "config", "atu", "app";
> ranges = <0x81000000 0x0 0x00000000 0x0 0x6ff00000 0 0x00100000>,
> <0x82000000 0x0 0x10000000 0x9 0x10000000 0 0x10000000>;
> @@ -1582,7 +1582,7 @@ pcie0_ep: pcie-ep@4c300000 {
> reg = <0 0x4c300000 0 0x10000>,
> <0 0x4c360000 0 0x1000>,
> <0 0x4c320000 0 0x1000>,
> - <0 0x4c340000 0 0x2000>,
> + <0 0x4c340000 0 0x4000>,
> <0 0x4c370000 0 0x10000>,
> <0x9 0 1 0>;
> reg-names = "dbi","atu", "dbi2", "app", "dma", "addr_space";
> @@ -1609,7 +1609,7 @@ pcie1: pcie@4c380000 {
> reg = <0 0x4c380000 0 0x10000>,
> <8 0x80100000 0 0xfe00000>,
> <0 0x4c3e0000 0 0x10000>,
> - <0 0x4c3c0000 0 0x2000>;
> + <0 0x4c3c0000 0 0x4000>;
> reg-names = "dbi", "config", "atu", "app";
> ranges = <0x81000000 0 0x00000000 0x8 0x8ff00000 0 0x00100000>,
> <0x82000000 0 0x10000000 0xa 0x10000000 0 0x10000000>;
> @@ -1649,7 +1649,7 @@ pcie1_ep: pcie-ep@4c380000 {
> reg = <0 0x4c380000 0 0x10000>,
> <0 0x4c3e0000 0 0x1000>,
> <0 0x4c3a0000 0 0x1000>,
> - <0 0x4c3c0000 0 0x2000>,
> + <0 0x4c3c0000 0 0x4000>,
> <0 0x4c3f0000 0 0x10000>,
> <0xa 0 1 0>;
> reg-names = "dbi", "atu", "dbi2", "app", "dma", "addr_space";
> --
> 2.37.1
>
next prev parent reply other threads:[~2025-03-14 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 6:01 [PATCH v1] arm64: dts: imx95: Correct the range of PCIe app-reg region Richard Zhu
2025-03-14 14:16 ` Frank Li [this message]
2025-04-22 2:35 ` Shawn Guo
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=Z9Q6I2roECiCkXG9@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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