From: Dinh Nguyen <dinguyen@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: dinguyen@kernel.org, devicetree@vger.kernel.org,
Dinh Nguyen <dinh.nguyen@intel.com>,
linux-stable <stable@vger.kernel.org>
Subject: [PATCH 3/3] arm64: dts: stratix10: increase QSPI reg address in nand dts file
Date: Mon, 29 Jun 2020 15:39:49 -0500 [thread overview]
Message-ID: <20200629203949.6601-3-dinguyen@kernel.org> (raw)
In-Reply-To: <20200629203949.6601-1-dinguyen@kernel.org>
From: Dinh Nguyen <dinh.nguyen@intel.com>
Match the QSPI reg address in the socfpga_stratix10_socdk.dts file.
Fixes: 80f132d73709 ("arm64: dts: increase the QSPI reg address for Stratix10
and Agilex")
Cc: linux-stable <stable@vger.kernel.org> # >= v5.6
Signed-off-by: Dinh Nguyen <dinh.nguyen@intel.com>
---
arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_nand.dts | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_nand.dts b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_nand.dts
index 4000c393243d..c07966740e14 100644
--- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_nand.dts
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_nand.dts
@@ -212,12 +212,12 @@
qspi_boot: partition@0 {
label = "Boot and fpga data";
- reg = <0x0 0x034B0000>;
+ reg = <0x0 0x03FE0000>;
};
- qspi_rootfs: partition@4000000 {
+ qspi_rootfs: partition@3FE0000 {
label = "Root Filesystem - JFFS2";
- reg = <0x034B0000 0x0EB50000>;
+ reg = <0x03FE0000 0x0C020000>;
};
};
};
--
2.17.1
prev parent reply other threads:[~2020-06-29 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 20:39 [PATCH 1/3] arm64: dts: agilex: add status to qspi dts node Dinh Nguyen
2020-06-29 20:39 ` [PATCH 2/3] arm64: dts: stratix10: " Dinh Nguyen
2020-07-10 14:02 ` Sasha Levin
2020-07-10 15:27 ` Dinh Nguyen
2020-07-10 15:27 ` Dinh Nguyen
2020-06-29 20:39 ` Dinh Nguyen [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=20200629203949.6601-3-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinh.nguyen@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).