devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Ma <peng.ma@nxp.com>
To: axboe@kernel.dk, robh+dt@kernel.org, shawnguo@kernel.org,
	mark.rutland@arm.com, leoyang.li@nxp.com
Cc: linux-ide@vger.kernel.org, devicetree@vger.kernel.org,
	andy.tang@nxp.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Peng Ma <peng.ma@nxp.com>
Subject: [PATCH 2/3] arm64: dts: ls1028a: Corrected the SATA ecc address.
Date: Mon, 11 Mar 2019 15:20:13 +0800	[thread overview]
Message-ID: <20190311072014.36565-2-peng.ma@nxp.com> (raw)
In-Reply-To: <20190311072014.36565-1-peng.ma@nxp.com>

Ls1028a SATA ecc address with more than 32 bit, so we should corrrect the
address.

Signed-off-by: Peng Ma <peng.ma@nxp.com>
---
 arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
index a8cf92a..3fcbd0a 100644
--- a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
@@ -277,7 +277,7 @@
 		sata: sata@3200000 {
 			compatible = "fsl,ls1028a-ahci";
 			reg = <0x0 0x3200000 0x0 0x10000>,
-				<0x0 0x20140520 0x0 0x4>;
+				<0x7 0x100520 0x0 0x4>;
 			reg-names = "ahci", "sata-ecc";
 			interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
 			clocks = <&clockgen 4 1>;
-- 
1.7.1

  reply	other threads:[~2019-03-11  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  7:20 [PATCH 1/3] dt-bindings: ahci-fsl-qoriq: add ls1028a chip name to the list Peng Ma
2019-03-11  7:20 ` Peng Ma [this message]
2019-04-11  1:35   ` [PATCH 2/3] arm64: dts: ls1028a: Corrected the SATA ecc address Shawn Guo
2019-03-11  7:20 ` [PATCH 3/3] ahci: qoriq: add ls1028a platforms support Peng Ma
2019-03-28  0:25 ` [PATCH 1/3] dt-bindings: ahci-fsl-qoriq: add ls1028a chip name to the list Rob Herring
2019-04-11  1:36 ` Shawn Guo
2019-04-12  9:44   ` [EXT] " Peng Ma

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=20190311072014.36565-2-peng.ma@nxp.com \
    --to=peng.ma@nxp.com \
    --cc=andy.tang@nxp.com \
    --cc=axboe@kernel.dk \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).